Approvals
Review escalated actions with the policy reason, evidence, and closure path in one place.
Use this page when
Open this page when a governed action needs human review or when you need to explain how risky work was approved, blocked, or closed.
What the reviewer should see
Every approval should answer five questions without leaving the page:
- why this action escalated
- which policy or tier applied
- who is allowed to review it
- what evidence is already attached
- how the decision will close into a receipt
Review flow
- Read the escalation reason and action summary.
- Confirm the destination, risk, and evidence context.
- Approve, block, or send the action back for more context.
- Verify that the result closes into a durable receipt.
What success looks like
The approval surface is working when a reviewer can explain both the action and the reason for the decision without translating internal vocabulary.
Common mistakes
- treating approvals as a generic inbox with no policy explanation
- approving without checking the attached evidence
- closing the action without confirming the receipt path