Buddy punching
Also known as: buddy clocking, proxy clocking, clocking in for a colleague, time theft
Buddy punching is when one employee clocks in or out for a colleague who is not there, so the colleague is paid for time they did not work. It is a known weak spot of any time clock that checks only a card, a PIN or a password.
The name comes from punch clocks, where a worker pushed a paper card into a machine that stamped the time on it. Asking a friend to punch your card was easy, and the habit survived every new kind of clock: badges can be handed over, PINs shared and passwords typed by someone else. Most of the time it starts small and friendly: a colleague who is running late asks someone already at work to clock them in. It still means the record says something that did not happen, and payroll pays for it. For employers it is a question of accurate pay and of fairness to the people who clock in honestly. For employees it can become a disciplinary matter, even when it felt like a favour.
Why it happens
- The clock checks only something that can be shared, such as a card, a badge, a PIN or a password
- Lateness rules are strict and there is no easy way to explain a delay, so covering for a friend feels safer than being late on the record
- The site is busy and nobody sees who is standing at the clock
- It is seen as a harmless favour between colleagues
Why it matters
Every clocked minute that was not worked is paid as if it were. Over time that adds up, and it also distorts overtime, attendance reports and staffing decisions built on the same records. The less visible cost is trust: people who clock in honestly notice when others do not, and a manager who finds out has to choose between looking away and a hard conversation.
Common ways to prevent it
- A code shown at the workplace that changes often, so the person has to be there to read it
- A location check at clock-in, which makes clocking in from somewhere else visible (see geofencing)
- Supervisors reviewing entries, especially unusual ones, before timesheets are approved
- Personal logins on personal devices, so each clock-in is tied to one person and not to a shared terminal
- Biometric clocks that read a fingerprint or a face. They are hard to share, but they collect biometric data, which many data-protection laws treat as especially sensitive, so they raise privacy questions of their own
- A clear written policy that says clocking in for someone else is not allowed and what happens if it is found
How HourSquare helps
HourSquare has two checks, set per workplace under Settings, Workplaces, Clock-in location, that can be used alone or together. The first is a location check: when someone clocks in or out, the Hub reads the device's location once, and each entry shows whether they were at the workplace. Under the Require rule, clocking in works only inside the circle around the workplace. The second is an on-site code: a screen at the workplace, such as a tablet, a monitor or a spare phone, shows a six-digit code that changes every 30 seconds, and people type it when they clock in. A determined person can fake a browser's location, so the on-site code is the stronger of the two.
Managers see a chip on each entry, such as "At workplace" or "Away" with the distance, and marks such as "New device", in Time & attendance, Today, with a "Flagged locations" filter. The same chips appear on timesheets and in approvals. Marks never refuse anyone; they point a manager at the entries worth a second look.