Human-in-the-loop: why the best automation keeps a person in charge

The fastest way to lose trust in automation is one bad email sent to one important client. The fastest way to keep it is making sure that email couldn't have sent itself.

What human-in-the-loop means in practice

The system does the work; a person makes the calls. An inbox automation reads, sorts, chases and drafts — but the draft sits in a queue until someone clicks send. An invoice system extracts and checks — but anything unusual routes to a person instead of posting. The human isn't doing the work anymore; they're doing the judging, which is the part they were always uniquely good at.

Where the loop belongs

• Anything outward-facing. Emails, quotes, letters — reputation rides on them.
• Anything financial. Payments, pricing, credit decisions.
• Anything irreversible. Deletions, filings, contract commitments.
• Anything the model flags as uncertain. Good systems know when they don't know, and say so instead of guessing.

Internal, reversible, low-stakes work — sorting, summarising, drafting, matching — can and should run free. Putting approvals on everything is how you build a system nobody uses.

The speed objection

"Doesn't the human slow it down?" Barely — and it's the wrong comparison. Approving a drafted email takes ten seconds; writing it took four minutes. The automation still removed 95% of the work. What the loop costs in seconds it repays in the one intervention a month that prevents a real mistake — and in something less measurable: your team trusts a system they supervise, and adopts it. Automation people don't trust gets quietly worked around, and dies.

It's also the law's direction of travel

UK GDPR already restricts significant decisions made solely by machine, and regulation is moving one way. Systems designed with human decision points aren't just safer — they're already shaped like the compliance environment they'll live in. More on that in GDPR and AI.

← All notes