Loading patterns…
Approval Queues & Escalation Chains(AQE)
First-class approval and escalation as an operational workflow rather than a single blocking gate. Actions are tiered by risk: reversible actions auto-approve, medium-risk actions go to asynchronous review where the agent persists its state, continues other work, and rehydrates when a decision arrives, and irreversible actions require synchronous approval before execution. Escalation is triggered by explicit signals including confidence breaches, an irreversibility flag, SLA-approach, and anomaly or injection detection, and routes the decision to a higher-authority adjudicator (a human, a more-privileged agent, or an external workflow). Distinct from `human-in-the-loop`: HITL is the generic synchronous stance, whereas this pattern adds risk tiering, asynchronous queueing with state rehydration, and adjudicator routing.
In 30 seconds
- What
- Routes actions through risk tiers: reversible auto-approve, medium-risk async review with state persistence, irreversible sync approval. Escalates by confidence, irreversibility flag, SLA, or anomaly to designated adjudicators.
- When to use
- Operations where some decisions can proceed without approval, others need asynchronous human review without blocking the agent, and some require synchronous sign-off before execution.
- Watch out
- State rehydration after approval delay can fail silently if context drifts or the agent's working memory is incomplete when resuming.
Ask the AI expert about this pattern
Opens the assistant with your question prefilled. You review it before sending.
Approval Queues & Escalation Chains: Overview
First-class approval and escalation as an operational workflow rather than a single blocking gate. Actions are tiered by risk: reversible actions auto-approve, medium-risk actions go to asynchronous review where the agent persists its state, continues other work, and rehydrates when a decision arrives, and irreversible actions require synchronous approval before execution. Escalation is triggered by explicit signals including confidence breaches, an irreversibility flag, SLA-approach, and anomaly or injection detection, and routes the decision to a higher-authority adjudicator (a human, a more-privileged agent, or an external workflow). Distinct from `human-in-the-loop`: HITL is the generic synchronous stance, whereas this pattern adds risk tiering, asynchronous queueing with state rehydration, and adjudicator routing.
- Risk tiers: auto-approve reversible, async-review medium, sync-approve irreversible
- Asynchronous approval: agent persists state, works other tasks, rehydrates on decision
- Escalation triggers: confidence breach, irreversibility, SLA-approach, anomaly or injection
- Adjudicator routing to a human, higher-privilege agent, or external workflow
- Decision-ready context packages (summary, diff, financial impact, reversibility flag)
- Time limits with automatic escalation so approvals do not stall operations
Get the Agent UX field guide
All 21 agent-UX patterns condensed into one guide: what each is, when to reach for it, and what bites in production. The link arrives with your confirmation, alongside the weekly Agent Architect.
Weekly email, one-click unsubscribe. We only use your address to send the briefing.
References
The papers, specifications, and repositories this pattern is based on.
From the engineer behind this catalog
Get your agent architecture reviewed
This page documents one pattern. Your system runs dozens, and most failures live in how they fit together. Have the whole design reviewed against the 288 patterns in this catalog: architecture, reliability, evaluation and cost, every finding mapped to the pattern that fixes it.
€750 instead of €1,500, one week, written report and walkthrough call, until 30 September