Human-in-the-loop

A system design where a person must approve, edit, or reject an AI action before it takes effect. The action does not proceed without explicit human sign-off.

Human-in-the-loop (HITL) is a system design where a person must approve, edit, or reject an AI action before it takes effect. The action does not proceed without explicit human sign-off. An AI drafts a customer email, and the system blocks sending until a person reads and approves it. A coding agent proposes a database migration, and the change cannot execute until a developer confirms. The pattern comes from safety-critical fields like aviation, nuclear operations, and surgical robotics, where high-stakes steps required human confirmation long before modern AI. AI adoption brings the same principle to everyday software and business workflows.

Builder example

Use HITL checkpoints wherever a wrong output can damage trust, privacy, money, safety, or reputation. The design cost is real: each checkpoint adds latency and requires a clear interface for the reviewer. Placing checkpoints at the right steps is one of the most consequential design decisions in any AI product.

An agent drafts a reply to a client using meeting notes and CRM history.

Let the agent draft and attach evidence. Require the human to approve before sending.

Common confusion: HITL means the action is blocked until a human approves. A vague promise that "someone can review outputs later" is post-hoc monitoring, which catches problems after they have already taken effect.