Arrive informed
See the assignment, asset, recent reads, issue history and location before the visit.
Field operations
Get the right meter, asset, account and incident context before arriving on site, capture evidence offline and verify the result after the repair.
Answer first
The field workflow is designed around assigned work, offline context, append-safe observations, photos, parts, meter swaps and a sync process that never silently overwrites newer server state.
Outcomes
See the assignment, asset, recent reads, issue history and location before the visit.
Record notes, photos, parts and new meter details in the work order instead of duplicating paperwork.
Require a post-intervention check when the task is supposed to reduce leakage or restore readings.
Capabilities
Store assigned work and safe append operations until connectivity returns.
Record old/new device identity, final/initial reads and server-side reconciliation.
Attach observation, photo, coordinates and reason codes to the canonical job.
Use entity versions for status changes and prevent silent overwrite of newer state.
“For every cubic metre entering the system: where did it go, what happened commercially, what action was taken, and what measurable result followed?”WaterPesa product invariant · derived from the connected Notion product specification
FAQ
Authorized assignments and relevant context remain available locally, and safe mutations are queued for sync.
Not by default. Access is capability-based and should be restricted to the functions required by the role.
The device removal and installation are separate historical events tied to the long-lived connection, with final/initial readings and evidence.
Keep exploring