Human-in-the-Loop Approval Design
Decide where a person must approve, and make approval easy to do well.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design approval points for this automated process: [PROCESS_DESCRIPTION]. Actions it can take: [ACTIONS]. Who could approve: [APPROVERS]. Typical time pressure: [TIME_PRESSURE]. Classify each action as safe to automate, approve before, or never automate, with a reason. For approvals, design what the approver sees: a one-paragraph summary, the evidence, what will happen on approval, how to undo, and a reject button with a reason list. Avoid designs where approval becomes a rubber stamp; suggest random deeper checks and a limit on queue size. Return a table of actions with classification, a mock-up of the approval screen in text, and metrics: approval time, rejection rate and later-corrected rate. Also suggest how to measure whether approvers are actually checking, such as seeded test items with known errors, and how to adjust the design when the queue grows too long for careful review. Finish with a list of the stop conditions that remove the automation's ability to act, such as a rise in rejections, so approvers can pause the process without waiting for permission.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.