Operations
Human in the loop
Also called: HITL, human oversight
Definition
Human in the loop means a person reviews or approves an AI system's output before it takes effect — meaningful only when that person has the time, information, and authority to disagree.
Oversight that exists on the org chart but not in the working day is theatre. If a reviewer sees four hundred recommendations a shift with no reasoning attached and no time budgeted to dissent, the loop is closed on paper and open in reality. Real oversight is a staffed, measured control with an observable override rate, and it costs real money to run properly — money that gets quietly cut once a system appears to be working.
Watch the override rate
An override rate near zero usually means the review is nominal, not that the model is perfect, because no real-world decision process is right one hundred percent of the time when a genuinely engaged second opinion is applied to it. A healthy control produces disagreement often enough to prove someone is genuinely looking, and a rate that drifts toward zero over time is a warning sign worth investigating before it is treated as a success metric. Track the rate over time rather than as a single snapshot, because the drift itself is the signal, not the level.
Half a job is the failure mode
Automating the easy portion of a role leaves a human with only the hard, ambiguous residue and none of the routine work that built the intuition needed to handle it. Oversight quality degrades over the following year even though nothing in the system changed, because the reviewer who once built judgment by handling a full range of cases is now seeing only the difficult tail, without the volume of straightforward cases that used to keep their pattern recognition sharp. This is a predictable consequence of automation sequencing, not a personnel failure, and it should be planned for rather than discovered.
Designing the review, not just requiring it
A review step is only as good as the interface it happens through. Reviewers who are shown a bare recommendation with no context tend to approve it by default, because disagreeing requires reconstructing the reasoning from scratch under time pressure. Reviewers shown the evidence, the confidence, and the specific factors the system weighed are far more able to catch a genuine error, because the interface does part of the reconstruction work for them. Investing in the review interface is often cheaper than adding reviewer headcount and produces a more reliable control either way.
In practice
- Budget review time explicitly; unfunded oversight becomes rubber-stamping
- Show the reasoning and the confidence, not just the recommendation
- Track override rate and reviewer tenure as control-health metrics
- Design the review interface deliberately; a bare recommendation invites default approval
