Working offline & how sync resolves
ClockNet is offline-first by design. Every clock-in, break and clock-out is written to your device the moment it happens — so a dead zone, a basement, or a rural job site never stops your team from tracking time accurately.
Nothing waits on a connection. Actions are saved locally and reconciled with the server automatically when you're back online.
How offline clock-ins work
When you tap the clock button without a connection, ClockNet records the action locally with its timestamp, GPS result and any verification outcome. The app keeps working exactly as it does online — the live timer runs, breaks and job switches all behave normally. Each pending action is marked so you can see what hasn't synced yet.
How sync resolves
As soon as a connection returns, ClockNet sends queued actions to the server in the order they happened. Entries are de-duplicated using a unique id generated on the device, so a flaky connection can't create double clock-ins. Once an action is accepted you'll see it move from “pending” to “Synced”.
Actions reconcile by the time they actually occurred on the device — not the time they happened to reach the server.
Conflicts & server truth
If the same entry was changed in two places — for example, a manager edited it while a device was offline — the server's version is treated as the source of truth. Your device updates to match and shows a brief note explaining what changed, so the record everyone approves is always consistent.