A lapsed licence is not paperwork, it is an illegal deployment
Most compliance features in scheduling software are about hours. In guarding the binding constraint is a licence, and the failure is categorical rather than gradual: an officer whose licence expired yesterday is not slightly less deployable today, they are unlawful to place on a site. The client does not get a partial breach and neither do you.
That makes expiry a scheduling rule rather than a filing task. A certificate in a folder is a record; the same certificate attached to a position is a constraint, and only the second one prevents anything. Checking the date rather than the existence is the whole difference, because nobody in this industry fails an audit for never having held a licence. They fail because one ran out in week three of a twelve-week contract.
That is why the check belongs at the point of assignment rather than in a monthly audit. An audit tells you that somebody worked eleven shifts they were not licensed for, which is a disclosure, not a control. A check that runs when the shift is created stops the eleventh shift and the first one, and it does it without anybody needing to remember the date.
Static sites, mobile patrols, and the rota that holds both
A static site wants the same officer at the same gate for continuity, and a mobile patrol wants whoever is nearest and qualified. Those two logics fight each other in one week, and most rotas resolve the fight by having a person hold it in their head.
Treating a site as a location with its own positions and its own cover requirement lets both live in the same grid without either being an exception. The static contract asks for the officer it wants; the patrol asks for a qualification and a window. The grid then shows which is short rather than which the planner remembered to check.
The two also fail differently when somebody is short. A static site with nobody on it is a contract breach that a client will notice within the hour. A patrol route running with one officer instead of two is a quieter failure that nobody outside the operation sees until something happens. Coverage set per site and per patrol keeps both visible rather than letting the loud one absorb all the attention.
Why the three in the morning gap is the one that gets missed
Daytime gaps get found because people are awake to notice them. The night gap is discovered by whoever should have been relieved and was not, and by then the options are one exhausted officer on a double or an empty site.
The only useful fix is finding it earlier, while it is still an ordinary scheduling decision. Cover requirements make an uncovered night read as short on the day the week is built, and the ranking that fills it checks rest gaps as well as licences, so the answer is not simply the person who has already worked six nights.
Nobody chooses this gap. It appears because a shift ends at three, the next starts at three, and one of them moved by half an hour for a good reason weeks ago. Reading cover as a continuous requirement rather than as a set of shifts that look adjacent on a grid is what surfaces it, and it surfaces it while the week is being planned rather than at three in the morning.
Hours across sites, when the contract is priced by the hour
An officer working three contracts in a week is one person accumulating one set of hours, but most systems count per site because that is how the billing is organised. The result understates overtime for exactly the staff who move around most, which in guarding is most of them.
Totalling across locations changes what the schedule can tell you before you publish it. On a contract priced by the hour, an overtime premium discovered at payroll is margin already spent; the same premium seen on a Wednesday is a shift you can still move.
There is a billing consequence as well as a payroll one. When a shift is attached to the site it was worked at, the hours a client is invoiced for and the hours a person is paid for come from the same record. Where those live in separate places they drift, and the drift is discovered during a contract review, which is the least convenient possible moment.
What a control room needs from a handover
Guarding runs on things that happened rather than things that were completed: a gate that would not lock, a vehicle seen twice, a contractor who arrived without notice. None of it belongs on a checklist and all of it matters to whoever comes on next.
A note attached to the shift survives the shift. It is still there when the client asks about Tuesday, it carries who wrote it and when, and it reaches the incoming officer rather than a group chat that half the team has muted. In an industry where the record is sometimes the product, that is not administrative overhead.
The test of a handover note is whether the incoming shift can act on it without a phone call. That means the specifics: which door was found unsecured and whether it was resolved, which vehicle was on site, what the client asked for at two in the morning. Attaching it to the shift rather than to a book on a desk means it is still there in six weeks when somebody asks.