Free tool

Review one process yourself, in eight steps

Most processes were never designed. They grew. Pick one, follow a real piece of work through it and write down what actually happens. Tick off the steps, fill in the worksheet as you go, then print it or copy it into a spreadsheet. Nothing you type leaves your browser.

A guide, not professional advice. Related reading: What a business process review actually finds.

In short. A business process review follows one real piece of work from start to finish and records every step, hand-off, wait and correction. Choose one process, agree what good looks like, trace a recent example, note who does what in which system, find the duplication and the bottleneck, compare simple fixes before software, and agree one first improvement with an owner and a date.

The eight steps

  1. Choose one process. Not the whole business: enquiries, quotes, invoices or onboarding a new starter.
  2. Agree what good looks like. How quickly should it happen, and what does a good outcome look like? Without this, improvement is a matter of opinion.
  3. Follow a real piece of work. Take a recent example and trace it through every stage, not what the procedure document says should happen.
  4. Record every hand-off. Who receives the work, who passes it on, where it waits and what information travels with it.
  5. Find the duplication and rework. Information typed twice, approvals repeated, corrections, and tasks that exist only because two systems do not talk.
  6. Find the bottleneck. The step where work queues. Speeding up every other step will not speed up the whole.
  7. Compare the fixes. Remove the step, change who owns it, write a clear procedure, use existing software better, connect systems, or build something new. Technology is not automatically the answer.
  8. Agree the first improvement. What changes, who owns it, by when, and how you will know it worked. A review without a decision is only a description.

You do not need special software, just one real process, the people who do it and a willingness to find out what actually happens. If you already know exactly what is wrong and how to fix it, skip the review and fix it.

A worked example

An illustrative quote process at a small service business: an enquiry arrives by email (1), is copied into a spreadsheet (2), waits two days for the owner to price it (3), is typed again into a quote template (4), and is emailed back (5). The worksheet shows the two-day wait at step 3 is the bottleneck and step 4 repeats step 2. The first fix agreed: a pricing guide so someone else can price standard jobs, owned by the office manager, live in two weeks.

Questions people ask

What is a business process review?

It is a structured look at how one piece of work really moves through a business, from start to finish, to find the delays, duplication and dependencies, and to decide what to change first.

How long does a process review take?

Reviewing one simple process yourself can take an afternoon with the people involved. A wider review across several connected processes takes longer, because the hand-offs between them matter most.

Do I need software to map a process?

No. Paper, a whiteboard or this worksheet is enough to understand most processes. Software can come later, if it turns out to be the right fix.

When do you not need a process review?

When you already know what is wrong, agree on the fix and have the time to make it. A review earns its place when the symptoms are obvious but the cause is not, or when the wrong fix would be expensive.

Where a good idea becomes a real business. The same enterprise-grade practice, now open to idea-stage founders and owner-led businesses.

From what-if to what’s next. · © 2026 Mowbray Ltd · Registered in England and Wales