How Do You Actually Stop Security Guard Time Theft?

Security guard time theft costs firms twice — wages out, billing exposure in. Learn the four forms, the real math, and the fix ladder to stop it.

Joe Juarez — Co-founder & CEO

Published July 12, 2026 Updated July 17, 2026 7 min read

Let me say the important part first: most guards are honest. I run a security company with 400+ employees across Houston, Corpus Christi, Las Vegas, and Florida, and the overwhelming majority of our officers show up, do the work, and go home. Time theft is a systems problem, not a "guards are lazy" problem. When your only record of a shift is a paper timesheet or an honor-system phone clock-in, the temptation exists, the honest guard can't prove they worked, and the one bad actor on your roster can bleed you for months before anyone notices.

Below: the four forms time theft takes on night shifts, what one ghost shift really costs (worse than you think), and the fix ladder we use — from policy up through anomaly alerts.

How Do Guards Clocking In for Each Other Actually Get Away With It?

Buddy punching in security is simple: Guard A can't make the 11 p.m. shift, so Guard B — already on site or nearby — clocks in for him. On a paper timesheet, that's a signature. On a shared tablet at the guard shack, it's typing in someone else's PIN. On a phone-based system with no location check, it's Guard B logging into Guard A's account from his couch.

Night shifts are where this lives, for an obvious reason: nobody from the office is awake. The client's facility manager left at 6, your account manager is asleep, and the only witnesses are the two guards covering for each other. The American Payroll Association has commonly cited that roughly 75% of US businesses experience some form of time theft, with buddy punching among the top methods — security is not special here, except that our labor is the product, so the loss hits harder.

The tell is in the details: identical clock-in times to the minute across weeks, two officers punching from the same device, or a guard "on post" at a Corpus Christi warehouse 40 minutes after clocking out of a Houston site.

What Do Off-Site Clock-Ins and Inflated Hours Look Like in Practice?

The softer forms are more common than outright buddy punching, and honest people drift into them:

• Off-site clock-ins. The guard clocks in from the parking lot of a gas station ten minutes away, then arrives at the post at 11:20 for an 11:00 start. Twenty minutes, five nights a week, is 100 minutes of paid, unworked, billed time — per guard, per week.
• Inflated hours. The relief guard is late, so the outgoing guard writes 7:30 instead of 7:10 on the way out. Or a four-hour special event gets logged as five because "setup counts." Individually small; across 50 officers, structural.
• Sleeping or leaving post while clocked in. Technically worked hours, but not delivered service — and it's what your client's camera catches at 3 a.m. right before they cancel the contract.

None of these require a dishonest person — just an unverifiable system plus normal human rationalization.

What Is a Ghost Shift, and Why Is It the One That Kills Security Companies?

A ghost shift is a shift that appears on the schedule and the timesheet but that nobody worked at all. In a security company, ghost shifts happen when scheduling and verification are disconnected: a post gets double-covered on paper, a canceled shift never comes off the timesheet, or — in the worst case — a guard or a rogue supervisor deliberately logs shifts at a low-supervision site where no one checks.

Here's why the ghost shift is the existential one, with real industry numbers. US commercial guard wages commonly run $15–20/hr and bill rates commonly run $25–35/hr. Take a middle case: one 8-hour ghost shift per week at an $18/hr wage, billed to the client at $28/hr.

That second row is the killer. The $144 is money gone. The $224 is worse: you invoiced a client for service that wasn't delivered. If they audit — and post-incident, they will — you're facing a canceled contract, a reputation problem in a referral-driven industry, and in a genuinely bad case an invoice-fraud allegation. One weekly ghost shift at one site is a $19,000-a-year problem that can end a client relationship worth ten times that. (If a dispute gets that far, talk to a lawyer — this is operational guidance, not legal advice.)

And remember the industry's context: annual guard turnover is commonly cited at 100%+. You are constantly onboarding people you barely know onto overnight posts nobody watches. The system has to do the verifying, because tenure and familiarity won't.

How Do You Stop Timesheet Fraud Among Guards Without Treating Everyone Like a Suspect?

You climb a ladder. Each rung costs a little more and closes more gaps. Most companies under 50 officers are still standing on rung one.

1. Written policy. Define time theft plainly — including buddy punching and off-site clock-ins — state consequences, and have every officer sign it. Texas DPS licensing already requires you to keep employment records straight; your time policy should be sitting next to them. Policy alone stops the drift-into-it cases.
2. Supervisor spot checks. Unannounced night visits and call-downs. Effective but expensive and unscalable — a supervisor covering 12 sites across a metro hits each one maybe twice a week, and everyone learns the pattern.
3. GPS/geofence clock-in. The clock-in only registers inside a radius around the post. This kills off-site clock-ins and most buddy punching in one move, because Guard B can't punch for Guard A from his couch. It's the single highest-leverage rung on the ladder.
4. Checkpoint-verified patrols. Geofenced clock-in proves the guard arrived. NFC or QR checkpoint scans on a patrol route prove the patrols actually happened — hourly, all night, with timestamps. This is the rung that kills ghost shifts, because a shift with zero scans is visible by 1 a.m., not at month-end.
5. Anomaly alerts. The system flags what humans miss on rung two: missed scan windows, clock-ins outside the geofence, identical punch pairs, hours logged against unscheduled posts. You review exceptions, not everything.

This ladder is exactly what we built into SNTNL's proof-of-service platform — geofenced clock-in, checkpoint patrols with missed-scan alerts, and the exception reporting on top — because we needed it for our own 400 officers before we ever sold it to anyone. At Ranger Guard, unverified-patrol exceptions dropped visibly within the first quarter after checkpoint verification went live. That's the shape of change you're buying: not "we caught more people," but "the gap where theft could hide got measurably smaller."

Why Verification Protects Honest Guards More Than It Polices Them

Here's the culture note that makes rollout work: transparency cuts both ways, and your honest guards — again, most of them — come out ahead.

When a client claims the overnight officer "was never there" (it happens; facility managers misread camera angles and schedules all the time), a guard on an honor system has only his word. A guard on a verified system has a geofenced clock-in at 22:58 and fourteen timestamped checkpoint scans — the accusation dies in one email. We've framed it to our own officers from day one: this is your alibi, not your ankle monitor. Reliable guards figure out fast that proof of work is job security. It's the same reason our own operation runs on this system — the data defends the company and the officer.

If you're currently on software that can't do rungs 3–5 and you're wondering about a change, mind your contract dates first — most guard software auto-renews, and the switching playbook walks through the 90-day notice window that traps most operators.

If you want to see what verified shifts look like on a real portfolio — geofenced punches, checkpoint scans, and the exception report that replaces 2 a.m. spot-check drives — book a 20-minute walkthrough. We'll show you our own live data, because we run our company on it.