Clock in and out

The time clock is built so a punch cannot vanish because the radio dropped. Clock-in writes on the device with a deterministic id. Sync is a later step. Reloading the page does not mint a second open punch.

Open Time clock, or the clock button in the top bar.

1. Select the location if you work more than one.
2. Clock in.

If the location has a geofence, you must be inside the radius. The kiosk will refuse a punch from the car park if that is how the store set it.

Only one open punch exists per person per location. A second clock-in hits the same slot instead of doubling labor.

Clock out closes the punch, computes hours (minus breaks that fall inside the window), and renames the record to a stable closed id derived from person + clock-in time. A double-tap, or a kiosk racing a manager correction, writes the same closed document — last writer wins — instead of two punches for one shift.

An open punch that runs far past a real shift is almost certainly a forgotten clock-out. The kiosk caps it rather than letting a 22-hour punch hit payroll. Managers see stale open punches that the one-card-per-person kiosk grid cannot show, and can close and correct them.

Breaks recorded on the punch are clamped into the clock-in / clock-out window. Moving the boundaries later cannot make break time exceed the span (which would drive paid hours negative).

Managers see closed punches waiting approval and the stale-open list. Corrections belong here and on Timesheets. Members clock themselves; they do not approve.

If the device is offline, the punch still holds in the local cache across reloads. When the network returns, sync is a separate step — the clock does not pretend a failed write was a successful one.

Optional web push can remind staff. There is no native App Store / Play app. The worker surface is this page in a browser.