The short answer

A process audit checklist helps you find which jobs in your business are worth automating first. List every repeating process, count how often it happens and how long it takes for two weeks, then score each one on time, errors, risk and how rule-based it is. The top five scores become your plan. Fix broken processes before automating them, and give every automation a named owner.

Your process audit checklist at a glance

  1. List every process that repeats at least monthly, with an owner against each.
  2. Count how often each one happens and how long it takes, for two normal weeks.
  3. Score each one for time, errors, risk, rules and whether the data is already digital.
  4. Sort the high scores into automate, fix first or leave alone.
  5. Pick the top five to automate, each with an owner, a measure and a one-page note.

Why most owners automate the wrong thing first

Most automation projects in small businesses start with whatever annoyed the owner most last week, or whatever a software salesperson demoed best. Sometimes that is the right job. Often it is not, and the business ends up with a clever tool that saves twenty minutes a month while the real time sink keeps chewing through someone's Tuesday.

A process audit fixes that by putting numbers on the table before anyone buys anything. It is not a quality audit in the manufacturing sense, and it is not about checking compliance. It is a simple way to see where the hours go, where the mistakes happen and where the risk sits, so you spend effort where it pays back.

business.gov.au makes the same point in plainer terms: review workflows that have grown over time, find bottlenecks, and look closely at where errors creep in, especially when staff re-enter the same information into more than one system. That last one is where most of our early wins come from.

Step 1: List every process that repeats

Get the people who do the work in a room for an hour, or walk around and ask. You are after a plain list of everything that happens more than once a month. Most businesses with 10 to 50 staff land on 25 to 50 processes.

Follow three threads so nothing hides:

  1. The money. Quoting, taking orders, purchasing, receiving stock, invoicing, chasing payment, paying suppliers, reconciling, payroll.
  2. The customer. Enquiries, bookings, delivery updates, complaints, returns, reviews, follow-up.
  3. The team. Onboarding, rostering, timesheets, leave, training records, offboarding, IT access.

Write each one as a verb and a noun: "enter supplier invoices", "send delivery confirmations". If a process has no obvious owner, write that down too. A process nobody owns is already a finding.

Step 2: Time and count the work for two weeks

Guesses are always wrong, usually by a lot. For two normal weeks, ask whoever does each process to keep a tally: how many times it happened and roughly how long each one took. A shared spreadsheet with one row per process works fine. So does a sheet of paper stuck next to the order desk.

Capture four things per process:

  • Count: how many times in the fortnight.
  • Minutes each: a typical time, not the worst case.
  • People involved: how many hands it passes through.
  • Problems: how many times it went wrong, got redone or someone had to chase it.

Multiply count by minutes and you have the real weekly cost in time. This is the step owners want to skip and the step that changes their mind most often.

If you are on Microsoft 365, Power Automate has a task mining feature that records the steps people take on their computer and suggests what could be automated. Microsoft describes it as a way to see how work is actually done and where mistakes happen. It needs Power Automate for desktop and a Power Automate Premium licence, which standard Microsoft 365 plans do not include, so for most small businesses the tally sheet is the better start.

Step 3: Score each process

Now turn the tallies into a ranking. Score each process from 1 (low) to 5 (high) on the five questions below and add them up.

Score this1 means5 means
TimeA few minutes a weekMany hours a week across the team
Errors and reworkRarely goes wrongRedone or chased every week
Risk if it goes wrongMild annoyanceMoney lost, a customer lost or a compliance problem
Rules, not judgementNeeds a person's call every timeSame steps, same rules, every time
Data already digitalPaper, phone calls, memoryAlready in email, a spreadsheet or a system

The last two columns matter as much as the first three. A process that takes hours but needs judgement on every case is a poor first automation. A process that is still on paper usually needs a small digital step before automation can help.

Owner takeaway: high time plus high rules plus digital data is the sweet spot. That is where automation pays back quickly and safely.

Step 4: Sort the list into automate, fix first or leave alone

Before you pick, sort every process with a high score into one of three piles. This is the part most process audit checklists leave out, and it is where we spend the most time with owners.

PileWhat it looks likeWhat to do
AutomateClear steps, stable, data in systems, happens oftenShortlist it
Fix firstEveryone does it differently, steps nobody can explain, constant exceptionsSimplify and document it, then score it again
Leave aloneRelationship work, judgement calls, rare eventsKeep it human; maybe give staff a better template

Automating a messy process just makes the mess run faster. Business Queensland lists reviewing procedures for faults and redundancies as part of improving them, and suggests keeping one current, version-controlled copy of each. Do that for anything in the "fix first" pile before you spend a cent on tools.

Step 5: Pick the first five and turn them into a plan

Take the five highest scores from the "automate" pile. For each, write one short paragraph:

  1. What changes: "Orders arriving by email are read and drafted into the accounts system for a person to check."
  2. Who owns it: one named person who checks it runs and fixes it when it does not.
  3. How you will know it is working: the count and minutes from Step 2, measured again a month after launch.
  4. What stays human: the approval, the exception or the customer conversation.
  5. Where it is written down: a one-page note that survives the person who built it leaving.

Do them one at a time. Launch, check for a month, then move to the next. Five automations that run reliably beat fifteen that nobody trusts.

A worked example: a Gold Coast building supplies wholesaler

This is an illustrative business, not a client. Picture a building supplies wholesaler in Yatala with 22 staff, a trade counter, a warehouse and a small office team of four.

The owner was sure the problem was the website. The two-week tally said otherwise. The office was keying trade orders from emails and PDFs into the accounts system by hand, about 60 a week at around six minutes each, with a handful re-keyed after wrong quantities or codes. Delivery confirmations were typed one by one. Supplier invoices were matched to purchase orders by eye.

Scored up, trade order entry came out on top: high time, regular errors, rule-based and already digital. Delivery confirmations and supplier invoice matching came next. Credit account applications scored high on time but landed in "fix first", because each branch used a different form. Complaints and pricing exceptions scored high on risk but were judgement calls, so they stayed with people.

The first five became: order entry with a person checking each draft, automatic delivery confirmations, invoice matching with exceptions flagged, a weekly overdue account summary, and stock reorder alerts. The website could wait.

What to watch out for

  • Payments and bank details. The Australian Cyber Security Centre warns that fraudsters send fake invoices and changed bank details by email, and recommends a formal process for payment requests and phoning a trusted number to confirm any change. Never let an automation update supplier bank details or release payments on its own.
  • Personal information. An audit often shows customer and staff details flowing through inboxes, spreadsheets and new tools. Many small businesses sit under the Privacy Act's turnover threshold, but some are covered regardless, such as health service providers. Check the OAIC guidance and know where the data goes before connecting a new tool.
  • Records you must keep. The ATO says most business records must be kept for five years, and Fair Work requires employee records to be kept for seven. Make sure an automation does not delete, overwrite or scatter records you are required to keep.
  • Get advice on obligations. This is general information. Confirm your privacy and record-keeping obligations with your accountant or adviser.
  • Who maintains it. Every automation breaks eventually, usually quietly, when a supplier changes an invoice layout or a password expires. The named owner and the one-page note from Step 5 are what stop a small failure becoming a month of missing orders.

When to get help

If you have a few hours to run the tallies and an honest team, you can do this audit yourself with the checklist above, and you will learn a lot about your business along the way. Outside help earns its keep when nobody has the time to run it properly, when staff will be more candid with an outside process auditor than with the boss, or when the top processes cross several systems and need careful design. That is the work our process audit does, and we will tell you plainly which items do not need automating at all. If you want the bigger picture of where technology fits your plans, see our fractional CIO service. For a trade business, our automation guide for tradies walks through the same thinking job by job.

Common questions

How long does a process audit take for a small business?

For a business with 5 to 30 staff, the listing step takes an afternoon and the counting step takes two normal working weeks, because you want real numbers rather than guesses. Scoring and choosing the first five takes another few hours. Most of the elapsed time is waiting for the tallies to fill up, not meetings or workshops.

Do I need process mapping software to do a process audit?

No. A spreadsheet and a whiteboard are enough for most small businesses. Tools like Power Automate task mining can record how people work on their computers, but they need a Power Automate Premium licence and set-up, and suit larger teams. Start with a simple tally sheet. If the audit shows a few processes worth studying in depth, look at mapping tools then.

What is the difference between a process audit and process mapping?

A process audit looks across the whole business to find which processes cost the most time, cause the most errors or carry the most risk. Process mapping takes one process and draws it step by step, showing who does what, in which system and where it gets handed over. You audit first to choose, then map the few processes you have chosen. When it comes to process mapping for small business, a one-page list of steps is usually enough.

Which processes should a small business automate first?

Start with work that happens often, follows clear rules, already lives in digital systems and causes errors or delays when it goes wrong. Retyping orders, chasing overdue invoices, sending standard updates and moving data between two systems are common first picks. Leave anything that needs judgement, a relationship or a messy process that has not been fixed yet.

What should never be fully automated?

Anything where a mistake is expensive and hard to undo. Changes to a supplier's bank details, large payments, decisions about staff, and replies to an upset customer should always keep a person in the loop. Automation can prepare the work, gather the details and flag it, but a named person should approve it before it goes out.

Can we do a process audit ourselves or do we need a consultant?

You can do it yourselves with the checklist in this guide, and you know your business better than anyone. Outside help is worth it when nobody has time to run the counting, when staff are unlikely to be candid with the owner, or when the top processes run across several systems and need someone to design the automation safely.

Sources

Want a hand with this?

Start with the quick-wins assessment to see where automation would save your team the most time, or book a discovery call and talk it through.

Start with our automation assessmentBook a discovery call

Running a business that needs someone accountable for technology decisions, not just automations? See the fractional CIO seat.

Keep reading