What works offline

Filled from the current native app (Drift + outbox). Do not assume a capability is offline unless this table says so.

Screen path: any cached job while the banner reads Offline — showing cached data. Native Field is not the Field PWA.

Preconditions

Successful login and at least one bootstrap. Photos can queue; do not claim killed-app periodic sync.

Capability	Offline read	Offline write	Sync later
Jobs / Today lists	Yes (cache)	No (office assigns)	Pull
Execution	Yes	Yes (allowed actions)	Push
Forms	Yes	Yes (draft + complete)	Push; version notice if server moved
Evidence	Yes	Yes (local file then upload)	Push / upload
Signatures	Yes	Yes	Push
Findings	Yes	Yes (Working)	Push
Resolve a finding	No until it has a server id	—	Wait until this finding has synced
Used items	Yes (if inventory downloaded)	Yes	Push; stock may go negative
Request parts	Yes	Yes (queued)	Push — not consume
Closeout / Complete job	Yes (evaluate locally)	Yes (queue)	Push; Completion pending sync; server may still reject
Login / licence	Needs network for first session	—	—
New assignments	No until pull	—	Pull when running

Exceptions: first bootstrap needs network. Auth frozen (401/403) stops automatic retry until you sign in again. Pending work stays on the device. A later 403 does not delete unsynced work.

Loop

1. Confirm the job is already on this device.
2. Work from the matrix above.
3. Open Sync when the radio returns. Photos stay Waiting to upload until multipart finishes while the app is running.

What works / does not work (summary)

	Offline	Needs server
Open cached job	Yes	—
See office’s new assignment	No	Pull
Sign in the first time	No	Network
Photos	Queue	Upload + accept

If you expected Resolve on a brand-new finding: wait until create has a server id.