Designing Human Approval Steps for Automation
An approval step is useful only when the reviewer can understand the proposed action. A button labelled Approve does little if the important change is hidden in a raw record.

Show what the decision means
Present the relevant input, the proposed result and the consequence of approval. Highlight changes that deserve attention and explain what happens after rejection. Avoid making reviewers inspect every technical field when only a few determine whether the action is appropriate.
Practical checklist
- Show the proposed action clearly.
- Identify the affected records.
- Provide approve and reject outcomes.
- Record the reviewer and decision.
How to review the result
Test with a deliberately incorrect proposal. The reviewer should be able to identify the problem and stop the action without needing developer assistance.