How to Map a Business Process Flow: 5 Steps and Examples
Asked to document a business process and not sure where to start? A process flow turns how work actually gets done into a diagram anyone can follow — the foundation for onboarding, handovers, and process improvement.
This guide walks through the basics, a 5-step method for building your first flow, the symbols and layout rules that keep diagrams readable, and concrete examples by department.
What you will learn
- What a process flow is and 4 benefits of mapping one
- A 5-step method from research to review
- The 4 essential symbols and 3 layout rules
- Real flow examples for sales, approvals, and fulfillment
What Is a Business Process Flow?
A business process flow is a diagram that captures a process from start to finish using three elements: tasks, decisions, and owners. Unlike a written manual, the sequence and branching are visible at a glance. Here is a minimal example for expense reimbursement:
- Smoother onboarding and handovers — knowledge stops living in one person's head
- Bottlenecks become visible — you can see where work piles up and who is overloaded
- Less key-person risk — undocumented know-how becomes a shared asset
- A foundation for automation — clear current-state flows make tool adoption far easier
5 Steps to Create a Process Flow
- Define the goal and scope: decide why you are mapping the process and exactly where it starts and ends
- List the actors and tasks: write down every department, role, and task involved — order does not matter yet
- Sequence the tasks and add branches: arrange tasks chronologically and add decision points and exception paths
- Draw it with standard symbols: use terminator, process, and decision shapes; swimlanes by role clarify ownership
- Review with the people who do the work, then keep it updated as the process changes
Symbols and Layout Rules
| Symbol | Shape | Meaning |
|---|---|---|
| Terminator | Rounded rectangle | Start and end of the flow |
| Process | Rectangle | A single task such as “create a quote” |
| Decision | Diamond | A branch point — always label the exits (Yes/No) |
| Arrow | Solid line | Direction of flow, one way only |
Readability matters more than strict notation: keep the flow in one direction, avoid crossing lines, and put exactly one task in each box. As a rule of thumb, split any diagram that grows beyond about 20 nodes — DrillSpark's drill-down feature lets you layer overview and detail flows.
Examples by Department
Sales: from lead to closed deal
Back office: request and approval loop
Request submitted → manager review → approve or send back → accounting. Making the rejection loop explicit shows exactly where time is lost.
Operations: order to shipment
Order received → stock check → in stock? → pick, pack, ship or reorder and wait. Cross-department flows like this are a classic fit for swimlanes.
Work Faster with Templates and AI
You can draw flows in Excel or PowerPoint, but aligning shapes by hand makes updates painful — and outdated diagrams are worse than none. With DrillSpark, describe your process in plain language and AI drafts the flowchart in about 30 seconds. Start from a template below, or generate your own for free.