Incident Management Process Flowchart
An incident response flow from alert to postmortem: triage, severity, incident lead, mitigation, status updates and closing the loop.
4 teams13 steps3 decisionsFree download
Free to download. Edit it in Flow Studio to change the teams and steps, ask AI for changes, or export to PowerPoint, Word or draw.io.
Step by step
The same flow as a numbered list, ready for an SOP, a BRD or a ticket.
| # | Step | Who | Next |
|---|---|---|---|
| 1 | Alert firesStartMonitoring · step 2 | Monitoring | step 2 |
| 2 | Acknowledge in 5 minutesOn-call engineer · step 3 | On-call engineer | step 3 |
| 3 | Real incident?DecisionOn-call engineer · Yes: step 5, No: step 4 | On-call engineer | Yes: step 5, No: step 4 |
| 4 | Tune the alertOn-call engineer · step 6 | On-call engineer | step 6 |
| 5 | Severity 1 or 2?DecisionOn-call engineer · Yes: step 8, No: step 7 | On-call engineer | Yes: step 8, No: step 7 |
| 6 | Alert closedEndOn-call engineer · Done | On-call engineer | Done |
| 7 | Fix in working hoursOn-call engineer · step 13 | On-call engineer | step 13 |
| 8 | Open the incident channelIncident lead · step 9 | Incident lead | step 9 |
| 9 | Mitigate: roll back or fail overOn-call engineer · step 10 | On-call engineer | step 10 |
| 10 | Service restored?DecisionIncident lead · Yes: step 11, No: step 9 | Incident lead | Yes: step 11, No: step 9 |
| 11 | Post the all-clearDocumentStakeholders · step 12 | Stakeholders | step 12 |
| 12 | Postmortem within 5 daysDocumentIncident lead · step 13 | Incident lead | step 13 |
| 13 | Incident closedEndIncident lead · Done | Incident lead | Done |
When to use it
Use it as the agreed playbook for on-call engineers, so everyone knows who leads, who talks to customers and when an incident is over.
Who's involved
- Monitoring1
- On-call engineer7
- Incident lead4
- Stakeholders1
Yours works differently?
Describe your own process in a few sentences and Flow Studio draws it, with your teams and your rules.
Describe your processarrow_forwardHow to get it right
- 1Decide severity in the first few minutes with a short written definition, not by gut feel.
- 2Give one person the incident lead role. They coordinate; others fix.
- 3Mitigate first (roll back, fail over) and find the root cause afterwards.
- 4Write the postmortem within a week while memories are fresh, and focus it on systems, not blame.
Questions
What are the steps of incident management?
Detect, acknowledge, triage and set severity, assign an incident lead, mitigate, communicate, confirm the service is restored, then review in a postmortem.
What is the difference between mitigation and resolution?
Mitigation stops the harm quickly, for example by rolling back. Resolution fixes the underlying cause, which can happen later and is tracked from the postmortem.
More process flow templates
- IT change managementA change request flow with standard changes, change advisory board review, a scheduled change window, testing and rollback.
- Bug triageHow a bug report is checked for duplicates, reproduced, prioritised, fixed in a hotfix or the next sprint, and closed with the reporter told.
- Access requestHow an employee gets access to a system: manager approval, data owner approval for sensitive data, least-privilege access and regular access reviews.
- Software releaseA release process from merged code to everyone: staging, regression tests, go or no-go, a staged rollout with monitoring, rollback and release notes.