Key takeaway: BPMN 2.0 elements provide a common language for describing business processes. An event indicates that something happens, an activity represents work to be performed, and a gateway controls how execution paths split or merge. Pools and lanes make participants and areas of responsibility visible. Connecting lines show the order in which work progresses and where communication takes place.
A good process model shows not only “what comes next,” but also who performs the work, what they are waiting for, and what constitutes completion. This installment of the BPMN 2.0 in Practice series explains the basic notation using a purchase request as an example. Choosing gateway types is a separate topic: here, we focus on the meaning of the elements and their relationships.
Practical focus – not an exhaustive manual: This series is focused on everyday business applications and executable workflows, rather than serving as an exhaustive BPMN 2.0 reference handbook. The official standard encompasses a much broader palette of specialized notations; here we highlight the essential building blocks that cover 90% of real-world business scenarios.
An Overview of BPMN 2.0 Elements in One Table
BPMN is more than simple flowchart notation: its shapes and connections have defined meanings. The following elements are worth learning to recognize first. You do not need to use every symbol immediately; the goal is to describe the process clearly, not to include as many symbols as possible.
| Element | Appearance | Meaning and example |
|---|---|---|
| Event | A circle with a border indicating the event’s role | Something happens: for example, a request arrives or a deadline is reached. |
| Activity | A rectangle with rounded corners | Work to be performed: for example, “Check request.” |
| Gateway | A diamond. An exclusive (XOR) gateway can be shown either empty or with an X marker. A parallel gateway is marked with a + sign. | Controls how execution paths split or merge. |
| Pool | A frame enclosing a participant | A participant in a collaboration: for example, the company or the supplier. |
| Lane, or swimlane | A distinct area within the process | An area of responsibility: for example, procurement or finance. |
| Sequence flow | A solid line with a filled arrowhead | The order of execution within the same process. |
| Message flow | A dashed line with a circle at the start and an open arrowhead | An exchange of messages between different participants. |
Reading tip: the shape indicates the element’s meaning, the lane shows where responsibility lies, and the connection shows its relationship to other elements. None replaces the others.
Events, Activities and Gateways: How Do They Connect?
Example 1: The Basic Path of a Purchase Request
A simple process can be described as follows: “Request received” start event → “Check request” activity → “Record request” activity → “Request processed” end event. Here, the arrows represent sequence flows. The start event has no incoming sequence flow, and the end event has no outgoing sequence flow.
Activity is an umbrella term. It can be a task, which is not broken down further in the given model, or a subprocess, which contains further steps. Task names should ideally express an action: instead of “Procurement,” “Request a quotation” describes the work to be done more precisely.
The task type can provide additional information. A user task requires human involvement through an application; a service task can represent an automated operation. This helps distinguish between employee and system steps, but does not implement automation on its own.
If different paths can follow the review, a gateway may be used. A gateway does not perform work: it does not review the document itself or replace the approval task. In this example, the review outcome determines which branch the purchase request follows. Choosing between gateway types is covered in a separate article in this series.
Pool and lane: participant or area of responsibility?
2. Example: company, procurement and supplier
In a procurement process, “Company” can be one pool and “Supplier” another. Within the company pool, the requester, procurement and finance can each have their own lane. This shows which area of responsibility each task belongs to within the same participant’s process.
A pool therefore represents a participant, while a lane categorizes process elements, often by role or organizational unit. Not every department needs a separate pool. If procurement and finance work within a shared internal process, lanes are typically the appropriate way to separate them.
However, the boundary does not simply follow the organizational chart. The purpose of the model should determine whether it depicts a handover of responsibility within a shared process or collaboration between independent participants.
We may not know the supplier’s internal operations. In that case, its pool can appear without internal steps, as a so-called black box. The model can still show the request for quotation and the quotation received in response.
An important distinction when designing an executable solution: a lane name is not an access control rule in itself. Just because a task appears in the finance lane, you still need to specify which users receive it and what access they have.
Sequence flow and message flow: two different connections
3. Example: internal handover and external request for quotation
The “Prepare request” task is in the requester’s lane, while “Review request” is in the procurement lane. They are connected by a sequence flow because they represent the execution order within the same process. A sequence flow can cross lane boundaries, but not pool boundaries.
When procurement sends a request for quotation to the supplier, different participants are communicating. This is represented by a message flow between the two pools. The connection can be labeled “Request for quotation,” and the return message “Supplier quotation.” A task handover within a pool is not represented by a message flow.
The practical significance of this distinction is that handing over internal work and waiting for an external response are different behaviors. A message flow alone does not specify when the receiving process can continue: this is clarified by the behavior of the event or activity on the receiving side.
Precision also matters when it comes to documents. An attached quotation may be an input to the work, but the document itself is not a sequence flow. Where needed, data objects and data associations are used to represent how data and documents relate to the process.
Event types: starting, waiting and ending
For events, two questions need to be distinguished: where does something happen in the process, and what trigger or result is it associated with? The circle’s border indicates the event’s position, while the icon inside may indicate a message or a timer, for example.
- Start event: a thin, single circle; marks the start of the process.
- Intermediate event: a double circle; can indicate waiting or throwing an event during the process.
- End event: a thick circle; indicates the end of an execution path.
4. Example: a message starts processing
If the process starts when an external request message arrives, a message start event can be used. If the running process later waits for a quotation, this can be represented by an intermediate catching message event. Both involve messages, but one starts a new process instance, while the other allows an existing instance to continue.
Events can be catching or throwing. Start events are catching events, while end events are throwing events; intermediate events can serve either role, depending on the event type.
5. Example: the approval deadline expires
A timer event can be placed on the boundary of the “Approve purchase request” task. If the timer is interrupting, it interrupts the task when the deadline expires, and work continues along the associated exception branch. With a non-interrupting timer, a reminder can be triggered, for example, while approval remains possible. Both timers are placed on the border of the approval task. An interrupting timer is shown with a solid double outline, and a non-interrupting timer with a dashed double outline, both containing a clock icon.
End events must also be interpreted precisely. Reaching a simple end event does not automatically stop all parallel branches. A terminate end event has a different meaning: it ends active execution within the scope of the relevant process or subprocess.
How can we check whether the model is understandable?
Before discussing automation, let’s walk through a specific request using the model. Don’t just follow the ideal path: ask about missing information, external responses and approaching deadlines as well.
- Start: is it clear what creates a new process instance?
- Work: does every activity have a clear outcome and an assigned owner?
- Connections: have we distinguished the internal sequence from message exchanges between participants?
- Waiting: is it clear what the process is waiting for and what happens if there is a delay?
- Completion: is the meaning of each end state clear from a business perspective as well?
Further articles in this series cover gateway selection, the ten most common modeling mistakes, the differences between BPMN, flowcharts and UML activity diagrams, and the steps involved in creating an executable process. For the latter, data, permissions, business rules and integrations must also be defined, beyond the notation itself.
Summary: in a good BPMN model, events, work, responsibilities and communication each have a distinct meaning. This consistency makes the diagram an operational description that everyone can interpret in the same way.
Would you like to apply these fundamentals to your own process? Consult with xFLOWer experts and explore together how to turn your current operations into a clear process model that can then be implemented.
This article is part of our complete guide: BPMN 2.0 in Practice: A Complete Guide from Modeling to a Working Process
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
