How to Stop Buddy Punching on a Field Crew
One worker clocks in for another who is not there yet. It is quiet, it repeats, and it lands straight on your payroll. Here is how to stop buddy punching with layered controls instead of one silver bullet.
A crew member is stuck in traffic, so their buddy taps them in on the shared time clock. Nobody thinks of it as stealing. It is a small favor between friends. But it happens again the next week, and the week after, and now you are paying for time that was never worked. That is buddy punching, and on a field crew it is one of the easiest ways for hours to leak out of your payroll without anyone raising a flag.
The frustrating part is that there is no single switch that ends it. Anyone who sells you a foolproof answer is overselling. What actually works is layering a few controls so that faking a clock-in gets harder at every step. This post covers the three layers that matter most for crews in the field: geofencing so a punch has to happen on site, optional clock-in selfies so a face is attached to a punch, and per-worker PINs on a shared kiosk so identity is not just an honor system.
What buddy punching actually is
Buddy punching is when one worker clocks in or out on behalf of another who is not actually there. It is different from an honest timekeeping mistake. It is one person standing in for another so the second person gets paid for time they did not work. On a job site it usually looks harmless: someone runs late, a friend covers for them, and the timesheet reads as a full day.
It costs you for a few reasons. You pay wages for hours nobody worked. If those hours push someone past 40 in a week, you may be paying overtime on top of it. And because the punch looks completely normal on the timesheet, you have no way to catch it after the fact. There is no red mark to review. The whole problem is that a buddy punch is designed to be invisible.
The layered way to stop it
No single control ends buddy punching on its own. Each one closes a different gap, and stacking them is what makes faking a punch not worth the trouble. Here is how the three layers fit together.
Layer one: geofencing, so the punch has to be on site
In Clox, a manager draws a radius around each job site on a map. That radius is the worksite fence, adjustable per site, with a sensible default around 200 meters. When geofencing is enforced for a worker, a clock-in from outside that fence is blocked at the punch. The off-site punch is never created. That matters, because most tools only warn a manager after the fact. Clox stops the punch from existing in the first place.
For buddy punching specifically, geofencing raises the bar. A coworker cannot tap someone in from the parking lot of a different job or from the couch at home, because the punch has to originate inside the fence. Enforcement is set per employee, so people who move between sites all day are not forced to fight it, and the crews who sit on one site can be locked to it.
There is a grace band so honest workers are not punished by a slightly noisy GPS reading. A punch just outside the radius can still land if it falls within the phone's reported accuracy, capped at 100 meters. Those allowed-but-marginal punches are flagged for you with an "Off the worksite" readout to review at approval, so you keep the day moving without waving through anything you should not. A fix too coarse to trust, worse than about 500 meters or wider than the fence itself, is rejected as too inaccurate.
Layer two: clock-in selfies, so a face is on the punch
Geofencing proves a punch happened on site. It does not prove which person tapped the screen. Clock-in selfies close that gap. When you turn them on, each punch captures a photo, so you can see at a glance that the right person clocked in. This is off by default, because a photo per punch is a real decision about your crew, and it is yours to make. Turn it on for the crews where identity is the weak point, and leave it off elsewhere.
A selfie does not stop a determined workaround by itself, and it should not be sold as one. What it does is make covering for a coworker awkward and obvious. A friend can tap a screen for you. It is much harder to explain why your face is not the one in the photo when a manager reviews the day.
Layer three: per-worker PINs on a shared kiosk
Some crews clock in from a single shared tablet at the site, not from personal phones. Clox supports that with kiosk mode: a shared tablet where each worker enters their own PIN. Identity there is the on-site tablet plus the worker's PIN, so a punch is still tied to a specific person rather than to whoever happens to be holding the device.
Be honest about the limits
Every one of these layers has an edge that a determined person could work around, and pretending otherwise would be lying to you. The location behind geofencing comes from the worker's phone. Clox reads what the phone reports. Geofencing is a strong deterrent, not a guarantee, and it is not tamper-proof. A selfie can be staged. A PIN can be shared. The honest framing is that these controls make cheating harder and more obvious at every step, which is what actually changes behavior on a real crew.
Clox does raise flags when the numbers do not add up. There are three review flags, shown at approval in priority order. The first is mock_location, when the device reported a fake or mock GPS provider. The second is impossible_travel, when a punch is impossibly far from the same worker's previous punch. The third is low_accuracy, a coarse but in-fence fix. You see these at approval so you can look closer at the punches that deserve a second look, instead of squinting at every single one.
Common objections
Will my crew feel like I am spying on them?
This is a fair worry, and it is why the controls are opt-in per crew rather than forced on everyone. Geofencing checks location only at the moment of a punch, not continuously through the day. Selfies are off by default and something you choose to enable. Framed plainly to the crew, most of this reads as protecting the people who show up on time, since their honest hours stop getting diluted by hours nobody worked.
What happens when there is no signal on site?
Field sites lose signal all the time. Clox works offline. The punch is saved on the phone with its real timestamp, the geofence is checked at punch time on the device, and it all syncs when signal returns. A dead zone does not become a loophole, and it does not cost your crew their clock-in.
Do I have to turn all of this on at once?
No. Start with the layer that fits your biggest gap. If your crews stay on one site, geofencing alone will close most of the buddy-punching door. If you run a shared tablet, lean on PINs. Add selfies for the specific crews where identity is the weak point. You can layer up over time rather than flipping every switch on day one.
Is any of this actually foolproof?
No, and be suspicious of anyone who tells you their product is. The location comes from a phone, a face can be staged, a PIN can be shared. What these layers do is stack deterrents so that faking a punch takes real effort and leaves a trail you can review. That is a genuinely different situation from a shared clock that anyone can tap for anyone. If you want to dig into the broader pattern, our guide on how to spot and stop time theft covers where hours tend to leak and what to watch for.
Where Clox fits
Clox is time tracking built for field and trade crews. Beyond the anti-buddy-punching layers, it is one-tap clock-in, with overtime and breaks calculated automatically and payroll-ready exports for QuickBooks, Gusto, ADP, and Paychex. The geofencing, selfies, and kiosk PINs are controls you layer on top of the day-to-day timekeeping your crew already has to do, not a separate system to run.
You can see the full picture of the geofencing side in our pillar guide to the best time tracking app with geofencing, and if you want to size up the whole toolkit for crews, start with our overview of the best time tracking software for field crews.
If you want to see what it costs before you set anything up, our pricing page lays out the plans, and you can start a free trial whenever you are ready to put the layers on your own job site.