The field service app that works in dead zones.

Seventeen action types queue offline on Android, thirteen on iPhone: clock-in, clock-out, task completion, task updates, task creation, comments, photo uploads, digital form submissions, safety incidents, grievances, SOS, org messages, direct messages, shift applications, inventory transactions, file attachments, and signed work-proof events. Each carries a UUID and a local timestamp so chronology is preserved when the queue flushes on reconnect.

Two mechanisms. For clock-ins, the server locks the worker's open time entry and returns the existing one, so a clock-in that retries three times during a flaky reconnection creates exactly one entry. Create-type actions (messages, comments, tasks, incidents, forms, and the rest) carry a UUID idempotency key that the server checks, so a resubmission is recognized and ignored.

Queued events live in an app-private store on the device, protected by the phone's own encryption and, on iPhone, excluded from cloud backup. The store survives app restarts, OS reboots, and battery deaths. Data in transit is protected by TLS, with certificate pinning in the Android app. Photos cached locally for upload are app-private, not visible to other apps or the device gallery, and deleted after upload.

There is no built-in expiry and no size cap on the queue, so days without connectivity keep accumulating rather than dropping work. Retry attempts cap at 15 per event, and a plain network failure never burns a retry; that cap only matters when the server rejects a specific record. The queue itself does not time out.

On the phone, yes: the offline banner shows a running count of queued actions, failed ones surface with a one-tap retry, and queued records confirm on screen. The office dashboard sees records as they arrive; it does not yet show which devices still hold pending uploads, so payroll practice is simply to approve after the crew is back in coverage.

Most field service apps treat the server as the source of truth and break the moment a crew loses signal, because they were built for office workers and ported to mobile later. WorkTrac is offline-first by design: the app never blocks on the network, it captures locally first and reconciles with the server on sync, so crews in basements, tunnels, parking structures, and rural job sites can clock in, capture photos, complete tasks, and log safety incidents with zero signal. Everything queues on the device and syncs automatically when coverage returns, with UUID idempotency so nothing duplicates and nothing is lost.

WorkTrac connects the field and the office in one system that works offline. The crew uses the mobile app on site, even with no signal, to clock in, complete tasks, capture photos, and message; the office runs scheduling, invoicing, and payroll from the web dashboard off the same data. When a crew member is in a dead zone, their actions queue locally and flow to the office dashboard automatically the moment the device reconnects, so there is no double entry between the job site and the back office and no gap while a crew is out of coverage.