You're looking at Tuesday's numbers and something doesn't add up. A tech logged nine hours, but the job list only accounts for about six. Maybe it's nothing — a long drive, a slow parts run. Maybe it's not. Either way, you don't actually know, and not knowing is the problem — and it's usually the moment employee time theft in field service stops being an abstract worry and starts being a specific Tuesday.
That's time theft, in the broad sense: hours paid for that weren't worked. It shows up as padded start and end times, breaks that run long and go unlogged, or — the more deliberate version — buddy punching, where one employee clocks in for another who isn't actually there yet. Time theft costs U.S. employers real money every year, and buddy punching alone is a large piece of it. But the fix isn't watching your crew more closely. It's making the record itself something neither side has to argue about.
What time theft actually looks like (and what it doesn't)
Most of what gets called time theft isn't a technician scheming to steal a paycheck. It's rounding: clocking in five minutes early "to be safe," stretching a 12-minute break to 20, forgetting to clock out and letting an extra hour ride. None of that is usually deliberate — it's the same memory-reconstruction problem that makes paper timesheets unreliable in the first place, which we've covered in more detail here.
Buddy punching is different, and it's worth naming separately because it's the one form of time theft that's unambiguously deliberate. It means one employee clocks in — or out — on behalf of a coworker who isn't actually there, usually by sharing a login or covering for someone running late, according to QuickBooks. It's the difference between "I rounded up" and "someone else punched my card for me." Both cost you money. Only one of them requires two people to agree to lie about it.
The cost, in numbers
Buddy punching costs U.S. employers more than $373 million every year, and in surveys roughly 16% of employees admit to having clocked in for a colleague at some point. When it happens, the most common adjustment is small — an extra 15 minutes here and there — which is exactly what makes it hard to catch by eye. Fifteen minutes doesn't look like fraud on a timesheet. It looks like rounding.
That's the uncomfortable part: the honest rounding problem and the deliberate buddy-punching problem produce nearly identical-looking numbers on paper. You can't tell them apart by squinting at a timesheet. You can only tell them apart by capturing a record neither one can produce — which is the actual fix, not closer scrutiny of the numbers you already have.
Why "watch them closer" backfires
The instinctive response to a number that doesn't add up is to watch more closely — spot-check job sites, call to verify locations, treat every discrepancy as a conversation about trust. Some of that is reasonable. All of it, done as the primary strategy, has a cost nobody puts on the spreadsheet: technicians who feel surveilled don't feel trusted, and technicians who don't feel trusted leave. Technician retention is already the most expensive lever in a service business — replacing a trained tech can take months — so a fix that solves time theft by making your best people feel policed is trading one cost for a bigger one.
The better fix doesn't ask you to watch more. It asks the record to do the watching, automatically, for both sides.
What actually stops it: verifiable, not surveilled
A handful of specific things close the gap between "I think something's off" and "I can see exactly what happened" — without turning the mobile app into a monitoring tool.
Clock-in tied to the technician's own device. Every clock-in is authenticated to the technician's own registered device through hardware-backed device authentication — cryptographic device binding means a session can't be replayed or reused from someone else's phone. One tech physically can't clock in for another, because the clock-in isn't a login anyone can share. It's tied to the hardware in their hand.
Every status change gets its own timestamp. Clocked in, en route, on site, on break, clocked out — each transition is recorded as it happens, tied to the job it belongs to, not reconstructed at the end of the week. That's the same live status data a dispatcher already sees on the board; it just doubles as the record if a number is ever questioned.
Clock-ins well outside the scheduled shift get flagged, not hidden. If a shift is scheduled for 8am and the clock-in lands at 9:40, that's visible to the dispatcher — not buried in a payroll export nobody reviews until Friday.
A forgotten clock-out doesn't just run all night. If a technician never clocks out, the shift auto-closes at day's end instead of quietly accumulating hours, and it's flagged for the dispatcher to review and correct.
GPS tracking while on duty. Location during a shift is part of the record — not to plot a technician's every move, but so "were you actually at the Henderson job at 2pm" has an answer besides someone's memory.
What this isn't: a minute-by-minute activity monitor watching what a technician does between clock-in and clock-out. It's a record of when a shift started, when it ended, which job the hours went to, and where the technician was while on duty — not surveillance of the work itself. If you're looking for keystroke-logging or screen-monitoring, that's not what this is, and it's not what field service actually needs.
Technician accountability that runs both ways
A verifiable record isn't just an owner's tool. It's what lets a technician say "check the log" instead of "trust me" when a customer disputes a bill, or when a payroll question comes up about a specific day. It's also what stops an honest disagreement about Tuesday's hours from turning into an accusation, because the record settles it either way — not in the owner's favor by default, and not in the technician's by default. Just accurately.
The actual fix for time theft isn't tighter suspicion — it's a record good enough that suspicion stops being the tool you reach for, and "check the log" works equally well for the owner and the technician.
FSM Navigator is free for the first 5 users, no credit card required, if you want to see how this looks on your own team before deciding on anything bigger.
See it in practice
See how FSM Navigator makes time records verifiable — device-authenticated clock-in, timestamped status changes, and shift-window visibility, tied to the same job-level timesheets that run payroll and job costing.