BPMN diagram
A BPMN diagram is a process map drawn using the Business Process Model and Notation 2.0 standard. It uses a fixed vocabulary of shapes — tasks, events, gateways, pools and lanes — so any BPMN-literate reader can interpret the same flow the same way.
BPMN is maintained by the Object Management Group and is the lingua franca for process-management tool chains — Camunda, Signavio, Bizagi, bpmn.io and BA Copilot all import and export BPMN 2.0 XML. Round-trip fidelity between any two tools depends on the subset each one supports and any vendor-specific extensions in the file (Camunda’s public BPMN coverage matrix is a useful reference for what is modeling-only versus engine-executable). In practice the notation shows up wherever you need a process map that is more precise than a flowchart: onboarding, order-to-cash, claims handling, audit documentation, digital-transformation discovery.
BPMN diagram example: bank payment
Two pools — Customer and Bank Teller — connected by message flows, with one exclusive gateway (“Are payment details valid?”) on the bank side. Every element is a standard BPMN shape and every label reads as normal text. The Customer pool intentionally models the happy path only; the rejection branch terminates inside the Bank pool, which is a common modeling choice when the customer-side rejection workflow is out of scope.
Making a payment at a bank
A two-pool BPMN 2.0 collaboration for making a payment at a bank. The Customer pool submits a payment and later receives a receipt; the Bank Teller pool receives the request, verifies the details, and routes through an exclusive gateway ("Are payment details valid?") — processing the transaction and providing a receipt on the yes path, or returning funds on the no path. Two message flows connect the pools: the customer sends the payment request to the bank, and the bank sends the receipt back.
- Customer submits the payment — the Payment Initiated start event fires the Submit Payment task.
- A message flow carries the request to the Bank Teller pool, triggering the Payment Request Received start event.
- Bank Teller verifies the payment details, then the "Are payment details valid?" exclusive gateway decides the path.
- On the no path, Bank Teller returns the funds and the Bank Teller process ends at Payment Rejected.
- On the yes path, Bank Teller processes the payment transaction and provides a receipt, ending at Payment Processed.
- A second message flow delivers the receipt back to the Customer pool, where the Receive Receipt task runs and the Customer process ends at Payment Completed.
Core BPMN symbols
Around five families of shapes cover most real-world BPMN diagrams.
Events (circles)
A thin-border circle marks a start event. A thick-border circle marks an end. A double-border circle is an intermediate event — used when the process pauses or reacts to something mid-flow (a timer, a message, an error).
Activities (rounded rectangles)
A single rounded rectangle is a task — a unit of work. A rounded rectangle with a small plus in the corner is a sub-process — a collapsed container holding a nested flow you can open for detail.
Gateways (diamonds)
Diamonds handle branching and merging. The marker inside tells you which kind: × exclusive (pick one path), + parallel (run paths at the same time), O inclusive (any combination), pentagon event-based (route on whichever event fires first). See gateway-bpmn for a deeper walk-through.
Pools and lanes
A pool is the outer container representing a participant. A lane sits inside a pool and represents one role, team or system. Every task sits in exactly one lane, which is what makes accountability obvious at a glance. See pool-and-lane for the full comparison.
Connecting objects
A solid arrow is a sequence flow — “this step happens before that one”. A dashed arrow is a message flow — information crossing between pools. A dotted line is an association — linking a comment or data object to the element it annotates.
How to draw a BPMN diagram in 6 steps
1. Write the process as a short paragraph first
Before drawing, describe the process in plain English: who starts it, what they do, which decisions get made, and how it ends. This forces you to agree the scope before wrestling with shapes.
2. List the roles and turn them into lanes
Every distinct role, team or system becomes one lane inside a pool. Keep the list short — three to six lanes is the readable maximum.
3. Place the start event and work left-to-right
A thin-border circle marks the start. Work forward one task at a time. Use verb-first task names ("Verify details", not "Verification").
4. Add a gateway where the path branches
Diamond shapes handle branching. An exclusive gateway (×) picks exactly one outgoing path. A parallel gateway (+) runs paths at the same time. Place the gateway in the lane of whoever makes the call.
5. Close every branch with an end event
A thick-border circle marks an end. Multiple end events are fine — every branch needs to terminate somewhere.
6. Validate the diagram with a stakeholder walk-through
Read the diagram aloud to someone close to the process. If any step makes them say "that is not how we do it" — fix the diagram, not the process description. Iterate once, then publish.
BPMN diagram FAQ
What is a BPMN diagram?
A BPMN diagram is a business-process map drawn using the Business Process Model and Notation 2.0 standard. It uses a fixed set of shapes — rounded rectangles for tasks, circles for events, diamonds for gateways, pools and lanes for roles — so any BPMN-literate reader can interpret the same flow the same way.
What is the difference between a BPMN diagram and a flowchart?
A flowchart is an informal process drawing — anyone can invent a shape vocabulary. A BPMN diagram is standardised: the Object Management Group publishes the notation, every shape has a defined meaning, and the same diagram can be read across tools (Camunda, Signavio, bpmn.io, BA Copilot) and, if modelled carefully, executed by a process engine.
What are the main BPMN symbols?
Five families cover about 90% of real-world BPMN diagrams: events (circles — start, intermediate, end), activities (rounded rectangles — tasks and sub-processes), gateways (diamonds — exclusive, parallel, inclusive, event-based), swimlanes (pools for participants, lanes for roles within a pool), and connecting objects (sequence flows, message flows, associations).
Is BPMN hard to learn?
The core shapes are quick to pick up — most business analysts are productive after an afternoon with the symbol reference. The tricky parts are gateway semantics (when to use exclusive vs inclusive vs event-based), message flow across pools, and keeping diagrams at a single level of detail. These are the same judgement calls that separate a readable flowchart from an unreadable one.
Can I turn a plain-English process description into a BPMN diagram?
Yes — that is exactly what BA Copilot is built for. Describe the process in a few paragraphs, mentioning each role, decision and outcome by name. The AI returns a full BPMN 2.0 flow with tasks, events, gateways and swimlanes that you can then refine in the drag-and-drop editor.
Skip the blank canvas
Describe your process in plain English. BA Copilot's AI returns a full BPMN 2.0 flow with tasks, events, gateways and swimlanes — ready to refine in the drag-and-drop editor.