The day guard is still waiting
The day guard at a logistics yard finishes at 7pm. At 7.20 he rings the control room: his relief has not turned up and he needs to leave to pick up his children. The control room had not noticed. They ring the night guard, who says he thought he was on tomorrow. Now the duty manager has to find cover, which means the ringing round starts, and the day guard is stuck or the site is left uncovered for a while.
On a worse night, the day guard leaves at 7pm assuming his relief is running late, and the site is empty until the client's manager arrives at 7am and finds nobody on the gate.
Why no-shows are noticed late
Booking on is the moment a shift is confirmed as covered, and many guarding companies rely on the guard calling in or texting. Noticing that a call has not come requires the controller to hold a mental list of everyone due to start at 7pm across every site, while also handling alarms and welfare calls. At a shift change, that is when the control room is busiest.
- Booking on is a call or a text, with no automatic check.
- The control room has no live list of who is due to start now.
- Rota changes made during the day may not reach the control room.
- The outgoing guard is not told whether relief is on the way.
- Late arrivals and no-shows are recorded inconsistently.
What late detection costs
An uncovered site is the core failure of a guarding contract. Even when it is short, clients take it very seriously, and often the first they hear of it is from their own staff. Outgoing guards are forced into extended shifts, which is a welfare issue and a working time issue, both for your advisers. And finding cover at 7.20pm is harder than finding it at 6pm, when a guard who is not answering their phone could have been spotted.
Booking-on checks with early warnings
- The rota tells the system who is due at each site and when. Changes made during the day update it straight away.
- Guards book on by app, with location confirmation at the site if your policy allows, or by calling an automated line, or on a site device.
- Before the shift, a confirmation request can go to the guard at a time you choose, such as two hours before, asking them to confirm they are on their way. No reply is an early warning.
- If a guard has not booked on within the grace period you set, the control room gets an alert with the site, the guard's contact details and the outgoing guard's details.
- The outgoing guard gets a message asking them to wait while relief is confirmed, under your procedure, and the controller can see who is waiting.
- The controller calls the late guard and, if needed, starts the cover request from the same screen.
- Late bookings and no-shows are recorded with reasons, so repeat patterns are visible.
| Time | What happens | Who sees it |
|---|---|---|
| Two hours before | Confirmation request to the guard | Guard; no reply flags to control room |
| Shift start | Guard books on at site | Control room board shows covered |
| Grace period passed | Alert with contact details | Controller |
| No contact | Cover request started | Duty manager |
The same evening with booking-on checks
At 5pm the night guard gets a confirmation request and replies that he thought he was off. The control room sees the warning at once and starts a cover request two hours before the shift, with plenty of eligible guards still available. By 6pm cover is confirmed. At 7pm the relief books on at the yard and the day guard leaves on time. The rota confusion is logged, and the scheduler checks how the guard's shift was communicated.
Signs no-shows are catching you out
- You hear about no-shows from outgoing guards or clients.
- Booking on is a phone call with no automatic check.
- Controllers have no live list of who is due now.
- Guards are sometimes confused about their shifts.
- Outgoing guards regularly stay late waiting for relief.