Editable Flowchart example

Swim lanes Mermaid diagram example

Updated 12 September 2026 · Renders with Mermaid 11.17.2

Edit this cross-team form workflow in Mermaid, inspect the rendered result, and adapt the working source for your own documentation.

About this example

This cross-team form workflow example is designed as an editable starting point rather than a finished specification. In the rendered diagram, user, application, and email responsibilities are separated into subgraphs. Read the structure once before changing the source so identifiers, labels, and connections stay aligned. The example is intentionally small enough to test after every edit, but it includes the syntax needed to communicate the central relationship. Open it in mermaid.tools, make one change at a time, and keep the Mermaid source alongside exported images so the diagram remains maintainable.

Mermaid source

flowchart LR
  subgraph User
    A[Submit form]
  end
  subgraph App
    B[Validate] --> C[Save]
  end
  subgraph Email
    D[Send confirm]
  end
  A --> B
  C --> D

Adapt it

• Rename each lane for an owner and move actions into the team that actually performs them.
• Keep identifiers short and stable while changing the visible labels for your audience.
• Preview after each structural edit, then remove sample nodes that do not represent real information.
• Export SVG for scalable documentation or PNG when the destination expects a fixed image.

• flowchart
• lanes
• process
• swim

This example source is dedicated to the public domain under CC0 1.0. Review generated diagrams before relying on them in documentation.

Learn more in the related guide.

Related examples