Human-in-the-loop automation: why not everything should be fully automatic
How to design business automations and AI agents so that routine steps run automatically while risky actions are approved by a person.
5 min read
Key takeaways
- Different actions carry different risks and need different controls.
- Automation prepares the action; a person approves anything with an external effect.
- Every proposal and decision must be traceable in a log.
- Expand autonomy gradually, once you have history and confidence in the quality.
Not every action carries the same risk
Classifying an incoming email is different from sending a reply to a customer or changing a price in the store. Good automation separates actions by risk and applies a different control to each of them.
- Low risk: reading, summarising, classifying, drafting.
- High risk: sending messages, changing products.
- Critical risk: prices, orders, payments, access to sensitive data.
What approval looks like in practice
The system prepares the action — for example an email draft or a proposed stock change — and places it in an approval queue. The responsible person sees what will happen, approves or rejects it, and the decision is recorded in a log.
This way automation saves the preparation work while control stays with people.
Logging and traceability
Every proposed, approved or rejected action must be traceable: who requested it, who approved it, when and with which data. The log helps when things go wrong, during audits and when improving the rules.
Expanding autonomy gradually
Start by requiring approval for anything with an effect outside the system. Once you have built up history and confidence in the quality, you can deliberately expand the automatic actions — with clear limits and the ability to roll back.
When not to automate
If a process happens rarely, depends heavily on judgment, or a mistake is expensive and hard to correct, manual handling with good tools is often the more sensible choice.