If you've ever tried to read a flowchart and felt lost because the shapes didn't make sense, you're not alone. Flowchart symbols are the shared language of process mapping. When everyone on a team uses the same shapes to mean the same things, diagrams become clear, error-free, and easy to follow whether you're sketching out a business workflow or designing software logic. Learning these standard symbols saves time, reduces miscommunication, and makes your diagrams professional.

What are the standard flowchart symbols?

Standard flowchart symbols come from guidelines set by organizations like the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO). These shapes were created decades ago so that engineers, analysts, and business professionals worldwide could read the same diagram without confusion. Each geometric shape represents a specific type of action or decision in a process.

Here are the most commonly used flowchart symbols and what each one means:

Oval (Terminator)

The oval, sometimes called a rounded rectangle, marks the start or end of a flowchart. Every process diagram should begin and end with this shape. Think of it as the "on" and "off" switch of your flowchart. You'll sometimes see it labeled with "Start," "End," "Begin," or "Return."

Rectangle (Process)

The rectangle is the workhorse of flowcharts. It represents any action, operation, or process step. When you see a rectangle, something is happening data is being calculated, a document is being reviewed, or a task is being performed. This is the symbol you'll use most often.

Diamond (Decision)

The diamond asks a yes/no or true/false question. It always has two exit paths (sometimes more), and the flow follows whichever answer applies. Common examples include "Is the order valid?", "Is the file available?", or "Does the amount exceed $500?" Decision points are what give flowcharts their branching logic.

Parallelogram (Input/Output)

This slanted rectangle indicates where data enters or leaves the process. It could represent reading user input, displaying a result on screen, writing to a database, or printing a report. If information is moving between the system and the outside world, use a parallelogram.

Arrow (Flow Line)

Arrows connect the symbols and show the direction of flow. They tell the reader which step comes next. Without arrows, a flowchart is just a collection of disconnected shapes. Solid arrows indicate normal flow; dashed arrows are sometimes used to show indirect or alternative connections.

Rectangle with Double Lines (Predefined Process)

When a process step is actually a subroutine, function, or pre-defined set of steps defined elsewhere, use a rectangle with vertical double lines on each side. This keeps your main flowchart clean and avoids repeating the same logic in multiple places. It's essentially a "see other document" marker.

Document Symbol

Shaped like a rectangle with a wavy bottom edge, this represents a physical or digital document an invoice, email, report, or form. Use it when a step specifically involves creating, reading, or filing a document.

Database Symbol (Cylinder)

The cylinder shape stands for a database or data storage. If your process involves storing or retrieving information from a database, this is the symbol to use. You'll see it frequently in system design and data flow diagrams.

Manual Operation Symbol

This is a trapezoid with the longer side on top. It represents a step done manually rather than by a computer or automated process. It's useful when documenting hybrid workflows where some tasks are automated and some require human effort.

Connector Symbol (Circle)

A small circle with a letter or number inside acts as a jump point. It connects parts of a flowchart that are spread across different pages or areas of a large diagram. Two connectors with matching labels mean "the flow continues here." This prevents long, tangled arrows crossing over everything.

Delay Symbol

Shaped like a half-oval or semicircle, the delay symbol indicates a waiting period in the process. This could be waiting for approval, a time delay between steps, or a queue before the next action begins.

Why do people use standardized flowchart shapes instead of making up their own?

You could draw any shape and label it, but standardized symbols solve a real problem: readability. When a new team member, a client, or a collaborator opens your diagram, they shouldn't need a legend to understand it. Standard symbols work like a common language. A diamond always means a decision. A rectangle always means a process.

Consistency also matters when your diagrams are reviewed by stakeholders who aren't familiar with your project. If you follow the same conventions that others in your industry use, your flowcharts will be understood faster and cause fewer misunderstandings. You can learn more about these conventions in our notation standards breakdown.

When should you use a flowchart?

Flowcharts are useful any time you need to visualize a sequence of steps. Here are common situations where they help:

• Documenting a business process Onboarding a new employee, handling a customer complaint, or processing an order.
• Planning software logic Mapping out if/else conditions, loops, and function calls before writing code. Our flowchart coding conventions guide covers this in detail.
• Troubleshooting a problem Creating a diagnostic flowchart to identify why a system is failing.
• Explaining a procedure to others Giving someone a visual step-by-step instead of a wall of text.
• Identifying bottlenecks Seeing where a process slows down or breaks down by mapping every step.

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

Even experienced professionals slip up with flowcharts. Here are the errors that show up most often:

1. Mixing up the process and decision shapes Putting a yes/no question inside a rectangle or putting a regular action inside a diamond. This confuses anyone trying to follow the logic.
2. Forgetting start and end points A flowchart without terminators leaves the reader guessing where the process begins and ends.
3. Using too many symbols Overcomplicating a diagram with dozens of steps when the flow could be simplified. If a flowchart is hard to read, it defeats its purpose.
4. Not labeling arrows Especially on decision branches. If a diamond has two exits, both arrows should be labeled (e.g., "Yes" / "No" or "True" / "False").
5. Creating one-way flow only Ignoring loops and feedback cycles. Real processes often loop back to earlier steps, and your flowchart should reflect that.
6. Inconsistent symbol sizing While this seems minor, wildly different symbol sizes make a chart look unprofessional and harder to scan quickly.

How do you choose the right symbol for each step?

Ask yourself a few simple questions about the step you're mapping:

• Is it the start or end of the process? Use an oval.
• Is something being done or calculated? Use a rectangle (process).
• Is there a question with different outcomes? Use a diamond (decision).
• Is data entering or leaving the system? Use a parallelogram (input/output).
• Does this step reference another process or function? Use a double-bordered rectangle.
• Is a document involved? Use the document symbol.
• Is there a waiting period? Use the delay symbol.

When in doubt, keep it simple. A clean flowchart with five well-labeled symbols is more useful than a cluttered one with twenty.

Do different industries use different flowchart symbols?

The core symbols stay the same, but some industries use specialized variations. Software engineering adds symbols for functions, loops, and data structures. Business process modeling has its own notation called BPMN (Business Process Model and Notation), which includes events, gateways, and swim lanes. Engineering and manufacturing sometimes use ANSI symbols with specific tolerances and specifications noted inside.

For most general purposes, the standard symbols listed above cover what you need. You can always check our full guide to standard flowchart symbols and their meanings for a quick reference.

Practical checklist: symbols you should know by heart

Before you start drawing your next flowchart, make sure you have these basics down:

• ☐ Oval = Start / End
• ☐ Rectangle = Process / Action step
• ☐ Diamond = Decision (Yes/No question)
• ☐ Parallelogram = Input / Output
• ☐ Arrow = Direction of flow
• ☐ Double-bordered rectangle = Predefined process or subroutine
• ☐ Document shape = A physical or digital document
• ☐ Cylinder = Database or storage
• ☐ Circle = Connector / Jump point

Next step: Pick a simple process you already know well like making coffee or logging into an account and draw it using only these standard symbols. Keep it to ten steps or fewer. This quick exercise will lock the shapes and their meanings into memory far better than just reading about them.