# Core BPMN Element Subset

**In short:** Most BPMN models need only a small part of the notation. A study of 120 diagrams found that analysts share a small set of constructs. Using that core set eases modeling and reading.

## Explanation

BPMN (Business Process Model and Notation) offers many symbols. Real models use few of them. Zur Muehlen and Recker (2008) studied 120 BPMN diagrams. They found that analysts use only a small, commonly shared share of the constructs. They suggested that narrowing the language could ease modeling.

A core subset is a practical answer. You pick the elements most models need. You leave the rest out unless a case demands them.

**What the core usually contains**

- **Sequence flow.** An arrow between two elements. It sets the order of steps in the process.
- **Tasks.** Atomic units of work. You combine them to produce a meaningful result.
- **Events.** A process can catch an event, which means it reacts. It can also throw an event, which means it emits one.
- **Subprocesses.** Containers for common functionality.
- **Pools and lanes (swim lanes).** They exist only at the top level of a process or collaboration. You cannot place them inside a subprocess.

For the elements themselves, see BPMN Core Elements, BPMN Swimlane (Pool and Lane) and BPMN Event.

**Readability matters more than symbol variety**

A small subset helps stakeholders who are not modelers. Camunda names well-chosen labels as the single most important factor for readable models. A small symbol set with clear labels is easier to follow than a rich symbol set with vague names.

## Example

A team models an order-handling process. They use one pool with two lanes, "Sales" and "Warehouse". They draw a start event, three tasks, sequence flows between them and an end event. One group of steps sits in a subprocess. They add no other symbols. A business reader can follow the diagram without learning extra notation.

## Trade-offs

A small subset makes models easier to create and read. The facts here do not say which exact elements fall outside the core, or how rarely they occur. Check whether a case needs an element outside the subset before you leave it out.

BPMN diagram: [A small process using only core elements: pool, lanes, start and end events, tasks, a subprocess and sequence flows.](https://arc.fuet.ch/diagrams/concepts/modeling-bpmn/bpmn-element-usage-frequency/diagram-1.bpmn)

## Checks

- The document states which BPMN elements the models use, and the set stays small.
- Process steps are labeled with well-chosen, meaningful names.
- Swim lanes appear only at the top level, not inside subprocesses.

## Related

- [BPMN Core Elements](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-core-elements.md)
- [BPMN Swimlane (Pool and Lane)](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-swimlane-pool-and-lane.md)
- [BPMN Event](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-event.md)
- [BPMN Activity](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-activity.md)
- [BPMN Modeling Guidelines](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-modeling-tips.md)
- [BPMN 2.0 Notation](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-2-0-notation-overview.md)
- [Process Model Complexity](https://arc.fuet.ch/concepts/modeling-bpmn/process-model-complexity.md)
- [BPMN 2.0 Model Quality](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-2-0-model-quality.md)

## Sources

- [How much language is enough? Theoretical and practical use of the business process modeling notation - Stevens Institute of Technology](https://researchwith.stevens.edu/en/publications/how-much-language-is-enough-theoretical-and-practical-use-of-the-/) — researchwith.stevens.edu, accessed 2026-11-09
- [BPMN primer | Camunda 8 Docs](https://docs.camunda.io/docs/components/modeler/bpmn/bpmn-primer/) — docs.camunda.io, accessed 2026-11-08
- [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