Works with no signal, syncs when there is.
Inspections happen where there is no network, so they're recorded on paper and typed up later — if they're typed up at all. By then nobody can say which reading came from which item.
What we build
- An offline-first Android app that captures everything locally and syncs when a connection returns
- Scan-to-identify, so a reading is bound to the right item rather than a hand-written reference
- Chain of custody — who handled what, when
- Export or sign-off at the end of a visit, including certificate and spreadsheet output
Hardware it runs on
- Chainway C5
- Rugged handheld for field conditions
- OEM UHF handhelds
- Built-in modules, integrated over serial where no SDK exists
- Zebra RFD40
- Sled where read range matters
Every device listed here is one we have written about or shipped against. If yours isn't on the list, the feasibility read covers whether it can be.
How it reaches your system of record
Captured records queue on the device and reconcile on sync, so a repeated upload can't create duplicates. Where a backend isn't ready, the visit ends in a signed spreadsheet export instead — usually the format the business already runs on.
What you get
- Offline-first Android application
- Sync and conflict-resolution logic
- Export or certificate templates
- Field procedure notes for the crew
What it costs
A fixed fee, scoped after the feasibility read. You see the number before any work starts, and it doesn't move.
How an engagement runsThe work behind it
We publish the engineering, not just the sales page.
Send us the device and the error
Model, SDK version, and what's failing. A written read within 24 hours, and nothing owed if it's a no-go.
Get a feasibility read