Comparison

Human in Control vs Human-in-the-Loop vs Human-on-the-Loop

Four ways to wire a person into an automated decision loop. The first three describewhere the human is positioned. The fourth, human in control, is different in kind: it is an operating model that defines who holds final decision rights, regardless of who does the work.

By Graeme Provan · 2026-06-11

The three loop positions

The in/on/out-of-the-loop taxonomy predates modern AI agents. It was formalised in the autonomous-weapons debate and builds on John Boyd's OODA decision cycle. Each position answers a single question: where does the human sit relative to the decision loop?

Human-in-the-Loop (HITL)

Nothing executes without a person. The AI proposes; the human approves; then the action happens. Maximum control, minimum speed - the loop runs at human pace. The characteristic failure mode is the bottleneck: work piles up behind a single approver, or approval becomes rubber-stamping.

Human-on-the-Loop (HOTL)

The loop runs by itself; a person watches.The human monitors from outside and steps in when something looks wrong. Fast, but intervention is reactive - after the fact. The characteristic failure mode is the "polite fiction": events outpace the watcher, and interventions come too late.

Human-out-of-the-Loop (HOOTL)

The system acts entirely on its own. No human sees the decisions in real time. Fastest of all - and the riskiest place to discover the system was wrong. The failure mode is silent failure with no recourse.

Human in control: an operating model, not a position

Human in control is an operating model for AI agents in which autonomous agents execute the work while a human retains final decision rights - the authority to approve, redirect, or stop any agent action at any time.

Unlike HITL or HOTL, human in control does not dictate where the human sits. It dictates what authority they retain. An agent under human control may propose, execute, or both - scoped by risk - while the human's standing authority never moves. The model is compatible with any loop position: low-risk tasks run autonomously (HOTL rhythm), while high-risk actions require explicit approval (HITL rhythm).

The reference matrix

DimensionHITLHOTLHuman in Control
Question it answersWhere the human sitsWhere the human sitsWho holds authority
What the AI may doPropose onlyExecute within boundsPropose and/or execute - scope set per risk tier
Final decision rightsHuman, per actionAI by default; human can overrideHuman, always - standing authority to approve, redirect, stop
Human interventionBefore every action (gate)After detection (reactive)At any time, by design
AccountabilityClear; erodes if rubber-stampingBlurs at machine speedExplicitly retained by a named human owner
Characteristic failureBottleneck; approval theaterEvents outpace the watcherGovernance debt - control on paper but not in practice

A worked example

Imagine a bank deploying an AI agent to process mortgage applications:

  • HITL mode:Every application stops at a loan officer. Safe, but the queue grows. The officer eventually clicks "approve" without reading - automation bias turns the gate into theater.
  • HOTL mode: The agent approves routine applications and flags anomalies for review. Fast for the 95%, but when the model drifts, the watcher misses the shift.
  • Human in control: The agent handles routine approvals (HOTL rhythm). High-value or borderline applications queue for human approval (HITL rhythm). The loan officer can pause the entire pipeline at any time. Every action is logged and attributed. The operating model is the same; the loop position changes with the risk.

Which should you start with?

Start human-in-the-loop while the agent earns trust, then widen autonomy toward an on-the-loop rhythm - but build human-in-control guarantees (approval surface, logging, kill switch) from day one. The loop position is a dial you turn as trust grows. The control model is the foundation you never remove.

Read the full canonical definition:

What is Human in Control?