BPMN — Business Process Model and Notation — is the worldwide standard for drawing how work actually gets done, one step at a time, in a way that both business people and software can understand.
BPMN is a visual language for business processes. It gives you a fixed set of shapes — circles, rounded rectangles, and diamonds — connected by arrows, so that anyone can read a diagram and understand what happens, in what order, and who is responsible.
The standard is maintained by the Object Management Group (OMG), the same body behind UML. The current version, BPMN 2.0, has been the de-facto standard since 2011 and is supported by virtually every serious process and workflow tool.
Every organization runs on processes: onboarding an employee, approving an invoice, handling a support ticket, fulfilling an order. For years, teams described these in whatever way they liked — a paragraph of text, a slide with boxes, a whiteboard photo. The problem is that everyone drew them differently, so a diagram made by the finance team was unreadable to IT, and vice versa.
BPMN was created to solve exactly that. It is a common notation: a shared alphabet of symbols with agreed meanings. When a symbol means the same thing in Warsaw, São Paulo and San Francisco, a process map stops being a personal sketch and becomes documentation an entire organization — and its software — can rely on.
Typical moments to reach for BPMN: documenting an existing procedure, redesigning a workflow, preparing for automation, aligning stakeholders before a project, or training a new team member.
You can read most BPMN diagrams knowing just four families of symbols:
| Element | Looks like | Means |
|---|---|---|
| Event | Circle | Something happens — a start, an end, a message received, a timer firing. |
| Activity / Task | Rounded rectangle | A unit of work someone or something performs, e.g. "Approve invoice". |
| Gateway | Diamond | A decision or branch point that splits or merges the flow, e.g. "Payment received?". |
| Flow | Arrow | The sequence — which step follows which. |
Two more you'll see constantly: Pools and Lanes (swimlanes) split the diagram by participant, so you can see who does what — the customer in one lane, the sales team in another, a system in a third.
Want the full picture? See the guide to BPMN symbols and elements.
They look similar, but the difference matters:
| Flowchart | BPMN | |
|---|---|---|
| Rules | None — draw however you like | A formal, versioned standard |
| Symbol meaning | Ambiguous, varies by author | Precise and universal |
| Multiple participants | Hard to show | Built in via pools & lanes |
| Events & messages | Not distinguished | First-class concepts |
| Machine-executable | No | Yes — engines can run it |
A flowchart is fine for a quick personal sketch. BPMN is what you use when the diagram has to be understood — and trusted — by other people and systems.
You don't have to master the notation before you start. The fastest route is to describe your process in plain language and let AI draft the BPMN for you, then adjust it:
Learn more about turning text into a BPMN diagram with AI, or browse ready-made BPMN examples.
Describe any process in plain English and get a BPMN 2.0 diagram in seconds. Free.
Open the BPMN GeneratorBusiness Process Model and Notation — a standardized graphical notation, maintained by the OMG, for drawing a business process from start to finish.
A flowchart has no fixed rules; BPMN is a strict standard where every symbol has a defined meaning, participants get their own swimlanes, and the diagram can be executed by a process engine.
No. Describe your process in plain language, generate a valid BPMN 2.0 diagram automatically, then refine it. The core symbols take minutes to learn.