Do digital field tickets work offline?
The objection is fair. Lease roads, tank batteries and remote pads are exactly where signal dies, and a ticket app that needs bars is worse than paper.
Yes, with conditions
5 things that decide this
- 01Digital field tickets work with no signal at all when the app is built offline-first: every ticket, photo and signature saves to the device's own database and syncs when coverage returns.
- 02Offline-first is different from caching. A cached app shows old data without signal but cannot reliably create new records. That distinction is where most field disappointment comes from.
- 03The crew's workflow does not change at a dead zone. Capture the work, collect the signature, drive on. Sync is the software's problem, not the operator's.
- 04Enverus lists lost and illegible paper tickets among the top field ticketing pain points, with tickets physically driven to offices for approval. Offline capture removes the drive without betting billing on cell coverage.
- 05We build field systems this way as standard. TankAware, our petroleum site platform for Sutherland Excavating Ltd., replaced paper inspection logs across hundreds of sites where coverage is never guaranteed.
What offline-first actually means
An offline-first app treats the device as the primary database. A ticket created at a well pad is complete the moment the operator saves it: line items, hours, photos, the customer signature, a timestamp. The record sits in a local queue. When the truck rolls back into coverage, the queue drains to the server in the background, oldest first, with retries until every record is acknowledged.
The engineering that matters is unglamorous. Photos are large, so they upload separately from ticket data and never block it. Every record carries a unique id from the device, so a retry cannot create a duplicate invoice line. And a sync that fails halfway leaves the queue intact instead of losing the ticket, which is the failure paper never had.
Offline-first against offline-capable
Vendors use both phrases. Only one of them survives a week in the field.
| Behaviour with no signal | Offline-first | Cache-only |
|---|---|---|
| Create a new ticket | Works, saves locally with signature and photos. | Often blocked, or saved in a state that dies with the app. |
| Two days with no coverage | Queue holds everything. Syncs on return. | Session expires. Work is lost or re-entered. |
| Same ticket edited in office and field | Conflict is detected and surfaced for review. | Last write silently wins. Billing disputes follow. |
| App killed mid-shift | Local database persists. Nothing lost. | Whatever was in memory is gone. |
The ticket that syncs tonight gets approved tomorrow
Paper tickets ride in trucks until someone drives them to an office, then wait in an approval pile. Enverus's field ticketing research describes exactly this chain, and every link in it adds days between finishing work and invoicing it. An offline-first ticket enters the approval queue the evening the crew gets coverage, signed and legible, with photos attached.
That is the honest business case. Offline capability is not a feature for bad coverage areas. It is the thing that lets a field services company invoice from the field instead of from a pile.
Field questions
01How long can a device stay offline without losing tickets?+
Days or weeks, in a properly built app. The local database is bounded by device storage, not by a session timer. Photo-heavy work fills storage first, which is why photo compression and per-ticket size budgets are part of the design.
02What happens if two people edit the same ticket?+
A well-built sync detects the conflict and puts the ticket in front of a human instead of silently overwriting one side. For field tickets the practical rule is usually field-wins on work data and office-wins on pricing, decided per field, not per record.
03Are offline signatures still defensible in a billing dispute?+
Yes, and usually more defensible than paper. The signature is stored with a device timestamp, a GPS fix where policy allows, and the exact ticket contents it was applied to. A signed paper ticket proves less and photocopies worse.
04Does this need special hardware?+
No. Ordinary iOS and Android devices handle it. The requirement sits in the software architecture, which is why retrofitting offline onto an online-only app is a rebuild rather than a setting.
Related
- Oil and gas software development →Field systems where proving the work happened is the product.
- TankAware →Petroleum site management for Sutherland Excavating Ltd., built for patchy coverage.
- Dead letter queue →The pattern that keeps a failed sync from losing records.
- Will your automation survive an API change →The other reliability question to ask before buying field software.
