Escalation fails when it depends on someone deciding to escalate. Time-based triggers remove the judgement call, so a ticket moves because the clock says so rather than because an agent felt stuck enough to ask.
Separate functional from hierarchical escalation. Functional escalation moves a ticket to more specialist skill. Hierarchical escalation informs management because the impact is commercial or reputational. Both can be needed at once, and conflating them means one of them does not happen.
Trigger on time, not on judgement. Agents under-escalate because escalating feels like admitting defeat. A rule that a P1 moves to tier 2 after fifteen minutes with no progress removes the social cost entirely.
Test the out-of-hours path twice a year. Out-of-hours escalation paths rot silently: people leave, numbers change, rotas are not updated. Call the numbers during a quiet period and record who actually answered.
Here's a preview. Unlock the free download to get all 4 sections (3 more below).
Time starts from ticket creation for the first tier, then from each escalation.
| Priority | Starts at | Escalate to tier 2 after | Escalate to tier 3 after | Escalate to vendor after | Who is notified |
|---|---|---|---|---|---|
| P1 | Tier 2 | Immediate | 30 min | 1 hour | Service desk lead, on-call manager |
| P2 | Tier 1 | 1 hour | 4 hours | 1 business day | Service desk lead |
More free templates IT teams use alongside this one.
A priority matrix only earns its place if two different agents classify the same ticket the same way. This one defines impact and urgency as countable things (how many people, and whether work has already stopped), so the grid produces one answer instead of a conversation.
Most severity matrices fail in the one moment they matter: at 02:00, when a tired engineer has to decide whether to wake anyone. This one is written so the level is readable off customer impact alone: no judgement call about root cause, no guessing how bad it might get.
Most internal IT SLAs are copied from a managed-service contract and then quietly abandoned, because they promise things the team was never staffed to deliver. This one starts from what you measurably do today and makes the exclusions explicit, so the document survives contact with a bad month.
Functional escalation moves a ticket to someone with more specialist skill. Hierarchical escalation informs management because of commercial or reputational impact. A major incident often needs both simultaneously.
Because agents consistently under-escalate: asking for help feels like admitting defeat. A rule that a ticket escalates after a defined period with no progress removes the social cost and makes escalation routine rather than exceptional.
At least twice a year for out-of-hours paths. People leave, phone numbers change, and rotas go stale. Call the numbers during a quiet period and record who actually answered rather than who should have.
