Process Flow Diagram (PFD)

What is a Process Flow Diagram (PFD)?

A process flow diagram (PFD) is a flowchart that uses standard shapes and arrows to show a process's steps, decisions and sequence, often with owners. In chemical engineering the term refers specifically to plant equipment and streams.

Updated November 2026 · 3 min read


A process flow diagram (PFD) is a picture of how a process runs from start to finish: the steps, the decisions, the order they happen in and, often, who does each one. Standard shapes stand for different kinds of steps, and arrows show the flow between them. A good diagram lets someone understand a process in a minute that would take pages to describe in text.

In business and product operations, process flow diagram is used broadly for any flowchart of a workflow. In chemical and process engineering the term has a narrower, technical meaning: a diagram of a plant showing major equipment, streams and operating conditions, which is less detailed than a piping and instrumentation diagram (P&ID). This entry covers the business sense.

Process flow diagram symbols

ShapeMeaningExample
Oval or rounded rectangleStart or end point"Customer submits request"
RectangleA process step or action"Support agent reviews ticket"
DiamondA decision with two or more outcomes"Refund over $500?"
ParallelogramInput or output"Approval email sent"
Document shapeA document or report"Signed contract"
ArrowDirection of flowConnects each step to the next

Teams that need a formal standard often use Business Process Model and Notation (BPMN), maintained by the Object Management Group, which adds defined symbols for events, gateways and message flows.

Types of process flow diagrams

  • Basic flowchart. A single sequence of steps and decisions. Good for simple or linear processes.
  • Swimlane diagram. Splits the diagram into lanes, one per role or team, so every handoff is visible. The most useful format for cross-functional processes.
  • High-level process map. Five to ten major stages with no detail, used to agree scope before mapping.
  • Value stream map. Adds time, wait and inventory data to show where value is created and where work waits. See value stream mapping.

How to create a process flow diagram

  1. Define the start and end. Name the trigger that starts the process and the outcome that ends it.
  2. List the steps with the people who do them. Walk through a real recent case rather than describing the process from memory.
  3. Choose the format. Use swimlanes if more than one team is involved.
  4. Draw the main path first. Map the most common route, then add decisions and exception paths.
  5. Add data where it helps. Note the time each step takes and how long work waits between steps.
  6. Validate with participants. Ask each role to confirm their part. Disagreements often reveal that people follow different processes.

A process flow diagram example

Consider a hypothetical software company whose customer refunds take an average of 6 days. The support operations lead draws a swimlane diagram with three lanes: support, finance and the account manager. The diagram shows nine steps and two decision points: whether the customer is on an annual contract and whether the refund exceeds $500.

Adding times exposes the problem. The actual work across all steps takes about 2 hours, but refunds over $500 wait an average of 4 days for account-manager approval, and finance processes refunds in a weekly batch. The team raises the approval threshold to $2,000 and moves finance to daily processing. The diagram also shows that annual-contract refunds are entered twice, once in the billing system and once in a spreadsheet, so the spreadsheet step is removed.

  • Workflow diagram. Often used interchangeably. Some teams reserve workflow diagram for flows that include system automation.
  • User flow. A user flow maps the screens and actions a user takes in a product, not an internal business process.
  • Cumulative flow diagram. Despite the name, a chart of work items by status over time, not a map of steps.

Common pitfalls

  • Mapping the official process. Diagrams drawn in a meeting room often miss the workarounds people use daily.
  • Too much detail. A diagram with 60 boxes is hard to read. Keep the main diagram high-level and link detailed sub-processes.
  • Hiding handoffs. Without swimlanes, the delays between teams, where most waiting happens, are invisible.
  • Inconsistent symbols. Mixing shapes without a legend makes diagrams ambiguous.
  • Never updating it. A diagram that no longer matches the process misleads new team members.

Process flow diagrams are a core tool in process documentation and operational bottleneck analysis, and they are often the starting point for workflow automation.

Frequently asked questions

What symbols are used in a process flow diagram?

An oval or rounded rectangle marks the start or end, a rectangle shows a process step, and a diamond shows a decision with two or more outcomes. A parallelogram represents an input or output, a document shape represents a report or form, and arrows show the direction of flow. Teams needing a formal standard often use BPMN notation.

When should you use a swimlane process flow diagram?

Use a swimlane diagram whenever more than one role or team takes part in a process. Each lane belongs to one role, so every handoff between teams becomes visible. That matters because most waiting time happens at those handoffs, and a basic flowchart without lanes tends to hide the delays a team is trying to find.

What is the difference between a process flow diagram and a user flow?

A process flow diagram maps an internal business process: the steps, decisions and handoffs between people or teams, such as how a refund gets approved. A user flow maps the screens and actions a person takes inside a product to complete a task. One describes how the organization works; the other describes how the product is used. See user flow.