The BPMN 2.0 notation system
BPMN (Business Process Model and Notation) 2.0 defines a precise set of symbols for modeling business processes. Unlike a flowchart, where a diamond could mean anything, a BPMN diamond with a specific marker means a specific gateway type with defined behavior. The symbol set is organized into five categories: flow objects (events, gateways, activities), connecting objects (sequence flow, message flow, association), swim lanes (pools, lanes), artifacts (data objects, groups, annotations), and participants. Understanding the symbol vocabulary lets you read any BPMN diagram and produce diagrams that can be imported into process automation tools like Camunda, Flowable, or jBPM.
How to create a bpmn notation diagram with AI
flow-chart.io generates bpmn notation diagrams from plain language in four steps. No notation knowledge required — describe what you need and the AI handles the symbols, layout, and relationships.
Describe what you need
Open flow-chart.io and type a plain-language description of the bpmn notation diagram you want. Name the key actors, systems, steps, or relationships. The more specific your description, the more accurate the generated diagram — but even a rough outline produces a solid first draft. You do not need to know any syntax or notation rules.
Review the generated diagram
The AI generates a fully editable diagram in seconds, using the correct notation for your domain. Review the nodes, connectors, and labels. Check that the relationships are accurate and the layout is readable. The diagram is a scene graph — every element is an independent object, not a flat image.
Edit any element directly
Click any node to rename it, change its type, or update its style. Drag nodes to reposition them. Add new nodes by describing what to add in the refinement panel. Remove elements you do not need. The AI can also refine the diagram for you: "add an error handling path," "split this step into two," "change the data store to a cloud icon."
Export in the format you need
Export the finished diagram as SVG for web and design tools, PNG at 2× or 4× resolution for presentations and documentation, PDF for print and client deliverables, JSON to version-control the editable scene graph alongside your code, or Mermaid (.mmd) to embed the diagram as text in GitHub or Notion.
What you can create
When to use bpmn notation diagrams
The following situations are the highest-value applications for bpmn notation diagrams in professional environments. Each represents a context where a well-constructed diagram reduces miscommunication, speeds decision-making, or produces a deliverable that would otherwise take hours to create manually.
- Learning BPMN: identify unknown symbols while reading a BPMN diagram
- Modeling a process that will run in a BPMN engine like Camunda or Flowable
- Compliance documentation: processes that require formal notation for audit
- Converting an informal flowchart to a standards-compliant BPMN diagram
- Teaching BPMN to a team or in a training session
In each case, the diagram is not decoration — it is the primary artifact that the team or stakeholder actually uses to make a decision, approve a design, or onboard a new member.
Best practices for bpmn notation diagrams
Experienced practitioners consistently apply a small set of principles that separate diagrams people actually use from ones that get ignored after the meeting. Apply these to every bpmn notation diagram you create.
- Start with the happy path — the primary successful flow through the bpmn notation — before adding error handling, edge cases, and alternative routes. A diagram that shows the happy path clearly is immediately useful; one that tries to show every edge case first becomes unreadable.
- Name every element specifically. "Process order" is more useful than "Process" and "Validate payment with Stripe" is more useful than "Payment validation." Specific names let readers understand the diagram without needing a separate explanation.
- Use the right level of detail for your audience. A bpmn notation diagram for a business stakeholder should show roles and outcomes, not implementation details. A diagram for engineers should show system boundaries, technologies, and data flows. When in doubt, create two versions.
- Export a JSON copy of every diagram you want to maintain over time. The JSON export contains the complete typed scene graph — you can re-import it to continue editing after weeks or months. This is your version-controllable source of truth.
AI bpmn notation generation vs. manual diagramming
Both approaches produce editable diagrams, but they differ significantly in where time is spent and what expertise is required. Use this comparison to decide which approach fits your team's workflow.
| Aspect | flow-chart.io (AI) | Manual diagramming |
|---|---|---|
| Time to first draft | Under 60 seconds from a plain-language description | 20–60 minutes drawing and connecting shapes |
| Notation accuracy | Standards enforced automatically (gateway rules, C4 zoom levels, ERD cardinality) | Depends on practitioner knowledge; violations are common |
| Editability | Every element is a live object — click to edit any node or connector | All elements are already individually editable by design |
| Iteration speed | Describe the change in plain language; AI updates the diagram in seconds | Manual drag, delete, and reconnect for each change |
| Export formats | SVG, PNG 2×/4×, PDF, JSON, Mermaid — all from one click | Depends on the tool; some require additional steps per format |
| Learning curve | None — describe in English, AI handles notation | Notation-specific for each diagram type (BPMN, UML, C4) |
Related guides
These guides cover diagram types that are commonly used alongside bpmn notation diagrams, or that share similar audiences and use cases.
Frequently asked questions
- What is the difference between a BPMN start event and an end event?
- A start event is a circle with a thin border — it marks where a process instance begins. An end event is a circle with a thick border — it marks where a process path terminates. A process can have multiple end events (representing different outcomes: Order Fulfilled, Order Cancelled, Payment Failed). Each end event represents a distinct final state. Intermediate events (double-border circles) happen between start and end — they catch or throw signals, timers, messages, or errors mid-process.
- What is the difference between an XOR gateway and an AND gateway?
- An XOR (exclusive) gateway (diamond with X) takes exactly one of its exit paths, based on which condition is true. Only one path executes. An AND (parallel) gateway (diamond with +) takes ALL exit paths simultaneously — it creates parallel branches that all execute concurrently. An OR (inclusive) gateway (diamond with circle) takes one or more exit paths depending on which conditions are true — it is more flexible than XOR but more complex to reason about.
- When do I use a pool vs. a lane in BPMN?
- A pool represents one participant in the process — typically one organization, system, or role that has complete control over its internal process. Lanes divide a pool into sub-participants: departments, roles, or systems within that participant. Use multiple pools when two separate organizations collaborate (a customer and a supplier). Use lanes when multiple people within one organization handle different steps of the same process.
- What is a BPMN event-based gateway?
- An event-based gateway (diamond with a circle and pentagon inside) pauses the process and waits for one of several events to occur — whichever event arrives first determines which path is taken. It is used to model waiting behavior: 'wait for customer approval or for the 24-hour timer to expire, whichever comes first.' The paths after an event-based gateway always start with intermediate catch events (timer, message, signal).
- What is a BPMN message flow?
- A message flow is a dashed line with an open arrowhead used to show communication between two separate pools (participants). It represents information or data exchanged between organizations or autonomous systems — for example, a Purchase Order sent from a Buyer pool to a Supplier pool. Message flows cannot cross within a single pool; they always connect two different participants. Within a pool, sequence flow (solid arrows) is used instead.