BPMN Gateways Explained: Choose, Split, Wait, React

Exclusive? Parallel? Inclusive? Event-based? Gateways decide how your process branches and rejoins. This quick read shows when to use each type in a BPMN diagram, gives small real-world examples, and highlights the pitfalls that trip up even seasoned modelers.

Exclusive Gateway (XOR)

An exclusive gateway allows exactly one outgoing path. This is the point where only a single answer can be valid — yes or no, approve or reject.

Example:

A travel-request process checks the requested amount. If the cost is €1,000 or less, the system auto-approves. If it's higher, the request routes to a manager. Because only one outcome should ever fire, the exclusive gateway is the perfect fit.

Common pitfall:

Forgetting to add explicit conditions on each outgoing flow. Without them, the process may stall.

Parallel Gateway (AND)

A parallel gateway splits — or later joins — the flow into all paths simultaneously. Use it when several tasks must happen in parallel.

Example:

Onboarding a new employee often triggers three parallel streams:

• IT prepares a laptop


• HR drafts paperwork


• Facilities assigns a desk

All three tasks run independently, then converge before the welcome email is sent.

Common pitfall:

Adding conditions. Parallel gateways are unconditional.

Inclusive Gateway (OR)

An inclusive gateway activates one or more outgoing paths, depending on which conditions hold true.

Example:

During order processing, an online store evaluates promotions:

• If the total is more than €200, the customer gets free shipping.


• If they also possess a valid coupon, a discount applies.

Either rule can fire independently, or both can trigger together.

Common pitfall:

Forgetting to add explicit conditions on each outgoing flow.

Event-Based Gateway

Unlike condition-driven gateways, an event-based gateway waits for whichever external event occurs first, then follows that path.

Example:

After sending a follow-up email, a support workflow pauses.

• If the customer replies, the ticket closes.


• If 48 hours pass with no response, a reminder email goes out.

The gateway listens for both events but commits to the first one that arrives.

Common pitfall:

Placing tasks or throwing events directly after the gateway. Only catching message, timer, signal, or condition events are allowed as immediate successors.

Choosing the Right Gateway — A Quick Memory Hook

• 
  Exclusive → one path: think "choose"
  


• 
  Parallel → every path: think "do simultaneously"
  


• 
  Inclusive → one or many paths: think "pick any that apply"
  


• 
  Event-based → first event: think "wait and react"
  

Wrapping Up

Choosing the right gateway is less about diagram aesthetics and more about keeping your process healthy.

• 
  Exclusive handles one-way choices


• 
  Parallel fires everything at once


• 
  Inclusive covers any mix of conditions or choices


• 
  Event-based waits for the first trigger

Keep those four ideas straight, and you'll prevent most of the race conditions, bottlenecks, and dead ends that haunt workflows.

👉 Explore all gateway types in the BPMN Element Reference