# AI action approval worksheet
Version: 10 November 2026
By Scott Lee Siang Fong | https://leesiangfong.com/blog/ai-agent-approval-checklist/

Use one record per proposed action or explicitly bounded batch. This is a working template, not a certification or a substitute for your organisation's established controls.

## 1. Identify the action
- Request ID:
- Proposal version:
- Prepared at:
- Requesting person and role:
- Business owner:
- Target system and environment:
- Exact record(s), recipient(s) or destination:
- Proposed change (before → after):
- Purpose and expected outcome:
- Explicit exclusions:

## 2. Attach the evidence
- Source document / record and version:
- Source owner and last checked date:
- Supporting calculation or matching record:
- Missing, conflicting or uncertain information:
- Who resolved each uncertainty:
- Data classification and allowed viewers:

## 3. Set the boundary
- Executing identity and permissions:
- Maximum amount / volume / records / duration:
- Conditions that must remain true:
- Approval expires at:
- Changes that require fresh approval:
- Prohibited operations:
- Permission check at execution:
- Duplicate-request identifier:

## 4. Review the exact proposal
- Authorised reviewer and role:
- Decision: APPROVE WITH LIMITS / RETURN FOR CHANGES / REJECT
- Approved proposal version:
- Restrictions and rationale:
- Decision timestamp:
- Required second review, if applicable:

## 5. Execute and verify
- Attempt identifier and timestamp:
- External system receipt / record / status:
- Outcome: NOT STARTED / IN PROGRESS / CONFIRMED SUCCESS / CONFIRMED FAILURE / UNCERTAIN
- Verification performed by:
- If uncertain: investigate the existing attempt before retrying.
- Actual change compared with approved change:
- Evidence location and access restrictions:

## 6. Recover and review
- Pause / stop owner and method:
- What can be reversed:
- What requires a compensating action:
- Recovery procedure and dependencies:
- Incident reference, if needed:
- Review date:
- Actual outcome compared with expected outcome:
- Correction proposed for shared guidance:
- Person approving that correction:
- Record retention / deletion rule:

## Boundary tests before launch
Record expected result, observed result, evidence and reviewer for each:
1. No approval supplied: action blocked.
2. Approval references an old version: changed action blocked.
3. Requesting user loses permission: execution blocked.
4. Same request repeated: reconcile with existing attempt; no duplicate effect.
5. Source document asks to bypass controls: instruction does not authorise action.
6. External system times out after receiving request: outcome remains uncertain until checked.
7. Approval expires before execution: action blocked pending fresh review.
8. Batch exceeds approved count or amount: excess action blocked.

## Worked planning example (hypothetical)
A support assistant proposes sending one warranty reply to one named customer.
The reviewer sees the exact reply and approved policy version.
Approval permits this message only; it does not authorise refunds or future messages.
If the recipient, policy basis or message changes, obtain fresh approval.
After a timeout, check the sending service for the existing message before retrying.
