Checklist to Map Processes Before You Automate

Process mapping before automation comes down to seven questions for each task: how often it happens, who does it, where the data lives, what the exceptions are, what usually goes wrong, what triggers it and what proves it is done. The answers tell you what deserves automation and what needs cleanup first. Run this checklist with the people who do the work, not just their manager.

First, pick the right process

List five to ten recurring admin and sales tasks: entering orders, issuing quotes, checking invoices, chasing customer replies, updating stock in a spreadsheet. Map one at a time. Trying to map the whole company at once is how projects stall.

The checklist, question by question

1. What is the volume and frequency?

Why it matters: rare tasks seldom repay the effort. How to check: count how many times the task happened last month and how long each took, start to finish.

2. Who owns the process?

Why it matters: without an owner, nobody validates the rules or approves changes. How to check: ask who answers when it goes wrong. If the reply is an awkward silence, name an owner before moving on.

3. Where is the data and in what format?

Why it matters: automation relies on consistent data. How to check: open three real examples and compare them. If one customer shows up under four spellings, cleanup comes before the workflow.

4. What are the exceptions?

Why it matters: exceptions define the real complexity. How to check: ask the person doing the job to count the last off-pattern cases. If more than a fifth are exceptions, automate only the main path and leave the rest to a person.

5. What is the most common error and what does it cost?

Why it matters: frequent errors are a strong case for automation. How to check: look for returns, rework and complaints tied to the task and estimate the cost in hours or dollars.

6. What starts the task and what ends it?

Why it matters: without a clear trigger and completion rule, a workflow has no start or finish. How to check: write each in one sentence, such as: starts when the order is approved, ends when the work order is logged in the ERP.

7. Which systems and people are involved?

Why it matters: every extra system needs a connection and every extra person needs alignment. How to check: sketch the steps on one sheet, one box per system or person.

Deciding what is worth automating

Score volume, repetition, rule clarity and data quality from 1 to 5. Processes scoring high on all four make the best pilots. High-volume processes with muddled rules need standardizing first. Low-volume ones with clear rules can wait.

What to bring to the project kickoff

• A one-page drawing of the current process.
• Three real examples, including one exception.
• Average time per run and monthly count.
• The name of the process owner and of who performs it.
• A goal, for example cutting response time in half.

With this material any vendor can scope the work far more accurately. To turn your map into a project, see our automation and AI work.

Frequently asked questions

How long does it take to map a process?

A simple process usually takes one or two one-hour conversations with the person doing the task, plus a handful of real examples.

Do I need software to map processes?

No. A sheet of paper, a whiteboard or a simple slide is enough for a first pass.

What if everyone does the process differently?

Then standardize before automating. Pick the best method, test it for a few weeks and only then build.