When the signal drops: what offline-first really means for field engineers
Field work happens in basements, plant rooms, cold stores, rural sites and buildings with walls that were not designed for mobile data. “We have an app” is not the same as “the app works when the signal does not”.
Offline-first is not a cache bolted onto a form. It is a contract between the field worker, the office and the record.
What the engineer needs offline
Before the shift, the device should download enough to work without a connection:
- The day's jobs, with customer, site, contact and access notes.
- The asset and its recent history.
- The checklist or form for each job.
- The ability to capture photos, readings and signatures.
- The ability to raise a defect and record parts used.
- A clear sync status, so the engineer knows what is waiting.
If any of those require a live connection, the field worker will fall back to paper or a phone call. That is the real competition.
What the office must see
The office needs more than a green tick. It needs to know:
- When the device last synced.
- How many items are pending.
- Which job they belong to.
- Whether an item was rejected, and why.
Silent failure is worse than a visible queue. A pending photo is manageable. A photo that disappeared is not.
The demo path
In the FieldElite demo workspace, the Acme pump repair is in a basement plant room. The engineer scans the asset QR label, opens the checklist, captures before-and-after evidence, records the defect and completes the job.
The same field data is available in the installable worker PWA at /worker and in the Android app. The office sees the record when it syncs; the worker sees what is still pending.
The Northwind cold store is the other useful test. Cold rooms are not known for reliable signal, and the temperature readings matter. The field record has to survive the room, not just the car park.
Design rules that make offline work
- Download before dispatch. The job should be on the device before the engineer leaves.
- Use stable local identifiers. A record created offline still needs an identity that survives the sync.
- Make the sync idempotent. A retry must not create a duplicate job, photo or defect.
- Surface conflicts. If the office changed the job while the engineer was offline, the worker should see the conflict rather than silently overwrite it.
- Never discard queued work. If a module is disabled or a validation fails, keep the payload and explain what is needed.
- Audit the result. The synced record should carry the original capture time, not just the upload time.
PWA or native app?
They solve different problems. The PWA is quick to deploy, installable from the browser and works on the devices the team already has. The Android app can use device capabilities and is a better fit for a dedicated field workforce. Both should share the same jobs, evidence and sync rules.
Do not choose one because it sounds more modern. Choose based on the devices, the connectivity and the field process.
Test the offline story before rollout
Give two engineers a week with the app and one deliberately disconnected day. Watch what they do when a photo fails to upload, when a checklist is rejected, and when the office changes a job while they are on site. The answers will tell you more than a feature list.
Plan fit
The mobile app, job scheduling, checklists, scanning and the customer portal are included from Starter. Growth adds forms, customer notifications and more users. Professional adds API access, the workflow engine, inventory and parts, and the dispatch board. Enterprise adds data migration, custom integrations and SSO.
Compare the plans, or start a 30-day trial and test the worker app on your own site.
The Acme Facilities and Northwind Cold Chain scenarios come from the FieldElite demo workspace and are illustrative, not real customer results.
