Working offline and syncing
Clocknet doesn't need a connection to record time. Every clock-in, break and clock-out is saved on the phone the moment you tap, so a basement or a remote site with no signal doesn't stop anyone from tracking time.
Clock in, take breaks and clock out as usual. The app sends everything to the server once you're back online.
How offline clock-ins work
When you tap with no connection, the app saves the action on your phone with the time you tapped and your position. If your workspace uses face verification, the selfie waits on the phone too and is checked when it reaches the server. The timer keeps running, and you can start and end breaks. Actions the server doesn't have yet are marked pending, and the sync status shows whether you're offline, syncing or synced.
How syncing works
When the connection comes back, the app sends the waiting actions to the server in the order you made them. Each action carries an ID created on the phone, so if a weak connection makes the app send something twice, the server keeps one copy. Once the server accepts an action, it's no longer marked pending.
Each action keeps the time you tapped, not the time it reached the server. A clock-in made at 08:00 and synced at 10:00 starts at 08:00.
When the server disagrees
Sometimes the server can't accept a waiting action. A manager may have edited or closed the time entry while you were offline. The action may be older than your workspace allows, or fall in a week whose timesheet is already approved. In each case the server's version stands: your phone updates to match and shows a short message saying what happened. If the action was too old or landed in an approved week, the message suggests adding a manual entry instead.