16:91 frame · BPMN
Case study

Why this artifact is built the way it is

When you’d need it

A simple flowchart is not enough because the work crosses roles. BPMN shows who does each step and where the process branches under formal rules.

Key decisions

  • Swimlanes separate clerk and underwriter responsibilities so handoffs are visible.
  • Gateways make the decision logic explicit instead of burying it in prose.
  • The diagram keeps one pool, because the example is about internal handoff rather than partner integrations.

When to copy vs. adapt

Use this for approval, compliance, finance, onboarding, and operations workflows. Use a plain flowchart when roles and formal notation are unnecessary.

Inside

What’s in this artifact

  1. 01Pool and lanes
  2. 02Tasks
  3. 03Gateways
  4. 04End states
FAQ

BPMN questions

What is a BPMN diagram?

BPMN is a standard process notation that uses events, tasks, gateways, pools, and lanes to show business workflows.

When is BPMN better than a flowchart?

Use BPMN when role handoffs, swimlanes, or formal decision gateways are important to understanding the workflow.

Can Toft generate BPMN from notes?

Yes. Describe the roles, steps, and decisions and Toft drafts the BPMN structure.

Make your own

Tools that build this.

Make your own bpmn.

Describe what you need. Toft returns the finished, editable artifact.

Try it with this prompt