Escalation Workflows: What Should Happen When an Officer Doesn't Confirm
An officer hasn't confirmed their shift. What happens next? In many firms the answer is "whoever notices rings round", which works until the control room is busy, or the person who noticed goes off shift.
An escalation workflow replaces that with a written plan: what happens at each stage, how long you wait, and who takes over. This guide sets out how to design one for a security or facilities firm, and which parts can run automatically.
What escalation means here
Escalation is the process of passing an unresolved problem to the next level, at a set time, until someone with authority deals with it. For unconfirmed shifts, that usually means moving from automated nudges, to a phone call, to a person who can decide.
The principle is simple: automation chases, people decide.
The building blocks
A workable escalation workflow has a few parts you define up front:
Shift states
Every shift has a clear status at any moment, such as:
- Awaiting confirmation: the request has gone out
- Confirmed: the officer has accepted
- Declined: the officer has said they can't work it
- No response: the deadline has passed with nothing back
- Escalated: a person has been alerted
- Resolved: covered, reallocated or closed
Clear states mean the control room can see where everything stands, rather than piecing it together from messages.
Timings
You decide how long to wait at each step. For example, an illustrative ladder might be:
| Stage | What happens | Who acts |
|---|---|---|
| 1 | Shift details and confirmation request sent | System |
| 2 | Reminder if no reply by a set time | System |
| 3 | Automated phone call asking for confirmation | System |
| 4 | Alert to the control room that the shift is unconfirmed | System tells a person |
| 5 | Control room decides: contact the officer another way, offer to a standby officer, or inform the client | Person |
The times are yours to set, depending on how much notice you give, how risky the site is and how your people work. Don't copy anyone else's numbers. The right ones depend on your firm.
Who gets told
Define who receives each alert and who has authority to decide. That might be the duty controller by default, with a manager alerted if the shift is close and still uncovered. Ambiguity here means everyone assumes someone else is handling it.
What counts as confirmed
Be specific. Does a thumbs-up emoji count? A reply of "ok"? A key press on a phone call? Decide what valid confirmation looks like, so there's no argument later.
What automation should and shouldn't do
Good candidates for automation:
- Sending requests and reminders on schedule
- Placing the follow-up call
- Updating the status as replies arrive
- Alerting the right person at the right time
- Recording what happened and when
Leave to people:
- Deciding whether to reallocate or offer a shift elsewhere
- Judging unusual situations, such as a reported illness or an unreachable officer
- Speaking to the client
- Anything involving discipline or reliability judgements
An escalation workflow that makes decisions about people on its own is a risk to your officers and to you. Keep a person in the loop for anything with consequences.
Handle the edge cases
Real life isn't tidy. Plan for these:
- Wrong or changed number: the message fails, or reaches someone else
- Officer replies late, after the shift has been given to someone else
- Officer declines at the last minute, with no time for the usual steps
- Delivery failures, where the message was sent but never arrived
- Out-of-hours alerts: who's reachable overnight?
- Repeated escalations for the same person: a human conversation, not an automatic penalty
If your workflow doesn't cover these, the control room finds out the hard way.
Keep a record
Every step should leave a time-stamped trace: when the request went out, when reminders and calls were made, what the officer replied, who was alerted and what was decided. It helps in three ways: your control room sees the full history at a glance, you can review what happened afterwards, and you can answer a client who asks.
Because this involves staff personal data, make sure it meets UK GDPR: tell staff how their details are used, limit access to those who need it, and keep records only as long as you need them. See UK GDPR and AI automation.
Test it before you rely on it
Walk through each route with test messages and calls: confirm, decline, silence, wrong number, delivery failure. An escalation process that fails quietly is worse than none, because everyone assumes it's working.
Where to go next
For a walk-through of the confirmation sequence this builds on, see how security firms can automate shift confirmations. For the wider problem of gaps and cover, see cutting shift no-shows and last-minute rota gaps.
Want to design one for your firm?
Every firm's rota, policies and risk tolerance differ, so we start with a conversation about how you work today.
SGI Solutions is a trading name of Shabbir Group of Industries Ltd · Registered in England & Wales · Company No. 17320561.