Map the work before choosing the tool
A process map for automation is a working specification, not a flowchart for the wall. This guide sets out what to record for each step, so that a platform setting, an in-house builder or a supplier can all be judged against the same page. It promises no result and does not replace talking to the people who do the work.
Start and end
Fix the two edges first. A map with a vague start or finish tends to grow until it covers the whole business.
- 01
Name the event that starts it
Use one event, such as a form submitted, a call missed or a quote reaching a set age. If two events start the work, you probably have two processes and two maps.
- 02
Describe the finished state
Say what exists when the work is done, for example a booked appointment, an assigned task or an issued quote, and who would check it.
- 03
Write down what is outside the map
List what you are leaving out on purpose, such as invoicing or the sales conversation. Work outside the map can be linked in later.
- 04
Check the process is stable enough to map
If the steps change every few weeks, or nobody owns the outcome, settle that first. A map of a moving process can be out of date before anyone acts on it.
Real current steps
Map what happens, not what the procedure says should happen. Workarounds and informal hand-offs are the parts an automation can break.
- 01
Walk through the work with the person who does it
Sit beside them, or ask them to talk through a recent case from trigger to finish. Written procedures often leave out the workarounds that keep the work moving.
- 02
Check the map against real cases
Pull a small recent set from the inbox, CRM or log, including one that went wrong, and see whether the map explains each of them.
- 03
Write one action and one owner per row
If a step needs the word "and", split it. The template has one row per step, with the trigger, input, owner, system, rule, exception, output and baseline in their own columns.
- 04
Count the baseline instead of recalling it
Record how often the step runs, how long a case waits and how often it needs rework, taken from records. Where no record exists, write that in the cell. Do not set a target yet.
- 05
Settle conflicting accounts
If two people describe the same step differently, record both and decide which version the change will follow.
Systems and access
Write down what the automation could reach before a tool is chosen.
- 01
Name the record that holds the truth
For each material field, such as a name, date or status, say which system holds it and which copy wins if two disagree.
- 02
List how each system is reached
Note whether the step can use an official integration, an export, email or only the screen, and who administers the account.
- 03
Ask for the least access that lets the step work
Start with read-only access and add write access only to the step that needs it. A smaller reach is easier to check and easier to remove.
- 04
Mark the steps that handle personal data
Flag them in the map, so that the data protection question is asked when the step is designed. This guide is not legal advice.
- 05
Write down who owns each account and where the exports live
Accounts, credentials and data should sit in your name. That keeps you able to change tool or supplier without redrawing the map.
People and decisions
Every step has someone who is accountable for it. The map should show whether that person is applying a rule or using judgement.
- 01
Name a person for each step
A team is not an owner. Someone has to be able to say what the step should have done.
- 02
Separate rules from decisions
A rule can be written down and applied the same way each time, such as a required field. A decision needs judgement, such as a concession or a complaint. Mark each row as a rule, a check by a person or a decision by a person.
- 03
Write each rule so someone else could apply it
If the owner says "I just know", ask what they look at first. A rule that cannot be put into words probably belongs with a person for now.
- 04
Keep consequential decisions with a named person
Customer, commercial, clinical, legal and financial judgements stay with the person who answers for them. An automation can prepare the case.
- 05
Have each owner confirm their own rows
Ask them to mark what is wrong before anything is built, and record the date and who confirmed it.
Exceptions
The normal path is easy to describe. The cases that do not fit are where an automation needs the most care.
- 01
Ask what goes wrong at each step
Look for missing, duplicate, late, contradictory and unreadable input, and for a system that is not available.
- 02
Give each exception a destination
Name the person or queue that receives it and how soon someone looks. An exception with no destination is a lost case.
- 03
Count how often exceptions happen
If most cases are exceptions, the process may not be ready to automate. If they are rare but costly, a clear stop rule matters more than speed.
- 04
List the cases the automation must not touch
Complaints, disputes and sensitive situations are common candidates. Write it as plain cases and not as a score.
- 05
Plan the manual route
Decide how the work continues by hand if the automation is stopped, who does it, and who can pause it.
Native alternatives
With the map in hand, check what you already have before adding anything new.
- 01
Read what your current systems can already do
Booking, CRM, accounting, form and email tools often include reminders, assignments and rules. Review their settings and documentation against each row first.
- 02
Take the lightest route that meets the row
A change to the process, a platform setting, a connected workflow, a controlled manual queue, a bounded AI step and a custom build are different amounts of work. The How it works page compares the options.
- 03
Use AI for a bounded information task
AI can classify, extract or draft from material you provide, with a review standard and a route to a person. It does not take over the owner's judgement.
- 04
Leave a step alone when change is not worth it
Some steps are rare, cheap or sensitive enough to stay as they are. Writing that down is a valid result of mapping.
- 05
Ask what you keep if you switch it off
For any option beyond a native setting, ask where the configuration, templates and logs are held and what stays with you if you change supplier.
Acceptance criteria
Agree how a changed step will be judged before anyone builds it. Otherwise the test becomes whatever the finished work happens to do.
- 01
Write a check for each step
Say what the output should look like in a form someone can test against a case, for example an enquiry logged once with a named owner.
- 02
Test with the cases you sampled
Run the awkward ones too. Each exception should reach its named destination.
- 03
Agree when to pause or step back
Decide beforehand what stops the test, such as a wrong record sent on or an exception that reached nobody.
- 04
Compare with the baseline you counted
Use the same measures, counted the same way, over a comparable period. The measurement guide covers costs, hours and outcomes.
- 05
Name who signs it off and who owns it afterwards
Release and later changes need a person who can approve them and a person who watches the exception queue.
Eight checks before you hand the map to anyone
Answer these in writing. The downloadable template has a column for most of them.
- 1.Does the map name one start event, one finished state and what is left out?
- 2.Was it built from real recent cases, including one that went wrong?
- 3.Does every step have a named owner, a system, a written rule and an output?
- 4.Is the baseline counted from records, with the gaps marked?
- 5.Does each exception have a destination and a named person?
- 6.Has each owner confirmed their own rows?
- 7.Have the existing systems been checked for what they already do?
- 8.Is there an acceptance check for each step, written before building?
Download the process-map template (CSV) A plain spreadsheet file with a header, one example row to replace and blank rows for your steps. Edit it freely; it opens in any spreadsheet program.
Continue with the next step
These pages cover the decisions that follow once the map exists.
Bring the map, gaps included
Send the rows you have filled in. We will say plainly what looks straightforward, what should stay with a person and whether something you already pay for covers it.