Field app
The field is inside the panel too
What it does
Six behaviours that finish the job on site
Reads with no signal inside the building
The meter list is downloaded once; reading continues in basements, car parks and lift shafts with no connectivity. Every index is saved to the phone the moment it is entered and syncs in the background when the connection returns.
- No connection needed after the list is downloaded
- The number of records synced is visible on screen
- A round closes only after the data reaches the server
A round cannot close with a blank meter
Every meter either gets an index or is marked unread with a reason. A value below the previous index or above the limit raises a confirmation bar, and the confirm button will not work until a photo is taken.
- No unread flag without a reason
- Photo mandatory on abnormal consumption
- Meter barcode and label read by camera
The office assigns and watches live
Task scope is built at block, unit or individual meter level; the form states how many meters it covers before assignment. When the technician sends the first reading, the task moves to in-progress on its own.
- Add unread meters to the scope
- Photo requirement per task
- Reading report with Excel attachment when the round ends
No duplicate records
If a transfer is interrupted the round stays on the phone and is resent. The same index is never written twice; the server knows which records already arrived.
- Resending creates no duplicates
- Unsent record count visible
- No data is lost before the round closes
The technician sees only their own work
A user in the field role sees only the tasks assigned to them and the meters in those tasks; the rest of the project data stays closed.
- Role-based task list
- Out-of-scope meters are invisible
- Limited access to personal data
Evidence travels with the reading
For abnormal consumption, suspected faults and unread flags, a photo is attached to the record. When a dispute arrives later, the state of that meter is visible.
- Photo attached to the meter record
- Timestamp and reading user
- Convert to a fault report
Task flow
From assignment to report
The office selects the scope and assigns the task; the form states how many meters it covers.
The technician opens the task and downloads the meter list to their phone.
Indexes are entered on site; meters that cannot be read are flagged with a reason.
An abnormal value triggers a photo requirement and a confirmation bar.
Records sync to the server in the background when connectivity returns.
Once every meter is complete the round closes and the report lands in the office.
At a glance
- Platform
- Phone browser — no separate app installation
- Offline
- Reading continues once the list is downloaded
- Evidence
- Photo, barcode, timestamp, reading user
- Task scope
- Block · unit · single meter
- Report
- Reading report with Excel attachment at round close
Frequently asked questions
What people ask about field reading
Our field team has no signal in the basement. Will readings be lost?
No. Once the meter list has been downloaded, reading continues without a connection and every index is saved to the phone immediately. When connectivity returns records sync in the background, and the round only closes after the data has been written to the server. If a transfer is interrupted, the round stays on the phone, is resent, and no duplicate records are created.
Can a technician enter an index against the wrong meter?
The meter barcode or label can be scanned with the camera, and the scanned meter is marked in the list automatically. A value below the previous index or above the limit also raises a confirmation bar.
Does the technician have to install an app?
No. The field screen runs in the phone browser; the technician signs in with their own account and sees only the tasks assigned to them.