Clock systems, from the edge inwards
The clock is accurate. The boundary is the argument.
Nineteen minutes a day, one site
Per person, per day
19 min
Per person, per year
76 hours
Across 240 people
18,240 hours
Which is
9 full-time posts
Nobody on the site has ever raised it, because for any individual on any day it is nineteen minutes. The unit of experience is the day and the unit of consequence is the year.
Fifty notes on clock in / clock out systems, written about the line the punch is supposed to mark. What happens in the minutes before it, what happens after, who required each of those activities, and what the difference is worth once multiplied by a workforce and a year.
Named product comparisons are kept in separate guides. Nothing here is legal or payroll advice: what counts as working time, what may be rounded or disregarded, and how pre- and post-shift activity is treated differ substantially by jurisdiction, sector and agreement.
One morning, measured
Warehouse operative, early shift
19 minutesbefore the clock, every day
Before the punchAfter it
The punch is at 07:00 and the person left their car at 06:41. Fifteen of those nineteen minutes are required by the employer; four are the walk from a car park the employer provides. The clock records none of the distinction, and the terminal's position past the changing room is what decides it.
The same morning, sorted by who required it
| What happens | Required by | Paid? |
|---|---|---|
| Changing into mandatory PPE | Employer, written rule | Contested |
| Queuing at the security search | Employer, entry and exit | Contested |
| Walking from the gate to the floor | Site layout | Not paid |
| Pre-shift briefing | Supervisor, every day | Paid |
| Arriving early out of habit | Nobody | Not paid |
The two contested lines are the ones nobody has decided. They are also the two longest. Everything in this collection is a way of getting those two lines off the fence.
Why this is about the boundary and not the clock
There is a great deal written about clock systems: which method to choose, how accurate the location is, how to stop people clocking in for each other, how to investigate when the minutes do not add up. That material is good and this is not more of it.
The practical lesson in “The clock is accurate. The boundary is the argument.” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring employee monitoring software with screenshots, the official product page can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
Every note here is about the line the clock exists to mark. A time clock records that a credential was presented at a device at a moment — that is all it knows. Everything downstream treats that moment as the start of the working day, and in most workplaces it is not: there is a walk, a queue, a changing room, a machine that takes four minutes to boot, a briefing. Which of those count, and who decided, is a question the device cannot answer and the policy usually does not.
For a separate benchmark relevant to “The clock is accurate. The boundary is the argument.”, consult the U.S. Wage and Hour Division. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.
01 / 07
What the punch marks
What a clock records, what everyone assumes it records, and the distance between them.
02 / 07
Before the punch
Parking, queues, changing, booting, briefings — the longest unpaid stretch in the day.
05 / 07
The machine itself
Where it sits, how long the queue is, what happens when it fails, and who fixes it.
06 / 07
From punch to payslip
Rounding, pay rules, premiums and the translation layer nobody has read.
07 / 07
When it is contested
Corrections, disputes, inspections, and what the records will actually support.
Independent product comparisons
Tool guides
Three differently structured guides connect product capabilities with clock-in boundaries, attendance, corrections and payroll review.
The short version
Measure the edge before you argue about the clock
Subtract the perimeter timestamp from the punch for a month. Sort what happens in between by who required it. Decide the contested lines rather than leaving them. Make the threshold symmetric and round at the latest point. Then look at where the terminal is, because that is the policy.