Business Process Mapping for Automation: A Worked Example
Map a business process before automating it. Use a completed lead-handoff example, a copyable worksheet and practical tests for decisions and exceptions.
— Craig Major
Business process mapping records how work moves from a starting event to a completed outcome. A useful map identifies the inputs, actions, decisions, owners and handoffs, including where work waits or goes wrong. For automation, it also shows which steps follow clear rules and which need a person's judgment.
Start with the editable process-mapping worksheet and a recent example of the work. The completed map below shows how to fill it in. A diagram becomes useful when several decision branches make the sequence harder to follow.
Choose the boundary before the tools
Select one process your team repeats. Write the starting event and the definition of done.
For this example, the process starts when a website enquiry arrives. It ends when the correct owner has reviewed the request and recorded a next action. Sending an internal notification alone does not complete the handoff.
The example below is a sample process you can adapt.
Completed process map: enquiry to reviewed handoff
| Step | Owner | Input | Action or decision | Output | Exception path |
|---|---|---|---|---|---|
| Capture enquiry | Intake coordinator | Website submission | Check required contact and request fields | Intake record with source | Incomplete details enter a clarification queue |
| Match account | Sales operations | Company and contact details | Check for existing customer and duplicate request | Matched or new account | Conflicting matches go to review |
| Assess service fit | Sales owner | Request and agreed fit rules | Identify relevant service and unresolved questions | Fit evidence and next question | Unclear fit remains unqualified pending review |
| Assign owner | Sales operations | Account owner, service and availability | Apply the agreed routing rules | Assigned review task | Missing owner goes to designated backup |
| Review and respond | Assigned owner | Request, context and outstanding questions | Confirm next action and approve response | Recorded next action | Scope or pricing exceptions go to the decision owner |
The map exposes where the process needs a clear rule. It also tells you what the system must preserve: the original enquiry, matching evidence and unresolved questions.
Mark time spent and time waiting separately
Active work and elapsed time reveal different problems. A person may spend a few minutes preparing a record that waits a day for review.
For a sample of recent requests, record when each step starts and finishes, along with the effort involved. Include the time spent correcting incomplete or incorrect work.
Use records to check your team's estimates. Inbox timestamps, CRM activity and task history can provide a more useful baseline.
Identify the right kind of change
| What the map reveals | Change to consider |
|---|---|
| The owner is unclear | Assign a responsible person and a backup |
| The same data is copied between tools | Use a supported integration |
| Free-text requests need interpretation | Test AI extraction or summarisation |
| Staff apply different fit criteria | Agree written criteria |
| A task waits because context is missing | Include the required evidence in the handoff |
| Nobody sees failed or stalled records | Create a review view and escalation rule |
The map may lead to a process change, ordinary automation, AI or a combination. Choose the change that addresses the observed problem.
Copy this worksheet for your own process
| Field | Your answer |
|---|---|
| Process name | |
| Starting event | |
| Definition of done | |
| Person accountable for the outcome | |
| Systems and source records | |
| Required inputs | |
| Main actions and decisions | |
| Handoffs and receiving owners | |
| Exceptions and backup paths | |
| Baseline measure | |
| First change to test | |
| Acceptance evidence |
Download the process-mapping worksheet to record the steps in a spreadsheet.
Test the map with difficult cases
Walk through a duplicate request, a missing field and an unavailable owner. Then ask someone who was not in the workshop to follow the map using a recent record.
If they need an unwritten instruction to reach the right result, add the rule or decision owner. Keep unresolved choices visible instead of treating them as settled.
A first automation scope is ready when the team can describe the normal path, identify exceptions and agree how to judge the output. The person operating the workflow should be involved in that decision.
Process-mapping questions
What is the difference between a process map and a flowchart?
A process map describes the work and responsibilities. A flowchart is one way to display the sequence and decision branches. A table can hold the same operational detail before you draw it.
How detailed should a business process map be?
Include enough detail for someone to carry out the work and recognise an exception. Record the source, owner, decision and required output at each handoff.
Can we automate directly from a process map?
The map is an input to the build. You still need access to the source systems, agreed rules, acceptance cases and a plan for operating the result.
Put the map to work
Use the Automation Opportunity Calculator for the numerical part of the business case. For an enquiry workflow, continue with the Lead Qualification System Planner.
A Strategy Day helps your team map and prioritise the work together. An AI Success Audit provides a detailed review of candidate workflows.