What is a process flowchart?

A process flowchart is a diagram that shows the steps of a process in the order they happen, using standard shapes for actions, decisions and start/end points. It turns a written procedure into a picture that anyone on the team can follow at a glance, without reading a paragraph.

The point of a flowchart is compression. A ten-paragraph SOP might describe the same procedure as a one-page diagram, but the diagram is faster to skim, easier to review and much harder to misinterpret. When two people disagree about "how the process works", a flowchart usually settles it in a minute — either the disputed step is on the chart or it is not.

A short history

The modern flowchart traces back to Frank and Lillian Gilbreth, who presented the "process chart" to the American Society of Mechanical Engineers in 1921 as a tool for industrial engineers studying factory work. The shapes we still use today — rectangles for actions, diamonds for decisions, rounded shapes for start and end — were later standardised by ANSI in the 1960s and adopted across manufacturing, software and business documentation. ISO 5807 later codified the same symbol set internationally, which is why a chart drawn in one country still reads correctly in another.

Anatomy of a process flowchart

Every process flowchart shares four building blocks:

• Start/end shapes (rounded rectangles) mark where a process begins and ends.
• Process shapes (rectangles) are individual actions — one step per shape.
• Decision shapes (diamonds) are yes/no branches where the process splits.
• Arrows connect the shapes and show the direction of flow.

A useful chart names each shape with a short verb phrase ("Approve invoice", "Send confirmation email") and reads top-to-bottom or left-to-right without loops crossing over each other. Labels stay short because the shape carries the meaning: a rectangle is understood as an action, so "Approve invoice" is enough — you do not need to write "The approver approves the invoice." See the full symbol reference for the extended vocabulary, including parallelograms for inputs, cylinders for data stores and connectors for jumping between pages.

A concrete example

Imagine a small team handling refund requests. Written as prose, the process reads: "When a customer requests a refund, support checks whether the order is under 30 days old. If it is, they approve it and finance issues the refund. If it is not, they escalate to a manager, who decides case by case." As a flowchart it is five shapes: a start, a decision ("Under 30 days?"), two branches and an end. The prose takes twenty seconds to read; the chart takes two.

When to use a process flowchart

Reach for a process flowchart whenever you need to make a repeatable procedure visible. Common cases:

• Onboarding new employees to an existing workflow.
• Documenting how a request moves between teams.
• Finding bottlenecks or redundant approvals.
• Explaining a policy to auditors or regulators.
• Aligning a team before automating a workflow.
• Preparing a diagram for a training deck so a new hire can follow along without a live walkthrough.

The wrong time to draw one is when the process is genuinely one-off, or when the "process" is really a checklist with no branches — a bulleted list is faster to write and just as clear.

Types of process flowcharts

The word "flowchart" covers several closely related diagrams. The most common variants:

• Basic process flowchart — the standard vertical or horizontal sequence, best for single-owner procedures.
• Workflow flowchart — focuses on recurring team work and hand-offs between roles.
• Business process flowchart — captures end-to-end business procedures for documentation and audit.
• Cross-functional flowchart (swimlane) — assigns each step to a role or department, useful when four or more teams are involved.

People also ask

Is a flowchart the same as a process map? Close but not identical. A process map is the broader category and can include value-stream maps or SIPOC diagrams; a flowchart is one specific notation inside that category.

What is the difference between a flowchart and an algorithm? An algorithm is the underlying logic; a flowchart is one way to draw it. The same algorithm can be written as pseudocode, prose or a flowchart.

How detailed should a process flowchart be? Detailed enough that a new hire can follow it without asking questions, and no more. If the chart spills onto a second page, split it into a top-level chart and linked sub-processes.

How to make one

You do not need to draw. The fastest way is to list your steps in plain English and let a tool render the chart. Follow the 5-step guide or copy a worked example for a starting point.