Skip to content
Business Process Mapping

Business Process Mapping

See How the Work Actually Gets Done.

Most processes live in people's heads. I map them out: who does what, in which tool, and where it stalls. Then you can fix it, automate it, or hand it to someone new.

What process mapping is

A process map is a picture of how a piece of work moves through your business, from the first request to the finished result. It shows every step, every hand-off between people or teams, every approval, and every tool the work passes through.

The map isn't the goal. It shows you what to fix. Most operations problems come down to a step nobody owns, an approval nobody chases, or data typed twice into two systems. They're hard to see from inside the day-to-day. On a map, they're obvious.

Signs you need one

  • — A job gets done differently depending on who does it
  • — Work stalls waiting for an approval, and nobody notices until someone complains
  • — The same information gets entered into a form, a spreadsheet, and an email
  • — Onboarding a new hire means "shadow Dave for two weeks"
  • — You want to automate something but can't describe exactly what happens now
  • — You're moving to new software and need to know what the old setup actually did

What I can map

Purchasing and approvals

Part requests, quotes, sign-off, purchase orders, receiving, and inventory updates. Where the order number comes from, who approves what, and how accounts finds out.

Site safety and compliance

Pre-starts, sign-in and sign-out, roll calls, inductions, and inspections. How the forms connect, what data flows into your registers, and what happens when someone doesn't follow the expected path.

Equipment and maintenance

Asset changes, servicing, certificate expiries, and the admin steps that keep your registers accurate. Often the most manual part of the operation, and the easiest to improve.

Client intake, sales, and onboarding

From enquiry or application through qualification, payment, and access. Every email, page, and automation in the chain, and what happens to the people who don't qualify.

Internal operations

Task hand-offs, reporting, meetings, hiring, and onboarding. The recurring work that holds the business together and is rarely written down.

How it works

  1. 1. Talk to the people who do the work. Not just managers. The person filling in the form knows where it breaks.
  2. 2. Map the current process (AS-IS) as it really runs, including workarounds and the steps people skip.
  3. 3. Mark the problems: delays, duplicate entry, missing owners, manual steps that could be automated.
  4. 4. Design the improved process (TO-BE), side by side with the current one, so the changes are clear.
  5. 5. Turn it into something your team uses: a step-by-step SOP with an owner and a review date, kept where your team already works.

What you get

  • — A clear visual map of the current process (swimlane or flowchart, whichever reads better)
  • — A list of the problems found, ranked by impact
  • — A proposed future-state process, if the work calls for one
  • — Written step-by-step documentation your team can follow
  • — Recommendations on what to automate, what to change, and what to leave alone
  • — Requirements, constraints, and dependencies, written down before anything is built
  • — A build-ready technical specification, if the improved process involves software or automation
  • — Success measures for each change

Maps are delivered in an editable format, so you can update them as the process changes.

From map to build

A map tells you what to change. A developer or automation builder needs more than that. If the improved process involves new software, forms, or automation, I turn the design into a build-ready specification: every decision rule, every integration point, which data moves where, and what happens when something goes wrong. Nothing is left for the builder to guess.

I stay involved while it's built, answering questions and checking the result against the original design. Before it reaches your team, we test it together against real scenarios.

Whether I build it, your in-house developer does, or you hire an outside agency, the spec means everyone works from the same plan.

Where this fits

Process mapping isn't a separate package. It runs through most of my work:

  • — Consultation: describe the process that's causing trouble; leave with a recommendation on whether mapping it is the right next step.
  • — Audit: map one area of your operation in depth, with a findings report and a prioritized action plan.
  • — One-Time Project: map, document, and fix a defined set of processes, including the automation or system changes that follow.
  • — Subscription and Fractional: keep your processes mapped and documented as the business changes.

Who this is for

  • — Industrial operators (mining, drilling, construction) whose field and office processes run across forms, registers, and email
  • — Small businesses that have grown past "everyone just knows how it works"
  • — Teams about to automate, migrate software, or hire, who need the current process written down first
Case study: Turning a construction company's compliance requirements into a working system

Not sure where the work is getting stuck? Let's find out.

Book a free 15-minute call or send a message. Either way, you get a clear next step.

Book a call