What works offline in a field-service web app?

Offline support in a field-service web app is action-specific. A record stored on the phone may be queued rather than confirmed on the server. Opening a page once does not prove that creating quotes, uploading photos or processing payments works without a connection.

Explore the wider trust, access and operational records guides for the steps around this decision.

Separate the states

State or action	What to understand
Previously loaded information	Availability depends on what the app/device retains
Supported queued update	Saved locally pending synchronisation
Confirmed server update	The server has accepted the change
New record or upload	Requires separate support; do not assume it is queued
Card payment	Do not infer payment completion from an offline tap

JobDiary’s crew implementation includes an outbox for supported updates to existing records and pending work handling. That is narrower than a promise that the entire CRM operates offline.

A practical acceptance test

Use synthetic work, load the supported field screen and remove connectivity. Try one documented action, inspect its queued indication and then restore the connection. Confirm that the office sees the accepted result. Also check a failed or rejected sync so the crew knows what remains unresolved.

Record each action as supported, unsupported or untested. Do not label photo uploads, new quotations or account changes offline-capable simply because another field update queues successfully.

Protect pending work

Avoid clearing site data, changing device or assuming a sign-out preserves every pending update before synchronisation is confirmed. Keep an operational exception routine for failed changes.

JobDiary’s published promise is supported field actions that queue and sync when the connection returns. Precise actions and device behaviour should be checked in the current account. This guide documents the boundary; it does not claim a complete live-device test of every function.

Connect this to the next step

Continue with What data can office and field staff access?. If the next issue is elsewhere in the workflow, use Can you leave a job app and take your data with you?.

See JobDiary product questions to check how the product supports this work. Use the current product description and a trial to verify the fit for your business.