On this page
When a field employee does not come back on time, the first ten minutes decide a lot. Somebody has to notice. Somebody has to call. And if that person is in a meeting, somebody else has to be next.
That is what an escalation matrix is for. This guide gives you a template you can copy, explains each choice in it, and lists the mistakes that make most matrices fail in practice.
What an escalation matrix is
An escalation matrix is a short table: who is told, in what order, and after how long. In IT, it decides who gets woken up when a server goes down. For people working in the field, it decides who is alerted when an employee:
- misses the time they said they would be back (a missed check-in), or
- raises an SOS.
It also decides when the alerting stops: when one person says “I have this”.
A template you can copy
This is a sensible starting point for a company with field staff such as sales, procurement, auditors, surveyors or service technicians.
| Level | Who | When, after the employee is overdue | What they do |
|---|---|---|---|
| 1 | Reporting manager | At once | Call the employee. If they answer, close it. |
| 2 | Manager’s manager (head of department) | After 5 minutes | Call the employee and the manager. |
| 3 | Safety Desk | After 10 minutes | Take ownership, call the employee, check the last location. |
| 4 | Admins (HR or operations heads) | After 20 minutes | Decide on escalation outside the company. |
| 5 | A named person (for example, the site head nearest the employee) | After 30 minutes | Go or send someone to the last known location. |
For an SOS, skip the ladder. The Safety Desk is alerted the moment an SOS is raised, along with whoever is closest. An SOS is not a late employee; it is someone asking for help now.
For high-risk visits, such as night audits, remote sites or a client the employee has not visited before, halve the gaps.
Why each choice matters
The manager goes first, but never alone
The reporting manager knows the employee and the visit, so they are usually the fastest to find out what is going on. But managers are in meetings, on leave or asleep. A matrix that ends with the manager is a single point of failure. That is why level 2 exists.
Minutes, not hours
A missed check-in usually means a phone battery died or a meeting ran long. But the rare real emergency is exactly the one where an hour of nobody noticing matters. Short gaps cost very little: most alerts are closed at level 1 within a couple of minutes.
One owner, visible to all
The most common failure in a real incident is not that nobody responds. It is that five people respond and none of them owns it. Everyone assumes someone else has called the police. The fix is one rule: the first person to take ownership is recorded, everyone else on the ladder sees their name, and the ladder stops.
The employee is never on their own ladder
It sounds obvious, but matrices built from an org chart sometimes include the employee or their own phone number. They cannot be both the problem and the responder.
Record what happened
Every alert should end with an outcome: safe, false alarm, helped by a colleague, police involved, taken to hospital. These records show where your matrix is slow, which sites produce the most alerts, and whether people are actually using check-ins. They are also what an auditor or a client will ask for.
Mistakes that make matrices fail
- It lives in a PDF. A matrix that relies on someone noticing a late employee and then looking up a document will not run at 9 pm on a Saturday.
- A group chat as level 1. Fifty people see a message, and everyone assumes someone else will act. Name people, not groups.
- Phone numbers that changed. Managers leave, desks change shifts. Check the matrix every month, or pull it from your HR system.
- No night cover. If your field staff work late, your Safety Desk needs someone on shift late too, or alerts must go to a phone that is answered.
- Never tested. Run a drill: an employee raises a test alert at an agreed time, and you time how long each level takes. You will find the gaps in one afternoon.
A one-page checklist
- Write down three to five levels, with a named person or role and a time for each.
- Send SOS alerts straight to the Safety Desk, not through the ladder.
- Use shorter gaps for high-risk visits.
- Make sure the first person to take ownership is visible to everyone else.
- Record an outcome for every alert.
- Review phone numbers and names every month.
- Run one drill per team, then fix what was slow.
How ORBII Teams runs this for you
ORBII Teams turns this table into something that runs on its own. An employee starts a trip in the ORBII app with a back-by time and can mark it high-risk. If they are late and do not answer, ORBII walks the ladder you set in the console: up to five levels (reporting manager, manager’s manager, Safety Desk, admins, or a named person), each with its own number of minutes. Recipients must belong to your workspace, and the employee is never on their own ladder.
The Safety Desk gets a phone alert, a browser alert and a full-screen alarm with the employee’s last location. The first person who presses Take ownership is shown to everyone, and the ladder stops. When the alert is closed, the desk records the outcome, and it stays in the travel history and the audit log.
Read more about ORBII for field and lone workers, or the HR guide to lone worker safety.
Frequently asked questions
What is an escalation matrix?
A short table that says who is told about a problem, in what order, and after how long. For field staff safety, it decides who is alerted when an employee misses a check-in or raises an SOS, and who is next if the first person does not respond.
How many levels should an emergency escalation matrix have?
Three to five. Fewer than three leaves you depending on one person who may be asleep or in a meeting. More than five is slow, and nobody remembers it. A common order is the employee's reporting manager, the manager's manager or head of department, the Safety Desk, then senior admins.
How quickly should an emergency be escalated?
For a missed check-in, a few minutes per level is typical: for example, the manager at once, the head of department after 5 minutes, the Safety Desk after 10. For an SOS, alert the Safety Desk immediately rather than waiting for the ladder. High-risk visits should use shorter gaps.
When does an escalation stop?
As soon as one named person takes ownership of the alert. Everyone else on the ladder should see who has it, so three people do not call the same employee while nobody calls the police.
Should the escalation matrix be automated?
Yes. A matrix on paper depends on someone noticing that an employee is late and remembering who to call. Software can notice the missed check-in, alert each level on time, and keep a record of who responded and when.