Standard Flowchart Symbols Reference Guide

If you've ever opened a flowchart template and stared at a wall of shapes with no idea which one to use, you're not alone. Picking the wrong symbol changes the meaning of your diagram, confuses your team, and defeats the whole point of making a flowchart in the first place. A solid standard flowchart symbols reference solves this problem it gives you a shared visual language so anyone reading your diagram understands exactly what each step means, whether it's a decision, a process, or a data input. This matters even more when your flowcharts move beyond your own desk and get reviewed by developers, analysts, or stakeholders who expect clarity.

What are standard flowchart symbols?

Standard flowchart symbols are the agreed-upon shapes defined by organizations like the International Organization for Standardization (ISO) and the American National Standards Institute (ANSI). These symbols represent specific types of actions or steps in a process. The most common set comes from ISO 5807, which has guided technical documentation since 1985.

Each shape has a fixed meaning. A rectangle means a process or action step. A diamond means a decision. A parallelogram means input or output. When everyone on your team learns these symbols, your flowcharts become readable without a legend or explanation and that's the whole point.

The core symbols you'll use most often

Terminator (Rounded Rectangle): Marks the start or end point of a flowchart. Every diagram needs at least one of these.
Process (Rectangle): Represents any action, task, or operation. This is the most-used shape in nearly every flowchart.
Decision (Diamond): Shows a yes/no or true/false branch. The flow splits into two or more paths depending on the answer.
Input/Output (Parallelogram): Indicates data going into or coming out of a process like reading user input or displaying a result.
Arrow (Flowline): Connects shapes and shows the direction of flow. No arrow, no sequence.
Connector (Small Circle): Links different parts of a flowchart when the diagram crosses pages or jumps between sections.
Document (Rectangle with wavy bottom): Represents a document or report that the process creates or reads.
Predefined Process (Rectangle with double vertical lines): Points to a process defined elsewhere useful when you're breaking a large chart into modules.
Delay (D-shape): Indicates a waiting period in the process.
Storage (Triangle pointing down): Refers to data stored in a database or file system.

For a deeper breakdown of each shape and its variants, you can check our complete flowchart symbols reference guide.

Why do flowchart symbols need to be standardized?

Without a shared standard, every person draws their own version. One person uses a rectangle for a decision. Another uses a circle for a process. A third person invents shapes nobody recognizes. The result is a diagram that only makes sense to the person who drew it.

Standardization fixes this. When your team follows ANSI/ISO symbol conventions, a new hire can read the diagram on their first day. A contractor in another country can follow it. Your compliance team can audit it. The symbols become a common language like road signs for your processes.

This is especially true in regulated industries like healthcare, finance, and software engineering, where process documentation gets reviewed by people outside your immediate team. If your flowchart uses non-standard shapes, reviewers may misunderstand the process or flag it for corrections.

How do I know which symbol to use for each step?

Match the shape to the type of action, not the content. Here's a simple decision process:

Is this a start or end point? Use a rounded rectangle (terminator).
Is this an action or task? Use a rectangle (process).
Is this a yes/no question? Use a diamond (decision).
Is this data entering or leaving the system? Use a parallelogram (I/O).
Is this a document being created or referenced? Use the document symbol.
Is this a wait or pause? Use the delay shape.

When in doubt, start with the terminator, work through your process using rectangles and diamonds, and add I/O shapes where data moves in or out. Keep it simple. If you need more advanced notation for things like parallel processing or swim lanes, our advanced flowchart notation guide covers those in detail.

What's the difference between a flowchart symbol and a flowchart shape?

Technically, they mean the same thing. "Symbol" is the formal term used in standards like ISO 5807. "Shape" is the casual term most people use when working in tools like Visio, Lucidchart, or draw.io. In practice, nobody will correct you either way but if you're writing documentation that needs to follow a standard, use "symbol."

What are the most common mistakes people make with flowchart symbols?

Using too many symbol types

A basic process map doesn't need 15 different shapes. If your audience isn't technical, stick to terminators, rectangles, diamonds, and arrows. More symbols doesn't mean a better diagram it often means a harder one to read.

Skipping the start and end points

Every flowchart needs a clear beginning and end. Without terminators, readers don't know where the process starts or finishes. This is the single most common omission in flowcharts made by non-technical teams.

Confusing process shapes with decision shapes

A rectangle carries out an action. A diamond asks a question. Mixing these up changes the logic of the entire diagram. If you write "Is order complete?" inside a rectangle, readers won't know it's a branching point.

Drawing arrows in unclear directions

Standard flowchart convention reads top-to-bottom and left-to-right. When arrows cross over each other or point backward without reason, the diagram becomes confusing. Use connectors to avoid messy crossing lines.

Not labeling decision branches

Every arrow leaving a diamond should say "Yes" or "No" (or another clear label). Unlabeled branches force readers to guess, which defeats the purpose of visual documentation.

Our process mapping cheat sheet covers these mistakes and more with quick visual examples.

When would I actually need a flowchart symbols reference?

You reach for a symbols reference when:

You're documenting a business process for the first time and want to get the shapes right.
You're onboarding new team members and need a shared visual standard.
You're preparing documentation for auditors or regulators who expect ISO/ANSI-compliant diagrams.
You're teaching or training others how to read and create flowcharts.
You're switching tools (say, from Visio to Lucidchart) and want to confirm the symbol names match.
You're collaborating across teams and need a common baseline so diagrams don't get misinterpreted.

Do different tools use different symbols?

The standard symbols stay the same regardless of the tool. What changes is how the tool names them in its shape library. For example, Visio calls the decision shape a "Decision," while some tools label it "Conditional." Lucidchart groups symbols into categories like "Flowchart" and "Data Flow." The shapes themselves follow the same ISO/ANSI conventions, but the menu names and drag-and-drop organization vary.

This is another reason to learn the symbols by their standard names rather than by whatever your current tool calls them. When you switch platforms, you'll still know exactly what to look for.

Are there different types of flowcharts that use different symbols?

Yes. The core symbols (terminator, process, decision, arrow) stay the same across most flowchart types, but specialized diagrams add their own:

Data flow diagrams (DFDs): Add external entities, data stores, and data flow arrows with specific notation rules.
Swimlane diagrams: Use the same process symbols but organize them into lanes by role or department.
BPMN diagrams (Business Process Model and Notation): Use a different symbol set entirely events, gateways, tasks, and sequence flows follow the BPMN 2.0 standard.
UML activity diagrams: Use fork bars, merge bars, and activity nodes from the Unified Modeling Language spec.

If you're working strictly with standard flowcharts, the ISO 5807 symbols are what you need. If your team uses BPMN or UML, those are separate systems with their own references.

Practical tips for using flowchart symbols correctly

Print a one-page symbol cheat sheet and pin it near your desk until the shapes become second nature.
Use a consistent style pick one color scheme and line thickness and stick with it across all diagrams.
Limit your flowchart to one page when possible. If it grows too large, break it into sub-processes using the predefined process symbol.
Test readability by showing the flowchart to someone unfamiliar with the process. If they can follow it without explanation, your symbols are working.
Name your shapes with verbs and nouns, not vague terms. "Approve invoice" beats "Step 3."

Quick reference checklist before you publish any flowchart

Every flowchart has a clear start terminator and at least one end terminator.
All decisions use diamond shapes with labeled branches (Yes/No or specific conditions).
Process steps use rectangles no actions hiding inside diamonds or parallelograms.
Data inputs and outputs use parallelograms, not rectangles.
Arrows flow top-to-bottom, left-to-right with no unexplained backward lines.
Connector symbols handle page breaks or jumps so arrows don't cross the entire diagram.
Every shape has clear, concise text no empty shapes or placeholder labels.
The diagram uses one consistent symbol style throughout (same colors, same line weights).

Next step: Print this checklist, grab your flowchart tool, and review one existing diagram against it. Fix anything that doesn't match. That single review will train your eye faster than reading any amount of theory.