Approval gates: how to keep humans in the loop without slowing down
A gate is a named person’s sign-off at a specific step. Place it on the step that is expensive to reverse, run everything before it unattended, and state what it costs.
Oversight fails at both ends, with no gate at all and with a gate on every step
Today
Sign-off everywhere or nowhere, paid for in attention
- You have seen both failure modes.
- A workflow with no human step did something expensive before anyone looked, and a workflow with a sign-off on every step trained its reviewers to click through without reading.
- "Keep a human in the loop" gets said in every planning meeting and almost never with a location attached.
- A badly placed gate is paid for in attention, which is the scarcer resource.
With agents
One gate, on the consequential step, held by a name
- Control moves from a promise to a position in the workflow.
- Review attention goes to one decision instead of many.
- The cost of oversight becomes visible and chosen.
The anatomy of an approval gate
An approval gate is a control with a position, a holder and a cost. The items below are the properties of a gate placed well.
01
The gate is a named person's sign-off at a specific step
Without it the workflow does not proceed. The name and the step are both part of the definition.
02
It sits on the consequential step
The consequential step is the one that is irreversible or expensive to reverse: a payment released, a message sent to a client, a permission changed, a record deleted. That is where the gate belongs.
03
Everything before it runs unattended
The agent gathers, reconciles and flags on its own, then presents a finished package at the gate. The person reviews one assembled decision rather than a stream of interruptions.
04
A gate differs from a review and from an escalation
A gate is sign-off before an action. A review is inspection after it. An escalation is the routing of an exception the rules cannot decide. Confusing them puts sign-off where inspection would do, or leaves an exception waiting at a gate built for routine approvals.
05
Human gate
The agent routes the consequential action to the named owner with the evidence attached, and waits. The gate is a step in the workflow's design, and How It Works describes how that step is enforced.
06
The gate costs something, and the cost is the reason placement matters
It costs latency at the gated step and it costs the reviewer's attention, and when gates sit on every step it costs the gate its meaning, because a reviewer who signs everything is inspecting nothing.
07
Gated by default, opened only by your decision
A consequential step starts gated. A gate is removed on a recorded human decision, never by the agent and never by drift. The evidence that supports such a decision is built in shadow mode, which has its own entry.
Results
What changes when the gate has a position
Control becomes structural
The gate is a step the workflow cannot pass without a person, so the guarantee is structural.
One decision, read once
The unattended steps deliver a finished package to the gate, so the reviewer reads a complete case once.
Oversight costed and chosen
Each gate is placed on purpose with its cost stated, so adding or removing one is a decision rather than a default.
Where this fits
Concept
This is the vocabulary every workflow entry in the library uses when it names a human gate on its consequential step, and the readiness checklist names the gate as one of its checks. How It Works is the way up from here. How It Works describes how a gate is enforced; this entry describes where it belongs and what it costs.
How It Works
Questions, answered
As few as its consequential steps require, which for most workflows is one. A gate on every step is the failure mode this entry opened with: the reviewer stops reading.
AI Opportunity Audit
Put the gate where the cost is real
Bring the workflow you are least willing to hand off and find its consequential step together.
Related use cases
Back to Use Cases
Workflow
What makes a workflow ready for an agent (the readiness checklist)
Most processes fail an agent handoff for the same few reasons. Here is the checklist to run before you pick a first workflow.
Learn More
Concepts
Shadow mode: how agents earn autonomy
An agent earns autonomy one gate at a time, on a human decision made against a shadow record. The record proves less than it seems
Learn More
Concepts
When NOT to automate: workflows that should stay human
A process resists a handoff for one of two reasons: it is not ready, which preparation fixes, or it should not move, which is a
Learn More
