Offline-first
What happens when you capture an issue
- It saves on the iPhone first. The photo, issue details and edits are written locally before you move on.
- The walk keeps moving. Capture, markup, filtering and reporting do not wait for a network request.
- Sync catches up later. When connection is available, Snagwalk uploads the outstanding records in the background.
- You can see the difference. Each record shows whether it is synced or still stored only on this iPhone.
What works without signal
Everything needed to complete the walk and prepare the output:
- Create projects and capture marked-up issues
- Edit, filter, reorder and batch-update the list
- Mark work resolved and add after photos
- Generate the PDF and CSV
Sending still needs connection. A report created offline remains queued and is labelled as waiting; it is not presented as sent.
The words match the real state
| Snagwalk says | What it means |
|---|---|
| “Saved on this iPhone” | The record is safe locally but has not reached the cloud |
| “Queued — will send when you are back online” | The report is ready but has not been sent |
| “Handed to Mail” | Snagwalk passed the message to Mail; Mail now owns delivery |
| “Synced” | The record has reached the cloud |
If two edits meet after syncing
If the same issue was changed in two places before syncing, the newest change is used and the earlier version remains recoverable. Snagwalk explains what happened instead of silently replacing the record.
Why inspectors care about this
The difficult part of losing signal is not the blank bar at the top of the screen. It is the doubt afterwards: did the photo save, is the latest note on the phone, and did the report actually go? Snagwalk shows the answer at record level so you can leave site knowing what is complete and what is still waiting.
For the working habits around this (the flight-mode test, offline documents, battery), read the guide to running inspections with no signal.