Human in the loop
A design where a named person makes the material decision, and the system's job is to prepare it well enough to decide quickly.
Category
What keeps it honest
Related terms
Human in the loop means a person decides. The phrase is often used loosely for any design with a person somewhere nearby, which is why it is worth being exact about what the person is actually holding.
Review is not the same as approval
A person shown an output and given an approve button is not reviewing; they are ratifying. Genuine review requires the same material the decision needs: the recommendation, the evidence behind it, what is uncertain, what the alternatives were, and which policy applies. If a reviewer cannot reconstruct why, the loop is decorative.
Designing for the reviewer's time
The failure mode of human-in-the-loop systems is volume. A reviewer facing more cases than can be considered will approve by default, and the control quietly disappears. The design question is therefore not “is a human involved” but “how many cases reach a person, and does each one arrive with what a decision needs.”
Where automatic action fits
Automatic action is allowed inside an explicit boundary: written policy, measured quality thresholds, delegated authority, approved tools, and stop conditions. Everything outside that boundary stops and reaches the responsible person or committee with a complete review packet. Both routes write the same evidence record, so the decision is traceable whichever way it went.
Often confused with
How it differs from similar terms.
| human in the loop | Compared with | What's different |
|---|---|---|
| Human in the loop | Human on the loop | In the loop: a person decides each case. On the loop: a person supervises a running process and can intervene. |
| Review | Approval click | Review needs evidence, uncertainty, alternatives, and policy. Without them the control is decorative. |
Want these terms worked through on one of your own decisions? Start with a Decision Blueprint