Use impact and urgency to choose a consistent P1-P4 priority without rewarding the loudest requester.
Created by the First Role Skills Editorial Team. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
A realistic scenario
Three requests arrive together: one person cannot print, six people cannot log in, and payroll cannot submit a required file. Which should be handled first?
DeliverableA documented priority decision with a clear reason and escalation route.
Three beginner mistakes
- Treating every request marked urgent as P1
- Using job seniority as the priority rule
- Escalating without recording impact and evidence
Complete it in six controlled steps
Define impact
Measure how many people or critical processes are affected. Record whether a workaround exists and whether data, safety, money, or a deadline is at risk.
Define urgency
Ask when harm will occur if nothing changes. A high-impact issue with a safe two-day workaround may be less urgent than a time-bound payroll failure.
Apply the matrix
Use P1 for critical widespread or business-stopping incidents, P2 for major degradation, P3 for normal individual issues, and P4 for planned requests or questions.
Record the reason
Write one sentence: ‘P2 because six users are blocked and no workaround is confirmed.’ This makes reassessment possible.
Follow the escalation route
Use the team’s actual incident channel and on-call process. A priority label alone does not notify the right person.
Reassess when facts change
Lower or raise priority when scope, workaround, or deadline changes. Keep the original timeline and explain the change.
Before and after
Before:
P1 – executive cannot print a draft
After:
P3 – one user affected, secure PDF workaround available, needed tomorrow. Owner: service desk queue.
Complete the exercise
Classify eight fictional tickets using the impact-urgency matrix. Write a one-sentence rationale for each and compare two borderline cases.
Download the priority practice set — Eight fictional requests with an answer key column left blank for practice. — Download file
Use only fictional or fully anonymized data. Never upload an employer’s confidential information to a portfolio.
Turn the exercise into credible evidence
Your evidence should include the completed matrix and the rationale column, not only the final P1-P4 labels. Choose two requests that could reasonably change priority when a new fact appears. Explain what that fact would be, how the label would change, and which route would be notified. This shows that priority is a revisable operational decision based on impact, urgency, workaround, and deadline rather than the requester’s tone or seniority.
Check your own work
- Impact counted
- Urgency dated
- Workaround checked
- Reason recorded
- Escalation route used
Primary reference: Atlassian: incident severity levels
Why this matters in your first job
If you start in IT support, customer support or operations, you will often face more requests than you can handle at once. Priority levels turn a stressful queue into a clear order of work and protect you from the common beginner mistake of answering whoever shouts loudest. They also make escalation easier: when you can explain why something is P1, people respond faster.
Common questions
Who decides the priority? Usually the team defines the rules and the support person applies them to each ticket. When in doubt, ask a senior colleague and note the answer for next time.
What if a customer insists their issue is urgent? Acknowledge their concern, apply the agreed definitions and explain the expected response time. If the impact is genuinely higher than it first appeared, raise the priority and document why.
Can priorities change? Yes. A minor issue affecting one user can become urgent if it spreads. Re-check open tickets regularly. Our guides on customer service skills and problem-solving at work cover the conversations around these decisions.