Job sites don’t come with good signal. Klees is built so a dead zone never costs a worker their hours — or costs you the truth about when the punch really happened.

How offline punches work

A worker taps Clock In (or Out) with no connection.
The app saves the punch on the device with the exact moment it was tapped, and tells the worker: “Your clock-in was saved and will sync when you have signal.” No scary error, no retry-mashing.
When signal returns, the queue syncs automatically. The entry is recorded at the original tap time, not the sync time — an offline replay never inflates hours.

What managers see

Entries that synced late are flagged with a late-sync alert (e.g. “Clock-in synced 28 min after it happened (offline replay)”) on the timesheet, so you know which punches traveled through the queue. The flag is informational — the times are correct — but it’s your audit trail for connectivity-heavy sites.

What never queues

Only network failures queue. If the server actively rejects a punch — expired session, already clocked in, invalid job — it does not queue for replay. That prevents a stale punch from clocking someone in behind their back hours later.

Tip

Basements, rural sites, metal buildings: tell crews to punch normally and pocket the phone. The queue does the rest. If a worker’s hours look missing mid-day, they usually appear as soon as the phone finds signal on the drive home.