An incident priority matrix turns a judgment call into a repeatable decision. It scores every incident on two axes — urgency and impact — and reads a priority level off the grid, so a P1 means the same thing no matter who logged the ticket.
Without a matrix, priority is decided by volume and volume of voice. The executive’s broken printer becomes a P1, while a failing backup that nobody has noticed yet sits unassigned. A matrix fixes that by making the decision about the incident, not the person reporting it.
How the matrix works
The matrix has two inputs. Impact answers the question how much damage is this doing? It is scored from 1 to 3: 1 is one person affected, 2 is a small group or a department, and 3 is the whole organization. A security breach or data loss scores at the top regardless of headcount.
Urgency answers the question how fast does this get worse? A system that is down now and blocking work scores high. A problem with a working workaround scores low, even if it is annoying. A deadline also raises urgency: a report that is due tomorrow matters more today than it did last week.
Priority is the combination of the two, on a fixed grid. Impact 3 and urgency 3 is a P1. Impact 3 with urgency 2, or impact 2 with urgency 3, is a P2. Impact 3 with urgency 1, impact 2 with urgency 2, or impact 1 with urgency 3, is a P3. Impact 2 with urgency 1, or impact 1 with urgency 2, is a P4. Impact 1 with urgency 1 is a P5. The grid never changes, so the same scores always give the same priority — agree what 1, 2, and 3 mean for your team once, then apply them the same way every time.
Worked example
The email server stops working for all 200 staff at 9 a.m. Impact is 3, because the whole organization is affected. Urgency is 3, because nobody can work and the damage grows every minute. The matrix reads P1, and work starts immediately with the on-call team.
Later the same day, one person in finance cannot open a spreadsheet. Impact is 1, because a single user is affected. Urgency is 2, because there is a workaround — the file opens on a colleague’s machine. The matrix reads P4, and the ticket joins the normal queue.
A third case sits in between. The VPN is slow for 40 remote workers, but it still works. Impact is 3, urgency is 2, and the matrix reads P2. It is not a P1, because nobody is fully blocked, but it outranks the spreadsheet because it affects a whole group.
How to use the result
Use the priority to set response and resolution targets. The calculator on this page uses P1: respond in 15 minutes, resolve in 4 hours; P2: respond in 30 minutes, resolve in 8 hours; P3: respond in 1 hour, resolve in 1 day; P4: respond in 4 hours, resolve in 2 days; P5: respond in 8 hours, resolve in 4 days. Your numbers should match what your team can actually deliver.
Review priorities when the facts change. If ten more people report the VPN problem, the impact has grown and the P2 may become a P1. If a workaround is found for the email outage, the urgency drops. A priority set at logging time is a first guess, not a verdict.
Audit the matrix itself every quarter. Look for tickets that were marked P1 but turned out to be minor, and P3s that turned into outages. Both are signs that the definitions need sharpening, or that the team needs a refresher on how to use them.
Note: Priority is not the same as severity. Severity describes the technical damage; priority adds the business context of who is affected and how soon it matters. Two incidents can have the same severity and different priorities.
Once the priority is set, the incident still needs a clear record. The incident report template captures the impact, urgency, and priority alongside the timeline, so the next person to pick up the ticket starts from the facts instead of from scratch.
Frequently asked questions
What is an incident priority matrix?
It is a grid that turns two judgments — how urgent an incident is and how much impact it has — into a single priority level, usually P1 to P5. It stops priority being decided by whoever shouts loudest.
What is the difference between urgency and impact?
Impact is how much damage the incident does: how many people are affected and how badly. Urgency is how quickly that damage grows if nothing is done. A small problem that gets worse fast can be more urgent than a big problem that is stable.
What do P1, P2, P3, P4, and P5 mean?
P1 is critical: a major service is down or data is at risk, and work starts immediately. P2 is high: a service is degraded for many users. P3 is medium: a limited group is affected. P4 is low: a minor issue or a single user with a workaround. P5 is planning: a minor issue with no urgency that can be scheduled, such as a small improvement or a request with no deadline.
Who decides the priority?
The person logging the incident makes the first call using the matrix, and the service desk can adjust it as facts come in. The matrix matters more than the person, because it makes the call consistent.
Can priority change during an incident?
Yes, and it should. If more users report the same problem, the impact grows and the priority rises. If a workaround is found, the urgency falls and the priority can drop.