# IT incident priority matrix worksheet

Adapt this planning resource to your environment. Examples are illustrative, not completed checks. Do not record secrets.

- Service / scope:
- Accountable owner:
- Reviewer:
- Environment / version:
- Review date:
- Approval / change reference:
- Next review trigger:

## Define impact in business terms

- [ ] High impact might mean a critical organisation-wide process cannot operate.
- Environment-specific action:
- Expected result / stop condition:
- Observed result and evidence:
- Owner / due date:

## Assess how quickly the harm grows

- [ ] High urgency means delay rapidly worsens the consequence or a deadline is imminent.
- Environment-specific action:
- Expected result / stop condition:
- Observed result and evidence:
- Owner / due date:

## Apply an illustrative matrix

| Impact / urgency | High urgency | Medium urgency | Low urgency | Your record | Owner | Evidence reference | Status / due date |
| --- | --- | --- | --- | --- | --- | --- | --- |
| High impact | P1 | P2 | P3 |  |  |  |  |
| Medium impact | P2 | P3 | P4 |  |  |  |  |
| Low impact | P3 | P4 | P4 |  |  |  |  |

## Reassess and communicate

- [ ] Review priority when the scope, workaround or deadline changes.
- Environment-specific action:
- Expected result / stop condition:
- Observed result and evidence:
- Owner / due date:

## Closure

- Outcome: not started / pass / partial pass / fail
- Exceptions, owner and due date:
- Acceptance / approval:
- Follow-up and cleanup:

Source article: https://happysysadm.com/it-service-management/incident-priority-matrix/