Automating an unmapped process just makes the mess run faster. Before anyone builds anything, you need a plain description of how the work actually flows today – not how the policy says it flows. This guide walks through the exact mapping method, step by step.

It is the practical companion to the full guide on cutting the HR admin tax. Once you have a map, use it to decide which tasks to automate first and to hunt down the duplicate data entry the map exposes. Mapping is the OpsMap™ phase 4Spot runs before every automation build, and it is the step teams skip at their peril.

Before you start

Block ninety minutes and gather three things: read access to the systems the process touches, a blank document or whiteboard, and fifteen minutes with the person who actually runs the workflow today. You are documenting reality, so the person doing the work is your most important source. Do not map from memory or from the policy manual – map from how it truly runs.

The step-by-step mapping method

Step 1: Pick one workflow and set its boundaries

Choose a single, high-volume process – onboarding, offboarding, a leave request, or the payroll input cycle. Define exactly where it starts and where it ends, because a map with fuzzy edges is a map you cannot automate. For onboarding, the boundary runs from “offer accepted” to “employee fully active on day one.” Write that start and end down first. Everything else fits between them.

Step 2: Name the trigger

Every workflow starts with an event. Name it precisely: an offer marked accepted in the ATS, a termination date entered, a form submitted. The trigger is what an automation listens for, so vagueness here breaks everything downstream. If you cannot name a single clear trigger, the process is really two workflows sharing one name – split them.

Step 3: Walk every step in order

List each action from trigger to finish, in sequence, one line per step. Include the small steps people forget – the copy-paste, the confirmation email, the “check with the manager.” The steps that feel too trivial to write down are usually the manual ones automation will remove. Aim for completeness over elegance; you can tidy later.

Step 4: Assign an owner to each step

Next to every step, write who is responsible. When a step has no clear owner, you have found a gap where work stalls. When a step has three owners, you have found duplicated effort. Both are worth fixing before automation, because an automated workflow needs one accountable owner per step to route correctly.

Step 5: Mark the approvals

Flag every point where the work waits for a sign-off. Approvals stuck in threads are the most common source of delay in HR workflows, so note who approves, what they are approving, and how the request reaches them today. These become routed, tracked approvals once you automate, which ends the status-chasing.

Step 6: Set a service level for each step

Write down how fast each step should happen – “provisioning complete within four hours,” “offer letter out same day.” Service levels turn a vague process into a measurable one, and they give your future automation a standard to hold. Without them, you cannot tell whether the workflow is actually working after you build it.

Step 7: Flag every manual and re-entry point

Go back through the map and highlight two things: every place a human types data that already exists in another system, and every place work waits on a person. Duplicate data entry is stealth friction – small keystrokes that add up to big costs – and these highlights are your automation shortlist. The more highlights, the bigger the time you will recover.

Step 8: Validate the map with the people who run it

Show the finished map to the person from step one and ask what you got wrong. You will always have missed a step or an exception. This review is what separates a map you can automate from a fiction that breaks the first time reality diverges from it. Fix the map until the person nods.

How to know it worked

Your map is done when someone who has never run the workflow can follow it end to end without asking a question, and when every step has an owner, every approval is marked, and every manual re-entry point is highlighted. A finished map reads like a recipe, not a description. If gaps remain, keep interviewing until they close – the map is the foundation everything else is built on.

How long should mapping take?

A single workflow maps in about an afternoon once you have the right person in the room. The first map takes longest because you are learning the method; by the third, you will map a process in under an hour. Do not stretch it into a multi-week documentation project – that is a different failure mode. The goal is a working map you can automate against, not a polished manual nobody reads. If a single workflow is taking more than a day to map, your boundaries are too wide. Narrow the scope, finish one clean map, and move to the next.

Common mistakes to avoid

• Mapping the ideal, not the real. If you document how the process should work, you will automate a fiction. Map what actually happens, exceptions and all.
• Skipping the person who does the work. The map built in a conference room without them will always be wrong in the details that matter.
• Trying to map everything at once. One workflow, fully mapped, beats ten half-mapped. Depth first.
• Leaving approvals and SLAs off. A map without them cannot become a routed, measurable automation.

With one clean map in hand, you are ready to build. Return to the pillar guide for the full path from a mapped process to a self-running workflow.