Priority vs Impact vs Urgency in ITIL® 5: What's the Difference?
Preparing for the ITIL® 5 Foundation exam? Priority, Impact, and Urgency are three terms that constantly appear together in incident and problem scenarios — and the exam expects you to know exactly how they relate. This guide breaks it down.
Quick Answer
Impact measures how much damage or disruption an issue causes. Urgency measures how quickly it needs to be resolved. Priority is calculated from the two together — it determines the order in which issues get worked on, based on their combined impact and urgency.
What Is Impact?
Impact measures the extent of damage or disruption an issue causes — how many users are affected, how critical the affected service is, and how serious the business consequences are.
A high-impact issue might affect an entire department, a critical business process, or a large number of customers.
What Is Urgency?
Urgency measures how quickly a resolution is needed — often tied to how fast the impact will get worse, or how time-sensitive the affected activity is.
An issue can have high urgency even with relatively contained impact, if time pressure is severe — for example, something affecting a small team right before a critical deadline.
What Is Priority?
Priority is the practical output: it determines the order in which issues actually get worked on. It's typically calculated by combining Impact and Urgency — often using a simple matrix that maps different combinations to a priority level.
Priority is what a support team actually acts on day to day. Impact and Urgency are the two inputs used to calculate it.
The Relationship Between the Three
| Impact | Urgency | Priority | |
|---|---|---|---|
| Measures | Extent of disruption | Speed needed to resolve | Order of work |
| Type | Input | Input | Calculated output |
| Key question | How much damage? | How fast? | What order do we work on this? |
Impact and Urgency feed into Priority. Priority is what determines the sequence of work — not the other way around.
Real-World Example
A company's payroll system fails the day before payday.
Impact is high — it affects every employee's pay.
Urgency is also high — payday is tomorrow, so there's very little time.
Combined, this produces a very high Priority, meaning it jumps to the top of the support team's queue ahead of lower-priority issues, even ones that were logged earlier.
Why This Matters
Understanding this relationship matters because:
- It explains how support teams decide what to work on first, especially when multiple issues are open at once
- It clarifies that "urgent" and "high priority" aren't automatically the same thing — priority depends on both impact and urgency together
- It's essential for correctly answering incident and problem prioritization questions
Common Exam Mistakes
The most common mistake is treating Priority as a standalone judgment call, rather than understanding it as calculated from Impact and Urgency together.
A second mistake is assuming high urgency alone means high priority. A low-impact issue with high urgency may still end up with only moderate priority, since priority depends on both factors combined.
Memory Trick
Think:
Impact = how bad.
Urgency = how fast.
Priority = Impact + Urgency = what gets worked on first.
Key Takeaways
- Impact measures the extent of disruption or damage an issue causes.
- Urgency measures how quickly a resolution is needed.
- Priority is calculated from Impact and Urgency together, and determines work order.
- High urgency alone does not automatically mean high priority.
- This relationship is a frequently tested area of the ITIL® 5 Foundation syllabus.
One Practice Question
Which statement best describes the relationship between Priority, Impact, and Urgency?
- Priority, Impact, and Urgency are all the same measurement.
- Priority is calculated from a combination of Impact and Urgency, and determines the order in which issues are worked on.
- Urgency alone always determines Priority.
- Impact only applies to Problems, not Incidents.
Show Answer
Correct Answer: B
Priority is derived from combining Impact (extent of disruption) and Urgency (speed of resolution needed), and it determines the order in which issues are addressed.
Frequently Asked Questions
Is Urgency the same as Priority?
No. Urgency measures how quickly an issue needs to be resolved, while Priority is calculated by combining Urgency with Impact to determine work order.
Can a low-impact issue still have high priority?
Yes, if its urgency is high enough — though typically the highest priority issues have both high impact and high urgency combined.
Who calculates Priority?
Support teams typically use a priority matrix that combines Impact and Urgency levels to determine a consistent Priority rating.
Is this topic tested on the ITIL® 5 Foundation exam?
Yes. Understanding how Priority, Impact, and Urgency relate is a frequently tested area of the syllabus.
Ready to Test Yourself?
Now that you understand how Priority, Impact, and Urgency connect, the next step is recognizing that relationship in realistic exam scenarios. Take our free diagnostic quiz to test yourself, or continue exploring the other ITIL® 5 comparison guides.