Offline fieldwork
What happens when the connection is not there.
Who this is for
Enumerators, and the people who supervise them.
Resumable uploads
A media upload interrupted by a dropped connection resumes rather than restarting. The server names the parts it is still missing, and a re-sent part is recorded as a retry, not as a second part.
On completion the assembled object is re-hashed and compared against the hash declared at the start. Integrity is verified, not asserted, and a mismatch fails the upload rather than storing a corrupt file.
Replayed operations
Every offline operation carries a client operation identifier that is unique within your organization. If a device sends the same operation twice — which is normal on a bad connection — the second attempt returns the original result instead of creating a duplicate.
Field data quality signals
The quality engine emits flags, risk signals and review requests. It reaches no verdict about a person and it does not describe anyone as fraudulent. A signal is a prompt for a human to look, and nothing more.
What is not claimed
What this does not do
Stated here rather than discovered later
- The field application is Android only. There is no iOS build.
- A first sign-in with no connection will not work. Signing in while you still have signal is what lets the device keep working when you lose it.
- No offline durability figure is published for any carrier or device fleet.