# Levels of Process Modeling

**In short:** Process models work best in levels. The top level shows the big picture, the middle level breaks it into subprocesses, and the lowest level shows detailed activities. Each level suits a different audience.

## Explanation

A large process model is hard to read on one page. Splitting it into levels keeps each page understandable. Higher levels simplify. Lower levels add activities, decisions and handoffs between parties.

**The levels**

- **Level 1** breaks the value chain into major end-to-end processes.
- **Level 2** breaks each process into meaningful subprocesses. A subprocess is a part of a process that has its own detail.
- **Level 3** shows detailed activity sequences, decisions, handoffs and responsibilities.

**Decomposition**

Subprocess detail moves into child diagrams. A child diagram can contain further subprocesses, each with its own child diagram. Real end-to-end models can therefore nest over many levels. In many tools, each diagram sheet matches one process level.

**Roles apply at every level**

The top-level diagram should show every participant, drawn as a pool. This includes external parties. A pool is a BPMN shape for one participant (see BPMN Swimlane (Pool and Lane)). Readability and traceability must hold from top to bottom. That includes the choreography, meaning the exchanges between the pools.

**Linking levels in BPMN**

- A collapsed subprocess is drawn as a small box that links to a separate child diagram. Silver prefers this form. The expanded form mixes parent and child on one diagram, and Silver rarely uses it.
- A call activity invokes an independently defined process. That process can be reused. The child level of a subprocess is only a diagram fragment and is not reusable.
- Camunda also describes call activities as reusable subprocesses.

**Choosing the level for the audience**

Leadership usually needs a high-level view of major processes. Analysts need detailed maps. Pick the level that fits the reader.

## Example

A company models its order handling. The top-level diagram shows the customer, the company and an external carrier as pools, with a few large steps between them. One of those steps, "Fulfill order", is a subprocess. Its child diagram lists the detailed activities and decisions. One step in that child diagram, "Check payment", calls a separate payment process that other processes also use. Leadership reads the top diagram. Analysts read the child diagrams.

## Trade-offs

Levels keep each diagram readable, but the reader must move between several diagrams to see the whole flow. Choreography between pools must stay traceable across all of them, which takes care. Collapsed subprocesses keep levels apart, but their child diagrams cannot be reused. A call activity gives reuse, but it needs a separately defined process.

BPMN diagram: [A top-level process with a subprocess (child level with its own activities) and a call activity that invokes a reusable process.](https://arc.fuet.ch/diagrams/concepts/modeling-bpmn/levels-of-process-modeling/diagram-1.bpmn)

## Checks

- The top-level end-to-end diagram shows all participating pools, including external parties.
- Readability and traceability, including the choreography between pools, hold from the top level to the bottom level.
- Subprocess detail sits in separate child diagrams reached through collapsed subprocesses, not mixed into the parent diagram.
- Processes reused in several places are modeled as call activities that reference an independently defined process.
- The level of detail of each diagram fits its audience, with high-level views for leadership and detailed maps for analysts.

## Related

- [BPMN Swimlane (Pool and Lane)](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-swimlane-pool-and-lane.md)
- [BPMN Activity](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-activity.md)
- [BPMN Collaboration Diagram](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-collaboration-diagram.md)
- [Process Model Complexity](https://arc.fuet.ch/concepts/modeling-bpmn/process-model-complexity.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)
- [Unclear Level of Abstraction Antipattern](https://arc.fuet.ch/concepts/documentation/unclear-level-of-abstraction-antipattern.md)
- [Capturing Business Behavior via Process Modeling](https://arc.fuet.ch/concepts/modeling-bpmn/capturing-business-behavior-via-process-modeling.md)

## Sources

- [Business Process Mapping Levels - SAP Signavio](https://www.signavio.com/wiki/process-discovery/business-process-mapping-levels/) — signavio.com, accessed 2026-11-09
- [BPMS Watch: Organizing Complex BPMN Models | BPMInstitute.org](https://www.bpminstitute.org/resources/articles/bpms-watch-organizing-complex-bpmn-models/) — bpminstitute.org, accessed 2026-11-09
- [BPMN Call Activity vs Subprocess: What's the Difference?](https://www.trisotech.com/bpmn-call-activity-vs-subprocess-whats-the-difference/) — trisotech.com, accessed 2026-11-09
- [Call activities | Camunda 8 Docs](https://docs.camunda.io/docs/components/modeler/bpmn/call-activities/) — docs.camunda.io, accessed 2026-11-09