Automation copies a process. If the process is slow, undefined, or lives in one person's head, automating it means you now run the same problem faster and at scale. That is why every implementation I take on starts with a business process audit, not a tool.
A business process audit is a structured review of how work actually flows through your company: where leads land, how clients get onboarded, who owns what, and where data goes to die. This checklist is the version I use: 47 questions across 7 areas, and every red flag is a place automation would amplify a problem instead of solving it. One benchmark that stuck with me: successful AI outcomes break down to roughly 10% algorithms, 20% tools and data, and 70% people and process. This checklist is that 70%.
How to Use These 47 Business Process Audit Questions
Copy the 47 questions into a document — or grab the business process audit template below — and answer each one straight: green, yellow, or red. You do not need to fix anything yet. Treat it as an operational audit checklist: a first pass is just a map of which of the 7 areas holds the most red, because that is where your next hire, tool, or automation should go, or where it definitely should not.
If you only have time for one area, start where the symptom below matches what you already feel.
| The symptom you recognize | Where to look first |
|---|---|
| Leads reply slowly or go cold | Area 1 — Leads and sales |
| Every client project feels custom | Area 2 — Onboarding and delivery |
| You are the bottleneck on most decisions | Area 3 — Delegation and ownership |
| Reports take days and start arguments | Area 4 — Data and reporting |
| You pay for tools no one fully uses | Area 5 — Tools and systems |
| You do not know your margin per client | Area 6 — Finance and cash |
| Meetings end without decisions | Area 7 — Communication and meetings |
Area 1 — Leads and sales (Questions 1-8)
- Do you know your average first-response time to a new lead, in minutes?
- Is there one place where every inbound lead lands, or several?
- Does every lead get a first reply without someone remembering to send it?
- Can you say which lead source produces paying clients, not just leads?
- Is your follow-up sequence written down, or does it live in someone's head?
- Do leads get lost between "interested" and "booked a call"?
- Is there a defined point at which a lead becomes a qualified opportunity?
- Does one named person own the pipeline number, or is it "everyone's job"?
What a "no" signals: revenue depends on memory and mood, not a system. This is the area where a fast lead-response automation pays back quickest, but only after the follow-up steps are actually defined.
Get a free 25-min ops audit. Working through this and finding more red than you expected? Bring your worst area and we will name the first thing to fix. No pitch.
Book a slotArea 2 — Client onboarding and delivery (Questions 9-15)
- Is there a repeatable onboarding sequence, or does each client start differently?
- Does a new client know what happens next without having to ask?
- Are handoffs between sales and delivery written down?
- Can you deliver the core service if the key person is away for a week?
- Do you track where projects stall most often?
- Is "done" defined the same way by you and by the client?
- Do you capture why clients leave, somewhere you can actually review it?
What a "no" signals: delivery quality rides on individuals, not on a process. Growth here multiplies rework, not revenue.
Area 3 — Delegation and ownership (Questions 16-22)
- Does every recurring task have a single named owner?
- Are there tasks only you can do that someone else should be doing?
- When you delegate, do you hand over the outcome or only the steps?
- Is there a written way to escalate a blocked task?
- Do people know which decisions they can make without you?
- How many open loops are waiting on your reply right now?
- Is there a task that breaks the week every time its owner is out?
What a "no" signals: you are the bottleneck. No tool fixes this until ownership is explicit; automation just routes more work back to you.
Area 4 — Data and reporting (Questions 23-29)
- Do you have numbers you trust, or numbers you argue about?
- Is the same metric defined the same way across the team?
- How long does it take to pull last month's key numbers?
- Are reports built by hand every time?
- Do decisions wait on data that arrives too late to matter?
- Is customer data in one system, or scattered across tools?
- If you switched on an AI tool today, would it find clean, consistent data?
What a "no" signals: this is the single most common reason AI projects fail. Question 29 is the one I check first before any automation quote.
Before you buy a tool, read what an operational audit actually covers, then how AI agents fit into business operations and what AI automation really costs.
Area 5 — Tools and systems (Questions 30-35)
- Do you know every tool the team pays for, and who uses each one?
- Do two tools hold the same data that has to be kept in sync by hand?
- Is there a tool bought for a problem that no longer exists?
- Do people re-enter the same information in more than one place?
- Does a process only work because one person knows the workaround?
- Are access and permissions reviewed, or does everyone have everything?
- Would a new hire find the tools documented, or have to ask around?
What a "no" signals: you are paying a tool tax with no return, and double data entry is quietly costing hours a week. Often the cheapest win in the whole audit.
Area 6 — Finance and cash operations (Questions 36-41)
- Do you know your true cost to deliver one unit of your service?
- Are invoices sent on a schedule, or when someone remembers?
- Do you track overdue payments in one place?
- Can you see margin by client or project, not just total revenue?
- Are recurring expenses reviewed, or do they renew unnoticed?
- Is approval for spending defined by amount and by role?
What a "no" signals: you are flying on revenue, not profit. Automating billing here is one of the fastest paybacks, once the numbers are defined.
Area 7 — Communication and meetings (Questions 42-47)
- Does every recurring meeting exist to make a specific decision?
- Are action items captured with an owner and a date?
- Is there one source of truth for "what we decided"?
- Do updates happen in threads no one can find a week later?
- How many of your meetings could be a written update instead?
- When something goes wrong, does the lesson get recorded anywhere?
What a "no" signals: the team is busy but not aligned. This is where an AI meeting-notes or summary agent earns its place, once decisions have an owner to route to.
Download the checklist template
Two ways to take this with you. Copy the plain-text version below straight into your doc, or request the Google Sheet version — same 47 questions with green / yellow / red scoring columns and an area summary.
BUSINESS PROCESS AUDIT CHECKLIST — 47 QUESTIONS Score each question: GREEN / YELLOW / RED AREA 1 — LEADS AND SALES 1. Do you know your average first-response time to a new lead, in minutes? 2. Is there one place where every inbound lead lands, or several? 3. Does every lead get a first reply without someone remembering to send it? 4. Can you say which lead source produces paying clients, not just leads? 5. Is your follow-up sequence written down, or does it live in someone's head? 6. Do leads get lost between "interested" and "booked a call"? 7. Is there a defined point at which a lead becomes a qualified opportunity? 8. Does one named person own the pipeline number, or is it "everyone's job"? AREA 2 — CLIENT ONBOARDING AND DELIVERY 9. Is there a repeatable onboarding sequence, or does each client start differently? 10. Does a new client know what happens next without having to ask? 11. Are handoffs between sales and delivery written down? 12. Can you deliver the core service if the key person is away for a week? 13. Do you track where projects stall most often? 14. Is "done" defined the same way by you and by the client? 15. Do you capture why clients leave, somewhere you can actually review it? AREA 3 — DELEGATION AND OWNERSHIP 16. Does every recurring task have a single named owner? 17. Are there tasks only you can do that someone else should be doing? 18. When you delegate, do you hand over the outcome or only the steps? 19. Is there a written way to escalate a blocked task? 20. Do people know which decisions they can make without you? 21. How many open loops are waiting on your reply right now? 22. Is there a task that breaks the week every time its owner is out? AREA 4 — DATA AND REPORTING 23. Do you have numbers you trust, or numbers you argue about? 24. Is the same metric defined the same way across the team? 25. How long does it take to pull last month's key numbers? 26. Are reports built by hand every time? 27. Do decisions wait on data that arrives too late to matter? 28. Is customer data in one system, or scattered across tools? 29. If you switched on an AI tool today, would it find clean, consistent data? AREA 5 — TOOLS AND SYSTEMS 30. Do you know every tool the team pays for, and who uses each one? 31. Do two tools hold the same data that has to be kept in sync by hand? 32. Is there a tool bought for a problem that no longer exists? 33. Do people re-enter the same information in more than one place? 34. Does a process only work because one person knows the workaround? 35. Are access and permissions reviewed, or does everyone have everything? 36. Would a new hire find the tools documented, or have to ask around? AREA 6 — FINANCE AND CASH OPERATIONS 36. Do you know your true cost to deliver one unit of your service? 37. Are invoices sent on a schedule, or when someone remembers? 38. Do you track overdue payments in one place? 39. Can you see margin by client or project, not just total revenue? 40. Are recurring expenses reviewed, or do they renew unnoticed? 41. Is approval for spending defined by amount and by role? AREA 7 — COMMUNICATION AND MEETINGS 42. Does every recurring meeting exist to make a specific decision? 43. Are action items captured with an owner and a date? 44. Is there one source of truth for "what we decided"? 45. Do updates happen in threads no one can find a week later? 46. How many of your meetings could be a written update instead? 47. When something goes wrong, does the lesson get recorded anywhere?
When you do not need this audit
If your team is three people or fewer and everyone can see the whole operation, a formal audit is overkill. At that size the answers live in the same room, and the better move is to fix the one obvious red rather than run a process. Run the full operational audit checklist once you cross roughly five people, when work passes between people who do not sit together, or when you are about to spend money on automation and want to know it will land on solid ground. For a small business right at that threshold, one pass through the worst area is usually enough to decide.
What this looks like in practice
I run operations for a network of nine business clubs across ten countries, plus several online schools. When we audited the member-facing side of one club in Dubai, the reds were not exotic: leads waited hours for a first reply, the same member data lived in three tools, and reporting was rebuilt by hand every week. The audit put a number on it too: about $23,000 a year was leaking through manual handoffs — unpaid orders nobody chased and leads that waited past the weekend. We did not start with AI. We fixed ownership and consolidated the data first, then put agents on the two processes that were finally clean enough to automate: lead response and member follow-up. Roughly 290 recurring tasks now run without a person touching them, and time spent on operational routine dropped by about 60%. None of that would have held if we had automated the reds instead of fixing them first.
Get a free 25-min ops audit. If your checklist came back mostly red, that is the useful outcome, not the bad one. Bring your reds and leave with a prioritized first move.
Book a slotFAQ
