BPMN examples
BPMN diagram examples generated from text
BPMN 2.0 process diagram examples — events, tasks, and gateways — generated from a plain-English description. Copy the prompt and make your own.
Prose in. Diagram out.
The prompt
A customer submits an order. Sales verifies stock. If in stock, the warehouse ships it; otherwise procurement reorders. Finance then issues the invoice.
ChartCraft draws
More BPMN diagram examples
Generated with ChartCraft and published in the examples gallery — open one to see its prompt, or use it as a starting point.
The notation, in 30 seconds
BPMN 2.0 has a large vocabulary, but five element families carry everyday process modelling.
| Element | What it means |
|---|---|
| Start / end events (circles) | Thin circle starts the process, thick circle ends it. One trigger in, one circle per distinct outcome. |
| Task (rounded rectangle) | A unit of work. User tasks (a person acts), service tasks (a system acts), script tasks (code runs). |
| Exclusive gateway (X diamond) | Either/or routing — exactly one outgoing path fires, each labelled with its condition. |
| Parallel gateway (+ diamond) | Both/and — all outgoing paths run; a matching gateway joins them back. |
| Lane | A horizontal band per role or department — the task's lane says who does it. |
| Message flow (dashed) | Communication crossing organizational boundaries, between separate pools. |
Best practices — and the classic mistakes
Do
- Label every path out of an exclusive gateway with its condition — an unlabelled gateway is a coin flip.
- One lane per role that actually does something; systems that merely store data don't earn a lane.
- Name tasks verb-first and keep them atomic — “Review application”, not “Handle stuff”.
- Separate the happy path from exception handling; boundary events or a second diagram beat a spaghetti main flow.
- Every parallel split needs a matching join — unbalanced gateways are the classic BPMN bug.
Avoid
- Gateways used as decisions AND merges inconsistently, leaving token flow ambiguous.
- A lane for every system in the architecture, most of which never act.
- Processes with one giant “Process request” task — no visibility into the actual work.
- Missing end events for rejection/withdrawal paths, implying every case succeeds.
Questions
How were these BPMN diagram examples made?
Each example was generated by ChartCraft from a plain-English prompt, then laid out automatically — the same way you'd make your own. Click any example to see its full page.
Can I use these BPMN diagram examples as templates?
Yes — open an example, copy its prompt into the studio, then edit it in plain English to fit your case.
What's the difference between BPMN and a flowchart?
BPMN is a standardized process language: lanes assign work to roles, event types distinguish triggers, and gateway semantics are precise enough to execute in a workflow engine. A flowchart is freer-form and better for quick explanations.
When do I need lanes?
As soon as more than one role touches the process. Lanes make handoffs visible — and handoffs are where processes stall, so they're usually the point of drawing the diagram.
Is it free?
Your first 3 diagrams are free with no account, then 5 a month on a free account.