What is a process flow diagram?
A process flow diagram (PFD) is a visual map of the sequential steps, decisions, and participants involved in completing a business process. It shows the path work takes from a trigger event to a defined outcome, using standardized ANSI symbols so that any reader — regardless of background — can interpret the diagram consistently.
Process flow diagrams are used across operations, quality management, HR, IT, and finance to document current-state ("as-is") workflows, identify bottlenecks and handoff failures, and design improved future-state ("to-be") processes. They are the most widely used process documentation artifact in ISO 9001 quality management systems.
ANSI process flow symbol reference
The five core ANSI symbols appear in every standard process flow diagram. flow-chart.io generates all five as typed objects with correct shape, size, and label placement.
| Symbol | Shape | Meaning | Example usage |
|---|---|---|---|
| ⬭ | Oval (Terminator) | Marks the start or end of the process. | "Customer submits request" (start); "Invoice paid" (end) |
| ▭ | Rectangle (Process) | A task, action, or operation performed by a person or system. | "Validate order details"; "Send confirmation email" |
| ◇ | Diamond (Decision) | A branching point where the flow takes one of two or more paths based on a condition. | "Order approved?"; "Credit check passed?" |
| ▱ | Parallelogram (Input/Output) | Data, a document, or a record entering or leaving the process. | "Purchase order received"; "Approval form submitted" |
| ○ | Circle (Connector) | Indicates that the flow continues on another part of the diagram or on another page. | Off-page reference "A"; on-page continuation |
Process types reference
Process flow diagrams are adapted to different analytical goals. The type you choose determines the symbols, lanes, and level of detail you need.
| Type | Description | Best for |
|---|---|---|
| As-is process map | Documents the current state of the process exactly as it operates today, including known workarounds and unofficial steps. | Baseline documentation, gap analysis, compliance audits |
| To-be process map | Defines the improved or redesigned future state after waste, redundancy, or handoff delays have been eliminated. | Process improvement projects, system rollouts, change management |
| Linear process flow | Each step has exactly one input and one output; no branching. Used for straightforward sequential processes. | Manufacturing steps, simple approval chains, data pipelines |
| Branching process flow | Includes decision diamonds that route the process down different paths depending on conditions. | Approval workflows, exception handling, customer service triage |
| Cross-functional (swimlane) | Divides the diagram into horizontal or vertical lanes, one per role or department, to show who performs each step and where handoffs occur. | Multi-department processes, SLA accountability, onboarding flows |
| Single-lane process flow | Shows a process performed entirely within one role or system, without cross-functional handoffs. | Standalone SOPs, system-only automation flows, focused sub-processes |
Real-world process flow diagram examples
These are common processes that teams document with process flow diagrams. Each can be generated in flow-chart.io by describing the steps in plain language.
| Department | Process | Why document it |
|---|---|---|
| HR / People Ops | Employee onboarding | Ensures consistent experience across hiring managers; surfaces steps where new hires stall before their first productive day. |
| Operations / Fulfillment | Order fulfillment | Maps each handoff from order receipt through pick, pack, ship, and delivery confirmation; identifies where orders are delayed or lost. |
| IT / Security | Incident response | Defines the triage, escalation, containment, and resolution sequence so on-call engineers follow a consistent runbook under pressure. |
| Product / Marketing | Product launch | Coordinates cross-functional deliverables across product, design, engineering, marketing, and support so nothing ships without the full checklist. |
How to generate a process flow diagram with flow-chart.io
- Create a free account — 40 AI credits/month, no credit card required.
- Describe your process — for example: "Employee onboarding process with swimlanes for HR, IT, and the hiring manager. Include equipment provisioning, system access setup, and a decision step for remote vs. on-site employees."
- Review and edit — every symbol is a live object. Click any step to rename it, drag to reorder, or add a new branch.
- Export — SVG, PNG, PDF, or JSON. All exports are derived from the scene graph, not screen captures.
Best practices for process flow diagrams
- Document the actual process, not the ideal one — walk the process with the people who do it before drawing anything.
- Keep the happy path on a straight left-to-right spine; route exceptions and error paths off to the side or downward.
- Name every process rectangle with a verb and a noun: "Review invoice", not "Invoice review".
- Label every decision diamond with a yes/no question: "Invoice approved?" with Yes and No exits clearly marked.
- Use swimlanes for any process that crosses two or more roles — handoff arrows between lanes are where delays concentrate.
- Keep each diagram to one process level; link to sub-process diagrams for steps that are themselves complex workflows.
- Validate the diagram with the people who actually do the work before using it for training, audits, or process improvement.
Frequently asked questions
- What is a process flow diagram?
- A process flow diagram (PFD) is a visual map that shows the sequential steps, decisions, and actors involved in completing a business process. It uses standardized ANSI symbols — ovals for start/end, rectangles for tasks, diamonds for decisions, parallelograms for inputs and outputs, and circles for connectors — to represent the flow of work from trigger to outcome. Process flow diagrams are used in operations, quality management, and process improvement to document current-state workflows, identify bottlenecks, and design improved future-state processes.
- What is the difference between a process flow diagram, a flowchart, and BPMN?
- All three are process visualization tools but differ in formality and purpose. A flowchart is a generic term for any diagram showing sequential steps using basic shapes — it has no enforced standard. A process flow diagram (PFD) specifically follows ANSI/ISO symbol conventions and is used to document operational business processes. BPMN 2.0 (Business Process Model and Notation) is a formal ISO standard (ISO/IEC 19510) with precise semantics for each element type, designed to produce executable diagrams that process automation engines like Camunda or jBPM can run directly. Use a process flow diagram for operational clarity; use BPMN when the diagram needs to drive automation.
- What are the standard ANSI symbols used in process flow diagrams?
- The five core ANSI process flow symbols are: Oval (Terminator) — marks the start or end of a process; Rectangle (Process) — represents a task, action, or operation performed by a person or system; Diamond (Decision) — marks a branching point where the flow takes one of two or more paths based on a condition; Parallelogram (Input/Output) — represents data entering or leaving the process, such as a form, report, or system record; Circle (Connector) — indicates that the flow continues on another part of the diagram or another page. Arrows connect all symbols and show the direction of flow.
- What is value stream mapping and how does it relate to process flow diagrams?
- Value stream mapping (VSM) is a Lean manufacturing technique that diagrams the end-to-end flow of materials and information needed to deliver a product or service to the customer. It extends the basic process flow diagram by adding data boxes below each step (cycle time, uptime, operator count), inventory triangles between steps, and a timeline showing value-added vs. non-value-added time. Process flow diagrams show what happens; value stream maps quantify how long each step takes and where waste accumulates. VSM is most useful for identifying elimination targets in production and service delivery processes.
- When should I use a process flow diagram instead of another diagram type?
- Use a process flow diagram when you need to document, communicate, or improve an operational business process and the audience includes non-technical stakeholders. Process flow diagrams are the right choice for onboarding procedures, order fulfillment workflows, incident response runbooks, compliance audits, and any situation where the goal is operational clarity rather than software specification. Choose BPMN if the process will be automated in a workflow engine. Choose a data flow diagram (DFD) if the focus is on data movement between systems rather than human tasks. Choose an org chart if you are showing reporting structure.
- How do I read a process flow diagram?
- Start at the oval marked Start or Trigger at the top or left of the diagram. Follow the arrows through rectangular process steps. At each diamond (decision), read the condition label and follow the Yes or No branch. Parallelograms indicate that a document, form, or data record is produced or consumed at that point. Circles (connectors) mean the flow continues elsewhere — look for a matching circle with the same letter or number. End ovals mark terminal states where the process concludes. In a cross-functional (swimlane) diagram, each horizontal or vertical lane represents a different role or department, and arrows crossing lane boundaries show handoffs.
- What are best practices for creating a process flow diagram?
- Seven best practices for effective process flow diagrams: (1) Capture the actual process, not the ideal — walk the process before drawing it. (2) Keep the happy path on a straight spine from left to right or top to bottom; route exceptions and error paths off to the side. (3) Name every step with a verb and a noun ("Review invoice", not "Invoice review"). (4) Label every decision diamond with a yes/no question ("Invoice approved?"). (5) Use swimlanes to show which role or department performs each step — handoffs between lanes are where delays most often occur. (6) Keep each diagram to a single process; link to sub-process diagrams for steps that are themselves complex. (7) Validate the diagram with the people who actually do the work before using it for training or process improvement.