Flowchart basics
Types of flowcharts and when to use each
Choose the type of flowchart from the question you want to answer: a process flowchart shows the order of steps, a swimlane diagram shows who does what, a data flow diagram shows where information goes, and an algorithm flowchart shows the logic of a program.
Process flowchart
The classic form: a single path of steps and decisions from a start to one or more ends. Use it when the main question is "in what order do things happen?", for example to describe how a refund is approved. It works best when one person or one team runs the whole process.
Swimlane diagram
The same steps, arranged in columns or rows, one per actor: customer, sales, finance, a software system. Use it when the question is "who does what, and where are the hand-offs?". Most business processes involve several people, which is why the swimlane diagram is often the most useful type in companies.
Workflow diagram
A workflow diagram is a flowchart focused on how work and documents move between people and tools, often with forms, approvals and notifications. In practice the term is used loosely and most workflow diagrams are swimlane flowcharts.
Data flow diagram (DFD)
A DFD does not show the order of steps. It shows where data comes from, where it is transformed and where it is stored, using external entities, processes, data stores and data flows. Use it to design or document an information system, not to describe a procedure.
Algorithm or program flowchart
Used in programming and teaching, it represents the logic of an algorithm: variables, conditions and loops. Its strictness is close to code, and it translates well into pseudocode. See algorithm flowcharts.
Decision flowchart
Also called a decision tree when it only branches, it guides someone through a series of questions to a result: which plan to choose, which support procedure to follow, whether a request is eligible. It is mostly diamonds; the rules for drawing decisions and loops apply.
Process map and BPMN
At the scale of a company, teams use process maps and sometimes BPMN, a formal notation with events, gateways and messages. They are not just bigger flowcharts: they serve analysis or execution in software. The comparison flowchart vs BPMN explains when the extra rigour is worth it.
How to choose
- One actor, a short procedure: process flowchart.
- Several actors and hand-offs: swimlane diagram.
- Information system design: data flow diagram.
- Program logic: algorithm flowchart.
- Guided choice: decision flowchart.
Whatever the type, the same symbols apply. Flowchartio produces a swimlane flowchart by default because it fits most business processes, and you can hide the lanes when only the order of steps matters.