Uncertainty goes to a person.
Missing data, an unfamiliar document or an uncertain result is queued for a named reviewer. The workflow does not invent an answer.
THE FAILURE PLAN / TRUST BY DESIGN
What happens
when AI is wrong?
Eventually, a document will be unclear, a connection will fail or a suggestion will be off. The workflow should know what to do before that day arrives.
STOP → HOLD → RECORD → RECOVER
01 / THE FAILURE PLAN
A safe answer
is sometimes “stop”.
Each exception has an owner and a defined next move.
Failed checks block the next step.
If a required identity, source or policy check cannot be completed, the item stays open. There is a visible owner and a route to resolution.
The decision leaves a trail.
The log captures the input, suggested output, checks, reviewer and outcome. The precise record and retention rules are set during scoping.
There is a way back.
Every build includes a documented pause or kill switch and a return to the manual process. We test the route before handover.
02 / THE RUBBER-STAMP TEST
Approval has to mean
someone looked.
A review screen should show the source, the proposed result and what changed. We design approvals that give the reviewer enough context to disagree. Approval patterns can then be checked for signs that review has become automatic.
The screen shown here is an illustrative design pattern. Each build’s exact checks and interface are agreed during scoping.
CLIENT FILE / EXAMPLEWAITING FOR REVIEW
SOURCE
Supplier invoice · $1,240 · details received
SUGGESTED ACTION
Match to purchase order and prepare for approval
!
Bank details differ from the saved supplier record.
Hold for a human callback.
HOLD ITEMCOMPARE SOURCE ↗
03 / THE BOUNDARY
Some work stays
entirely human.
We automate the preparation around these decisions. We do not make the professional judgement for you.
- Professional advice or opinions issued in your name
- Affidavits, witness statements and expert evidence
- Final decisions to decline an applicant, tenant, patient or client
- Clinical judgement or suspicious-matter decisions
- Lodgments and payments without an agreed human release
04 / WHAT THE CONTROL FILE HOLDS
What the workflow does
Inputs, tools, data paths, decision points and named roles.
What happened
The agreed audit trail and the information a reviewer can inspect.
How to stop it
Exception routes, a kill switch, rollback and a manual fallback.
MDX Labs designs workflows to support your obligations; it does not provide legal or professional compliance advice. For current guidance, see the Tax Practitioners Board’s AI guidance, the OAIC’s APP 1 guidance and the National AI Centre’s adoption guidance.
NEXT / START WITH ONE WORKFLOW
Keep the hours.
Keep the control.
We will map the failure routes and named review points before a build begins.
Book an Automation Audit