How to Map a Business Process Before You Automate It

Automating a messy process produces a faster mess. Mapping the process first lets you see the steps people actually follow, the places work stalls and the parts that should be deleted instead of automated. This guide is for owners and team leads who have picked a process and want to prepare it properly. You end with a one-page map, a list of exceptions and a clear brief for whoever builds the automation. The glossary entry on process mapping has the short definition and the business process mapping article covers the formal notations.

Step 1: Define the start and the finish

Every process has a trigger and an outcome. Write both in one line each.

• Trigger: "A new enquiry arrives by email, web form or phone."
• Finish: "The enquiry has an owner, a category and a first reply sent."

If you cannot name a clear start and finish, you are looking at two processes tangled together. Split them and map one at a time.

Step 2: Gather the right people

Talk to the person who does the work every day, not only the manager. Managers describe the process as designed. The person at the desk describes the process as it runs, including the workarounds. Bring both if you can, and ask the person doing the work to talk while someone else writes.

Better still, watch one real run. Sit beside them for a single enquiry, quote or invoice and note what they do, including the small things like checking another tab or asking a colleague a quick question. Those small things are often where the hidden logic lives.

Step 3: Walk through the steps in order

Write each step as a short verb phrase: "Open the email", "Copy the phone number into the CRM", "Check the diary for availability", "Reply with a price range".

For each step, capture five facts:

Fact	Question
Who	Which person or role does this?
Where	Which system, inbox or document?
Input	What information do they need?
Output	What do they produce or change?
Time	Roughly how long does it take?

Resist the urge to tidy as you go. Record what happens. A step done in a sloppy way is still a step.

Step 4: Mark every decision

Decisions are where automation succeeds or fails. Wherever someone says "it depends", stop and write out the rule.

Ask: "What do you look at to decide?" and "What would you do in each case?" Turn the answers into if-then lines:

• If the job is outside our service area, reply with the decline template.
• If the budget is under our minimum, send the starter information.
• If the enquiry mentions an emergency, call the customer.

Some decisions will have crisp rules. Others rely on judgement that the person cannot easily explain. Mark these clearly. A tool can handle the first kind. The second kind should stay with a person, or have a person review the result.

Step 5: Collect the exceptions

Ask: "What goes wrong? What was the last odd case you had?" Write every exception on a separate list. Typical examples are missing information, duplicate entries, customers who reply from a different email address and urgent jobs that skip the queue.

Exceptions matter because automations handle the usual case well and the odd case badly. For each exception, decide now what should happen: handle automatically, flag for a person, or stop and ask. This list becomes the safety net of your automation.

Step 6: Look for waste

With the map on a page, look at it with fresh eyes. Circle:

• Steps that copy the same information into a second place.
• Steps that exist only because of a past problem that no longer applies.
• Waiting time, where work sits until someone notices it.
• Approval steps that always say yes.

Delete what you can before automating. A removed step costs nothing to run and never breaks. Be careful with approvals, because some exist for good reasons such as financial control or record keeping, which the ATO's record keeping help for small businesses covers. Ask why the step was added before you cut it.

Step 7: Redesign the process on paper

Draw the improved version. Keep it simple: trigger, steps, decisions, finish. Mark each step as one of three types:

1. Automate: a tool does it with no human involved.
2. Assist: a tool prepares it, a person approves or edits.
3. Keep human: a person does it.

Where the step involves reading or writing free text, such as classifying an enquiry or drafting a reply, an AI model like ChatGPT or Claude can often take the first pass. Mark it Assist until you have seen it perform on real examples. This is the human-in-the-loop pattern (Wikipedia has the background), and our guide on keeping a human in the loop covers how to set up that check.

Step 8: Write the brief

Turn the map into a short brief for whoever builds the automation, whether that is you, a colleague or an agency. Include the trigger, the steps, the decision rules, the exceptions and the goal sentence. Add a handful of real examples, including the ugly ones, so the builder can test against reality. A builder with real examples builds a better tool than one working from a neat description. If you wonder whether you need a developer at all, see do I need a developer to automate. For finished designs, look at an enquiry triage workflow and quote follow-up. To check the process is worth automating, score it first.

Copyable process map template

PROCESS: ____________________
Owner: ________   Date mapped: ________

Trigger:  ______________________________
Finish:   ______________________________

STEPS
#  Action          Who    System    Input     Output    Minutes
1  ________        ____   ______    ______    ______    ___
2  ________        ____   ______    ______    ______    ___

DECISIONS
D1  Question: ________  If yes: ________  If no: ________
D2  Question: ________  If yes: ________  If no: ________

EXCEPTIONS
E1  What happens: ________  Handle: auto / flag / stop-and-ask
E2  What happens: ________  Handle: auto / flag / stop-and-ask

WASTE SPOTTED
- ________________________

REDESIGN  (mark each step Automate / Assist / Keep human)
1 ____  2 ____  3 ____

REAL EXAMPLES (attach 5 to 10, including messy ones)

What to do next

A good map makes the build quick and the result reliable. If you would like a second pair of eyes on your map, or want someone to turn it into a working automation, workflow automation from 21Labs begins with a free discovery. Tell us the process through the form below and we reply within 24 hours.