Where Does Revenue Leakage Actually Happen in a Security Company?

Revenue leakage in a security company hides in overtime, invoices, and disputes. Find the 6 biggest margin leaks and run our leak audit this week.

Yonah Nathan — Co-founder & Head of Product

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

I run operations for Ranger Guard — 400+ employees across Houston, Corpus Christi, Las Vegas, and Florida — and the most expensive lesson I've learned is that guard companies almost never lose margin in one dramatic event. At bill rates commonly running $25–35/hr for US commercial work and wages commonly $15–20/hr, your gross margin per hour is thin enough that a 2–3% leak across the book is the difference between growing and treading water.

Here are the six places the money disappears, with what each one looks like on the ground and how proof-of-service data closes it.

Why Is Your Security Company Losing Money on Unbilled Overtime?

The scenario: A guard at a Houston distribution center stays 90 minutes past shift end because relief no-showed — an everyday event in an industry where annual turnover is commonly cited at 100%+. Your scheduler covers the gap, payroll pays the overtime at 1.5x, and the invoice goes out based on the scheduled hours. You just paid a premium wage for hours you billed at zero.

Overtime you pay but don't bill is a double leak: the cost went up and the revenue didn't move.

How proof closes it: GPS-verified clock-ins and clock-outs create a per-position record of actual hours versus scheduled hours — the same records that stop guard time theft on the payroll side. When the variance report flags "worked 9.5, scheduled 8" the same day, billing can decide — bill it, eat it knowingly, or fix the relief problem. The leak isn't the overtime itself; it's not knowing it happened until payroll closes.

When we first reconciled actuals against invoices across our own book at Ranger Guard, the single biggest category — hours worked but never invoiced — was large enough to fund a supervisor's salary. Money we had already earned and simply never billed.

Where Do Hours Worked but Never Invoiced Hide?

The scenario: A client in Corpus Christi calls Friday afternoon: "Can you add a second officer this weekend for an event?" Your ops manager says yes, staffs it, and moves on. Nobody creates the billing line. Three weeks later the invoice reflects the standing contract, and the extra 24 hours of coverage — call it $700+ at typical commercial rates — evaporates.

On-demand coverage, special events, escort requests, and verbal scope additions are the most common form of this leak, because they're born outside the schedule.

How proof closes it: When every worked hour requires a clock-in tied to a position, there's no such thing as an invisible shift. The billing reconciliation becomes mechanical: every clock-in either maps to an invoice line or throws an exception. Exceptions get answered weekly, not discovered at renewal.

How Many Billing Disputes Do You Concede for Lack of Proof?

The scenario: A property manager disputes 16 hours from last month's invoice: "My tenants say nobody was patrolling the north lot on the 12th." Your officer was there — but your evidence is a paper log the client doesn't trust. The invoice is $18,000; the disputed portion is $450. You credit it to protect the relationship. Do that monthly across 20 accounts and you've conceded a full-time guard's worth of annual revenue for work that was actually performed.

Conceding disputes you could win isn't diplomacy — it trains clients that disputing works.

How proof closes it: GPS clock-ins, timestamped checkpoint scans, and delivered daily activity reports turn a dispute from a negotiation into a lookup. You respond with a packet, not an apology. We covered the full playbook in how to defend a security guard invoice dispute — the short version is that the side with timestamps wins.

What Are the Hidden Margin Leaks in a Guard Business Contract Setup?

The scenario: A post gets added mid-contract — a temporary construction gate that becomes permanent. It was staffed under a verbal "same rate as the main gate," but the main gate's rate was negotiated in 2023 and the annual escalator was never applied to the new position. The post runs 168 hours a week at a stale rate. Even a $1.50/hr gap on a 24/7 post is roughly $13,000 a year, on one position.

Positions running without an active, current rate — or without any rate attached at all — are the most structural leak on this list, because they compound silently for the life of the contract.

How ops data closes it: A rate audit is only possible if positions, rates, and effective dates live in one system. When every scheduled position must carry an active bill rate, a stale or missing rate becomes a visible exception instead of an archaeology project. Note that per-location licensing (TrackTik's runs roughly $78–85/mo per location, per Capterra reviews as of mid-2026) can discourage tracking small posts as distinct positions — exactly where rates go stale.

How Much Do Supervisor Admin Hours Chasing Paper Really Cost?

The scenario: Your Las Vegas field supervisor spends Monday mornings collecting paper DARs from six sites, deciphering handwriting, retyping the usable ones for clients, and calling guards about the missing ones. That's four hours a week of your most expensive field labor doing data entry. Across four supervisors, it's roughly 800 hours a year — not guarding, not selling, not training.

This one leaks cost rather than revenue, but it lands on the same margin line — and retyped reports arrive late and thin, which feeds the next leak.

How proof closes it: Mobile reporting with templates (we use a DAR template studio internally) means reports are complete at shift end, AI-polished for grammar, and emailed to clients automatically with a delivery log. Supervisors go back to supervising. OSHA-reportable incidents and use-of-force reports also get cleaner, faster documentation — which matters when Texas DPS or a client's counsel comes asking.

Why Does Weak Reporting Cause Contract Churn — and What Does That Churn Cost?

The scenario: A solid account quietly goes out to bid. When you ask why, the answer is some version of "we never really knew what we were paying for." A competitor walked in with a sample client report and a portal login, and your incumbency advantage evaporated.

Churn is the largest leak on this list. Replacing a $250,000/yr account means sales cost, onboarding cost, and typically a margin concession to win the replacement. Retention is a reporting problem more often than a service problem: guards can perform well every night and still lose the contract if the client never sees it.

How proof closes it: Automatic report delivery, a client portal, and patrol verification the client can independently check convert your service from invisible to documented. The renewal conversation changes from "trust us" to "here's the log."

The One-Week Leak Audit: What Should You Check First?

Run this against last month's data. Each row is one leak, one test, and what a finding typically looks like.

Most operators who run this find something in rows 1–2 within a day. The fix for all six is the same architecture: capture actuals at the post, reconcile weekly, deliver proof to clients continuously. That's the entire reason we built the SNTNL platform inside a working guard company instead of buying our way around the problem.

If you'd rather see how another operator plugged these leaks than read about it, I'll walk you through our own reconciliation screens — real positions, real variance reports, nothing staged. Book a 30-minute walkthrough and bring last month's invoices; we'll usually find the first leak together on the call.