Human in the loop (HITL) is a design where a person is a required step in an AI system's workflow. The AI proposes, the human checks, and only then does anything happen. It is the opposite of full automation.
How it works
Picture a junior employee who drafts everything and a manager who signs off. In an AI product, the model drafts the email, flags the transaction or proposes the code change. A person reads it and approves, edits or rejects it.
There are three common patterns:
- Human in the loop: nothing happens until a person approves each action.
- Human on the loop: the system acts on its own while a person watches and can step in or stop it.
- Human out of the loop: the system acts with no routine review.
Where it matters
The more costly or irreversible a mistake, the more sense a human checkpoint makes. Sending payments, deleting data, publishing to customers, giving medical or legal information and changing production code are typical examples. An AI agent that can use tools deserves an approval step before it does anything it cannot undo.
It also helps against model errors. A hallucination is far less harmful when a person is positioned to catch it before it reaches anyone else.
The trade-offs
A person in the loop adds delay and cost. People also get tired. If a reviewer approves hundreds of items a day, the review turns into clicking "yes", which gives the look of oversight without the substance.
Good designs keep the checkpoint meaningful. They show the reviewer what changed and why, ask for approval only on risky actions, and make rejecting as easy as approving. Many teams start with approval on everything, measure how often reviewers change the AI's output, and relax the checks only where the data supports it.
Human review pairs naturally with AI guardrails, which are automatic limits on what a system may do, and with evals, which measure how often the system is right before you decide how much review it needs. Systems that run tool use steps in a chain often put the human checkpoint right before the step with side effects.
A useful rule: the review should happen at the moment where an error would still be cheap to fix.