What good looks like
Required job information is available offline and locally recorded work reaches the server without duplicate or missing entries.
Have these details ready
- A supported signed-in device
- Assignments synced while online
- Enough battery and storage for photos and files
Run the workflow
-
Sync before entering the dead zone
While connected, open My Jobs, refresh assignments, and open the jobs, contacts, notes, checklists, and documents needed that day.
-
Confirm offline readiness
Verify the correct job and core details remain visible after connectivity drops. Keep critical emergency contact or access information available under company policy.
-
Record work normally
Enter statuses, time, notes, checklist results, and photos once. Watch for the app's pending or offline indicator instead of repeatedly submitting.
-
Protect pending changes
Keep the app signed in and avoid clearing storage, reinstalling, or switching accounts while unsynced work remains.
-
Reconnect and verify
When service returns, keep the app open, trigger the supported sync/refresh, and confirm pending indicators clear and server-backed records show the changes.
Check your work
Do not call the workflow complete until these statements are true.
- No pending offline indicator remains
- Photos, notes, time, and statuses appear after refresh
- No duplicate entry was created during retry
If something does not look right
A change remains pending
Restore stable service, keep the app open, retry sync once, and capture the pending item details before contacting support.
Two people edited the same record
Review the server history after sync and resolve the conflicting field with the dispatcher; do not delete evidence blindly.