How to Stop Buddy Punching and Persistent Lateness

Practical ways to reduce time theft and lateness without turning into a surveillance operation, and what the numbers actually look like.

Buddy punching, one employee clocking in for another, is not usually malicious. It starts as a favour for someone stuck in traffic and becomes normal. The cost is real, but the fix is rarely disciplinary.

What it costs

Industry estimates put losses from inaccurate time capture at up to around 4% of gross payroll. On a £1m wage bill that is £40,000 a year, and most of it is not dramatic fraud: it is ten minutes here, a rounded-up shift there, and a reconciliation nobody has time to do properly.

Three fixes that work, in order of effort

1. Make the punch personal

You cannot clock in for a colleague if the system needs their fingerprint, their face, or a photo taken at the moment of clocking. Photo capture is the underrated option, it needs no hardware, is far less sensitive than biometrics under UK GDPR, and resolves almost every dispute instantly.

2. Match every punch to an expected shift

Lateness is only visible if the system knows what time someone was due. Matching punches to a published rota converts a list of timestamps into a short list of exceptions, and it is the exceptions, not the timestamps, that a manager should ever look at.

3. Set tolerance deliberately

Most businesses want a few minutes of grace. Set it explicitly, say five minutes, and apply it consistently. An unwritten tolerance that varies by manager is the single biggest cause of grievances about lateness.

Consistency matters more than strictness. Staff accept a rule they can predict.

What not to do

• Do not track location continuously. Capture location at the moment of clocking, not throughout the shift, anything more is disproportionate and damages trust.
• Do not use lateness data punitively without conversation. The data tells you a pattern exists. It does not tell you why.
• Do not introduce monitoring silently. Tell staff what is captured, why, and what it will and will not be used for.

Making it stick

The businesses that solve this treat it as an administration problem rather than a behaviour problem. When clocking is quick, the rule is clear and the exception process is easy, the incentive to work around it largely disappears.

How to measure whether it is working

Pick three numbers before you change anything, so you can tell whether the change did something:

• Exception rate, missed or mismatched punches as a percentage of shifts. A healthy figure after a few months is low single digits.
• Median lateness: the middle value, not the average, which one person with a two-hour delay will distort.
• Time to resolve, how long an exception sits before it is explained and approved. If this is measured in weeks, it is being done at month end.

Writing the policy so it holds

A time and attendance policy does not need to be long, but it should be explicit about four things: what is captured, what the tolerance is, how an employee corrects a mistake, and what repeated lateness leads to. Ambiguity in any of those four is where disputes come from.

Share it before switching anything on, and make the correction route genuinely easy , if fixing a forgotten clock-out is harder than asking a manager, staff will keep asking the manager.

ClockedInOne captures a photo and location with every browser or mobile punch, matches it to the published rota, and routes exceptions to the employee to explain before a manager ever sees them. See attendance software and employee self-service.

Frequently asked questions