Punching Out and Carrying On

Plot punch-out times against the scheduled end of shift. A healthy distribution is a small spread either side, with a tail where work overran.

The practical lesson in “Punching Out and Carrying On” is that a timesheet only becomes reliable through a process people can operate consistently. For teams exploring how to monitor employees without being intrusive, how to monitor employees without being intrusive can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

An unhealthy one is a spike exactly on the hour, with almost nothing after it. That shape does not occur naturally. It means the hour is being treated as a target, and whatever happens afterwards is happening unrecorded.

For a separate benchmark relevant to “Punching Out and Carrying On”, consult the CIPD working-time guidance. 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.

What produces the spike

An overtime control that requires prior approval, so recording a late finish means explaining it.

A supervisor who queries anything over the scheduled hours, however mildly. Two queries are enough.

An adherence or utilisation measure that counts time past the hour against somebody.

A system that refuses punches outside a window, which forces the choice directly.

Or a straightforward instruction, which is rare and does happen.

Why it is worse than unpaid overtime

Unpaid overtime that is recorded is a pay problem with a known size. Unrecorded work is a pay problem, a records problem and a safety problem at once.

The records problem: the organisation's own data says the person left at the hour. If something happened at twelve past, the record contradicts everybody's account including the supervisor's.

The safety problem: a clocked-out worker is outside whatever arrangements exist for people on site. In lone-working, late-shift and field contexts this matters a great deal, and it is the argument that moves senior people when the pay argument does not.

Detecting it

The punch distribution alone is suggestive. Joined to perimeter exit data it is conclusive: a spike on the hour with exits consistently later is the pattern, and the gap is the size.

By team and by supervisor, because this is almost always local. One department with a tight cluster and the rest with a normal spread is a finding about one manager's practice, and it is usually not malice — it is somebody managing an overtime budget with the only lever they have.

Fixing the cause rather than the symptom

Instructing people to record their actual finish time will not work while the consequences of doing so remain. The instruction has been given in most places where this pattern exists.

What works is removing the cost of recording: approval after the fact rather than before, a supervisor response about the work rather than the hours, and an overtime budget held at a level where a twenty-minute overrun is not a problem.

Then watch the distribution. It widens within a month if the change is real, and it does not move at all if the change was only announced.

The conversation with the supervisor

They are usually doing what they were asked. Somebody above them set an overtime figure and the figure is being met by the only method available.

The useful version of the conversation is with the person who set the figure, carrying the distribution chart and the exit data. A department whose overtime is zero and whose people are in the building seventeen minutes past the hour is not under control; it is reporting a number that is not true.

The related pattern at the start

The mirror image exists and is less common: punches clustered exactly on the hour at the start, with perimeter entries much earlier, which is the unpaid pre-shift edge described throughout this collection.

Both clusters together are the signature of a site where the clock records the schedule rather than the work. The schedule is already known; recording it twice adds nothing.

What a healthy distribution looks like

A peak near the hour, a spread of a few minutes either side, and a visible tail of genuine overruns with reasons attached.

It will look worse on an overtime report and it will be true, and every other thing built on the record — the safety arrangements, the scheduling data, the position in a dispute — gets better the moment it is.

Where the spike is sharpest

The cluster is tightest in roles with a visible overtime figure attached to a named manager, and loosest where the record is simply what happened. That is diagnostic: the sharpness of the peak measures how much pressure sits on the number rather than how well the schedule fits.

Compared across teams doing the same work, the differences are about supervision rather than about work content. A team with a soft distribution and a team with a spike on the hour are not working differently; one of them is recording differently, and the records of the other are the ones that can be relied on.