BPMN vs Flowchart: When a Diagram Needs to Become a Process
By Kirill Stolbushkin
BPMN vs Flowchart: When a Diagram Needs to Become a Process
A flowchart is a sketch. BPMN 2.0 is a standard. Use a flowchart when one person needs to see steps in order. Use BPMN when work crosses roles, branches on real rules, or has to run. Swimlanes name owners. Typed gateways name decisions. Engines read the XML.
What is the difference between BPMN and a flowchart in business process modeling?
A flowchart shows sequence. Boxes, arrows, a diamond or two. Anyone can read it. Anyone can draw it. That is the point, and also the limit.
BPMN — Business Process Model and Notation, version 2.0, also called Business Process Modeling Notation — is an OMG standard (ISO/IEC 19510). It looks like a flowchart until you need it to mean something. A rectangle is not “a step.” In business process modeling, it is a task with a type: user, service, manual. A diamond is not “a decision.” It is a gateway: exclusive, parallel, or inclusive. A horizontal band is not decoration. It is a lane, and it names who owns the work. For a one-page reference of these shapes, see our BPMN symbols cheat sheet.
The other difference sits under the picture. A flowchart lives as a PNG on a wiki. BPMN is a better way to document process information when the model has to mean something precisely. A BPMN 2.0 model exports as XML a process engine can read. Lucidchart, Miro, Draw.io, and Visio are diagramming tools that help create diagrams. They are good at pictures. They are not a process standard.
Flowchart | BPMN 2.0 | |
|---|---|---|
What it is | An informal sketch | A defined language |
Standard | None. Shapes drift by tool and author. | OMG / ISO/IEC 19510 |
Who does the work | Usually unlabeled | Pools and lanes |
Decisions | A diamond that says “yes/no” | Typed gateways with conditions |
Exceptions | Extra arrows, if you remember them | Timer, error, and boundary events |
What you can export | A picture | XML an engine can read |
Right job | Whiteboard, one-team SOP, a slide | Cross-team work you may later run |
A diagram is a photograph of a car. You can point at it. You cannot drive it.
When should I use BPMN vs a flowchart?
Keep the flowchart when the work is linear, one team owns it, and the picture is the deliverable. A flowchart is fine for simple work, but BPMN is better once complexity rises. You will not automate that this quarter. You do not need a gateway catalog to hang it on a wall.
Move to BPMN when any of these is true:
More than one role touches the work. Invoice approval is not “AP does stuff.” It is AP, a manager, a controller, and sometimes the buyer who raised the PO.
The branch is a rule, not a vibe. Under $5,000, the AP lead signs. Over $5,000, the controller signs. Over $25,000, dual control. A diamond labeled “approved?” does not encode that.
Time is part of the process. Form I-9 Section 2 is due within three business days of the start date. A sticky note that says “follow up” is not a timer event.
The happy path is the least interesting path. Vendor onboarding fails on a missing W-9, a contract stuck in legal, a duplicate vendor master. If your picture only shows the day everything arrives complete, you documented a wish.
Someone will have to rebuild this to run it. That rebuild is the translation tax: analyst draws, developer interprets, QA tests a third version, instead of starting in BPMN and moving more efficiently. By then the process on the floor has already changed.
BPMN gives organizations a clear way to handle cross-role workflow requirements.
You do not graduate from flowcharts. You stop asking a sketch to do a standard's job.
Is BPMN just a fancy flowchart?
No. Shared DNA is not sameness.
A flowchart has no official meaning for “this runs at the same time as that.” People fake it with two arrows leaving one box. BPMN has a parallel gateway. Split means split. Join means join.
A flowchart has no official meaning for “this is a person, this is a system.” I-9 Section 1 is a user task. An E-Verify lookup, if you use it, is a service task. Mix those in one unlabeled rectangle and HR and IT will argue about a picture they both think they understand.
A flowchart has no file an engine will accept. BPMN 2.0 does.
What are the BPMN symbols I actually need for business process diagrams?
You will hear “100+ symbols.” You will use a handful: this is a simple set of BPMN symbols most teams actually need.
Start and end events. One start. Separate ends for “invoice paid” and “invoice rejected.”
Tasks. Verb plus object: “Match invoice to PO,” not “Invoice,” because it is the most effective way to label a task so the action is immediately understandable.
Exclusive gateway (X). Exactly one path. Amount threshold. Approve or reject.
Parallel gateway (+). Work that runs at the same time. In vendor onboarding, finance collects tax forms while legal reviews the MSA.
Inclusive gateway (O). One or more paths. Rare. Do not reach for it first.
Sequence flow vs message flow. Solid arrows inside a pool. Dashed arrows between pools — the vendor sends a W-9. That is a message, not a step inside your company, and the distinction helps visualize who sends what across participants.
Boundary timer. If I-9 Section 2 is still open on day three, escalate. A flowchart puts “3 days??” in a comment box and hopes.
What is a swimlane in BPMN?
A pool is a participant. Your company is a pool. The vendor is a pool. A lane is a role or a common system type inside that pool: AP Clerk, Controller, HR Coordinator, the ERP, or other connected systems.
Read an invoice-approval flowchart without lanes and you will not know whether the three-way match is a person or a batch job. In BPMN the match sits in a system lane, the exception in the buyer's lane, sign-off with the controller when the amount requires it. The handoff is the process. Swimlanes keep everyone on the same page about ownership.
If you cannot name the lane, you cannot name the owner. You have a drawing, not a process.
How do I turn a flowchart into BPMN?
Do not redraw the same boxes in a BPMN stencil and call it done. A proper conversion should create a real business process diagram, not just a prettier sketch. That is still a flowchart wearing a badge.
Write the trigger and the outcomes. Invoice received. Vendor request submitted. First day of employment. Then the real ends: paid, rejected, I-9 complete, I-9 escalated.
List roles, then make lanes. Not “Finance.” AP Clerk, AP Lead, Controller. Not “HR.” Coordinator, hiring manager.
Keep the happy path. Translate each box to a task so the first pass stays easy to follow. Do not add exceptions yet.
Replace every diamond with a typed gateway. Exclusive if one path. Parallel if work forks. Label flows with the rule: “Amount > $5,000,” “W-9 missing,” not “Yes.”
Add what the flowchart omitted. Three-way match fails. Contract redlines. Section 1 incomplete. Put a timer on any deadline.
Check the file, not the screenshot. Export BPMN 2.0 XML. Image-only export or import is not enough. PNG, SVG, or a slide means you are still in diagramming.
You can do that by hand in a modeler. Vevos is a solution provided to create BPMN 2.0 models from plain English. You can also describe the process in plain English and let Vevos generate a BPMN 2.0 model that features lanes, gateways, and documentation. Intro is $0, and three process models are included with no credit card. If you later want a live app from the signed-off model, Conductor starts on Tempo at $199/month. Modeling and deploying are not the same plan.
Is a BPMN diagram executable?
A valid BPMN 2.0 model can be. A picture of BPMN shapes cannot.
Executable means the XML names the task, the lane, the gateway condition, and what happens when a timer fires, which ensures the model can be interpreted correctly by an engine. Vevos, Camunda, Signavio, and other engines speak that file. Engine support matters when teams want models that can run across real systems. Your Miro board does not.
Most “BPMN” in a diagramming tool will not run. Treat “we have it in Lucidchart” as “we have a picture,” until someone produces a .bpmn file and an engine accepts it. Starting in BPMN means you do not throw the diagram away and begin again in a developer's head. The model is the spec.
Stop drawing. Start executing.
If the artifact has to explain the work to a new hire, a flowchart is honest. If it has to survive a handoff, an audit, or a build, it has to become a process.
Describe invoice approval, vendor onboarding, or I-9 the way you would to a colleague. Vevos returns BPMN 2.0 — lanes, gateways, the exception paths a whiteboard skips.
Free to model · No credit card required
What is BPMN 2.0 (Business Process Modeling Notation)?
BPMN 2.0 is the OMG standard (ISO/IEC 19510) for modeling business processes. It defines tasks, events, typed gateways, pools, lanes, and XML that engines can read, and it is used to visualize and document business processes with standard rules. It is a language with rules, not a stencil pack.
What is the difference between BPMN and a flowchart?
A flowchart is an informal sketch of steps. BPMN 2.0 is a standard: swimlanes for ownership, typed gateways for decisions, events for time and errors, and XML a process engine can read. Use a flowchart to explain. Use BPMN to define.
When should I use BPMN vs a flowchart?
Use a flowchart for a linear, single-team procedure. Use BPMN when more than one role is involved, when it is the better choice for complex processes with real business rules, when branches are real rules, when deadlines matter, or when you may automate. Invoice approval, vendor onboarding, and I-9 all cross that line.
Is BPMN just a fancy flowchart?
No. BPMN adds task types, exclusive vs parallel vs inclusive gateways, message flows between participants, and a file format engines understand. Looking similar is not being the same.
Can I convert a flowchart to BPMN?
Yes. Keep the happy path. Put each role in a lane. Replace diamonds with typed gateways. Add the exception and timer paths the sketch left out. Export BPMN 2.0 XML, not a PNG. Pasting boxes into a BPMN shape library is not a conversion.
Is a BPMN diagram executable?
A complete BPMN 2.0 model can be, because the XML carries the semantics. A screenshot of BPMN-looking shapes cannot. A valid model can also link process logic to engine behavior more reliably than a static picture. Lucidchart, Miro, Draw.io, and Visio produce pictures. Execution needs the standard's file.
Do I need all 100+ BPMN symbols?
No. Most operational processes need start and end events, tasks, exclusive and parallel gateways, sequence and message flows, pools, lanes, and the occasional timer. Learn those. Ignore the rest until a real case demands it.
What is a swimlane in BPMN? Pool vs lane?
A pool is a participant — your company, a vendor, a new hire. A lane is a role or system inside that pool — AP clerk, controller, HR coordinator. Swimlanes make ownership and handoffs visible. Flowcharts usually leave that unlabeled.
Does Lucidchart export BPMN 2.0 XML?
Treat Lucidchart, Miro, Draw.io, and Visio as diagramming tools. They can look like BPMN because they ship a shape library. Their drag and drop editing is useful for presentations, but it does not by itself produce a standards-compliant BPMN file. The standard is the XML and the semantics, not the resemblance. If you cannot hand an engine a .bpmn file, you still have a picture, for example a polished diagram that still is not executable.
Related blog posts
- Business Process Examples: 30+ Processes Every Department Runs, With Steps and Owners — 31 business process examples grouped by department, from HR onboarding and invoice approval to lead routing, content approval, access requests, contract approval, and work orders, each with an owner and the main steps, plus how to pick your first one to map.
- Property Management Processes: How Property Managers Map Leasing, Rent, Maintenance, and Move-Outs — The 8 core property management processes, from tenant application and lease signing to rent, maintenance, vendor invoices, renewals, and move-out: who does what between owner, property manager, and tenant, what to automate, and how to map one.
- Customer Service Processes: How Support Teams Map Intake, Triage, Escalation, and Refunds — The customer service processes every support team runs, from intake and triage to routing, escalation, SLA breaches, refunds, complaints, bug handoffs, and the feedback loop: steps for each, what to automate, what needs a person, and how to map one.