What the Punch Actually Marks

A time clock records one fact: that a credential was presented at a device at a moment. That is all it knows and all it can ever know.

The practical lesson in “What the Punch Actually Marks” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring employee monitoring software, employee monitoring software can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

Everything built on top of it treats that moment as the start of the working day — payroll, the rota, the attendance report, the overtime calculation, the evidence in a dispute. The gap between what the device recorded and when work actually began is where almost every argument in this subject lives, and it is nobody's field in any system.

For a separate benchmark relevant to “What the Punch Actually Marks”, consult the ILO working-time resources. 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.

Three different moments

Arrival at the premises. Often the earliest, often recorded by something — a car park barrier, a security turnstile, an access door — that is not the time clock and does not talk to it.

The start of required activity: the moment the person begins doing something the employer requires. Changing into protective equipment, collecting a radio, queuing for a security search, starting a vehicle check, logging into a machine that takes four minutes to boot.

The punch, which happens whenever the person reaches the device, and whose position relative to the other two is determined by where the device is.

In a well-arranged site these three are within a minute of each other. In most sites they are not, and the distance between them is a decision somebody made about where to put a terminal.

Why the device's position is a pay decision

Put the clock at the gate and the punch captures the walk to the floor. Put it on the floor and it does not. Put it past the changing room and changing is unpaid; put it before, and it is paid.

Nobody experiences this as a pay decision. It is made by whoever installed the system, on grounds of cabling, supervision or convenience, usually years ago. It then determines, for every worker on that site, which minutes are counted — and in many jurisdictions whether the arrangement is lawful.

This is the single most useful thing to understand about clock systems: the hardware placement is the policy, and the written policy is frequently a description of something else.

What the record will be asked to prove

In a pay dispute, in an inspection, in a tribunal, or in a client audit, somebody will produce the punch data and say it shows the hours worked.

It does not. It shows the times at which a credential was presented. Whether those times coincide with the start and end of work is an assumption, and it is an assumption the organisation will be asked to justify, usually years later, by somebody who has walked the site and timed the distance from the gate to the terminal.

Organisations that can answer — because they measured it, wrote it down, and placed the device deliberately — are in a very different position from those that cannot.

The question that sits underneath all of this

Not "is the clock accurate", which it almost always is to the second. But: does the moment it records correspond to the moment the paid day begins, and who decided that?

Everything in this collection comes back to it. The sections that follow take the two sides of the punch in turn — what happens before it and what happens after — then the day in between, the machine itself, the translation from a punch into money, and what happens when somebody disputes the result.

The two systems that never speak

Almost every site that has a time clock also has access control, and the two are separate products bought by separate departments in separate years. Security owns the door; payroll owns the clock; nothing joins them.

That separation is the reason the gap described here is invisible. Both halves of the measurement exist, in the same building, with the same person's identifier on them, and nobody has ever subtracted one from the other. The join is a day's work for anybody with both exports, and it is the first thing this collection asks you to do, because every later argument depends on having the number.

What this collection is not about

It is not about choosing or deploying a clock system, which is a procurement subject with plenty written about it. It is not about people deliberately cheating the clock, which is a disciplinary subject with its own literature and its own difficulties.

It is about the boundary the clock is supposed to mark: where it actually falls, who put it there, what lies on each side of it, and what that is worth once multiplied by a workforce and a year.