Skip to content

Quality Tools

Flowchart Generator

Map a process step by step — actions, decisions, and branches — to make bottlenecks and rework loops visible.

Instructions:

  • • Add nodes using the form above
  • • Drag nodes to reposition them
  • • Click on a node to edit its text
  • • Use "Connect Nodes" to link nodes together
  • • Click two nodes in sequence to create connections

Process Flow Chart

Add nodes to start creating your flow chart

Node Types:

Start/End
Process
Decision
Connection

What is a flowchart?

A flowchart is a visual representation of a process, workflow, or algorithm that uses standardized symbols to show the sequence of steps and decision points. Flowcharts help teams understand, analyse, and improve processes by making them visible.

SymbolMeaning
OvalStart / end
RectangleProcess step
DiamondDecision point
ArrowDirection of flow

Uses: visualise complex processes, find bottlenecks and rework loops, standardise procedures, train new staff, and document how work is actually done.

How to create an effective flowchart

  1. Define the process scope and boundaries
  2. Identify the start and end points
  3. List all process steps in sequence
  4. Identify decision points and branches
  5. Connect the elements with arrows
  6. Review and validate with the people who do the work

Best practices: use standard symbols consistently, keep text short, keep flow top-to-bottom or left-to-right, avoid crossing lines, and include every path — including the failure branches.

Flowchart applications

SectorTypical uses
ManufacturingProduction process mapping, QC procedures, maintenance workflows, safety protocols
Service industriesCustomer service, order fulfilment, complaint handling, onboarding
HealthcarePatient pathways, emergency response, medication administration, infection control

Worked example: order fulfilment

An illustrative e-commerce fulfilment flow, mapped as it actually runs:

  1. Start: customer places an order
  2. Decision: is the payment valid?
  3. Process: check inventory
  4. Decision: are all items in stock?
  5. Process: pick and pack
  6. Process: generate the shipping label and ship
  7. End: customer receives the order

Drawing the “no” branches is where the improvement ideas come from: what happens to a failed payment, who handles a partial stock-out, whether inventory is checked before or after payment. Those exception paths are usually where delays and errors concentrate.

Frequently asked questions

What’s the difference between a flowchart and a process map?
Flowcharts focus on the logical flow and decision points in a process, while process maps often add details such as roles, systems, and timing. Flowcharts concentrate on the sequence of activities and decisions.
How detailed should a flowchart be?
It depends on the purpose. High-level flowcharts show major steps; detailed ones include every action and decision. Start high-level and add detail as needed for analysis or training.
Who should be involved in creating flowcharts?
The people who perform the process, the process owner, its customers (internal or external), and subject-matter experts. Different perspectives help ensure accuracy and completeness.
How often should flowcharts be updated?
Whenever the process changes significantly, during improvement projects, or at least annually as part of process reviews.