A business process mapping template is a fixed list of questions you answer for every step of a workflow: what starts it, who owns it, which systems it touches, where it hands off, what goes wrong, how often it runs and how long it takes. Fill it in honestly and you get a map you can actually automate from.
Why map a process before automating it
Mapping comes first because automation copies whatever you give it. If the process has unclear owners, duplicate approvals or missing rules, a bot or an AI model will repeat those problems faster. A one-page map shows where the time goes, where errors start, and which steps are worth automating at all.
Hypothetical example: a team suspects data entry, but the map reveals a three-day approval wait. Assigning an approver may address the delay more directly than automating entry. This illustrates the method; it is not a measured client result.
A map also gives everyone the same picture. Operations, finance and IT usually describe one process three different ways. Putting it on one page ends that argument early.
The process mapping template
Copy the table below into a spreadsheet and add one row per step. The example values are hypothetical, not benchmarks; replace them with measured counts and your actual approval policy. Keep each step to a single action by a single owner.
| Column | What to write | Example |
|---|---|---|
| Step number | Order in the flow | 3 |
| Trigger | What starts this step | Supplier invoice arrives by email |
| Action | One verb, one object | Enter invoice into accounting system |
| Owner | Role, not person | AP clerk |
| Systems | Every tool touched | Outlook, QuickBooks, shared drive |
| Input and output | What comes in, what leaves | PDF in, draft bill out |
| Handoff to | Next owner | Department manager |
| Rules | Decisions applied | Over 5,000 CAD needs a second approval |
| Exceptions | What goes wrong and how often | Missing PO number, roughly 1 in 10 |
| Volume | Items per week or month | 400 per month |
| Time per item | Hands-on minutes | 6 minutes |
| Wait time | Elapsed time before next step | 2 days |
Add a header block above the table with five fields:
- Process name and the business outcome it delivers.
- Start event and end event, so scope is clear.
- Process owner who can approve changes.
- Date mapped and who was in the room.
- Known pain points in the team's own words.
How to run a mapping session
Plan a mapping session with the people who do the work, not only their managers. Its length depends on complexity. Walk one real recent example from start to finish. Write each step as it actually happened, including workarounds. Capture exceptions and volumes before proposing fixes.
Here is the running order we use:
- Invite the doers, the process owner and one person from IT or the system owner.
- Agree the start and end events in the first five minutes.
- Pick one real item, such as last Tuesday's invoice, and trace it step by step.
- Ask "then what happens?" until you reach the end event.
- Go back and ask "what goes wrong here?" at every step.
- Fill in volume and time last, using real counts from reports where possible.
- Read the map back to the group and correct it before anyone leaves.
Keep a "parking lot" list for ideas. People will want to fix things as they go. Write the idea down and keep mapping. Solving during the session skews the AS-IS picture.
Remote sessions work fine. Share a screen with the spreadsheet or a simple diagram tool and type as people talk. Send the draft map the same day while memories are fresh.
AS-IS vs TO-BE maps
The AS-IS map records how the process runs today, including workarounds and delays. The TO-BE map shows how it should run after changes. You need both. AS-IS gives you the baseline to measure savings against. TO-BE shows what will change, who is affected, and what must be built.
| Aspect | AS-IS map | TO-BE map |
|---|---|---|
| Purpose | Record reality | Design the target |
| Source | Interviews and real examples | Workshop plus requirements |
| Includes workarounds | Yes, always | No, they should be removed |
| Used for | Baseline time, cost and errors | Build scope and change plan |
| Common mistake | Mapping the policy, not the practice | Automating steps that should be deleted |
Build the TO-BE in three passes. First remove steps that add no value. Then simplify rules and approvals. Only then mark the remaining steps for automation. This order matters. Removing a step is always cheaper than automating it.
Swimlane diagrams
A swimlane diagram draws the process in horizontal or vertical lanes, one lane per role or system. Each step sits in the lane of whoever owns it. Every time the flow crosses a lane, you have a handoff, and handoffs are where most delays, lost items and errors appear.
Use one lane per role and, where it helps, one lane per system. A lane for "QuickBooks" or "CRM" makes system-to-system movement visible. That is often where an integration can replace a person retyping data.
Keep the notation simple. Rectangles for actions, diamonds for decisions, and arrows for flow are enough for most teams. If you need a formal standard, BPMN covers it, and our glossary explains the terms. Count the lane crossings on your AS-IS diagram. A process that crosses lanes ten times for one item is a strong candidate for redesign.
How the map feeds automation decisions
A finished map tells you which steps to remove, which to automate and which to leave with people. Steps with structured input, clear rules and high volume suit workflow or RPA. Steps with messy input such as emails or PDFs suit AI with human review. Steps with rare, high-risk judgment stay manual.
Go through the TO-BE rows and tag each one:
- Remove when the step adds no value or duplicates another check.
- Integrate when data moves between two systems that both have an API, so no one needs to retype it.
- Automate with rules when input is structured and the rules are written down. See process automation.
- Automate with AI and review when input is unstructured but the outcome can be checked. See AI automation.
- Keep manual when volume is low or a mistake would be costly.
Then use the volume and time columns to size the benefit. Our AI automation ROI calculator guide walks through the maths. If you are torn between bots and models, read RPA vs AI automation.