How to Stop Buddy-Punching at Multi-Location Stores
The 6 AM phone call. The schedule that shows 38 hours but the store was dead from 10 PM on. The employee whose timecard says Tuesday but the security footage says they left Monday. Here is what actually fixes it.
What buddy-punching actually costs you
In my experience, few operators know their buddy-punching number. They know it happens — the manager covers for the late opener, the closing crew clocks each other out at 11 when the store closed at 10:30 — but the cumulative cost is invisible until someone runs the math.
Here is the math. At a $15/hr wage floor, 10 minutes of unauthorized time per shift per employee, one location, five employees, six shifts per week:
- 10 minutes × $15/hr = $2.50 per event
- 5 employees × 6 shifts = 30 events per week
- 30 × $2.50 = $75/week per location
- $75 × 52 weeks = $3,900/year per location
And that number leaves out overtime that tips because of padded hours, payroll taxes on the phantom labor, or the compliance exposure if a wage-and-hour audit catches clock records that do not match actual work performed.
At 10 locations, this is $39,000 per year in labor that never produced a shift. That is a part-time manager's salary walking out the door in 10-minute increments.
The 6 AM phone call version of this problem is the ghost shift: an employee who is scheduled, clocked in by a buddy, and never showed up. The manager only discovers it when a customer complains or a health inspection is violated because nobody opened the sanitizer logs. That is the high-stakes version of the same underlying failure.
Why per-PIN systems alone do not work
Replacing shared timecards with per-employee PINs was the right move in 2015. It stopped the most obvious abuse — an employee logging in under the manager's credentials — and it created individual accountability on the time record.
But PINs are four digits. They are written on sticky notes. They are texted in group chats. "Hey can you punch me in I'm 5 minutes out" is a text that gets sent every morning in multi-unit stores across the country. The PIN controls the timecard system. It does not control geography.
The PIN problem is not a technology problem — it is a human behavior problem. The fix requires adding a layer that the employee cannot delegate to someone else: their physical location at clock-in time. That is GPS.
A PIN verifies identity. GPS verifies location. Together, they verify that the right person is in the right place at the right time. Missing either one leaves a meaningful gap.
GPS + geofence: how it closes the gap
A geofence is a virtual boundary around your store: in DohOps, a GPS radius you set for each location. When an employee clocks in from their phone, the system checks the device's GPS coordinates against that radius. Depending on the setting you choose, a clock-in from outside it is either blocked or allowed and flagged for a manager.
Set the radius for each location: tight enough to reject a punch from the parking lot across the street, but loose enough to allow for GPS drift on older phones. Widen it for hotel campuses with multiple detached buildings or gas stations with large lot footprints.
The GPS layer makes the texted-PIN problem much harder. It does not matter if someone else knows your PIN — they cannot use it from their couch at home. Phone clock-ins have to come from inside the radius (or get flagged), and the kiosk only works on the store's own network.
DohOps also supports Kiosk Mode, where a single shared tablet at the back of the store handles all clock-ins. Employees enter their PIN on the tablet, and the kiosk only works from your store's own network, so every punch on it happens at the store. Wrong-PIN guesses are capped. It is a good fit for QSR and gas stations, and it takes the employee's personal phone out of the equation.
Photo capture at clock-in: the identity layer
GPS confirms location. A PIN confirms account. Photo capture at clock-in confirms the person. The combination of all three makes sustained buddy-punching much harder to get away with.
Here is how it works in DohOps: when an employee clocks in, the system can prompt for a selfie (you choose whether to require it). The photo is timestamped and stored with the punch and its GPS location, so a manager can check it when something looks off — for example, a clock-in flagged as outside the GPS radius, or one that does not match the schedule. Nobody has to review every photo every morning.
This is not facial recognition in the biometric sense. It is a photo audit trail that creates accountability: employees know the photo is there, managers can pull it on demand, and any dispute about whether someone was actually present has a timestamped record attached.
In my stores, the existence of photo capture — even without anyone reviewing every photo every day — changed behavior. The crew knows it is there. The plausible-deniability window closes.
The audit trail: what you need for disputes and compliance
Buddy-punching is a labor compliance issue, not just an operational one. When a Department of Labor audit or a wage-and-hour lawsuit requires you to produce clock records, those records need to be complete, with every change logged. A system where managers can edit time records without a log — or where clock-in data can be deleted — is a compliance liability regardless of whether buddy-punching is happening.
DohOps keeps every clock event — clock-in, clock-out, breaks, GPS location, and photo if applicable — with every edit logged in an append-only audit trail kept for 7 years. Export the Time & Attendance report (CSV, Excel, PDF) for any date range; every edit to a time record is in the audit log, with a timestamp and the manager who made the change.
This is the documentation a franchise audit wants to see. 7-Eleven's store audit process, for example, requires that time records match labor cost calculations in the weekly report. An audit trail of every edit makes that reconciliation much easier.
The audit trail is also the first thing that changes employee behavior. When crews understand that every change is logged and visible to the owner, the casual buddy-punch stops being casual. The risk calculation changes.
How DohOps handles it end to end
DohOps's Time & Attendance module was designed specifically for multi-unit operators who have already been burned by every failure mode above.
The setup is straightforward. You add a location, set its GPS radius, add employees with their PINs, and decide whether to require photo capture. That is it. From the first shift, the Time & Attendance report lists hours by person and day with exceptions; the clock-vs-schedule view shows who came in early or late or stayed past their relief; an open clock-ins banner catches forgotten clock-outs so a manager can close them; GPS "flag" mode marks punches from outside the radius; and an optional schedule-based limit blocks clock-ins outside the shift window.
Owners and managers see this for the stores they have access to, so nobody has to dig through raw time logs. The system flags what matters and lets the manager deal with people, not spreadsheets.
Payroll reports come from the same system: clean hours, with overtime by federal rules or the CA, AK, NV or CO presets, exported to CSV, Excel or PDF for your payroll provider. The buddy-punching cleanup does not create new payroll work — it reduces it.
Start the 30-day free trial and set up GPS clock-in for all your locations in under an hour. Or book a 15-minute demo to see the Time & Attendance report live.
Buddy-punching FAQ
Stop paying for shifts that were never worked.
30-day free trial. Set up GPS clock-in for all your locations in under an hour. Exceptions show in the Time & Attendance report from the first shift.