Offline-capable mobile and web capture, GPS-validated, with the integrity controls and operations support that defensible data needs.
Most "mobile data collection" projects fail not on the software but on operations. The form works. The phone works. The field worker can't get signal at the back of the field, the QA team isn't reading the inbound records until a fortnight after they land, and nobody knows which device was assigned to which sampler on which day.
We build the capture stack and the operating model around it. Offline-first by default. GPS validated at submission, not just collected. Device fleet, sampler roster, QA cadence and exception handling all documented from the start.
The form is 20% of the job. The other 80% is what stops it from falling over at month three.
Android and web forms that work without a connection. Capture queues locally, validates locally, syncs on return to coverage. Conflict resolution is deterministic, not last-write-wins.
Every record is GPS-fixed at capture, with accuracy logged. Outside-the-parcel and impossible-velocity records are flagged before they leave the device.
Field worker identity, device identity, time-of-capture, and accuracy metadata are bound to every record. Photo timestamps and EXIF locations are checked against the form's claimed position.
Sampler training, device fleet management, daily QA queues, exception escalation. The unglamorous monthly cadence that determines whether the dataset is usable at the end.
Data lands in your database from day one. PostGIS, ArcGIS Online, SharePoint, S3, or your data warehouse. We don't intermediate copies on servers we control.
Yes. Offline-first is the default. Android devices capture in the field without signal, sync when they're back in coverage, and resolve conflicts deterministically. The web form is offline-capable in modern browsers via service worker.
We've supported programmes capturing tens of thousands of geo-referenced records under strict quality requirements. The constraint is rarely the software — it's the operations: sampler training, device fleet management, QA cadence, and someone in the chain who actually owns the data.
Whichever fits. XLSForm-based capture is our default. Survey123 where you already have an ArcGIS estate and want native integration. Our own Android stack when the workflow needs case management, multi-stage approval, or features the standard tools don't have.
Standard phone GPS is fine for most uses (±3–8m). For sub-metre work we integrate Bluetooth GNSS receivers (Trimble, Emlid, Bad Elf) directly into the capture app, with RTK corrections where the network supports them.
You do. Data lands in your database — PostGIS, SharePoint, ArcGIS Online, or your own — not on our servers. We do not retain copies of operational data.
Yours isn't here? Ask us directly.
