Flow Diagram Symbols Examples: Every Shape With a Real Label

Published October 26, 2026 · Updated October 26, 2026 · 8 min read · by the Sakura5 team

Flow diagram symbols are easiest to learn by example: an oval labeled “Customer places order” marks a start, a rectangle labeled “Print receipt” is an action, a diamond labeled “Paid?” is a decision, a parallelogram labeled “Enter PIN” is input, and an arrow shows which step comes next. Those five shapes cover most flowcharts, and each one becomes obvious the moment you see it holding a real label instead of the word “Process.”

The catch is that “flow diagram” covers more than one kind of chart. A classic flowchart, a swimlane diagram, a data flow diagram and a BPMN business process diagram all use boxes and arrows, but they don’t use them the same way. A circle means a connector in one, a process in another and an event in a third. Mixing the conventions is the most common reason a diagram confuses its reader.

This guide gives a concrete example label for every common symbol, shows how the symbols change across the four main types of flow diagram, then draws one named scenario two ways so you can see the difference, and ends with the questions people ask most.

Why symbol charts without examples don’t stick

Most symbol references are a grid of empty shapes with a one-word caption: “Decision,” “Data,” “Document.” You nod along, then sit down to draw and can’t remember whether “Email the invoice” goes in a rectangle or a parallelogram. The caption names the category but never shows you a label that belongs in it.

The second problem is that those grids rarely say which diagram type they describe. A beginner sees a circle captioned “Connector” in one tutorial and a circle captioned “Process” in a data flow tutorial, and reasonably concludes the symbols are arbitrary. They aren’t. Each notation is internally consistent; you just have to know which one you’re using.

The fix is to learn each symbol through a label you’d actually write, and to pick one notation per diagram.

Flow diagram symbols with examples: the flowchart set

These are the shapes you’ll use in an ordinary flowchart, the kind drawn for school assignments, work procedures and simple programs. Each entry has a sample label so you can test your own.

1. Oval (terminator)

Marks where the process begins and ends. Example labels: “Start,” “Customer opens the app,” “Order collected,” “Request rejected.” One start, one or more ends.

2. Rectangle (process)

One action, written verb-first. Example labels: “Calculate total,” “Send confirmation email,” “Steam the milk.” If your label has “and” in it, split it into two rectangles.

3. Diamond (decision)

A question with a fixed set of answers, each written on an arrow leaving the diamond. Example labels: “Payment approved?” “Stock above 5?” “Older than 18?” Avoid vague questions like “Order OK?” that two people would answer differently.

4. Parallelogram (input/output)

Data entering or leaving the process. Example labels: “User enters postcode,” “Display error message,” “Print label.” Programming courses expect it; informal business charts often use a rectangle instead.

5. Document, database, delay and connector

The wavy-bottomed document holds “Monthly sales report” or “Signed contract.” The cylinder holds stored data: “Save order to database.” The D-shaped delay holds waiting: “Wait 24 hours for reply.” The small circle holds a letter, like “A,” and joins two parts of a chart without a long arrow. If you want the meaning of each shape in more depth, our guide to flowchart symbols and meanings for beginners covers them one by one.

How the symbols change in other flow diagrams

Here’s where examples matter most. The same shape can mean different things depending on the notation, so decide the diagram type before you draw the first box.

Swimlane diagrams

A swimlane diagram uses the ordinary flowchart shapes but splits the page into lanes, one per person or team: “Customer,” “Barista,” “Payment system.” Each shape sits in the lane of whoever does it. An arrow crossing a lane line is a handoff, and handoffs are usually where delays hide.

Data flow diagrams

A data flow diagram (DFD) shows how information moves, not the order of steps, so it has no diamonds and no start or end. It uses four symbols. An external entity is a rectangle, such as “Customer” or “Bank.” A process transforms data; in the Yourdon–DeMarco notation it’s a circle, in Gane–Sarson a rounded rectangle, labeled something like “1.0 Validate order.” A data store is drawn as an open-ended rectangle or two parallel lines, such as “D1 Orders.” A data flow is an arrow labeled with the data itself: “payment details,” not “pay.”

BPMN process diagrams

Business Process Model and Notation is a formal standard used in larger organizations. Its circles are events: a thin circle is a start event (“Order received”), a thick one an end event (“Order fulfilled”). Rounded rectangles are tasks (“Prepare drink”). Diamonds are gateways, where the flow splits or merges. A solid arrow is sequence flow inside one organization; a dashed arrow is a message between participants. The full rules live in the BPMN specification published by the Object Management Group, though most teams only use a small subset.

A worked example: one café order drawn two ways

Say you run a small café called Juniper that takes mobile orders. The rules are simple: the customer orders and pays in an app, the order prints at the counter, the barista makes it, and the cup goes on the pickup shelf. If an item is out of stock, the customer gets a refund. If nobody collects the order within 30 minutes, it’s logged as a no-show. You want one diagram for the new staff and one for the developer building the ordering system.

Step 1: list everything before choosing shapes

Write down every action, check, piece of data and person involved, in any order. A mind map is a good fit for this, because you can put “Mobile order” in the middle and branch out to people, data and outcomes without deciding the sequence yet. In Mindmap AI, a Pro subscriber can type the rules above as a topic, get a starting map in seconds, and expand a node like “Out of stock” into sub-steps. The outline view then lets you drag those nodes into the order they happen.

Step 2: draw the staff version as a flowchart

Staff care about what to do next, so a flowchart with two lanes, “Customer” and “Barista,” fits best. Start oval: “Customer places order.” Parallelogram: “Order ticket prints.” Diamond: “All items in stock?” No leads to the rectangle “Refund missing item” and back to the main path. Yes leads to “Make drinks” and “Place on pickup shelf.” Delay: “Wait up to 30 minutes.” Diamond: “Collected?” Yes ends at “Order complete”; No ends at “Log no-show.”

Count it: 1 start oval, 2 end ovals, 1 parallelogram, 3 rectangles, 2 diamonds and 1 delay, for 10 shapes across two lanes. That fits on a single printed page you can tape beside the espresso machine.

Step 3: draw the developer version as a data flow diagram

The developer cares about what data goes where, so the decisions disappear. External entities: “Customer” and “Payment provider.” Processes: “1.0 Take order,” “2.0 Charge card,” “3.0 Print ticket.” Data stores: “D1 Orders” and “D2 Menu stock.” Labeled flows include “order items” from Customer to 1.0, “card token” from 2.0 to Payment provider, and “stock levels” from D2 to 1.0. That’s 2 entities, 3 processes and 2 stores.

Step 4: test both with the same case

Trace one order through each: a flat white and a croissant, croissants sold out, collected after 12 minutes. In the flowchart it should take the refund branch and end at “Order complete.” In the DFD you should be able to point to where the system learns the croissant is out of stock (the “stock levels” flow). If either trace gets stuck, a symbol or arrow is missing.

Same café, same rules, two different sets of symbols, because the two readers ask different questions. For more patterns like this, see our collection of examples of flow chart diagrams.

Common symbol mistakes and how to fix them

• Using a diamond for emphasis. A diamond always reads as a decision. Use bold text or color to highlight an important step instead.
• Mixing notations. A DFD process circle dropped into a flowchart looks like a connector. Pick one notation per diagram and stick to it.
• Unlabeled arrows. Every exit from a decision needs an answer on it, and every DFD arrow needs the name of the data it carries.
• Decisions in a data flow diagram. If you find yourself drawing a diamond in a DFD, you’re describing sequence. Move that logic to a flowchart.
• Drawing before you understand the process. If you can’t list the steps, no symbol will rescue the chart. Map the parts loosely first, on paper or on an infinite canvas in Mindmap AI, then convert to shapes once the order is clear.

FAQ

What are examples of flow diagram symbols?

Common examples are an oval labeled “Start,” a rectangle labeled “Send invoice,” a diamond labeled “Payment received?”, a parallelogram labeled “User enters email,” a cylinder labeled “Customer database” and arrows connecting them. Seeing each shape with a real label is the fastest way to remember what it means and when to use it.

What is the difference between a flowchart and a data flow diagram?

A flowchart shows the order of steps and the decisions between them, so it uses ovals, rectangles and diamonds. A data flow diagram shows how information moves between people, processes and storage, with no decisions and no start or end. Use a flowchart to explain what to do next and a DFD to explain where data goes.

What does a circle mean in a flow diagram?

It depends on the notation. In a standard flowchart a small circle is a connector that joins two parts of the chart. In a Yourdon–DeMarco data flow diagram a circle is a process that transforms data. In BPMN a circle is an event, such as a start or end. Check which notation a diagram uses before reading it.

How many symbols do I need to draw a flow diagram?

For most flowcharts, five are enough: oval, rectangle, diamond, parallelogram and arrow. Data flow diagrams need four: external entity, process, data store and data flow. The larger symbol sets exist for specialist uses, and you can add a document, database or delay shape only when a step genuinely needs it.

← All articles