Types of Flowcharts: A Complete Visual Guide to All Diagram Types

Not all flowcharts are the same. A swimlane diagram used to map a cross-departmental approval process looks nothing like a data flow diagram used to design a software system—even though both use arrows and labeled boxes. Picking the wrong type creates more confusion than it resolves.

This guide covers every major flowchart type, explains what it's for, and shows a real example of each. At the end, you'll find a comparison table and a decision framework to help you pick the right type for your specific situation.

Process flowchart

The process flowchart is the default. When someone says "draw me a flowchart," they almost always mean this type.

Definition: A sequential diagram of the steps in a process, with decision points that branch the flow.

Best for:

• Documenting how something works end-to-end
• Training and onboarding materials
• Identifying bottlenecks or missing steps
• Process improvement analysis

Example: Employee onboarding

          ╭───────────────╮
          │     Start     │
          ╰───────┬───────╯
                  │
                  ▼
          ┌───────────────┐
          │ Send offer    │
          │ letter        │
          └───────┬───────┘
                  │
                  ▼
          ◇───────────────◇
         ╱  Offer accepted?╲
        ╱                   ╲
      Yes                    No
       │                     │
       ▼                     ▼
┌─────────────┐        ╭──────────╮
│ Set up      │        │   End    │
│ accounts    │        ╰──────────╯
└──────┬──────┘
       │
       ▼
┌─────────────┐
│ Schedule    │
│ orientation │
└──────┬──────┘
       │
       ▼
  ╭──────────╮
  │   End    │
  ╰──────────╯

When to use: Anytime you need to document or explain a process that has a clear start, end, and at least one decision point.

Swimlane flowchart (cross-functional diagram)

A swimlane diagram is a process flowchart divided into horizontal or vertical lanes. Each lane represents a specific actor—a person, role, department, or system. Steps are placed in the lane of whoever is responsible for them.

Definition: A process flowchart with responsibilities organized into parallel lanes.

Best for:

• Processes that cross departments or teams
• Identifying handoff points and accountability gaps
• Showing who does what and when

Example: Purchase approval process

┌──────────────┬──────────────────────────────────────────────┐
│ Requester    │  [Submit request] ─────────────────────────→  │
├──────────────┼──────────────────────────────────────────────┤
│ Manager      │     ↓            [Approve?]──No──→[Reject]   │
│              │                      │Yes                     │
├──────────────┼──────────────────────┼─────────────────────── │
│ Finance      │                   [Process payment]           │
├──────────────┼──────────────────────────────────────────────┤
│ Vendor       │                              [Deliver goods]  │
└──────────────┴──────────────────────────────────────────────┘

Common mistakes: Forgetting to include system actors alongside human ones. If a software system performs a step, it gets its own lane.

When to use: Any process where multiple people, teams, or systems are involved. The moment you find yourself writing "then the manager reviews, then finance approves, then the system sends a notification," you need a swimlane.

Data flow diagram (DFD)

A data flow diagram is fundamentally different from a process flowchart. It does not show steps in sequence—it shows how data moves through a system.

Definition: A diagram showing the flow of data between processes, data stores, and external entities. No decision diamonds, no start/end terminators.

Key components:

• External entities (rectangles): Sources or destinations of data outside the system
• Processes (circles or rounded rectangles): Transformations performed on data
• Data stores (open rectangles or parallel lines): Where data is stored
• Data flows (arrows with labels): Data moving between components

Best for:

• Software system design and architecture
• Documenting API interactions
• Database design and planning
• Understanding what data a system consumes and produces

Example: Order management system (Level 1 DFD)

[Customer] ──order data──→ (Process Order) ──order record──→ [=Order DB=]
                                   │
                            shipping request
                                   │
                                   ▼
                           (Ship Order) ──tracking info──→ [Customer]
                                   │
                           [=Inventory DB=]

DFD levels:

• Level 0 (Context diagram): The entire system as a single process with all external entities
• Level 1: The main sub-processes within the system
• Level 2+: Each sub-process broken into more detail

When NOT to use: DFDs are not for showing steps in sequence or who is responsible. If you need to show that a person does step A before step B, use a process flowchart or swimlane.

Workflow diagram

A workflow diagram is a broader, less formally constrained visualization of how work moves through a system. It often blends process steps, roles, documents, and communications into a single view.

Definition: A diagram showing the end-to-end flow of work, including tasks, decision points, and the people or systems involved.

Best for:

• Business process documentation for non-technical audiences
• Content production pipelines
• Approval and review workflows
• Project management processes

Example: Content publication workflow

[Writer] ──draft──→ [Editor] ──revisions──→ [Writer]
                        │
                   approved?
                      │Yes
                      ▼
               [Legal Review]
                      │
                   cleared?
                      │Yes
                      ▼
               [Publish to CMS]

The difference from a process flowchart is mostly in formality and audience. A workflow diagram often appears in project management tools, while a process flowchart appears in technical documentation.

Decision tree

A decision tree is a specialized flowchart where every node is a decision and every branch is an outcome. There are no loops—the tree always branches forward until it reaches a leaf node (an outcome).

Definition: A tree-shaped diagram where each branch represents a decision or condition, and each leaf represents a final outcome.

Best for:

• Troubleshooting and diagnostic guides
• Pricing or eligibility calculators
• Customer service scripts
• Risk assessment frameworks

Example: Technical support triage

                 Is the device on?
                 /              \
               No               Yes
               │                 │
       Charge the device    Is there WiFi?
            │               /         \
           [End]           No          Yes
                           │             │
                    Check router    Run speed test
                           │             │
                        [End]    Speed < 10 Mbps?
                                 /          \
                               Yes           No
                                │             │
                        Contact ISP     Restart app
                                │             │
                              [End]         [End]

When NOT to use: Decision trees only work for processes where every path is a forward branch. If there are loops (retry logic, iterative steps), use a process flowchart instead.

System flowchart

A system flowchart shows how data flows through a computer system, including inputs, processes, outputs, storage, and hardware components. It uses the full set of flowchart symbols including document, database, and manual operation shapes.

Definition: A flowchart representing the components of a computer or information system and how data flows through them.

Best for:

• IT infrastructure documentation
• Legacy system analysis
• Describing batch processing jobs
• System audits and compliance

Example: Payroll system

    ╱────────────────╲
   ╱  Time sheets     ╲   ← Manual input
  ╱    (paper)         ╲
 ╱─────────────────────╲
           │
           ▼
  ┌────────────────────┐
  │  Data Entry System │   ← Process
  └────────┬───────────┘
           │
           ▼
      ╭────────────╮
     (│Employee DB │)       ← Database
      ╰────┬───────╯
           │
           ▼
  ┌────────────────────┐
  │  Payroll Processor │   ← Process
  └────────┬───────────┘
           │
  ┌────────┴──────────┐
  │   Payslip report  │    ← Document output
  └───────────────────┘

When to use: When you need to document a complete information system including storage, hardware interactions, and document outputs—not just the logical steps.

Document flowchart

A document flowchart tracks the movement of documents through an organization or process. Each column represents a department or role, and the symbols show what happens to the document at each stage (created, reviewed, approved, filed, destroyed).

Definition: A flowchart that traces how documents flow through a process, showing who handles them and what happens at each stage.

Best for:

• Accounts payable/receivable processes
• Contract management
• HR document processing
• Compliance and records management

The document flowchart uses the document symbol (wavy-bottomed rectangle) as its primary shape, as opposed to a process flowchart which uses rectangles.

Program flowchart (algorithm flowchart)

A program flowchart (also called an algorithm flowchart) maps the logic of a computer program or algorithm at a step-by-step level. Developers used these extensively before high-level programming languages and modern IDEs made them less necessary, but they remain useful for teaching and for documenting complex logic.

Definition: A detailed flowchart showing the precise steps and decision logic of a program or algorithm.

Best for:

• Teaching programming logic to beginners
• Documenting complex algorithms for review
• Pseudocode before implementation
• Legacy code documentation

Example: Simple login algorithm

╭───────────╮
│   Start   │
╰─────┬─────╯
      │
      ▼
┌─────────────────┐
│ Get username    │
│ and password    │
└──────┬──────────┘
       │
       ▼
  ◇────────────◇
 ╱ Valid user?  ╲
╱               ╲
Yes              No
│                │
▼                ▼
┌──────────┐  ┌────────────────┐
│ Load     │  │ Increment      │
│ dashboard│  │ attempt count  │
└──────┬───┘  └──────┬─────────┘
       │             │
    ╭──────╮         ▼
    │  End │    ◇────────────◇
    ╰──────╯   ╱ Attempts ≥ 3?╲
              ╱                ╲
            Yes                 No
             │                  │
             ▼                  │
  ┌──────────────────┐          │
  │ Lock account     │          │
  └────────┬─────────┘          │
           │                    │
        ╭──────╮                │
        │  End │    ←───────────┘
        ╰──────╯

BPMN diagram (Business Process Model and Notation)

BPMN is a formal standard (ISO/IEC 19510) for modeling business processes. It uses a specific notation with events, activities, gateways, and sequence flows. BPMN diagrams are more expressive than basic flowcharts—they handle parallel processing, timers, message events, and error handling.

Definition: A standardized notation for modeling business processes with rich support for parallel flows, events, and error conditions.

Key elements:

• Events: Circle shapes (start, intermediate, end)
• Activities: Rounded rectangles (tasks, sub-processes)
• Gateways: Diamond shapes (exclusive, inclusive, parallel, event-based)
• Sequence flows: Solid arrows
• Message flows: Dashed arrows (between pools)
• Pools and lanes: Swimlane structure representing organizations and roles

Best for:

• Enterprise process automation (BPM software implementations)
• Formal process documentation for large organizations
• Communicating with business analysts and enterprise architects
• Processes that require precise handling of parallel flows and exceptions

When NOT to use: BPMN is complex. For most business process documentation, a simple swimlane flowchart is more readable and easier to maintain. Reserve BPMN for situations where the precision of the notation is required—typically when the diagram will drive software automation.

State diagram (state machine)

A state diagram shows the states that a system, object, or process can be in, and the transitions between those states triggered by events or conditions.

Definition: A diagram showing the states of a system and the events or conditions that trigger transitions between states.

Best for:

• Software object lifecycle documentation
• UI state management
• Protocol design
• Embedded system behavior
• Order, ticket, or entity status tracking

Example: Order status lifecycle

                    ┌────────────┐
    ────────────→   │  Pending   │
                    └─────┬──────┘
                          │ payment confirmed
                          ▼
                    ┌────────────┐
                    │ Processing │
                    └─────┬──────┘
                          │ item picked
                          ▼
                    ┌────────────┐
          ┌──────── │  Shipped   │
          │         └─────┬──────┘
     returned             │ delivered
          │               ▼
          ▼         ┌────────────┐
    ┌──────────┐    │ Completed  │
    │ Returned │    └────────────┘
    └──────────┘

Difference from process flowchart: A state diagram focuses on what an object is at any point in time, not on what happens step by step. The order is not "doing" processing—it is in a "Processing" state.

Comparison table

Type	Best for	Shows sequence	Shows responsibility	Shows data flow	Complexity
Process flowchart	Documenting a process end-to-end	Yes	No	No	Low
Swimlane diagram	Cross-department processes	Yes	Yes	No	Medium
Data flow diagram	System data architecture	No	No	Yes	Medium
Workflow diagram	Business process for general audiences	Yes	Partial	No	Low
Decision tree	Troubleshooting, eligibility, diagnosis	Yes	No	No	Low
System flowchart	IT systems with data storage	Yes	No	Partial	High
Document flowchart	Document-centric processes	Yes	Yes	No	Medium
Program flowchart	Algorithm logic	Yes	No	No	Medium
BPMN diagram	Formal enterprise process automation	Yes	Yes	Partial	High
State diagram	Object or system lifecycle	No	No	No	Medium

How to choose the right type

Work through these questions in order:

1. Are you mapping data, not steps? Yes → Use a data flow diagram or state diagram.

2. Does the process involve multiple people, departments, or systems? Yes → Use a swimlane flowchart.

3. Is every branch a decision with no loops? Yes → Use a decision tree.

4. Are you documenting a computer system with databases and document outputs? Yes → Use a system flowchart.

5. Do you need formal BPMN for software automation? Yes → Use a BPMN diagram.

6. Is the primary concern what happens to a document? Yes → Use a document flowchart.

7. Everything else: Use a process flowchart. It handles 80% of cases.

The most common mistake is choosing a complex diagram type (BPMN, DFD) when a simple process flowchart would communicate more clearly to the actual audience. Match the complexity of your diagram to the complexity of your audience's needs, not to what the notation is theoretically capable of representing.

Creating any flowchart type with Flowova

Flowova supports all the major flowchart types. Describe your process in plain text—including the type you want—and the AI generates the diagram automatically. You can then switch layouts, add swimlanes, adjust shapes, and export for sharing.

For common use cases, the template library has ready-to-use starting points for process flows, swimlane diagrams, decision trees, and more. The text to flowchart tool is the fastest way to convert an existing written process into a diagram.

Summary

There are ten major flowchart types, each suited to a different purpose:

• Process flowchart for sequential steps
• Swimlane for cross-functional responsibility
• Data flow diagram for system data architecture
• Workflow diagram for business processes and general audiences
• Decision tree for branching logic without loops
• System flowchart for IT systems with storage and hardware
• Document flowchart for document-centric processes
• Program flowchart for algorithm logic
• BPMN for formal enterprise automation
• State diagram for object or system lifecycles

Start with a process flowchart for most needs. Add swimlanes when responsibility matters. Choose specialized types only when a process flowchart genuinely cannot represent what you need to show.

Related resources

• What Is a Flowchart? Everything You Need to Know – Foundational flowchart guide
• Flowchart Symbols and Their Meanings – Complete symbol reference
• How to Make a Flowchart: Complete Beginner Guide – Step-by-step creation guide
• Text to Flowchart Tool – Convert text descriptions instantly
• Browse flowchart templates – Ready-to-use starting points