One Authoritative Record for 210,000 Regulated Network Assets
Enterprise Software / Field Operations
Field Service Management Platform
Dispatch, Work Orders and Compliance for 120 Mobile Technicians
Background
A fire and essential-services contractor dispatched 120 technicians using a whiteboard, a phone and a scanned PDF per job. Compliance certificates were transcribed from paper into a portal days later, which meant the contractor's regulatory exposure sat in a technician's ute for most of every week.
The problem
What made it hard.
Technicians work in basements, plant rooms and lift shafts with no signal, so the mobile application had to be genuinely offline-first rather than merely tolerant of dropouts. Two technicians editing the same asset record hours apart, both offline, had to reconcile without silently losing one of them. And the certificate output was a regulated artefact — it had to be provably derived from what the technician actually recorded on site.
Approach
What we built.
The mobile client keeps a full local SQLite replica of the technician's assigned assets and writes every action to an append-only local log, so the app is fully functional with the radio off. Sync reconciles per field rather than per record, with genuine conflicts surfaced to a supervisor rather than silently resolved last-write-wins — the case that quietly corrupts most offline systems. Certificates render server-side from the immutable event log rather than from mutable form state, so what is lodged is provably what was recorded. Dispatch runs on skills, licences and live location, and a technician's licence expiry blocks assignment to work it covers.
Outcome
What it measured.
Certificate lodgement moved from a median of six days after attendance to same-day for 94% of jobs, which removed the contractor's largest compliance exposure. Technicians complete roughly 1.4 more jobs per day, mostly recovered from travel and paperwork rather than working faster. The supervisor conflict queue averages under three items a week across 120 technicians, which is what confirmed the sync model was right.
Our role
Offline-first architecture; mobile application; dispatch and scheduling engine; compliance certificate pipeline; rollout.
Technologies
Gallery
Inside the build.
Figure 1 — Dispatch board with technicians on a map, skills and licence badges on each card..
Figure 2 — Offline sync architecture.
Figure 3 — Generated compliance certificate beside the on-site record it derives from..
Figure 4 — Mobile work order flow across three screens.
Next case study
Tell us what you’re building.
Send the constraint that worries you most — a latency budget, a power budget, a certification date. We’ll tell you straight whether we’re the right team.