Diagramate

Incident Response Flowchart Template

Production incident handling from alert to closure: severity triage (P1 / P2), escalation, root cause, rollback or mitigation, verification, incident report and retrospective. For runbooks; free PNG, Word and PowerPoint export.

One feature

Core feature down

Yes

No

No

Yes

Alert or user report

On-call confirms the incident

Impact

P2 minor incident

P1 major incident

Open a war room and page the owner

Find the root cause

Quick recovery possible?

Roll back / restart / failover

Apply a temporary mitigation

Verify recovery

Back to normal?

Publish the incident report

Retrospective and action items

Close the incident

Previewed in the “Ink Black” theme; you can switch themes in the editor
Open in the editorFree · No sign-up · No watermark

Edit the text, pick a theme, export Word / PowerPoint / PDF

When to use it

Operations runbooks, on-call handbooks and incident management policies. Severity is drawn with two levels (P1 / P2), and recovery comes before root-cause analysis: stop the bleeding first, then learn.

Making it yours

  • Severity criteria are the edge labels out of C{Impact}; add a level by adding an edge.
  • Put the notification channel and people in the node: F[Open a war room<br/>page owner and support].
  • Add nodes for the retrospective deliverables (incident report, action item tracking).
  • Ink Black suits a dark on-call dashboard; switch to Light or Indigo for a white document.

Mermaid code

flowchart TD
    A([Alert or user report]) --> B[On-call confirms the incident]
    B --> C{Impact}
    C -- One feature --> D[P2 minor incident]
    C -- Core feature down --> E[P1 major incident]
    E --> F[Open a war room and page the owner]
    D --> G[Find the root cause]
    F --> G
    G --> H{Quick recovery possible?}
    H -- Yes --> I[Roll back / restart / failover]
    H -- No --> J[Apply a temporary mitigation]
    I --> K[Verify recovery]
    J --> K
    K --> L{Back to normal?}
    L -- No --> G
    L -- Yes --> M[Publish the incident report]
    M --> N[Retrospective and action items]
    N --> O([Close the incident])

Ask an AI for one with this structure

Send the prompt below to ChatGPT or Claude, then paste the whole reply into the editor; the code inside is detected automatically.

Draw an incident response flowchart in Mermaid flowchart TD syntax: after an alert or user report the on-call engineer confirms the incident and triages impact into P2 minor (one feature) or P1 major (core feature down, which opens a war room and pages the owner); then find the root cause and decide whether quick recovery is possible: roll back, restart or fail over if yes, apply a temporary mitigation if no; verify recovery, going back to root cause if not recovered; finally publish the incident report, run a retrospective with action items and close the incident. Use rounded nodes for start and end. Output only the mermaid code block.

FAQ

Are slashes in node text a problem?

[Roll back / restart / failover] is fine inside square brackets. What must be avoided are brackets, parentheses and braces themselves; wrap the text in quotes if you need them: A["Text (note)"].

Is the PNG exported from a dark theme dark?

Yes, the export background follows the theme, so Ink Black exports a dark background. Choose "Transparent" in the export options for a transparent PNG.

How do I print this large for the on-call wall?

Export the PNG at 3x, or export SVG for the print shop; vector scales without loss.

More in this category

All templates

Updated 2026-09-05