A practical field guide from Automation Ace.
The short answer
A current state vs future state map shows the same process twice, side by side: how it runs today and how it will run after automation. For each step, note the time it takes, the handoffs and waits, and, crucially, the new failure points automation introduces. The comparison makes the value obvious (minutes saved, handoffs removed) and the risks visible, which is why it doubles as a sales and approval tool.
Start from the current map you built in a discovery workshop. Part of the automation planning playbook.
What to capture for each step
- Who or what does it (person, team, or system).
- Time per step and wait time before the next step.
- Handoffs: each crossing between people or systems.
- Error rate or rework today.
- In the future state: what changes, time saved, handoffs removed, and new failure points with their mitigation.
Example: inbound lead handling
| Step | Current state | Future state | Change | New failure point and mitigation |
|---|---|---|---|---|
| 1. Lead arrives | Rep checks inbox (avg 4h delay) | Instant webhook creates CRM contact | −4h wait | Webhook failure: alert + retry |
| 2. Qualify lead | Rep reads form, decides tier (5 min) | Rules + AI score; borderline to review | −4 min | AI misclassification: review lane |
| 3. Assign owner | Manager assigns in weekly sheet | Round-robin by territory table | Handoff removed | Inactive rep: fallback owner |
| 4. Send intro email | Rep writes email (10 min) | Template email sent on assignment | −10 min | Bounce: flag record |
| 5. Log activity | Rep updates CRM manually (3 min) | Logged automatically | −3 min | Duplicate log: idempotency key |
Total: roughly 17 minutes of hands-on time and about 4 hours of waiting removed per lead, plus one handoff eliminated. At 200 leads a month that is about 57 hours of work. Check your own numbers with the workflow time savings calculator and time saved by automation calculator. The full build pattern is in lead routing automation.
Do not hide the new failure points
Automation removes manual errors but adds new ones: webhook outages, expired credentials, API limits, misrouted records, and AI mistakes. Listing them, with an owner and mitigation for each, builds trust with approvers and feeds the monitoring plan. See Zapier points of failure and why automations break.
How to build the map
- Copy the current swimlane map and lay the future version beside or below it.
- Collapse automated steps into system lanes and remove handoffs that disappear.
- Keep human steps that remain, such as approvals and exception reviews; do not oversell full automation.
- Annotate time saved, waits removed, and new failure points.
- Summarize in a short table: hours saved per month, handoffs removed, error reduction expected, and remaining manual work.
Using the map to win approval
- Executives see hours and dollars: pair it with the automation ROI calculator.
- Process owners see their team's workday get simpler.
- IT and security see which systems and data are touched; attach the systems and data inventory.
- Builders get a clear target, formalized in the requirements doc.
After launch: prove it
Measure the future state against the baseline you captured before building; see defining success metrics. Update the map when the process changes so it stays the living reference for how work flows.
Frequently asked questions
What is a current state vs future state process map?
Two versions of the same process side by side: how it works today and how it will work after automation, with time per step, waits, handoffs, and new failure points noted for each.
How do I show time saved by automation?
Record time per step and wait time in the current state, show which steps are removed or shortened in the future state, then multiply time saved per item by monthly volume.
Why include new failure points in a future state map?
Automation introduces new risks like API outages, expired credentials, and misrouted records. Listing them with owners and mitigations builds trust and shapes the monitoring plan.
How can a future state map help get automation approved?
It makes the value concrete for executives, the workday changes clear for process owners, the systems and data touched visible for IT, and the target precise for builders.
Disclaimer: Templates and checklists are starting points; adapt them to your process, policies, and tools. Product features, limits, and pricing mentioned here change over time, so confirm current details in each vendor's documentation. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.