Security guard scheduling software fills each post with an officer who holds the licensing class, site clearance, and client training that post requires, and who is billed at the correct tier. The question it has to answer is eligibility, not availability: which guards can take an open post right now without breaking a credential rule, a coverage minimum, or an overtime threshold.
Every post covered by a guard the contract allows.
Licensing classes, site clearances, post minimums, lone-worker rules, and a bill rate that has to match the tier who worked. Checked while the shift is built, not after payroll finds it.
The replacement has to be qualified before the shift publishes.
A guard calls off at nine at night and the post cannot go dark. Whoever picks it up has to be someone that post is allowed to have.
An availability list will hand you a name. It will not tell you whether that name holds the armed certification the post requires, whether their site clearance for that client is current, or whether taking the shift pushes them past a threshold that costs you the margin on the contract.
WorkAxle answers that before the offer goes out. Guard qualifications are matched to site requirements, so an open-shift offer reaches the officers who can actually take it. Moving a guard to cover another site automatically checks certifications for that site, client, and role.
Licenses and certifications are tracked in effective-dated fields. Expiry triggers automatic reclassification, and the rule engine flags the conflict at assignment time. Renewal alerts fire before the expiry date, with time left to act.
It warns rather than blocks. A supervisor who needs to make a judgment call can still make it, with the rule shown and the override logged. The record of who overrode what, and when, is the thing a client audit asks for later.
A post minimum is a contract term, not a preference.
Minimum coverage, armed and unarmed requirements, qualifications, and time-of-day rules are checked at scheduling time. A breach surfaces before the shift publishes, which is the only point where the scheduler can still act on it.
Single-guard assignments are flagged for check-in protocols, solo-work certifications, and fatigue management rules. New guards become assignable only once every required credential is verified, which closes the compliance gap that otherwise opens on day one.
Turnover is what keeps reopening these gaps. In an operation that churns, classification is a decision made constantly, for new officers, often on a first shift.
The billing tier is decided when the shift is assigned.
Qualifications are tied to billing rates, so every shift is assigned at the correct guard tier. Hours are captured and validated per site, per client, per billing tier, with exceptions flagged at the punch. Time worked and time billed match, and invoices reconcile to contracts.
Hours also accumulate centrally across every site. Overtime thresholds apply to a guard's total assignments, regardless of which site each individual shift sits on.
That threshold is where the margin goes. The bill rate in contract guarding is locked the day the deal is signed, so the premium you pay to keep a post covered is usually overtime the client contract will not let you bill. Closing the coverage gap at the standard rate is the lever, not tightening approval after the hour is already logged.
When the jurisdiction sets the rate.
Guard pay rules are not uniform across a footprint. A wage schedule can classify officers by certification rather than by tenure, which means the rate follows the credential and changes the moment the credential does. Rates can also step on dates fixed in advance that do not line up with a calendar year.
Two things follow for the system. Configuration has to be effective-dated, so a rate can be staged with a start date and activate without touching schedules already published. And labor rules have to sit in a no-code rule engine a customer's own team configures per site, so one location carries its local classifications while a site under no comparable rule inherits nothing it should not.
Records are the other half. Every assignment, credential status, and override is logged with a timestamp, which turns a six-month client audit into a matter of minutes. The New York City guard wage law, tier by tier works through one jurisdiction in full, including what its classifications and its retention rule ask of a scheduling system.
Wage and hour rules vary by jurisdiction and change over time. Verify against the issuing agency for your own sites. Nothing here is legal advice.
Two operations that already run it.
A national airport-operations security provider, Canada
Multiple union collective agreements, 8,000+ unionized screening agents, and a fixed contract start date with no soft launch. The provider went live across major Canadian airports in eight weeks, against an industry norm of twelve to twenty-four months. It reported 100% ROI within two months of go-live, a 22% reduction in workforce-management administration costs, and 14% fewer error corrections.
A global ops-tech security operator, Australia
A company that builds its own software chose to buy for this one. It folded two legacy systems into one configurable rule engine, with three lanes of Australian overtime and registered-contractor time types running by configuration rather than custom code.
The vertical in full, including lone-worker compliance and client audit readiness, is on the security and guarding operations page.
Frequently asked questions about security guard scheduling software
What is security guard scheduling software?
Security guard scheduling software fills each post with an officer who holds the licensing class, site clearance, and client-specific training that post requires, and who is billed at the correct tier. It checks qualifications against the site, client, and role before an assignment publishes, tracks licenses and certifications in effective-dated fields, and logs every assignment, credential status, and override for audit.
How is it different from a general shift scheduling tool?
A general shift tool answers who is available. A guarding operation needs to know who is eligible, which is a different question. Eligibility depends on licensing class, armed or unarmed status, site clearance, lone-worker certification, the overtime threshold a guard is approaching across every site, and the collective agreement in force at that site. Those checks run at assignment time rather than in a reconciliation after payroll.
Can it stop an unlicensed guard from being assigned to a post?
It flags the conflict before the assignment publishes, and expiry triggers automatic reclassification so the guard drops out of the eligible list. A supervisor who needs to make a judgment call can still override, with the rule shown and the override logged. The record of who overrode what, and when, is what a client audit later asks for.
Does it handle union contracts and collective agreements?
Yes. Labor rules sit in a no-code rule engine that a customer's own team configures per site, so several collective agreements can run side by side in one engine. A national airport-operations security provider moved multiple union contracts into that engine and went live across major Canadian airports in eight weeks.
How long does a rollout across multiple sites take?
A national airport-operations security provider was fully operational across major airports in eight weeks, against an industry norm of twelve to twenty-four months for a deployment of that complexity, and reported 100% ROI within two months of go-live. WorkAxle implementations run 4 to 5 times faster than legacy systems, which quote 18 to 24 months.
Bring the post your current system cannot fill cleanly.
See it built for guarding.
Licensing classes, post coverage minimums, lone-worker protocols, and the audit report a client asks for six months later.
See how one operation did it.
Multiple union contracts, 8,000+ screening agents, live across major Canadian airports in eight weeks.
Bring your hardest coverage scenario.
Your site contracts, your credential requirements, your multi-location complexity. We will walk it live.