On August 27, 2026, n8n published guidance on tracking workflow changes and restoring a stable state in Workflow Versioning for Reliable Automation and Maintenance. Version control makes production operations safer, but it cannot repair a poorly designed process: before building the workflow, the company must understand the actual work, its exceptions and its decision rules.
Starting point
Consider a typical scenario, purely for illustration: a customer request arrives by email, an employee updates a spreadsheet, a manager approves it, and the same information is then entered into both the CRM and ERP. Management wants to automate the flow, but each department describes it differently.
The expected result is not simply a diagram. It is a decision pack showing what should be removed, standardized, automated or kept under human control, supported by a time and cost baseline.
| Item to quantify | Current baseline | Target to define |
|---|---|---|
| End-to-end lead time | Closing timestamp minus receipt timestamp | Acceptable customer lead time |
| Human handling time | Sum of manual handling time | Remaining time after simplification |
| Fully loaded cost per case | Human time multiplied by loaded hourly cost, plus software costs | Target cost after investment |
| Exception cost | Rework, errors, credits or penalties | Accepted residual risk |
France Num recommends calculating current effort from process frequency, unit duration and the people involved, then comparing the potential gain with implementation complexity and the impact of errors in Automation: a solution for saving time and managing an SME. This prevents management from selecting the most visible irritation rather than the most relevant investment.
If you first need to identify a candidate, use our list of administrative processes to automate first. Our guide to process optimization in SMEs provides the broader improvement framework.
Prerequisites
Gather the following before inviting employees to a workshop:
- A sponsor and a process owner: the sponsor arbitrates budget and priorities; the owner validates business rules and remains accountable after deployment.
- A provisional scope: define the trigger, final outcome, customers and exclusions. “From receipt of a complete request to closure in the ERP” is more actionable than “improve customer service.”
- Real evidence: completed cases, emails, forms, CRM or ERP exports, execution logs and tracking files. Do not rely solely on the official procedure.
- Read-only technical access: an IT representative must be able to explain interfaces, APIs, permissions, identifiers and data locations without granting premature write access.
- Internal financial inputs: loaded hourly costs, existing licences, external services, maintenance charges and the average cost of an error.
- A shared modelling environment: Business Process Model and Notation provides a graphical notation intended to bridge business process design and software implementation. BPMN Studio, our BPMN modelling application, can centralize the maps and their validation.
For process mining, the data team must be able to retrieve a case identifier, activity name and timestamp from system logs. Microsoft lists these required fields in Prepare processes and data.
The step-by-step workflow
1. Define the boundaries and expected outcome
Who does what: the sponsor appoints the process owner. The owner defines the trigger, outcome and exclusions, while the process analyst converts the scope into a testable statement.
Realistic duration: allocate 60 minutes. This is enough to frame the main path, roles and open questions without attempting to solve every exception, as described in Run a 60-Minute Process Discovery Workshop.
Deliverable: a scope sheet naming the boundaries, owner, customers, systems and indicators.
2. Reconstruct the work as it is actually performed
Who does what: employees who execute the process walk through completed cases. The analyst records every action, waiting period, re-entry, file and rework loop. IT identifies the source and owner of each data item.
Realistic duration: schedule a 90-minute session for each clearly bounded process. This format can cover framing, the normal path, branches, hand-offs and open questions, according to Process Mapping Workshops: From Walkthrough to BPMN.
Deliverable: an evidence-based inventory of tasks, roles, applications, inputs, outputs, controls and exceptions.
3. Model the current process in BPMN
Who does what: the analyst builds the as-is model. Each lane represents a role or system, each task uses an action verb, and every decision has an explicit condition. Participants describe the current work without designing the future solution.
Realistic duration: allow a 90-minute workshop for the normal path and common exceptions. A structured session of this length is also used by the Business Process Mapping Workshop.
Deliverable: a current-state BPMN map and a register of ambiguities and unresolved business rules.
4. Validate the map against evidence
Who does what: each practitioner reviews their lane and tests the model against a completed case. The process owner resolves disagreements. IT compares the map with application statuses and available logs.
Realistic duration: run a focused 20-minute review for each role instead of holding another large meeting. This short review format is described in Real-World Process Map Examples.
Deliverable: a validated and dated model with a named owner, approval status and assigned open questions.
5. Design the target process before selecting the tool
Who does what: the owner decides which activities disappear, which data becomes mandatory and which controls remain human. The architect then classifies each step as a deterministic rule, human approval, API integration, user-interface RPA or AI-assisted treatment.
Realistic duration: allocate 60 minutes to the initial target model and place unresolved decisions in a separate register, following the time-boxing approach in Run a 60-Minute Process Discovery Workshop.
Deliverable: a to-be map and a matrix listing each task’s owner, input, control, target treatment and failure behaviour.
6. Build the decision pack
Who does what: finance validates internal costs; IT estimates licences, integrations, hosting and maintenance; the process owner derives volumes from available data; the sponsor decides whether to launch, postpone or stop.
Realistic duration: use a 90-minute decision meeting when the model, assumptions and open questions have been circulated beforehand, following the operational agenda in Process Mapping Workshops: From Walkthrough to BPMN.
Deliverable: a business case containing initial cost, recurring cost, monthly net benefit, payback period, risks and acceptance criteria. For a detailed costing method, see our article on the cost of Power Automate automation in 2026.
How to measure whether it works
Use identical definitions before and after deployment. Application logs are more reliable than subjective estimates: Microsoft explains that process mining uses system events to visualize actual steps, variants, errors and bottlenecks in its Overview of process mining and task mining.
- Median processing lead time = median time between the trigger and closing timestamps.
- Human handling time per case = total manual handling time divided by completed cases.
- Rework rate = cases containing a repeated activity or backward loop divided by all completed cases.
- Net financial benefit = avoided costs and valued employee time minus licences, hosting, support and maintenance.
The reporting dashboard should filter results by request type, channel, entity and process variant. An overall average may conceal an infrequent but expensive path.
Mistakes that cause the project to fail
- Mapping the official procedure instead of reality. Ask practitioners to show a completed case and its traces, rather than merely explaining how the process is supposed to work.
- Designing the target process during observation. Record improvement suggestions separately; otherwise, the diagram will mix facts, wishes and technical assumptions.
- Starting with Power Automate, n8n or Make. The choice depends on applications, APIs, hosting, permissions and monitoring. Use our Power Automate, n8n and Make comparison only after validating the target process.
- Automating data re-entry without removing its cause. If two systems hold the same data under different rules, address data governance before building a robot to copy it.
- Ignoring exceptions. Define who takes control, what information they receive, how processing restarts and how the incident is logged.
- Leaving the diagram without an owner. Any change to a rule, form or interface must trigger updates to the map, tests and operating documentation.
- Treating production deployment as success. Keep the project open until actual indicators have been compared with the baseline and maintenance has a named owner.
Getting support
D1 Consulting delivers business process audits and mapping, including scope definition, practitioner interviews, current and target BPMN models, exception analysis, costing, prioritization and acceptance criteria.
Once the target process is approved, our Automation & Optimization service covers workflow implementation, integrations, monitoring and operating documentation. Depending on your environment, we can deploy Power Automate within Microsoft 365 or build n8n and Make workflows, including controlled AI-assisted processing.
👉 Book your free 30-minute diagnostic to identify a priority process, define its mapping scope and receive the list of data you need to collect.
