BPMN Glossary

By Nikhil Gupta

BPMN Glossary

BPMN (Business Process Model and Notation) is an open standard, maintained by the Object Management Group (OMG), for drawing business processes so that business people and technical teams read them the same way. BPMN 2.0 is the current version. This glossary explains each core term in one or two sentences, with an example.

Activity

Work performed in a process. Activities are either tasks (one unit of work) or subprocesses (a group of tasks). Example: "Review invoice."

Task

A single unit of work, drawn as a rounded rectangle. Common types include user task (a person does it), service task (a system does it), and manual task (done outside any system). Example: user task "Approve expense claim."

Subprocess

An activity that contains its own detailed process. It can be shown collapsed (with a "+" marker) or expanded. Example: "Background check" containing several verification steps.

Event

Something that happens during a process, drawn as a circle. There are three kinds: start, intermediate, and end events.

Start event

Where a process begins, drawn as a thin circle. Example: "Order received."

End event

Where a path of the process finishes, drawn as a thick circle. A process can have several end events. Example: "Order shipped" or "Order cancelled."

Intermediate event

Something that happens between start and end, drawn as a double circle. Examples include waiting for a message, a timer, or an error.

Timer event

An event triggered by time, such as a deadline, delay, or schedule. Example: "48 hours without approval → escalate."

Message event

An event triggered by receiving or sending a message from another participant. Example: "Customer reply received."

Gateway

A decision or branching point, drawn as a diamond. Gateways control how the flow splits and merges.

Exclusive gateway (XOR)

Exactly one path is taken, based on a condition. Drawn as a diamond, optionally with an "X." Example: "Amount over $5,000?" → Yes / No.

Parallel gateway (AND)

All paths are taken at the same time, and later merged. Drawn as a diamond with a "+." Example: IT provisioning and manager preparation happen in parallel.

Inclusive gateway (OR)

One or more paths are taken, depending on conditions. Drawn as a diamond with an "O." Example: notify Legal and/or Finance depending on contract type.

Event-based gateway

The path is chosen by whichever event happens first. Example: customer replies, or 7 days pass, whichever comes first.

Sequence flow

A solid arrow showing the order of activities within one participant's process.

Message flow

A dashed arrow showing communication between separate participants (pools). Example: the company sends a quote to the customer.

Pool

A participant in a process, such as an organization, a customer, or an external system. Each pool contains its own process. Example: "Your company" and "Vendor" as two pools.

Lane (swimlane)

A subdivision of a pool, usually a role or department, showing who does each task. Example: HR, IT, and Manager lanes inside "Your company."

Pool vs lane

A pool is a separate participant; communication between pools uses message flows. A lane is a role inside one participant; work between lanes uses sequence flows.

Data object

Information that an activity needs or produces, drawn as a page with a folded corner. Example: "Purchase order."

Artifact / annotation

Extra information that doesn't affect the flow, such as text annotations or groups.

BPMN XML

The file format that stores a BPMN 2.0 model, so models can be exchanged between BPMN tools and, in some cases, executed by process engines.

BPMN vs flowchart

A flowchart shows steps and decisions informally. BPMN is a standard with defined meanings for each symbol, covering roles, events, messages, parallel work, and exceptions, so anyone trained in BPMN reads the model the same way, and tools can validate or execute it.

Happy path

The ideal route through a process with no exceptions. Good BPMN models also show the exception paths: rejections, delays, and errors.

Process model vs process map

Often used interchangeably. A process map usually means a visual overview. A process model usually means a more formal, standards-based representation, such as BPMN, that can be analyzed or automated.

Practice with real BPMN

The fastest way to learn BPMN is to see your own process in it. Describe a process at vevos.ai/free and Vevos generates a BPMN 2.0 model using these elements. Then ask it to explain any symbol.