MERMAID TEMPLATE

Incident response process: Mermaid Template Example

Turn an incident response playbook into a diagram that makes ownership, mitigation, resolution, and follow-up easy to scan. Manage code and settings in one place, then export the result as SVG or PNG.

  • Live Mermaid preview
  • Automatic browser draft saving
  • Strict security rendering
  • Start instantly from templates

How to get started

  1. 1. Write Mermaid syntax in the Code panel.
  2. 2. Choose a diagram type and theme in Config.
  3. 3. Pan, zoom, and inspect the canvas.
  4. 4. Export as SVG or PNG, or sign in to save a project.

What you can adapt

  • Document on-call procedures
  • Train new incident responders
  • Review missing escalation or recovery paths

How to use this template

  1. 1. Rename the alert and triage nodes for your service.
  2. 2. Add the role responsible for each handoff.
  3. 3. Include mitigation and rollback paths for high-impact incidents.
  4. 4. Link the final node to the post-incident review process.

Incident response process Mermaid code

Copy this starting point, replace the labels with your own domain, and preview the result in the editor.

flowchart TD
  Alert[Alert Occurs] --> Triage{Severity Triage}
  Triage --> Owner[Owner Assign]
  Owner --> Mitigate[Impact Mitigation]
  Mitigate --> Resolve[Root Cause Resolve]
  Resolve --> Review[Post-incident Retrospective]

Template FAQ

What should an incident response diagram include?

Include detection, severity assessment, ownership, mitigation, resolution, and a post-incident review.

Should every incident have the same flow?

Use this as a common starting point, then add service-specific escalation and recovery steps where they matter.

Flowchart tips

Use TD or LR to change the flow direction.

Use diamond nodes for decisions.

flowchart TD
  Alert[Alert Occurs] --> Triage{Severity Triage}
  Triage --> Owner[Owner Assign]
  Owner --> Mitigate[Impact Mitigation]
  Mitigate --> Resolve[Root Cause Resolve]
  Resolve --> Review[Post-incident Retrospective]

EXPLORE

Explore other diagrams

Flowchart

Visualize processes, decisions, and system flows with connected nodes.

Sequence

Map requests, responses, and asynchronous events between services.

Class

Design domain objects, properties, methods, inheritance, and relationships.

ER

Document database entities, fields, relationships, and cardinality.

State

Show how an object or workflow changes state in response to events.

Mindmap

Organize ideas and subtopics hierarchically around a central theme.

Gantt

Plan projects with tasks, milestones, dependencies, and dates.

C4

Explain software architecture from system context to detailed components.

User Journey

Describe user actions, sentiment, and experience across a journey.

Pie Chart

Compare parts of a whole with a simple Mermaid pie chart.

Quadrant

Position items across two axes to compare priorities or trade-offs.

Requirement

Connect requirements, elements, and verification relationships.

GitGraph

Explain branches, commits, merges, and release paths visually.

Timeline

Present milestones and events in chronological order.

ZenUML

Write concise sequence diagrams for object interactions and messages.

Sankey

Show how quantities flow between sources, stages, and destinations.

XY Chart

Plot values across two axes to show trends and comparisons.

Block

Arrange system blocks and connections to explain structure at a glance.

Packet

Document the fields and bit layout of a network packet.

Kanban

Organize work into visual columns such as backlog, active, and done.

Architecture

Show cloud services, infrastructure groups, and their connections.

Radar

Compare multiple options across a consistent set of dimensions.

Treemap

Show hierarchical values as nested areas for quick comparison.

Bar Chart

Compare discrete values across categories with vertical bars.

Line Chart

Show change over time or across ordered values with a line.

100%