Terminator (Start/End)
Marks where the process begins and ends. Use clear labels like "Start request" or "Close ticket."
Flowchart symbol guide
Learn when to use each symbol so your flowcharts stay readable, auditable, and easy for teams to execute.
Last updated: May 23, 2026
Most process diagrams can be created with a small set of symbols. Keep meanings consistent across your team.
Marks where the process begins and ends. Use clear labels like "Start request" or "Close ticket."
Represents a concrete action step such as "Validate order" or "Assign owner."
Used when the flow can branch. Label each outgoing path with explicit outcomes like Yes or No.
Shows where data is entered or produced, such as "Receive form" or "Send confirmation email."
Indicates a generated document, report, or file that affects downstream steps.
Represents stored records like customer tables, audit logs, or configuration data.
Links long process paths cleanly when lines would otherwise cross and reduce readability.
Defines sequence direction. Keep arrow direction mostly consistent, left-to-right or top-to-bottom.
For full process examples, visit flowchart examples. If you are new to diagramming, start with the step-by-step tutorial. For advanced interface controls, use the editor shortcuts guide.
FAQ
Learn terminator, process, decision, connector, and arrows first. They cover most real team workflows.
Use it whenever a condition creates two or more paths that change what happens next.
Yes, but keep symbol meanings consistent and add a short legend if collaborators are new to the notation.
Keep direction consistent, avoid crossing lines, and split very large processes into connected sub-flows.