If you've ever opened a flowchart template and stared at a row of shapes wondering what each one actually means, you're not alone. Flowchart symbols are a shared visual language and getting them right is the difference between a diagram that clarifies a process and one that confuses everyone who reads it. Whether you're mapping a simple customer workflow or documenting a complex engineering system, knowing which symbol to use (and when) saves time, reduces miscommunication, and makes your diagrams professionally credible.

What do the basic flowchart symbols actually mean?

Most flowcharts rely on a small set of standard shapes. Each one has a specific job. Here's what the most common symbols represent:

  • Oval (Terminator): Marks the start or end point of a process. Every flowchart should have at least one.
  • Rectangle (Process): Represents an action, task, or step in the workflow. This is the symbol you'll use most often.
  • Diamond (Decision): Indicates a yes/no question or a branching point. It always has at least two exit paths. If you're working with decision logic, this guide on decision diamond best practices covers the nuances.
  • Parallelogram (Input/Output): Shows where data enters or leaves the process think form submissions, file imports, or printed reports.
  • Arrow (Flow Line): Connects symbols and shows the direction of the workflow. Without arrows, your reader has no idea what comes next.
  • Document Symbol: Looks like a rectangle with a wavy bottom edge. It represents a document or report generated during the process.
  • Predefined Process (Subroutine): A rectangle with double vertical lines. It points to another process defined elsewhere useful when one step is itself a full workflow.

These symbols come from standards set by the American National Standards Institute (ANSI) and later adopted by ISO 5807, which standardizes documentation symbols for data processing.

Why do flowchart symbols need to be standard?

Imagine two engineers on the same project using different shapes for "decision" points. One uses a diamond, the other uses a hexagon. Anyone reading that diagram has to guess what the hexagon means. Standard symbols eliminate that guesswork.

Standardized flowchart symbols matter because they:

  • Make diagrams readable by anyone familiar with basic flowcharting conventions
  • Reduce onboarding time when new team members join a project
  • Allow cross-team and cross-company collaboration without a legend
  • Support regulatory and audit documentation where consistency is required

If you work in engineering or manufacturing, having a reliable reference for engineering process flowchart symbol definitions is especially helpful since those fields often use additional specialized symbols beyond the basics.

When should you use a flowchart instead of just writing steps?

Written step-by-step instructions work fine for simple, linear tasks. But once a process involves decisions, parallel paths, loops, or multiple stakeholders, a flowchart communicates faster and with less ambiguity.

Use a flowchart when:

  1. Your process has if/then branches (e.g., "If the application is approved, move to onboarding. If rejected, send a notification.")
  2. Multiple people or systems are involved, and you need to show handoffs
  3. You're troubleshooting mapping the actual process helps spot where things break down
  4. You need to document a process for compliance or training purposes
  5. You want to compare the current process ("as-is") to a proposed one ("to-be")

What are the less common flowchart symbols you might need?

Beyond the basics, some flowcharts require specialized symbols. You won't use these every day, but knowing they exist prevents confusion when you encounter them:

  • Connector (Small circle): Links parts of a flowchart across different pages or sections. Useful for large processes that don't fit on one screen.
  • Merge Symbol: Combines multiple paths back into one. Looks similar to a process rectangle but is used at convergence points.
  • Storage Symbol (Cylinder): Represents a database or storage system in system flowcharts.
  • Manual Input Symbol: A rectangle with one slanted side. Indicates a step where a user manually enters data.
  • Delay Symbol (D-shape): Shows a waiting period in the process.
  • Display Symbol: Indicates output shown on a screen different from the general input/output parallelogram.

For a complete breakdown including ISO-referenced shapes, our ISO standard flowchart symbol reference chart gives you a visual lookup you can bookmark.

What are common mistakes people make with flowchart symbols?

Even experienced professionals get some of these wrong. Here are the errors that come up most often:

  • Using rectangles for decisions: If your shape has more than one exit path, it should almost always be a diamond. Rectangles are for single-path process steps.
  • Forgetting start and end points: Every flowchart needs at least one terminator. Without them, readers don't know where the process begins or ends.
  • Overloading a single flowchart: Trying to document an entire department's operations in one diagram creates a tangled mess. Break large processes into linked sub-processes using the predefined process symbol.
  • Inconsistent symbol sizing and spacing: This isn't about the symbols themselves, but messy layouts make even correct symbols hard to follow. Use alignment tools.
  • Mixing symbol systems: Don't combine UML notation, BPMN symbols, and ANSI flowchart symbols in the same diagram unless you clearly label which system you're using.
  • Missing arrows or flow direction: Without clear directional arrows, the reader can't determine the sequence. Always connect symbols and always show the flow.

How do you choose the right symbol for each step?

Ask yourself these three questions about each step in your process:

  1. Does something happen here, or is it a question? If it's an action, use a rectangle. If it's a question with different outcomes, use a diamond.
  2. Is this the start or end of the process? Use an oval/terminator.
  3. Does data come in from outside or get sent out? Use a parallelogram.

If a step doesn't fit neatly into those categories, it's likely one of the specialized symbols a document, a database, a manual input, or a connector. Refer back to the symbol definitions when you're unsure.

Can you give a practical example of these symbols in use?

Here's a simple employee expense reimbursement process:

  1. Oval: "Employee submits expense report" this is the start
  2. Parallelogram: "System receives expense data" input
  3. Rectangle: "Manager reviews report" process step
  4. Diamond: "Is the amount under $500?" decision point
  5. Rectangle: "Auto-approve and process payment" (yes path)
  6. Rectangle: "Route to finance director for review" (no path)
  7. Diamond: "Director approves?" second decision
  8. Rectangle: "Process payment" (yes) or "Return to employee with feedback" (no)
  9. Oval: "Process complete" end

Each symbol matches its standard meaning. A new team member reading this diagram can follow it without a verbal explanation. That's the point.

What tools work best for creating flowcharts with correct symbols?

Most modern diagramming tools include built-in libraries of standard flowchart symbols. Here are some options people use regularly:

  • Lucidchart: Browser-based, good template library, supports real-time collaboration
  • Microsoft Visio: Industry standard for Windows users, deep integration with Office 365
  • Draw.io (diagrams.net): Free, open-source, works in the browser or as a desktop app
  • Miro: Whiteboard-style, good for brainstorming and quick drafts
  • Google Drawings: Simple, free, adequate for basic flowcharts

Whatever tool you pick, confirm that its default shape libraries align with ANSI/ISO standards. Some tools use their own shape conventions, which can confuse readers expecting standard symbols.

What should you check before sharing a flowchart?

Before you send or publish a flowchart, run through this checklist:

  1. Every path from a decision diamond leads to a clear outcome no dead ends
  2. Start and end points are marked with terminator ovals
  3. All flow arrows point in the right direction and connect to a shape on each end
  4. Symbol usage is consistent throughout (no switching between notation systems)
  5. Text inside each symbol is short and action-oriented ("Review application," not "The application is reviewed by the manager at this stage")
  6. The diagram reads top-to-bottom or left-to-right, matching natural reading patterns
  7. You've tested it: ask someone unfamiliar with the process to follow it. If they get stuck, revise.

Next step: Pick a real process from your work something with at least one decision point and map it out using only the six basic symbols. If you get stuck on a particular shape, bookmark the references linked above and build from there. The more you practice matching the right symbol to the right step, the faster it becomes second nature.