How AI workflows stay under control: checks, approvals and stop points
Before you let AI near invoices, enquiries or reports, you should know where it stops. This is how I keep a human in the loop: rules check, AI drafts, a person approves.
Rules do the maths. AI drafts. A person decides.
Every workflow I build is split into three jobs.
- Rules do the checking and the sums. Totals, dates, rates and duplicates are calculated the same way every time. AI does not set a price or change a figure.
- AI reads free text and drafts things, such as a reply or a summary. It is a draft, not a decision.
- A person approves what matters before it moves on. Anything that goes to a customer, posts or pays waits for a person.
If something does not match, the workflow stops and says why. It does not guess.
An agent is one narrow job inside a workflow
In plain terms, an AI agent is one step in a workflow that does a single, narrow job, such as ‘draft a reply to this enquiry’ or ‘summarise this month's exceptions’.
Several steps linked together make a workflow. The agent is never the whole thing. The steps around it are the rules, the checks and the approval.
Whatever the number of steps, each one has an owner and a stop.
Human approval: what runs on its own and where a person steps in
| Build | What runs on its own | Where it stops for a person |
|---|---|---|
| Invoice Check | Reads the invoice and the job. Checks for duplicates and mismatches. | Anything odd goes into a queue. A person approves, corrects or holds it. |
| Enquiry and Quote Follow-up | Sorts and routes the enquiry. AI drafts the reply and the follow-up. | Staff approve every reply and follow-up before it is sent. |
| Job Profit Report | Collects records and calculates margins on a weekly schedule. | A person reviews the exceptions. A low margin is a question, not a verdict. |
| KPI Report | Processes each submission, calculates the KPI, emails the employee and management, and writes the result back. | The emails are internal notices, so they go automatically once you've agreed them. Where a manager's check matters for your business, we add one in the acceptance criteria. |
| Supplier Bill Approval | Checks bills for duplicates and for a match to the purchase order. | A person approves or rejects every flagged bill. The build does not pay anything. |
Seven safeguards I build in
Read-only first.
The audit is a read-only review of your systems. We agree the access before any work starts.
Rules for the numbers.
Amounts, dates and rates are calculated by agreed rules, not by AI. That makes them checkable.
Checks before action.
The workflow checks for duplicates and mismatches before it moves anything on.
A person approves what matters.
Anything that goes to a customer, posts or pays waits for a person. Internal notices, such as the KPI Report's emails to staff, can go automatically once you've agreed them.
Missing or conflicting data stays visible.
If a figure is not available, it shows as not available. It is never filled in with a guess or shown as zero.
Failure is tested before go-live.
Missing information, wrong AI suggestions and failed connections go into the test plan. We agree in writing what ‘working’ means before I build. After delivery you have 30 days of fixes.
A way back.
The agreed design says where the process pauses, who reviews exceptions and how your team falls back to the existing process if something stops.
What happens when a supplier bill does not match
Sample data. Nothing connects to your accounts, approves a bill or moves money.
| Step | What happens |
|---|---|
| Bill arrives | Example Supplies Pty Ltd (sample), bill 7731, $1,840.00, for Job 2102. |
| Rules check | The same bill is already in the accounts. The purchase order was $1,640.00, so the bill is $200.00 over. |
| The workflow stops | It flags the bill and shows both reasons beside the numbers. It does not guess which is right. |
| A person decides | The approver rejects it as a duplicate and records why. |
| Result | The bill is not approved. Nothing is paid. |
The same shape applies to an enquiry reply in automated quote follow-up, an exception in a job profitability report or a KPI submission. The thing in the middle changes. The pattern does not.
Where this comes from
I have built these ideas into real work. Here is what that work is, and what is not claimed.
KPI automation for Elliotts Landscape and Harrys Tyres. Paid client work, two builds, one for each business, both named with their agreement. A Jotform form, Airtable and n8n. Before: about 4 hours each month and countless emails, for each business. After: one click per KPI submission. Revenue and financial return were not measured. The 4 hours is time saved, not cash saved. Hours saved and dollars saved are counted apart. Beside them are the running costs: optional support from A$350 a month, and software and AI usage paid to the providers. Running costs (software and AI usage) are estimated in your audit, before you commit to a build.
See selected past work and about Renzo.
Chartered Accountant (CA ANZ) · MBA · Xero certified · 16 years in finance, operations and systems · Canberra, working across AU and NZ
About RenzoThe same approach runs an agentic finance system I built: 30 agents, about 10,000 automated tests, and a person approves every money decision.
What people ask before they trust a workflow
What happens if the AI is wrong?
A person sees the draft before anything goes out, and the facts it relies on come from your approved information and from rules. If the information is missing, the draft asks for it or hands over to a person. I also test wrong answers before go-live.
Can the AI send an email or an invoice by itself?
Not to a customer. Anything that goes to a customer, posts or pays waits for a person. Internal notices, such as the KPI Report's emails to staff, can go automatically once you've agreed them.
Can it pay a bill?
No. Supplier Bill Approval checks and records an approval. Payment stays a separate step for a person.
What if a connection fails?
The test plan covers it. We agree the alerts, the manual fallback and who is accountable before release.
Where does my data go?
During scoping we identify the information each step needs, who receives it, the access controls and the retention. I do not make claims about certifications, encryption or data regions on this page. Please do not send passwords or confidential records through the enquiry form. How enquiries are handled
Does every workflow need AI?
No. Many of the steps are plain rules. AI is used where it adds something, such as drafting a reply.
Bring one process to the audit
Tell me where your work gets stuck, which tools are involved and what a good result looks like. The audit shows what is worth building, and where a person should approve.
A$990, credited to your build.
Get a free fit check by email
Send the form with your software, the workflow, your team size and your timing. I reply by email, usually with a question or two, and tell you whether it's a fit. No call needed. If it is, the next step is the A$990 Workflow Audit.
Thanks, it's with me.
I read every enquiry myself and reply by email to the address you gave, .
Next, I reply by email, usually with a question or two, and tell you whether it is a fit. No call needed.
If it is a fit, the step after that is the A$990 Workflow Audit.
In the meantime, see how each build runs: worksbetter.ai/#builds
Sending saves your details in HubSpot so I can reply. No mailing list. No payment is taken. How your enquiry is handled.