Priority matrix - quick start guide
Priority matrix - quick start guide
Every service desk eventually hits the same problem: two agents triage the same type of incident and assign different priorities. One calls it a P2, the other a P3, and the SLA clock starts ticking at different speeds for what is essentially the same situation. The Priority Matrix schema eliminates that inconsistency by encoding your prioritisation logic into structured data.
When to use this schema
Deploy the Priority Matrix when your organisation needs consistent, auditable incident prioritisation. It is the right choice if you are formalising ITIL priority logic, if agents assign different priorities for similar incidents, if SLA targets are tied to priority levels, or if you want automation rules to drive priority assignment from structured matrix data.
Choose a different schema if you need full SLA lifecycle management (use SLA Management), a general-purpose CMDB (use Core Schema or Standard CMDB), or if Jira's built-in priority field already meets your needs without matrix logic.
Not sure which schema fits? Which Schema Should I Choose? walks through the decision.
Schema overview
The Priority Matrix implements the classic ITIL model: Priority = f(Impact, Urgency). Four object types, two reference types, 19 records for a complete 3x3 matrix.
| Benefit | What it delivers |
|---|---|
| Consistent prioritisation | Same impact/urgency combination always produces the same priority, regardless of which agent triages |
| Faster triage | Agents look up the matrix rather than deliberating; reduces mean time to assign |
| SLA alignment | Response and resolution targets are embedded in each Priority Level |
| Audit trail | The matrix is versioned data in Assets, not tribal knowledge |
| Override governance | Lock critical combinations while allowing flexibility on lower-severity rules |
Object types at a glance
| Object Type | Purpose | Records in starter matrix |
|---|---|---|
| Priority Level | The output: P1 through P4 with response/resolution targets and colour codes | 4 |
| Impact Level | One input axis: how broadly the issue affects the organisation (Single Team to Organization-wide) | 3 |
| Urgency Level | Other input axis: how time-sensitive the issue is (Next Business Day to Immediate) | 3 |
| Priority Rule | The junction: maps one Impact + one Urgency to one Priority Level | 9 |
Relationship architecture
Impact Level ──(Determines)──> Priority Rule ──(Maps To)──> Priority Level
^
Urgency Level ─(Determines)──────────┘
Screenshot coming soon
Two reference types: Determines (blue, #0052CC) links the input axes to the rule; Maps To (green, #00875A) links the rule to its resulting priority. In a 3x3 matrix, each foundation type is referenced by 3 rules, and each Priority Level is referenced by however many rules map to it.
Pro tip: The Priority Matrix pairs naturally with the SLA Management schema. Priority Matrix defines what each level means; SLA Management tracks performance against those targets. Together they provide the complete SLA lifecycle.
Guide contents
This guide is split into three focused pages:
Object type reference · Attribute tables for all four object types, implementation guidance, scope and time sensitivity definitions, naming conventions, override strategy, and example records.
Building the matrix · Step-by-step deployment, the complete 3x3 starter matrix (19 records), population sequence in dependency order, verification queries, and common setup mistakes.
Integration and operations · Five integration patterns (incident, request, SLA, automation, reporting), priority distribution metrics, override frequency tracking, essential AQL queries, and recommended dashboards.