The engineer app now works offline

eControl's engineers spend their days in plant rooms, basements and half-built sites - exactly the places where mobile signal gives up. The engineer app used to assume a connection: without one, job updates simply failed, so engineers fell back on paper notes and re-keyed everything once they were back in coverage. Statuses arrived late or out of order, the office lost sight of where jobs stood, and a tool meant to save time was quietly creating admin.

What we built

The app now treats the network as optional. Every job assigned to an engineer is stored locally on the device, along with the details the work needs - site information, unit serial numbers and the job history so far. When an engineer changes a job status or adds notes, the change is written to a local queue first and the app carries on instantly, connection or not.

A background sync engine watches for connectivity. The moment the device comes back online, queued changes are replayed to the platform in the order they were made, and each change carries its own identifier so a retry on a flaky connection can never be applied twice. Anything the server rejects is surfaced back to the engineer in the app rather than silently dropped.

• Job statuses, notes and completions all work with no signal at all.

• Changes sync automatically in the background - there is no send button to remember.

• Idempotent retries mean patchy coverage cannot create duplicate updates.

The outcome

Engineers have stopped thinking about connectivity, because they no longer need to. Work is recorded once, at the point it happens, and the office sees an accurate picture within minutes of an engineer regaining coverage. It also completes a chain we have been building across the eControl platform: a fault report arrives on the website, flows into the CRM, becomes a job - and now gets closed out from a basement with no bars on the screen.