BPMN pool and lane
In BPMN — the ISO-standard notation for business process modeling — a pool represents a participant (usually an organization or department), and lanes inside the pool represent the sub-roles that perform the work. They are the formal equivalents of informal swimlanes.
Need a swimlane diagram, not full BPMN?
ProcessMapping.app builds informal swimlane diagrams from a spreadsheet in real time. Free, no signup.
Start Process Mapping FreeDefinition
A BPMN pool is a rectangular container that represents one participant in a process. Inside a pool, lanes divide the participant into the specific roles or systems that actually perform the steps. The pool answers "which organization" and the lanes answer "which person or team inside it."
When a process involves multiple organizations — a customer and a vendor, a hospital and a payer — each organization gets its own pool. Lanes only live inside pools; you can't have a lane that crosses pool boundaries.
Pool vs. lane
The distinction matters when the process spans multiple parties:
- Pool = participant (typically an organization, department, or system at the top level).
- Lane = sub-role inside a pool (typically a specific team or job function).
- Message flow = communication between pools (rendered as dashed arrows).
- Sequence flow = order of steps within a single pool (rendered as solid arrows).
BPMN pools/lanes vs. informal swimlanes
Informal swimlane diagrams use the same visual idea — bands grouping steps by role — but without BPMN's strict semantic rules:
- BPMN requires specific shape semantics: gateway types (exclusive, inclusive, parallel), event types (start, intermediate, end), activity types (task, sub-process).
- BPMN distinguishes sequence flow from message flow.
- BPMN diagrams are meant to be executable — a workflow engine should be able to read the diagram and run the process.
- Informal swimlane diagrams use the same lane metaphor with looser shape conventions; the goal is human-readable documentation, not machine execution.
When to use full BPMN
Reach for BPMN pools and lanes when:
- A workflow engine will read the diagram and execute the process.
- An external party (a consulting firm, a regulator, a vendor) requires BPMN format.
- The process spans multiple organizations and the message flow between them needs to be precise.
When informal swimlanes are enough
For everyday process documentation — training, reference, internal use — informal swimlane diagrams are simpler and just as readable. They use the same lane metaphor without the strict BPMN semantics, which keeps them easier to author and to read.
Frequently asked questions
What is a BPMN pool?
A pool is a rectangular container in a BPMN diagram representing one participant — usually an organization or department. Each pool contains lanes for sub-roles.
What is a BPMN lane?
A lane is a band inside a pool that groups steps by the specific role or system performing them. Lanes are what make a BPMN diagram cross-functionally legible.
What's the difference between a BPMN lane and a swimlane?
A swimlane is the general concept; a BPMN lane is its formal equivalent inside a BPMN pool. BPMN adds strict rules about shape semantics, gateway types, and flow types.
When do I need full BPMN versus an informal swimlane diagram?
Use BPMN when a workflow engine will execute the diagram or an external party requires it. For internal documentation, informal swimlane diagrams are simpler.
Can a lane span multiple pools?
No. Lanes only exist inside a single pool. Cross-pool communication is shown with message flow (dashed arrows), not lanes.
Does ProcessMapping.app support full BPMN?
ProcessMapping.app builds informal swimlane diagrams from a spreadsheet — fast, readable, no notation training required. For full BPMN with executable semantics, use a dedicated BPMN modeller.
Ready to map your first process?
The editor opens with a starter template. Edit the spreadsheet to define your process — the diagram updates as you type. No signup required to get started.
Start Process Mapping Free