When an IT incident occurs, responder velocity depends heavily on clear, objective prioritization. Allowing requesters or support technicians to assign priority based on emotion or subjective urgency frequently leads to "P1 inflation"—where minor requests block critical system outages.
An objective Incident Priority Matrix evaluates two distinct variables: Impact (the number of affected users or critical business services) and Urgency (how quickly the business suffers operational loss).
The Standard ITIL Priority Matrix Formula
Priority is calculated deterministically by intersecting Impact and Urgency levels:
| Impact \ Urgency | High Urgency | Medium Urgency | Low Urgency |
|---|---|---|---|
| High Impact | P1 — Critical | P2 — Major | P3 — Moderate |
| Medium Impact | P2 — Major | P3 — Moderate | P4 — Low |
| Low Impact | P3 — Moderate | P4 — Low | P4 — Low |
Detailed Breakdown of Priority Levels
P1 — Critical Outage (Emergency Response)
A P1 incident represents a complete failure of an enterprise core service (e.g., primary ERP offline, payment gateway down, site-wide network failure) impacting multiple business units or external customers with immediate financial risk.
- SLA Response Target: < 15 minutes
- SLA Resolution Target: < 4 hours
- Operational Action: Automatic page out to Major Incident Response Team & Incident Commander.
P2 — Major Incident
A P2 incident involves severe degradation of a core service or total failure of a non-critical department service without a workaround available.
- SLA Response Target: < 30 minutes
- SLA Resolution Target: < 8 hours
- Operational Action: Priority assignment to Tier 2/3 engineering leads.
P3 — Moderate Incident
A P3 incident impacts an individual user or small team, but a temporary workaround exists or operational impact is minimal.
- SLA Response Target: < 2 hours
- SLA Resolution Target: < 24 hours
P4 — Low Priority / Service Request
Routine service requests, password resets, minor UI issues, or enhancement requests with negligible impact.
- SLA Response Target: < 8 hours
- SLA Resolution Target: < 5 business days
Automating Priority Triage with MBX CORTEX
MBX CORTEX features built-in multi-dimensional queue filtering and automated P1-P4 matrix calculation. Incoming tickets are dynamically assigned SLA timers and escalated based on live operational rules.