Offline sync calculator
Part 1 sizes the upload queue after a day with no signal. Part 2 counts edits overwritten after a sync conflict.
A planning aid. Every starting value is invented (our example crew, photo size and link speed). It is not a measurement of any app. Use 1 MB = 1,000 KB and 8 Mbit = 1 MB. Write decimals with a dot or a comma; write thousands as 1,000 (not 1.000).
1. Upload queue after a day offline
| Result | Value |
|---|---|
| Data per job (MB) | - |
| Queue size (MB) | - |
| Share of the queue that is photos | - |
| Time to clear the queue | - |
| Clears within your connection time? | - |
| Data still waiting at the end of that time (MB) | - |
2. Sync conflict count
| Policy (our model, not a vendor's) | Edits overwritten | Held for review |
|---|---|---|
| Whole record, last sync wins | - | - |
| Field by field, latest edit time wins | - | - |
| Field by field, overlaps held for review | - | - |
Method: queue MB = jobs × (photos × photo MB + (form + signature + measurement KB) ÷ 1,000). Time = MB × 8 ÷ (Mbit/s × share). Conflict counts: whole-record replaces every edit made by the side that synced first; field-level counts only the overlapped fields. Edit-time rules also depend on device clocks being right.