AI Transformation · Glossary
Human in the Loop (HITL)
Updated
Human in the loop (HITL) is a workflow design in which an artificial intelligence (AI) model produces or proposes an output and a person checks it against a reference before it takes effect. It belongs where an error would be both costly and hard to spot, such as the steps an AI agent takes on its own. An AI agent is a model that uses tools and picks its own next step. The check is also where a person can catch an AI hallucination, a fluent, confident answer that is false or invented.
The control is the check, not the person's presence: the Human in the loop AI: verify, not approve article argues that a reviewer has to compare the output to something known and own the result. How the tool is framed can weaken the check. In one 2026 Boston University experiment by Emma Wiles, as MIT Technology Review reported it, people caught 18% fewer errors when the same output was attributed to an "AI employee" rather than a chatbot, and were 44% more likely to escalate questionable work rather than correct it. A second account says the effect was concentrated at companies that already list AI on the org chart, so treat it as a risk to design against, not a universal rule.
When does a process need a human in the loop?
When an error would be high-stakes and hard to detect, and nothing else can check the output. Barry Zhang of Anthropic, speaking at a conference, said such errors make full autonomy untenable, because nobody finds out the system was wrong. The test that follows for any AI automation: what plays the role that automated tests play in software? If nothing does, expect a fixed workflow, or budget for a human. Andrew Ng describes three ways to check AI output, chosen case by case rather than ranked:
- A code-based check, where correctness follows a rule.
- A model as judge, where quality is a matter of degree and human review does not scale.
- A human in the loop, where the judgment is subjective, high-stakes, or still being defined.
To keep the check real, an AI vendor's public playbook (Anthropic, August 2026) carries separation of duties over from finance: the tool that produced the work cannot approve it, and a named person authorizes release. In an AI transformation, call AI systems tools, name a human owner for each AI-produced output, and write both rules into the AI acceptable use policy before the first output goes live. The Why human judgment still matters in AI work article takes up the wider question.
Related reading
- Human in the Loop AI: Verify, Not Approve
AI Transformation
- Why Human Judgment Still Matters in AI Work
AI Transformation