# BPMN Layout Guideline

**In short:** A BPMN layout guideline is a set of drawing habits that make process diagrams easy to read: one flow direction, few crossings, no very long arrows, and clearly marked gateways.

## Explanation

A BPMN diagram shows a business process as boxes and arrows. A layout guideline says how to arrange those shapes on the page. Related articles: BPMN Modeling Guidelines, BPMN Gateway, and Link Event.

**Pick one direction.** Camunda recommends modeling from left to right. This matches the reading direction of a western audience. Trisotech adds a convention for line types. Sequence flows run horizontally. Message flows and data associations run vertically.

**Keep lines short and apart.**
- Avoid flows that cross each other. Trisotech says minimizing crossings eases reading.
- Avoid flows that cross many pools or lanes where possible.
- Avoid very long sequence flows, especially ones that run against the reading direction. A link event can replace such a flow.

**Draw gateways explicitly.**
- Always draw the X marker on an XOR gateway, even if your tool allows a blank one.
- Join alternative paths with an explicit XOR merge gateway. Do not mix split and join meaning in one symbol.
- Place split and join gateway pairs symmetrically.

**Name things consistently.** Camunda also recommends naming conventions. Labels then convey the business meaning in the same way throughout.

**Readability wins.** Camunda says not to be dogmatic. If breaking a rule makes the model clearer, aim for the most readable model.

## Example

Imagine an order process. It starts at the left with "Receive order". An XOR gateway with an X splits it into "Standard shipping" and "Express shipping". Both paths run left to right. An explicit XOR merge gateway, placed symmetrically to the split, joins them before "Send invoice". No arrows cross, and no arrow loops back across the whole page. A reader follows the process from left to right.

## Trade-offs

The rules are not absolute. Camunda says explicit modeling should not be dogmatic. A symmetric gateway pair or a short crossing may sometimes hurt readability more than it helps. In that case, choose the clearer diagram.

BPMN diagram: [Left-to-right order process with an explicit XOR split and a matching XOR merge before the shared task.](https://arc.fuet.ch/diagrams/concepts/modeling-bpmn/bpmn-layout-guideline/diagram-1.bpmn)

## Checks

- Process diagrams are modeled in one consistent direction, such as left to right.
- Sequence flows do not cross each other, and very long flows are avoided or replaced by link events.
- Every XOR gateway shows the X marker.
- Alternative paths are joined with an explicit XOR merge gateway.
- Naming conventions for BPMN elements are defined and applied.

## Related

- [BPMN Modeling Guidelines](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-modeling-tips.md)
- [BPMN Gateway](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-gateway-semantics.md)
- [Link Event](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-link-event.md)
- [BPMN 2.0 Model Quality](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-2-0-model-quality.md)
- [BPMN Gateway Mismatch Antipatterns](https://arc.fuet.ch/concepts/modeling-bpmn/antipatterns-for-process-flows.md)
- [BPMN Connecting Object](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-connecting-object.md)
- [BPMN Swimlane (Pool and Lane)](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-swimlane-pool-and-lane.md)
- [BPMN 2.0 Notation](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-2-0-notation-overview.md)

## Sources

- [Creating readable process models | Camunda 8 Docs](https://docs.camunda.io/docs/components/best-practices/modeling/creating-readable-process-models/) — docs.camunda.io, accessed 2026-11-09
- [BPMN Modeling Best Practices :: BPMN Quick Guide](https://cloud.trisotech.com/bpmnquickguide/bpmn-quick-guide/bpmn-modeling-best-practices.html) — cloud.trisotech.com, accessed 2026-11-09