An escalation path is the written route a problem follows when the person who found it cannot resolve it within their own authority. A usable one names who to go to, for what, and within what time. The harder and more valuable half is the decision limits underneath it, because most escalations exist only because nobody wrote down what the first person was allowed to do.
In more detail
Teams tend to build the path and skip the limits, which produces a queue rather than a resolution. Every problem travels upward because nobody at the bottom knows what they may decide.
Written limits invert this. Below a value floor, act. Above it, escalate, and here is to whom. Most problems then resolve where they were found, and the ones that arrive upward are genuinely worth the attention.
The limits are a kindness as much as a control. Being told exactly where your authority ends removes the anxiety of guessing, which is what makes people escalate things that did not need escalating.
The five parts, and how often each is actually written
| Written down | Effect | Commonly present? |
|---|---|---|
| Who to go to | The problem has a destination | Usually |
| For what kind of problem | It reaches the right person first time | Sometimes |
| Within what time | It can be prioritised against other work | Rarely |
| Who covers them | A week off does not stall everything | Rarely |
| What you may decide alone | Most problems never escalate at all | Almost never |
Where people get it wrong
- Writing the route without the limits. This produces a queue to a bottleneck.
- Setting limits so low they are bypassed. A bypassed rule is worse than none, because it creates a false impression of control.
- Naming a role rather than a person without saying who covers when they are away.
- No time bound. An escalation with no expected response time sits.
Why the last row matters most
The bottom row is the one nearly every store omits, and it is the one that determines the volume of everything above it. Without written limits, every problem travels upward, and the path becomes a queue to whoever is most senior.
Written limits also remove a hidden cost that rarely gets named: the time people spend deciding whether they are allowed to decide. Telling someone exactly where their authority ends is faster for them and cheaper for you.
Common questions
What should an escalation path contain?
Who to go to, for what kind of problem, within what time, and who covers them when they are unavailable. Underneath it, the decision limits that determine what does not need escalating at all.
Why do escalations pile up?
Usually because nobody wrote down what the first person was allowed to decide. Without limits, everything travels upward and the path becomes a queue.
What makes a good escalation message?
What happened, what has already been tried, what decision is needed, and by when. A forwarded email fails because the recipient has to reconstruct the situation before they can decide anything.