Open saved claim and inspection details
Assignments and inspection data already downloaded to the device remain available when the connection drops.
Offline inspections
Keep documenting the inspection when the internet disappears
Adjuster Copilot is an offline claims inspection app that keeps downloaded assignment data and new field work on the device, then shows exactly what is pending, syncing, synced, or failed.
Screenshots show the current product with synthetic demonstration data.
Available offline
What keeps working with no bars
Once the claim is on the device, the inspection carries on — basement, attic, or the far end of a CAT zone.
Continue inspection documentation
Record and edit inspection details, questionnaire responses, damage items, photo-checklist decisions, and narrative text.
Capture and label photos
New photos are retained locally with their inspection context and wait for their metadata and files to upload.
Capture signatures
Signatures can be collected on the device and queued with the rest of the inspection work.
Stored locally
Field changes wait on the device until they can be sent
The local inspection record holds downloaded inspection data and queued changes. Captured photos retain a local file and their inspection metadata while upload is pending. Offline records are isolated to the signed-in user on that device.
Get back in range with the inspection open and the queue runs on its own — then each item reads as synced, so you know the office has it before you move on.
Before and after
Bookend the day with a connection
Download in the morning, sync when you're back in range. Everything between those two moments works without a signal.
Connect before entering the field
- Download an assignment or inspection that is not already saved on the device.
- Refresh the local copy with newer server data.
- Generate a new AI-assisted narrative draft.
Reconnect before final handoff
- Upload queued changes and photo files to the server.
- Submit or resubmit an inspection for review.
- Confirm that no work remains pending or failed.
Existing narrative text can be created or edited offline and queued. Generating a new AI draft is a connected action. Learn what the current AI does on the AI narrative page.
Offline to synced
The workflow from assignment to reconnection
Download, inspect, queue, reconnect — and confirm the server has everything before you close the day.
- STEP 01
Open the assignment while connected
Load the claim and inspection before entering a dead zone. If an inspection has never been downloaded, the app asks you to connect once rather than showing incomplete data.
- STEP 02
Keep working when signal drops
The app continues from saved inspection data. New field entries are written locally and queued instead of depending on a live request for every action.
- STEP 03
Check what is waiting
Offline and pending indicators separate device-saved work from server-synced work. Photo items also identify locally saved, upload-pending, uploading, uploaded, and failed states.
- STEP 04
Reconnect with the inspection open
When connectivity returns while the inspection home screen is active, Adjuster Copilot attempts to flush that inspection’s queue. Returning the app to the foreground can also trigger the attempt.
- STEP 05
Confirm the result
Wait for the synced state before treating the handoff as complete. If the app shows pending or failed work, use Sync Now or Retry from the affected inspection.
Current product proof
Sync status remains accessible from app settings
The current app includes a Sync Status destination for offline changes and uploads. This screenshot uses approved demonstration data and shows the current settings entry—not a conceptual mockup.
Visible sync states
Always know where your work stands
Local, moving, complete, or needs attention — every piece of the inspection carries a state you can read at a glance.
Offline — changes saved on this device
The app identifies the lost connection and shows that work is saved on this device. A count appears when changes are waiting.
Changes pending sync
Queued changes remain visible as waiting to sync. On the inspection home screen, Sync Now is available when connected.
Syncing…
While the active inspection queue is being sent, the inspection home screen shows that synchronization is in progress.
All changes synced
A successful flush shows that all changes are synced. The temporary success banner then clears.
Sync failed — Retry
A failed item is shown separately from pending work. Open the affected inspection and use Retry; a failed item is not presented as safely synced.
See the states in context
Test the offline-to-sync workflow before taking it into the field
Start a trial, put the phone in airplane mode, and watch the offline, pending, successful, and failed states behave against a practice inspection.