Priority, SLAs and escalation: what do I fix first?
▶ Start the interactive lesson
10:02. Three tickets land at once. The CEO's spare monitor flickers. The card payment system is down at all 12 depots. One warehouse scanner won't charge. The CEO's PA rings asking for an update. Priya points at the queue: "Seniority isn't priority. Work it out the same way every time, and you'll…
Two questions decide priority
How many people or how much of the business is affected? One person, a team, or the whole company? Card payments at every depot is huge; one flickering spare monitor is tiny.
Put them in a grid
Combine the two answers and you get a priority, usually P1 (drop everything) to P4 (when you can). Burrow's grid:
Promises with a clock: SLAs
Each priority comes with promised times: how quickly someone responds (picks it up and contacts the user) and how quickly it's resolved. These promises are written in a service level agreement.
Escalation: passing it up or across
1st line is the service desk. 2nd line is deeper desktop, server or network support. 3rd line is the specialists, architects or the vendor.
Key points
- Priority = impact × urgency. Impact: how many people or how much of the business. Urgency: how fast it hurts.
- Each priority has an SLA with a response time and a resolution time. Missing one is a breach.
- Functional escalation passes it to more skill (1st → 2nd → 3rd line). Hierarchical escalation tells managers.
- A P1 usually becomes a major incident: one person coordinating, regular updates, everyone else working the fix.
Words you'll learn
Impact · Urgency · Priority (P1–P4) · SLA (service level agreement) · SLA breach · Functional escalation · Hierarchical escalation · Major incident