An IT ticket priority matrix combines the impact of an issue with how urgently it needs attention. Use the example below to agree on Urgent, High, Normal, and Low priorities, then adjust it to your services and support hours.
By Troublesheet · Published · UpdatedImpact describes the effect on people, services, and essential work. Urgency describes how much delay the situation can tolerate before that effect becomes unacceptable. The number of affected people matters, but it is not the whole decision: one person may operate a service that everyone else depends on.
Identify the service, location, work that cannot continue, and scope of the interruption. Check whether a workaround actually allows the work to proceed.
Ask for the real deadline and consequence of delay. An appointment starting in ten minutes differs from a setup request for next month.
Record confirmed facts and missing details. Treat the initial priority as a decision to review when the situation changes.
The impact-and-urgency approach is described in Atlassian’s priority documentation. The four-level matrix and scenarios below are Troublesheet examples, not an official ITIL standard or a universal SLA.
First agree on three impact levels: high for a critical service or broad interruption, medium for a team or important workflow, and low for limited disruption with work still possible. Then choose the urgency column. Read the cell where the row and column meet.
| Impact | High urgency Work cannot wait | Medium urgency Delay has a cost | Low urgency Work can be planned |
|---|---|---|---|
| High impact | Urgent | High | Normal |
| Medium impact | High | Normal | Normal |
| Low impact | Normal | Normal | Low |
Use the matrix to make a consistent starting decision. Follow your established emergency or security incident process when it applies; do not leave a critical report waiting in a routine queue while someone completes a form.
Priority labels do not promise a response time. Define response and resolution targets separately, accounting for business hours, available coverage, dependencies, and any agreed service commitments.
Staff cannot reach the systems needed to work, and there is no usable alternative connection. Start the incident response, assign a coordinator, and provide a next-update time. Link or identify related reports so the scope remains visible.
The room’s scheduled session is blocked and moving rooms is not practical. Confirm the start time and available alternatives, then assign someone to restore a usable teaching setup. A single room can still represent a meaningful service interruption.
The request affects several people, but current work continues. Confirm the required date, licensing, approvals, and a planned installation window. A future deadline should be tracked without treating the work as an outage today.
The existing workstation remains usable. Confirm requirements and the purchasing process, then schedule the work. Reassess if new information shows the current setup prevents essential work.
If a printer appears to affect only one person, ask what it prints. A convenience printer and the only printer for time-sensitive shipping labels can have different business impact.
Use the matrix as a team reference, then have an authorized staff member select Urgent, High, Normal, or Low on the ticket. Record the triage reasoning in an appropriate team note, assign the technician, and set a follow-up for the next action. Troublesheet does not automatically calculate priority from this article’s matrix.
Use ticket ownership and priority controls to organize the queue, then review help desk metrics by priority to understand follow-through. If you are still working from email, the shared inbox transition checklist can help you introduce a consistent intake process.
At the next team review, compare a few real tickets without ranking individual technicians. Look for inconsistent definitions, missing information, and workarounds that changed the outcome.
Open the demo, choose a request, and explore its priority, assigned technician, notes, and follow-up.
Try the IT help desk demoNo signup required. Browse all IT help desk guides.
