Skip to content
DT Nova

Process mapping: how to document a business process before you automate it

Process mapping is the practice of drawing how work actually flows through your company: who does each step, in what order, with which information and systems, and where it waits, loops back or goes wrong. A good process map is the cheapest way to find waste and the essential first step before you buy software or automate anything, because a system built on a misunderstood process automates the misunderstanding. This guide explains the main types of process maps, the BPMN notation, a step-by-step method, an example and the tools.

The BPMN facts in this guide come from the Object Management Group's specification page, read on 12 November 2026. The method is the one we use in our own discovery work for automation and software projects.

Why map a process first

  • The process on paper is rarely the process in practice. Mapping with the people who do the work reveals the workarounds, the spreadsheets and the email loops that nobody wrote down.
  • Waste becomes visible. Waiting times, double entry, approvals nobody needs and handovers that lose information are obvious on a map and invisible in a meeting.
  • Software requirements become concrete. A map with decisions, data and exceptions is the backbone of a software requirements specification.
  • Automation gets the right target. You can see which steps are rule-based and frequent enough to automate, and which need judgement.

Types of process maps

TypeWhat it showsBest for
SIPOCSuppliers, inputs, process (5 to 7 high-level steps), outputs, customersAgreeing the scope and boundaries before detailed mapping
Basic flowchartSteps and decisions in orderSimple processes, quick understanding
Swimlane diagramSteps arranged in lanes per role, team or systemHandovers and responsibilities between teams
Value stream mapSteps with processing time, waiting time and inventoryFinding delays and waste in flows such as order to delivery
BPMN modelEvents, tasks, gateways, flows and messages in a standard notationPrecise documentation and processes to be automated

BPMN in five minutes

BPMN, Business Process Model and Notation, is maintained by the Object Management Group. Its specification page describes it as the de facto standard for business process diagrams, intended for the people who design, manage and realise processes, yet precise enough to be translated into software process components. The current version is 2.0.2, published in January 2014. The core symbols are few:

  • Events (circles): something that happens, such as "order received" (start) or "invoice paid" (end), or a timer or message along the way.
  • Tasks (rounded rectangles): a unit of work done by a person or a system.
  • Gateways (diamonds): a decision or a split, such as "amount over limit?" or "do these in parallel".
  • Sequence flows (arrows): the order of steps.
  • Pools and lanes: who does the work; message flows between pools show communication with customers or suppliers.

With these five elements most business processes can be drawn clearly. The rest of the notation matters mainly when a model is executed by a workflow engine.

How to map a process, step by step

  1. Choose one process and name its trigger and outcome. "From customer order received to invoice sent" is a process; "sales" is not.
  2. Set the purpose. Understanding, improvement, a new system or automation. The purpose sets the level of detail.
  3. Draw the SIPOC. Five to seven high-level steps, with inputs, outputs, suppliers and customers. Agree on it before going deeper.
  4. Map the as-is process with the people who do it. Walk through a real recent case, step by step. Ask: what do you receive, from where, what do you do, which system, what do you pass on, to whom? Note every workaround.
  5. Add decisions, data and exceptions. For each decision, the rule. For each step, the data used and produced. For each exception, how often and what happens.
  6. Measure. Volume per month, processing time per step, waiting time between steps, error and rework rates. Estimates are a start; samples from the systems are better.
  7. Find the problems. Mark waiting, double entry, manual copying between systems, unnecessary approvals, and steps where errors start.
  8. Design the to-be process. Remove steps first, simplify second, automate third. Map the result.
  9. Validate and publish. Walk the new map through with the team and owners, then keep it where people can find it, with an owner and a review date.

An example: supplier invoice approval

A typical as-is map of supplier invoice handling in a midsize company looks like this: invoices arrive by email and post; an administrator scans the paper ones, types the header data into accounting, forwards a PDF by email to the budget owner, chases them after a week, gets approval by reply email, then posts the invoice and schedules payment. The map shows four handovers, two rounds of manual data entry and approval waiting as the longest step by far.

The to-be process: e-invoices and scanned invoices are captured automatically, matched to purchase orders, sent to the right approver by rules on cost centre and amount, with reminders and a deputy when the approver is away, and posted on approval. Exceptions, such as a price that does not match the order, go to a person with the reason shown. This is the shape of most document workflow automation projects, and the European move to e-invoicing makes it more urgent; see our e-invoicing guide.

Common mistakes

  • Mapping how the process should work instead of how it does.
  • Mapping without the people who do the work.
  • Too much detail too early, so the map is never finished.
  • No data and no exceptions, so the map cannot be turned into a system.
  • Automating before simplifying.
  • No owner, so the map is out of date within months.

From process map to software

A process map with decisions, data and exceptions translates almost directly into software. Lanes become roles and permissions. Tasks become screens or automated steps. Gateways become rules, which should be configurable when they change often. Data on the map becomes the data model. Exceptions become the cases the system must route to a person. Measurements become the baseline for proving the result. Whether the target is business process automation, a robotic process automation bot as described in our RPA use cases guide, or a custom system, the map is where the requirements come from.

Tools for process mapping

For the first workshop, sticky notes on a wall or a shared online whiteboard are best: everyone can move things, and nobody is waiting for the person with the mouse. For documentation, general diagram tools and dedicated BPMN modellers are both common; choose one that exports BPMN 2.0 files if automation is a possibility, so the model can move into a workflow engine without being redrawn. Store the maps with an owner and a version date.

How we help

Every automation or software project we run starts with mapping the process with the people who do the work, measuring the baseline and agreeing the to-be process before we build. We deliver the maps as part of the documentation, then build the automation or system on them, hosted in the EU, with the code in your company's account. See business process automation and internal tools development.

Questions people ask

What is process mapping?

Process mapping is the drawing and description of how a piece of work actually flows through a company: who does what, in which order, with which information and systems, and where decisions, waiting and errors happen. The result, a process map, is used to understand, improve, standardise or automate the process.

What is the difference between a process map and a flowchart?

A flowchart is one kind of process map: a simple diagram of steps and decisions. Process mapping also includes swimlane diagrams that show who does each step, value stream maps that add time and waiting, SIPOC overviews and BPMN models precise enough to run in a workflow engine. The right type depends on what the map is for.

What is BPMN?

BPMN, Business Process Model and Notation, is a standard notation for business process diagrams maintained by the Object Management Group. Its current version, 2.0.2, was published in January 2014. It uses a small set of shapes for events, tasks, gateways and flows, and is precise enough that many workflow tools can execute BPMN models directly.

Which tools are used for process mapping?

For a first map, sticky notes on a wall or a shared whiteboard tool work best, because the people who do the work can change them. For lasting documentation, general diagram tools or BPMN modelling tools are common. If the process will be automated, a BPMN tool that exports to a workflow engine saves rework.

How detailed should a process map be?

Detailed enough for its purpose and no more. A map to agree on responsibilities needs steps and roles. A map for automation needs every decision rule, every data field and every exception. Start at a high level, then go into detail only for the parts you plan to change.

Sources