The Escalation Nobody Answers
Most escalation routes have never been tested at the hour they exist for. Testing one takes four minutes and usually surprises.
Escalation tried at 06:52 on a Tuesday
- Duty manager mobileNo answer
- Duty manager, second attemptNo answer
- Area manager, number from a 2022 listNo answer
- Out-of-hours line, rings to an officeNo answer
- Director, personal number held informallyAccepted
Four of the five routes did not work and the fifth was not an official route at all. The escalation chart on the wall listed the first four.
There is a laminated sheet with a chain of names and numbers on it. It was produced at some point, it has been photocopied, and in most operations no one has rung any of those numbers at six in the morning to see what happens.
The practical issue in “The Escalation Nobody Answers” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring fte meaning, see the complete product overview can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.
When it is finally tested, under pressure, it fails in predictable ways: a number for somebody who left, a mobile switched off overnight, an out-of-hours line that rings into an unstaffed office, a rota of on-call managers that was never updated.
For an independent benchmark relevant to “The Escalation Nobody Answers”, consult the Basecamp Shape Up guide. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.
Testing it
Ring every number on the chart at the hour the chart exists for. Say it is a test, note whether it was answered and how quickly, and move on.
Four minutes per test, done quarterly. In most operations the first test fails on at least half the chain, and every failure is fixable the same week.
This is the single highest-value item in this section and it is almost never done, because testing an escalation route feels like an odd thing to spend a morning on until the morning you need it.
What a working chain has
A first point that is a role on duty at that hour, not a person who might be. In operations that run overnight this is straightforward; in those that do not, it is the hardest part and usually means an on-call rota.
A defined wait before moving to the next step — five minutes is typical — so the person escalating is not deciding how long to hang on while a shift starts.
At least three levels, because two will both be unreachable often enough to matter.
A documented final fallback: what the person on the ground may do if nobody at all answers. Without it the chain ends in nothing, which is the state most charts are actually in.
The on-call rota
If there is one, it needs the same maintenance as everything else here: who is on, with a number that works, published where the person escalating can see it at six in the morning, and covering every date including the awkward ones.
The standard failure is the handover between two on-call periods, where the chart says one person and the reality is another. The second is the holiday period, where the rota was built in November and the person named is abroad.
Making it answerable
Somebody woken at six forty needs to be able to answer in one minute. That means they need to know what they are being asked — authorise spend, authorise running short, or make a judgement about safety — and to have the information to answer it.
A standard opening is worth agreeing: the shift, the shortfall against requirement, what has been tried, and the specific decision being requested. Thirty seconds, and it converts a vague distress call into a question with an answer.
What happens when it is not answered
This is the clause that gets used most and the one most charts omit entirely.
It should say: after the chain has been exhausted, the person on the ground may act within a stated authority, must record what they did, and must report it by a stated time. Anything else leaves them choosing between inaction and unauthorised action while a shift starts.
Recording the failures
Every time an escalation does not reach somebody, write down which step failed. Over a quarter this produces a short list of the broken links, which is a far more useful thing than a general complaint that the route does not work.
It is also the evidence for fixing it, because a specific finding — the out-of-hours line has not been answered in any of the eleven attempts this quarter — is actionable in a way that an impression never is.
What the chart should look like
Most escalation charts are organisational diagrams with boxes and reporting lines. At six forty nobody needs a reporting line; they need a sequence.
Rewrite it as a numbered list: ring this, wait five minutes, then this, then this, then if none of them answer do the following. Put the date it was last tested at the bottom. It fits on a card, it can be read by somebody who has never used it, and the test date tells the reader whether to trust it.