BPMN Pools, Lanes and Message Flows: Modeling Cross-Organizational Processes in Sparx EA
A Pool is a participant. A Lane subdivides one participant. Message Flows connect pools; Sequence Flows stay inside them. Cross a pool boundary with the wrong connector and your BPMN model is quietly wrong.
The rules are strict and worth memorizing: Sequence Flows cannot cross pool boundaries, and Message Flows cannot exist within a pool. Using Sequence Flows between pools is the most common cross-organizational BPMN error. Get the structure right and a collaboration diagram becomes a precise interface specification — exactly what an integration architect or process analyst needs.
Pool: the participant boundary
A Pool is the process container for a single participant. Everything inside belongs to that participant — all activities, gateways, events, and sequence flows are its internal process.
Create a Pool when the participant is a different organization (your company and a customer, or a supplier), a separate autonomous system (an ERP, a CRM, an external API), or has a process engine that cannot see another participant's internal state. Don't create one for subdivisions of the same organization — a purchasing department and an accounts payable department are lanes in the same pool, not separate pools — or for modules of the same application.
The key test: can the two participants see each other's internal state? If they can only communicate through defined messages, they are separate pools. If one participant's process can branch on the other's internal state, they are lanes in the same pool.
Lane: subdivisions within a participant
A Lane represents a role, department, team, or system that performs specific activities within a participant's process. Lanes don't change process semantics — they are organizational annotations, and Sequence Flows cross lane boundaries freely. That is how handoffs within an organization are shown.
In practice, lanes take three forms. Role-based: Loan Officer, Underwriter, Compliance Officer. Department-based: Sales, Finance, Legal, Operations. System-based: CRM System, ERP System, Workflow Engine, for models that mix human and system activities within one organization. BPMN 2.0 also allows lane nesting — a department lane containing role lanes — created in Sparx EA by adding sub-lanes within a parent lane.
The connector rules, at a glance
The whole topic reduces to which connector is legal where. This is the picture worth keeping in front of you while modeling.
Black Box Pool: the external participant
A Black Box Pool shows that an external participant exists and interacts via messages, but hides its internal process — no activities, gateways, or sequence flows inside, just the boundary and the Message Flows connecting to it. Use it when modeling from your own organization's perspective and the external party's process is not relevant, not known, or not yours to specify, or when showing both full processes would make the diagram unreadable. Expand instead when the model is genuinely collaborative — the “collaboration diagram” pattern. In Sparx EA, draw a Pool, leave its interior empty, and connect Message Flows to its boundary.
Message Flows: communication between pools
Message Flows are the communication lines between pools — a message, data exchange, or signal crossing from one participant to another. They render as dashed lines with an open arrowhead, optionally with an envelope icon. The rules: they connect activities (tasks or events) in one pool to activities in another; they cannot connect items within the same pool (that's what Sequence Flows are for); and they can connect to a pool boundary (Black Box) or to specific activities in an expanded pool.
Direction carries meaning — the arrowhead shows which participant sends. You can also type a Message Flow with a Message element: in Sparx EA, create a Message artifact, name it (“PurchaseOrder”, “InvoiceApproval”, “CreditDecision”), and attach it to the flow. That turns the collaboration diagram into a formal interface specification.
Collapsed vs expanded pools
An expanded pool shows the internal process — every activity, gateway, event, and lane visible. It is right when you own the process and need to specify it. A collapsed pool shows only the boundary, appropriate for Black Box Pools, your own sub-processes detailed on a separate diagram, or simplifying a busy collaboration by hiding one participant. In Sparx EA, draw and populate a Pool for expanded; draw an empty Pool resized to a narrow band for collapsed. Collapse your own pool when presenting to external stakeholders who need to see only the interface — what you send and receive — not your internal detail.
Building a supplier-buyer model in Sparx EA
- Draw two expanded Pools — one for the Buying Organization, one for the Supplier.
- Add lanes to each: Procurement and Finance in the buyer; Sales, Fulfillment, and Accounts in the supplier.
- Model each internal process with Sequence Flows between activities in different lanes.
- Connect activities across the boundary with Message Flows: Purchase Order (Procurement → Supplier Sales), Order Acknowledgment (back), Invoice (Supplier Accounts → Finance), Payment Confirmation (back).
The result shows both organizations' internal processes and their message exchange — the complete picture for designing cross-organizational automation. For system integration, model the application system as a Pool (it is an autonomous participant) and show message flows between the human-process pool and the system pool to produce a clean interface specification. That kind of rigor is the heart of disciplined process modeling.
Frequently asked questions
Can a process have activities in both a pool and directly on the diagram?
No. If you have a pool, all participants must be in pools. Activities outside a pool count as an implicit, unnamed pool — technically allowed in BPMN 2.0 but producing ambiguous diagrams. Always place every process element inside an explicitly named pool.
How many lanes should a pool have?
As many as needed to show meaningful role or department separation. Beyond six or seven, a pool gets visually cluttered — at that point, consider decomposing the process across multiple diagrams: a top-level process plus expanded sub-process diagrams for each major phase.
What is the difference between a Message Flow and a Message Intermediate Event?
A Message Flow is the connector between pools showing communication. A Message Intermediate Event (Catch or Throw) is an event element within a process representing the act of sending or receiving. When an activity explicitly sends a message (a Throw event), the Message Flow connects from that event to the receiving pool. The Message Flow is the channel; the Message Event is the act.
Should IT systems be shown as pools or lanes?
Systems that operate autonomously — their own process engine, triggering their own activities, communicating via APIs or messages — should be Pools. Systems that are tools operated by a human (someone entering data in a CRM) are lanes, or appear as data objects within a human-performed lane. The test: does the system have its own internal process logic, or does a human operate it?
How do collapsed pools work with message flows?
Message Flows connect to the collapsed pool's boundary rather than to specific internal activities, since those are hidden. This is the Black Box Pool pattern: the flow says only that a message enters or exits the pool. When you later expand the pool, refine the flows to connect to specific activities.
How does Sparx EA handle the formatting of pools and lanes?
In the BPMN 2.0 toolbox, Pool and Lane elements offer options for orientation (horizontal or vertical lanes), lane sizing, and label position. Message Flows use the dedicated Message Flow connector type — not a standard UML association — and Sparx EA enforces that they cannot be placed between elements within the same pool.
Model collaborations that double as interface specs.
Talk to a practitioner about BPMN standards, cross-organizational modeling methodology, and model review for your Sparx EA repository.
Book a call →Keep reading
You might also be interested in
BPMN Gateways: XOR, OR, AND and Event-Based — When to Use Each
The five gateway types and the routing each one is right for.
Read → InsightBPMN Sub-Processes, Call Activities and Error Handling
Reuse and exception handling across cross-organizational models.
Read → DisciplineProcess Modeling
Build BPMN capability that produces precise, governable process models.
Explore → For architectsFor Architects
How Sparx Services helps practitioners model with rigor and confidence.
Explore →