Key takeaway: BPMN gateways control which paths a process follows and when it can continue after multiple branches converge. An exclusive gateway activates a single path, a parallel gateway activates every path, and an inclusive gateway activates one or more conditional paths. With an event-based gateway, a future event—not existing data—determines what happens next. Alongside choosing the right symbol, you also need to plan how the branches will rejoin.
In this installment of the “BPMN 2.0 in Practice” article series, we explore the four types using examples from a procurement process. More than diagram readability is at stake: an incorrectly chosen join can leave a process waiting, trigger a task multiple times or cause a check to be skipped.
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.
1. BPMN gateways: a quick decision table
A gateway does not perform business work itself: it neither checks a contract nor makes a human decision. It controls how the process proceeds. A check or approval is a separate activity; the gateway can select a path based on its outcome.
| Type | When should you use it? | Splitting | Joining |
|---|---|---|---|
| Exclusive, XOR | You are choosing between mutually exclusive options. | Exactly one outgoing branch starts. | Does not wait for other branches; passes every arrival through. |
| Parallel, AND | Every listed task is required. | Every outgoing branch starts. | Waits for the required arrival from every incoming branch. |
| Inclusive, OR | Multiple conditions may be met simultaneously. | One or more branches start. | Synchronizes the branches from which execution may still arrive. |
| Event-based | The next event determines what happens next. | In the standard exclusive variant, the path of the first event to occur wins. | Not a general-purpose joining mechanism; the continuation must be designed separately. |
The XOR symbol is a diamond with an optional X marker; AND contains a plus sign, and OR contains a circle. The event-based gateway has its own event marker. The diamond is the common shape for gateways. Both an empty diamond and one marked with an X denote an exclusive gateway. A plus sign indicates a parallel gateway, while an inner circle indicates an inclusive gateway.
During modeling, it is worth explicitly asking: are we selecting a path, starting parallel work or waiting for multiple results to come together? The same business statement may conceal different execution rules.
2. Exclusive gateway: when exactly one path is right
An exclusive gateway makes its selection based on existing process data. In procurement, a typical question might be: “Does the requisition value exceed the internal approval threshold?” If it does, managerial approval follows; if not, the requisition proceeds directly.
The conditions on outgoing branches should be defined so that they are mutually exclusive and cover all possible cases. For example, the pair “below the threshold” and “above the threshold” leaves out a value exactly equal to the threshold. A better split is “less than or equal to the threshold” and “greater than the threshold.”
Default branch and rejoining paths
The default branch can be used when none of the other conditions is met. This is not the same as a condition that is always true. For example, it may be useful to route the process to a data completion step if the classification cannot be determined. The data quality issue must still be addressed separately.
If multiple conditions are true simultaneously, XOR still selects only one branch, but business operations should not rely on the engine’s evaluation order. If no condition is true, the process follows the default branch. If there is no default branch either, gateway execution raises an error. If we want to route requisitions with incomplete classifications to a data completion step, we should test this case as well.
A joining XOR gateway does not synchronize. It is suitable for bringing alternative paths back together, but it does not wait for parallel branches to complete. If two arrivals occur, the activity that follows it may start twice.
3. Parallel gateway: when every branch is required
Use a parallel gateway when multiple tasks can be performed independently and all of them are required. For a purchase requisition, for example, Finance checks the budget while Procurement requests quotations. Contract preparation can begin only after both are complete.
A diverging AND gateway activates every outgoing branch; it does not select among them based on conditions. Parallel execution does not necessarily mean people working at the same time: it means the model imposes no sequential dependency between the branches.
A common synchronization pitfall
A converging AND gateway waits for a token from every incoming branch. If an XOR gateway previously selected between two paths, only one starts, and nothing arrives from the other. The join therefore cannot complete during normal execution.
Do not ask how many lines meet at the diamond. Instead, ask: which branches must actually reach this point for the process to continue?
Handling rejection is equally important. If one parallel check rejects the requisition, you must define what happens to the other branch. Does it continue working, do we wait for it, or do we interrupt it in a controlled way? A line leading to a separate end event does not necessarily release a join waiting elsewhere.
4. Inclusive gateway: when multiple conditional branches may be needed
An inclusive gateway is appropriate when several of the possible tasks may be required, but not necessarily all of them. In procurement, a legal review may be needed for a non-standard contract, while an information security review may be required if the service provider will access corporate data.
If both conditions are true, both branches start. If only one is true, only the corresponding task runs. If neither is true, a properly designated default path can allow the process to continue.
An OR join is more complex than an AND join. It does not automatically wait for every incoming branch, but considers which branches can still deliver a token given the current state of the process. In a simple, structured split-and-join pattern, this means waiting for all activated branches.
With loops, nested branches and multiple entry points, this becomes harder to follow. It is therefore advisable to define clear boundaries for the inclusive structure and, where necessary, organize it into a subprocess. Not every diverging gateway must mechanically be paired with a gateway of the same type, but the behavior of any alternative solution must be verified.
The practical test is simple: test cases requiring only a legal review, only a security review, both reviews and neither review. Each case must reach the intended continuation exactly once.
5. Event-based gateway: when we do not yet know the answer
The difference between a data-driven and an event-based decision is timing. XOR evaluates what we already know. An event-based gateway waits for something to happen.
For example, we have sent a request for quotation to the supplier. Either their response arrives or the response deadline expires. After a standard exclusive event-based gateway, an intermediate message catch event and an intermediate timer event can model this race. On the supplier response branch, a receive task named “Receive supplier response” can replace the intermediate message catch event. The timer event on the other branch can be used in either approach. A receive task and an intermediate message catch event cannot both appear among the alternatives belonging to the same event-based gateway.
The first event to occur determines how the process continues. The other alternative waits are canceled at this decision point. However, this does not eliminate the cause of the event in the outside world: the supplier may still send a response after the deadline.
Separate rules are therefore needed to handle late messages and correlate them with the correct process instance. We do not place data conditions on the outgoing branches of an event-based gateway, nor do we place general work tasks immediately after it: the choice is driven by the occurrence of the event.
6. Checklist for reliable execution
In the xFLOWer approach to process design, a diagram is useful when it clarifies execution scenarios as well as business rules. Before handover, it is worth working through the following numbered points:
- Define the decision. Do we need one path, all paths, multiple conditional paths, or are we waiting for a future event?
- Separate work from control flow. Approval is an activity; routing based on its outcome is handled by a gateway.
- Check the conditions. Examine boundary values, missing data and rules that can be satisfied simultaneously.
- Trace the branches. Which branch starts, where does it end, and which join waits for it?
- Test the exceptions. Include scenarios for rejection, timeouts, late messages and repeated execution.
- Check the runtime environment. Knowing BPMN notation is no substitute for checking the specific engine’s support and configuration.
In summary: XOR selects a path, AND starts every branch, OR can activate multiple branches based on conditions, and an event-based gateway lets the next event determine the choice. A correct model always includes planning for joins and exceptions.
Further installments in this series cover examples of BPMN 2.0 elements, the ten most common modeling errors, the differences between BPMN, flowcharts and UML activity diagrams, and the steps for creating an executable process.
Would you like to review the branches in your own process? Consult xFLOWer’s experts and walk through a real approval or procurement process together, from branch activation to synchronization.
This article is part of our comprehensive guide: BPMN 2.0 in practice: a complete guide from modeling to an operational 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.
