Small business process improvement checklist

If your team spends too much time chasing answers, correcting mistakes or entering the same information twice, start by looking at how one piece of work gets done.

This small business process improvement checklist helps you find the gaps. It is designed for everyday work such as handling enquiries, preparing quotes, booking jobs, fulfilling orders and sending invoices.

Choose one process you can actually follow

Pick something that happens regularly and causes a recognisable problem. “Sort out the business” is too broad. “Get an approved quote turned into a booked job” gives you a clear starting point and finish.

Ask someone who does the work to walk you through a recent real example. Note each step, the person handling it and where the information lives. Include the workarounds: the extra spreadsheet, the reminder on a phone and the question that always goes to the owner.

For each check below, write clear, needs attention or not sure. Add one example alongside your answer. This is a way to organise a discussion, not a score or certification.

The 12-point process improvement checklist

1. Does everyone know what starts the job? Identify the trigger: an accepted quote, a received order or a customer request. Check whether work sometimes starts before the required information arrives.
2. Is “finished” clear? Name the result and who accepts it. An invoice being prepared is different from it being checked and sent to the correct person.
3. Can the person doing the job find the information? List what they need and where it is kept. Look for details buried in individual inboxes or known only to one colleague.
4. Is the same information entered more than once? Follow a customer's details or job number through the process. Note each re-entry and whether it serves a useful purpose.
5. Is someone responsible at every handover? Check who owns the next step, how they know work is ready and what happens if they are away.
6. Where does the work wait? Record time spent waiting separately from time spent doing the job. A ten-minute task can sit untouched for two days because nobody knows it is theirs.
7. Which decisions need the owner? Separate unusual exceptions from routine questions. Write down the information or agreed limits that would let someone else handle a routine decision.
8. Can another trained person follow the steps? Ask them to use the current instructions. Note where they need help. Keep access secure; instructions should explain authorised access rather than contain passwords.
9. Where do mistakes come back for correction? Look at actual examples. Find the missing detail, unclear instruction or unchecked assumption behind the repeated error.
10. Is there one reliable place to check progress? A colleague should be able to tell what is waiting, what is underway and what is complete without asking several people.
11. What happens when the usual route fails? Think about missing information, a delayed supplier or an unavailable colleague. Agree who handles the exception and when it needs attention.
12. How will you tell whether a change helped? Choose one useful measure: time from enquiry to reply, jobs returned for correction or hours spent entering information. Record a starting point before changing the process.

Worked example: an accepted quote that never gets booked

Illustrative example: a customer accepts a quote by email. The owner forwards it to the office. The office needs a delivery address and preferred date, so the job waits while somebody chases both. The customer calls for an update, and the owner gets pulled back in.

The review finds three gaps: the quote acceptance does not collect everything needed, nobody clearly owns the handover, and there is no shared record of jobs waiting to be booked.

A first change could be to agree the information needed at acceptance, give one person responsibility for checking it and record the next action in the team's existing job list. Test it on the next few accepted quotes. Count how many still need chasing and how long booking takes. Those observations tell you whether the change is worth keeping.

Turn the review into one practical change

Choose an issue that happens often, has a clear consequence and is within your control. Discuss it with the people affected before changing their work. Avoid starting with a rare exception simply because it was the most recent frustration.

Write a short action note using these headings:

• The problem: what happens, how often and what it costs in time or rework.
• The change: the specific step, instruction or responsibility you will alter.
• The owner: who will make it happen and answer questions.
• The trial: which jobs it will cover and when you will review it.
• The evidence: what you will compare with the starting point.

After the trial, keep what helped, amend what did not and update the instructions. Then choose the next issue. If the process is still unclear, buying another tool is unlikely to settle who does what.

For a closer look at work that always returns to the owner, read why everything goes through one person. If missing figures are the main difficulty, start with getting a clearer financial picture.