Business process flowchart: document how work gets done

A business process flowchart is a diagram of an end-to-end business procedure — from the event that triggers it to the outcome — so the process can be reviewed, trained on and audited. It is the artifact you point auditors, new hires and cross-team partners at when they ask "how does this actually work?".

Unlike a workflow flowchart, which zooms in on hand-offs between people, a business process flowchart takes the whole procedure as its subject. Order-to-cash, procure-to-pay and hire-to-retire are the classic examples — long-running processes that touch several teams, several systems and often several months of elapsed time.

What belongs in a business process flowchart

• Trigger. The event that starts the process (customer submits form, invoice arrives, month closes).
• Owner. The role or team accountable for the outcome — noted in the chart title or the first shape.
• Steps and decisions. Every meaningful action and branch, in order.
• Systems of record. When a step reads or writes to a specific system (CRM, ERP, ticketing tool), name it. Auditors and integrators need this.
• Outcome. What "done" looks like — a shipped order, a paid invoice, a closed ticket.
• Exceptions. The one or two "unhappy paths" that happen often enough to matter (refund, escalation, rejection).
• Controls. For regulated processes, mark the steps where a control is enforced (segregation of duties, approval threshold, mandatory review).

A concrete example: invoice approval

A typical invoice-approval business process flowchart begins with "Invoice received" and ends with "Invoice paid and archived". In between it captures the AP clerk logging the invoice, the match against the purchase order, a routing decision by amount (manager for under $5,000, manager plus finance director above), the payment scheduling and the archive step. The exception branch — "no PO match, query supplier" — is on the same chart, because it happens often enough that leaving it off would misrepresent the process. The full step list is on the examples page.

How to keep it useful

Business process flowcharts fail for the same reasons every time: they get too long, they use custom notation nobody understands, or they never get updated. Three habits fix all three:

1. Cap each chart at one page. Break long processes into a top-level chart plus linked sub-processes. A reader who needs to zoom to read a label will not read the chart.
2. Stick to standard symbols. Rectangle, diamond, rounded rectangle, arrow. Add complexity only when reviewers ask. The full set lives on the symbols page.
3. Store the source, not just the image. If your chart was generated from a list of steps, keep the list — editing text is faster than editing shapes, and it also survives a switch of drawing tools.

Common pitfalls

• Documenting the ideal. The chart has to reflect what actually happens, including the workarounds. Save the "should" version as a separate to-be diagram.
• Hiding the exceptions. If 20% of invoices go through the exception branch, the exception branch is not an exception — it is a second path and deserves equal weight.
• Mixing SOP prose with the chart. Keep the diagram lean and put the detailed policy in a linked SOP. Trying to fit both into shapes makes the chart unreadable.
• Letting it go stale. A chart labelled with a last-updated date is trusted; one without a date is not. Put a review cadence on every business process chart.

Popular business process flowcharts

The five that most teams end up drawing first are order fulfillment, employee onboarding, invoice approval, customer support triage and content publishing. Copyable walkthroughs are on the examples page.

People also ask

What is the difference between a business process flowchart and BPMN? BPMN (Business Process Model and Notation) is a richer, formal notation with dozens of symbols. A business process flowchart uses the standard four shapes and prioritises readability over formal completeness. Use BPMN when the diagram will feed an execution engine; use a plain business process flowchart for humans.

Who should own the flowchart? The process owner — the role accountable for the outcome — owns the chart and its updates, even if someone else draws it.

How often should it be reviewed? Annually at a minimum, and any time the process itself changes. Put the review date on the chart so readers know how much to trust it.