What human approval should look like in an agent workflow
A useful approval is a decision package with evidence and consequences—not a generic “allow” button.
Approval should resolve a real decision
If every step requires approval, the workflow is a slower task list. If no step requires approval, the operation may lose control. Place review where ambiguity, financial consequence, policy, or irreversible action warrants human judgment.
Show the proposed change in context
The reviewer should see the source, the current record, the proposed record, the reason for the recommendation, and what downstream work will occur. Approval must bind to that exact action; a changed payload should require a new decision.
Treat rejection as information
Capture why work was corrected or rejected and route the workflow accordingly. Those outcomes reveal weak identity rules, missing context, schema drift, and policy gaps that a simple accuracy score cannot show.