A flowchart is the diagram that translates a process into shapes and arrows so that any reader — engineer, auditor, operator, or new hire — can follow what happens, in what order, with what decisions branching where. It is the workhorse of process documentation: simple enough to draw quickly, structured enough to enforce clarity, visual enough to expose gaps that prose hides.

This guide explains the standard flowchart symbols, when to use a flowchart versus other diagrams, how to draw one that gets used, and the mistakes that produce diagrams everyone politely ignores.

Standard Flowchart Symbols

  • Oval / Rounded rectangle — Start and end points
  • Rectangle — Process step or action
  • Diamond — Decision point with branching outcomes (yes/no, true/false)
  • Parallelogram — Input or output (data, document, user entry)
  • Cylinder — Data store (database, file, archive)
  • Document shape — A document produced or consumed
  • Manual operation — Trapezoid; human-performed step
  • Predefined process — Rectangle with vertical lines; references a sub-process documented separately
  • Connector — Small circle linking parts of the chart that span pages
  • Arrows — Direction of flow

Stick to standard symbols. Custom shapes confuse readers and undermine the diagram's purpose.

When to Use a Flowchart

  • Process documentation — How something is done, step by step
  • Onboarding new staff — Visual aid for understanding workflows
  • Process improvement — Mapping current state to identify waste, redundancy, bottlenecks
  • Standard operating procedures — Visual companion to written SOPs
  • Audit and compliance — Demonstrating controls and approval chains
  • Software / system design — Logical flow of code, data, or user interactions
  • Troubleshooting guides — Decision trees for diagnosing problems

Flowchart Types

Linear Flowchart

Simple sequential steps from start to end. Used for straightforward processes.

Decision Flowchart

Includes branching at diamonds. Used when outcomes depend on conditions.

Swimlane Flowchart

Horizontal lanes for each actor (department, role, system). Steps placed in the lane of who performs them. Clarifies handoffs — useful for cross-functional processes.

Workflow Diagram

High-level flowchart focusing on tasks and approvals, often used in business process management.

Data Flow Diagram

Focused on data movement rather than process steps. Used in system design.

Drawing a Useful Flowchart

1. Define Scope and Audience

What process are you mapping? At what level of detail? Who will read it? An auditor wants different detail than a new hire.

2. Identify Start and End

What triggers the process? What completes it? Pinning these first constrains the diagram.

3. List the Steps

Walk through the process in order. Use verbs for actions. Keep step descriptions short — fit in a rectangle without wrapping.

4. Identify Decisions

Where does the flow branch? Each diamond has 2 (sometimes 3) outgoing arrows with labelled outcomes (Yes, No, Approved, Rejected).

5. Draw Top to Bottom or Left to Right

Consistent flow direction. Avoid arrows looping backward unless representing a real loop (retry, escalation).

6. Validate with Process Owners

Show the draft to people who actually perform the steps. Their corrections always reveal missing branches and edge cases.

7. Iterate and Publish

Version number, date, owner. Update when the process changes.

Common Pitfalls

  • Too detailed. Every keystroke documented; chart unreadable
  • Too vague. "Process invoice" as a single box hides the complexity that matters
  • Missing decisions. Real processes have exceptions; flowcharts that ignore them mislead
  • Inconsistent symbols. Mixing shapes arbitrarily
  • Unlabelled arrows. Decision branches without "Yes" / "No"
  • Dead ends. Branches that never converge to an end point
  • Spaghetti routing. Arrows crossing chaotically — readers can't trace flow
  • No version or owner. Outdated charts persist with no one accountable
  • One mega-chart. Should be broken into sub-process charts with predefined-process callouts
  • Drawn once, never updated. Diagram and reality drift apart; trust in the chart erodes

Flowchart vs Other Diagrams

  • Flowchart — Process flow with decisions
  • BPMN — Business Process Model and Notation; richer notation for cross-functional processes
  • Sequence diagram — Interactions over time between actors or systems (UML)
  • State diagram — System states and transitions between them
  • Mind map — Hierarchical brainstorm, not sequential process
  • Org chart — Reporting hierarchy, not process

Practical Tips

  • One process per chart — sub-processes get their own
  • 3–10 steps per visible page — break larger processes into linked sub-processes
  • Use colour sparingly — to highlight decision branches or critical steps, not for decoration
  • Label connectors with letters or numbers when a chart spans pages
  • Include a legend if non-standard symbols are unavoidable
  • Put the chart where the work happens — wall in the warehouse, screen at the workstation

Industry-Specific Notes

Manufacturing

Quality control checkpoints, rework loops, scrap decisions, batch versus continuous flow distinctions.

Finance / Accounting

Approval workflows (PR, PO, invoice approval), exception handling, segregation of duties enforced via routing.

IT / Software

Login flows, error handling paths, API call sequences, integration logic.

Healthcare

Patient pathways, triage flows, escalation procedures, medication reconciliation.

Customer Service

Ticket triage and routing, escalation tiers, response SLAs, resolution paths.

Compliance and Audit

Control activities, evidence collection, review and sign-off chains.

Generate a Flowchart with Popupnote

The Flowchart Maker on Popupnote produces clean flowcharts with standard symbols (start, process, decision, document, data store), labelled arrows, decision branches, and swimlanes — suitable for process documentation, SOP visualisation, audit deliverables, system design, and onboarding materials. The generator runs in your browser without any account required.