BPMN
BPMN Gateways Explained (with examples)

Thom Uffing

BPMN gateways determine the route through a process. They are the diamond-shaped decision points that decide which path a process follows, or that split and merge paths. In this guide we walk through the most important gateways, with a concrete example for each type.
Without gateways, a BPMN diagram is just a straight line. It is the gateways that make choices and parallel flows explicit. That is why this is the part every realistic process needs.
What is a gateway in BPMN?
A gateway is a diamond and steers the flow of a process. It does two things: split (one path becomes several) or merge (several paths become one). The symbol inside the diamond tells you which type of gateway it is and which logic applies.
Important: a gateway does not make a decision itself. It routes based on data or events determined earlier in the process.
Exclusive gateway (XOR)
The exclusive gateway, a diamond with an X, chooses exactly one path. Based on a condition, the process goes one way or the other, never both.
Example: after "Review request" an exclusive gateway checks whether the amount is below €1,000. If yes, then "Approve automatically" follows. If no, then "Manual review" follows. Exactly one route is always chosen.
Parallel gateway (AND)
The parallel gateway, a diamond with a plus (+), activates all paths at once. There is no condition; all outgoing flows start simultaneously.
Example: after "Order confirmed" a parallel gateway starts "Create invoice" and "Notify warehouse" at the same time. Both happen in parallel. A second parallel gateway further on waits until both are done before the process continues (synchronization).
Inclusive gateway (OR)
The inclusive gateway, a diamond with a circle (O), chooses one or more paths. Every condition that is true is followed.
Example: after "Check customer profile" an inclusive gateway can activate both "Send email" and "Send SMS", depending on the customer's preferences: one of the two, or both.
Event-based gateway
The event-based gateway chooses a path based on which event happens first, rather than on data.
Example: after "Quote sent" the process waits for a response. Does an "Approval received" arrive? Then signing follows. Does the 14-day timer expire first? Then a reminder follows. The first event determines the route.
From gateways to a complete diagram
Choosing the right gateway is a craft: a wrong choice makes a process illogical or incomplete. Drawing and checking that by hand takes time.
With ModelMatic you turn a conversation or description automatically into a validated BPMN 2.0 diagram, with the gateways in the right place. New to the notation? Start with What is BPMN? and BPMN symbols.
Conclusion
Gateways are the steering wheel of every BPMN process. With the exclusive (choose one), parallel (do everything at once), inclusive (choose one or more) and event-based (first event wins), you cover almost any process decision.
BPMN is maintained by the Object Management Group and standardized as ISO/IEC 19510:2013. You can find the full definition of every gateway in the OMG BPMN 2.0 specification and a friendly overview at bpmn.org. Start small and let AI create the first diagram for you.




