Flowchart template · local export
Incident Response Flow Mermaid Template
Incident runbook flowchart: triage, severity call, mitigation, updates, and postmortem. Edit the code below, choose a publish preset, then export without signup, watermark, or cloud upload.
incidentrunbookSRE
Paste or edit Mermaid code
Replace the sample below, or load another example.
Load example
Preparing the local renderer without uploading your diagram.Preparing editor…
Live previewSample preview · Clean Docs
Preparing local editor…
Render & export
Export controls activate after your diagram renders locally.
Flowchart
Mode
Default renderNative MermaidOptimized exportStyled download
Export style
Clean DocsGitHub READMETransparent DocsWarm Editorial✦ ProWhiteboard Sketch✦ ProAurora Noir✦ ProBlueprint✦ ProChampagne✦ ProEmerald Suite✦ ProEditorial✦ Pro
Scale
1x2x4x
Or exact width, e.g. 1200px wide
Output: White · comfortable padding
Size: calculated after render
Filename: mermaid-flowchart-white-2x.png
When to use the Incident Response Flow template
An incident runbook as a flowchart: a Monitoring Alert gets triaged, and the Customer Impact decision either files a follow-up ticket or declares the incident. Declaring opens the incident channel, Mitigate or Roll Back starts the loop, status updates repeat until the Resolved check passes, and the flow ends at the postmortem.
- •Publishing an on-call runbook so responders follow the same triage and declaration path under pressure.
- •Training new on-call engineers on when an alert becomes an incident and what must happen in what order.
- •Auditing your response process after incidents, using the loop between mitigation and resolution checks.
Template code
The full Mermaid source for this template — copy it into any Mermaid-compatible tool, or edit and export it in the editor above.
flowchart TD
Alert[Monitoring Alert] --> Triage[Triage Signal]
Triage --> Sev{Customer Impact?}
Sev -- no --> Ticket[Create Follow-up Ticket]
Sev -- yes --> Declare[Declare Incident]
Declare --> Channel[Open Incident Channel]
Channel --> Mitigate[Mitigate or Roll Back]
Mitigate --> Update[Send Status Update]
Update --> Resolved{Resolved?}
Resolved -- no --> Mitigate
Resolved -- yes --> Postmortem[Write Postmortem]How to customize this template
- •Define what counts as customer impact in the Sev decision, or add severity-level branches (Sev1/Sev2) under Declare.
- •Point Update at your real status page and stakeholder channels by expanding it into its own steps.
- •Add a communication cadence loop (update every 30 minutes) between Mitigate and the Resolved check.
- •Link the Postmortem step to your template or tracker so the flow ends in an actionable artifact.