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

Edit this flowarrow_forward
Incident management processMonitoring1On-call engineer7Incident lead4Stakeholders1YesNoYesNoYesNoAlertfires2Acknowledge in5 minutes?Real incident?4Tune the alertAlertclosed?Severity 1 or2?7Fix in workinghours8Open theincidentchannel9Mitigate: rollback or failover?Servicerestored?Post theall-clearPostmortemwithin 5 daysIncidentclosed

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
1Alert firesStartMonitoring · step 2
2Acknowledge in 5 minutesOn-call engineer · step 3
3Real incident?DecisionOn-call engineer · Yes: step 5, No: step 4
4Tune the alertOn-call engineer · step 6
5Severity 1 or 2?DecisionOn-call engineer · Yes: step 8, No: step 7
6Alert closedEndOn-call engineer · Done
7Fix in working hoursOn-call engineer · step 13
8Open the incident channelIncident lead · step 9
9Mitigate: roll back or fail overOn-call engineer · step 10
10Service restored?DecisionIncident lead · Yes: step 11, No: step 9
11Post the all-clearDocumentStakeholders · step 12
12Postmortem within 5 daysDocumentIncident lead · step 13
13Incident closedEndIncident 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_forward

How to get it right

  1. 1Decide severity in the first few minutes with a short written definition, not by gut feel.
  2. 2Give one person the incident lead role. They coordinate; others fix.
  3. 3Mitigate first (roll back, fail over) and find the root cause afterwards.
  4. 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

See all 34 process flow templates