Process Mapping: Find Admin Bottlenecks

Admin work often feels slow without anyone being able to say exactly why. Invoices take a week to approve, new starters wait days for equipment, and customer requests bounce between teams. Process mapping makes these delays visible. By drawing each step, who does it and how long it waits, you can see where work piles up, which steps add little value and where automation or a simple rule change would help. This guide explains how to map an admin process, measure waiting time, find bottlenecks and turn what you find into practical improvements.

What process mapping is

Process mapping is the practice of drawing a process as a sequence of steps, decisions and hand-offs. A map shows:

• Where the process starts and ends
• Each step and who performs it
• Decision points, such as approve or reject
• Hand-offs between people, teams or systems
• Waiting time between steps
• Inputs and outputs, such as documents or data

The result is a shared picture that everyone involved can discuss, instead of each person describing their own part.

Why admin processes need mapping

Admin processes grow over time. New checks are added after mistakes, teams change, and systems are replaced, but the process is rarely redesigned as a whole. Common results include:

• Duplicate data entry across systems
• Approvals that require more people than necessary
• Work waiting in inboxes for days
• Steps nobody remembers the reason for
• Exceptions handled differently by each person

Mapping reveals these problems so they can be fixed deliberately rather than worked around.

Choose the right process to map

Start with a process that is:

• Frequent enough to matter
• Causing visible pain, such as complaints or delays
• Crossing more than one team or system
• Small enough to map in a workshop of a few hours

Good starting points include supplier invoice approval, employee onboarding, purchase requests, customer refunds and contract approvals.

Gather the right people

Map the process with the people who actually do the work, not only managers. Include someone from each team involved and, if possible, someone who receives the output. Their knowledge of workarounds and waiting points is what makes the map accurate.

Map the current process first

Resist the urge to design the ideal process straight away. Map how work actually happens today:

1. Agree the start trigger and the end point
2. List each step in order, using sticky notes or a simple diagramming tool
3. Mark who performs each step, often using horizontal lanes for each role
4. Add decision points and the paths that follow
5. Note systems used and documents passed along
6. Mark where work waits and roughly how long

Follow a few real examples through the process to check the map matches reality.

Measure working time and waiting time

For each step, estimate two numbers:

• Working time: how long someone actively spends on the step
• Waiting time: how long the item sits before the step starts

In many admin processes, waiting time far exceeds working time. A step that takes ten minutes may wait three days in an approver's inbox. Real data from email timestamps, ticket systems or workflow logs gives more reliable figures than estimates.

Worked example: process mapping an invoice approval

The table below shows a hypothetical current-state map for supplier invoice approval at a mid-sized company. Times are illustrative.

StepWhoWorking timeWaiting before stepProblem foundInvoice received by emailAccounts inboxNoneNoneArrives in shared inbox with other mailInvoice opened and logged in spreadsheetAccounts assistant5 min1 dayManual logging duplicates later entryMatched to purchase orderAccounts assistant10 min0.5 dayPurchase orders kept in a separate systemSent to budget holder for approvalAccounts assistant2 minNoneSent by email with no reminderApproved by budget holderBudget holder3 min4 daysMain bottleneck: no reminders or deputiesSecond approval above thresholdFinance manager3 min2 daysThreshold set low years agoEntered in accounting systemAccounts assistant8 min1 dayData re-keyed from spreadsheet

Total working time is about half an hour, while waiting adds up to more than a week. The map points to approval reminders, deputies, a reviewed threshold and removing the duplicate spreadsheet as the main fixes.

Find bottlenecks and waste

Look for:

• Steps with long waiting times, especially before approvals
• Repeated data entry of the same information
• Hand-offs that bounce back and forth
• Checks that rarely find problems
• Steps nobody can explain the purpose of
• Exceptions that are common enough to deserve their own path

Mark each problem on the map and discuss causes with the team.

Design the improved process

Once problems are clear, design a future-state map:

• Remove steps that add no value
• Combine or reorder steps to reduce hand-offs
• Set rules for routing and thresholds
• Add reminders, escalations and deputies for approvals
• Automate data transfer between systems where possible

Our guide to business process automation explains how to decide which improved steps to automate and which to simplify first.

Document and test the new process

Turn the future-state map into written procedures for each role, then pilot the change with a small group before rolling it out. Our guide to standard operating procedures explains how to write procedures that people actually follow.

Measure the results

Compare the improved process with the baseline from your current-state map:

• Total time from start to finish
• Waiting time at former bottlenecks
• Errors or rework
• Staff time spent per item

Revisit the map every year or after significant changes to systems or teams.

Common process mapping mistakes

• Mapping the official process instead of what actually happens
• Leaving out the people who do the work
• Adding too much detail too early, so the map becomes unreadable
• Jumping to automation before removing unnecessary steps
• Producing a map and never acting on it

Keep maps simple enough to use

A process map is a communication tool, not a technical specification. Use a small set of symbols, such as boxes for steps, diamonds for decisions and arrows for flow, and keep labels short. If a map grows too large, split it into a high-level overview and separate detailed maps for complex sections. Share the final version where the whole team can see it, and record the date it was last checked, so people know whether it still reflects reality.

Frequently Asked Questions

What is process mapping?

It is drawing a process as a sequence of steps, decisions and hand-offs, showing who does each step, what systems are used and where work waits.

How do you find bottlenecks in a process?

Measure waiting time before each step. Steps where work sits longest, often approvals or hand-offs between teams, are usually the bottlenecks.

Should you map the current or ideal process first?

Map the current process first, based on how work really happens, then design the improved version once problems are clear.

What tools do you need for process mapping?

Sticky notes and a wall work well for workshops. Simple diagramming tools help for sharing and updating maps afterwards.

See where your admin work really waits

We map admin processes with your team, remove unnecessary steps and automate the hand-offs that slow work down. See our AI automation solutions, or talk to us about mapping your processes.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.