Stockertim Dictionary · Artificial intelligence · Business
Approval gate
Also called approval checkpoint, approval gates
In short
An approval gate is a point in a workflow where an action waits until a named person approves it, placed before steps that are costly, visible to outsiders or hard to undo.
- Beginner
- Process
- Checked
In detail
An approval gate pauses a workflow at one specific action. The system prepares everything, such as the drafted email, the proposed payment or the record change, then holds it in a queue and notifies the approver. Only when that person approves does the action run; if they reject it, the item goes back with their reason or to someone who can deal with it.
Gates are placed by the risk of the action, not by the system as a whole. Reading data or writing an internal note rarely needs one. Sending anything to customers or suppliers, spending money above a set amount, changing bank details, deleting records and publishing content usually do. A useful test is to ask what happens if the action is wrong: if the answer is embarrassing, expensive or permanent, a gate belongs there.
The approver needs enough to decide well: the proposed action exactly as it will run, the inputs it came from and any warnings. A gate that shows only "approve payment?" invites a reflex click. Approvals are logged with who approved, when and what they saw, which also creates the evidence for later review.
Too many gates cause their own failure. When approvers face dozens of routine requests a day, they stop reading them, so teams keep gates for actions that matter and remove them where a record of reliable decisions supports it.
Worked example
Kestrel Print Works places gates in its quote-to-order workflow.
- Drafting a quote from a customer request: no gate; the draft is internal.
- Sending a quote under £5,000: the account manager approves.
- Sending a quote of £5,000 or more: the account manager, then the sales director.
- Changing a customer's credit terms: always the finance manager, with the reason recorded.
Routine drafting runs freely, and every action that commits the firm waits for the right person.
In practice
Teams list every action an automation can take, mark those needing approval and by whom, show approvers the exact action and its sources, log each decision, and review approval volumes so that gates stay meaningful.
Watch out
- An approver who sees too little, or too many requests, approves by habit.
- A gate the system can bypass on error or timeout is not a gate.
Learn it properly
Official sources
- AI Risk Management Framework · National Institute of Standards and Technology
- Top 10 for large language model applications · OWASP Foundation
Facts last checked on 9 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.