How to Track Guard Hours Across Multiple Client Sites
A guard company runs dozens of posts for different clients, and guards rotate and cover across them. When the hours do not stay tied to the right client, payroll and billing both break. Here is how to keep them straight.
The Hour You Pay for and the Hour You Bill Stop Matching
Every guard hour has to do two jobs at once. It pays a guard, and it bills a client — and those two numbers are supposed to come from the same shift. The moment they drift apart, you’re either eating cost you could have billed or sending an invoice you can’t defend.
A guard company is a multi-site operation by definition. You might run forty posts across fifteen clients, with guards who rotate between them, pick up open shifts on short notice, and sometimes cover two different clients’ sites in a single night. Record that by memory or on a stack of per-site paper sheets and the billing side breaks constantly. A guard covers an emergency shift at Client B’s warehouse, but it gets written to Client A because that’s his usual post. A mid-week rotation gets logged a day off. Now Client A is overbilled, Client B is underbilled, and payroll matches neither. The hour was honestly worked and honestly paid. It just landed on the wrong customer.
This is the same multi-site tax that hits contractors, but with an extra edge. A contractor’s bad cost code only distorts an internal number. Yours goes out on an invoice. A client who catches an overbill you can’t defend doesn’t just dispute that line — they start auditing every hour you’ve ever sent them, and the contract review meeting gets a lot less friendly.
Where the Billed Hour and the Paid Hour Split Apart
Short-notice coverage. A guard calls out, someone covers his post, and the swap happens faster than the paperwork. On paper, that covered shift routinely bills to the wrong client, because the record was built around the schedule, not what actually happened. And the client whose guard never showed still gets the full invoice.
Two clients in one night. A guard does part of a shift at one site and part at another. Splitting that cleanly by memory days later is guesswork, and the guess usually dumps the whole night on one client. So one invoice runs long and the other comes up short.
Rotations. Guards who move across posts on a rotating pattern are a billing headache when each site keeps its own sheet. Assembling one client’s billable week means collecting and cross-checking several logs, and any hour you miss is revenue you never charge for.
Per-location pricing. Some time-tracking tools bill you for every site you add. For a business whose growth means adding client sites, that’s a fee on your own success. It nudges companies toward sloppy shortcuts like lumping nearby posts together to save money — which is exactly how billable hours go missing.
Letting the Post Stamp Each Billable Hour
The fix is to let the post itself stamp the hours, instead of reconstructing them later.
A geofence per post. Set a boundary around each client site once. A guard who clocks in there has those hours attributed to that client automatically — no choosing the right client from a dropdown of forty at 10 PM. Cover a second site later, clock in there, and the new block lands on the second client on its own. Crossing onto the post does the coding, so last-minute coverage gets attributed correctly even when the schedule said otherwise.
Clean splits when a guard covers two clients. Clock out of the first post, clock in at the second, and the night divides into two blocks with real timestamps, each tied to its own client. The exact moment that wrecks paper logs is the moment geofenced clock-ins handle best.
Offline capture at low-signal posts. Plenty of posts sit in parking structures, remote yards, or dead zones. A time clock built for the field records the punch and its location offline and syncs when signal returns, so a no-service post still produces correctly attributed hours instead of a hole.
One source for both payroll and billing. Because every punch is tied to a guard and a post, the same records total by guard for payroll and by client for billing. The billed-vs-paid spread you used to find at month-end stops existing, because both numbers trace back to the same verified events. That’s the foundation for billing clients accurately.
Flat pricing, unlimited posts. A per-seat time clock with no per-location fee means forty posts cost the same as four. Win a contract, add the site, draw the fence. No new line item, no incentive to cut corners on how you record it.
Invoices a Client Cannot Argue With
When the post attributes the hours, every invoice line traces back to a timestamped clock event at that client’s site. So a billing dispute ends with a record, not a he-said argument.
If your guards cover more posts and clients than you can keep straight on paper, see how a time clock built for security teams ties every hour to the right post automatically, or put ShiftFlow on your contracts and let the geofences do the attribution.
Frequently Asked Questions
How do I track guard hours across many client sites accurately?
Use a time clock that ties each clock-in to a specific post through GPS and a geofence, so hours attribute to the right client automatically. A guard who covers two posts in a night produces two clean blocks of time, each tied to its site, instead of one lump someone has to split by memory for payroll and billing.
Why do guard hours end up on the wrong client?
Guards rotate between posts, cover open shifts at short notice, and sometimes work two clients in one night. Record the post by memory or on a per-site paper sheet, and last-minute coverage and rotations get mis-assigned — so one client is overbilled, another underbilled, and payroll matches neither. The hours are real, they just land on the wrong account.
Should I pay per location for guard time tracking software?
No. Running many client sites is the core of a guard company, not an add-on, so per-location pricing taxes your basic model and grows every time you win a contract. A flat per-seat time clock lets you add unlimited posts at no extra cost, so the price scales with guards, not with the number of sites you protect.
Can one time clock handle both payroll and client billing hours?
Yes, when every punch is tied to a guard and a post. The same records total by guard for payroll and by client site for billing, from one source of truth. You stop keeping two reconciliations that never quite agree, because the hours you pay and the hours you bill come from the same verified clock events.
