An approval audit should establish who authorised which exact customer update and what actually executed. A note saying “manager approved” is insufficient when several proposals or revisions existed.
Decision evidence needs a trusted actor
Approval evidence links an authenticated authorised reviewer to a specific proposal revision, decision, time, and policy context. It should remain distinguishable from the AI’s recommendation and the executor’s later result.
For a proposed audit record, include reviewer identity, relevant role or scope reference, proposal identity, revision, decision, trusted timestamp, and execution operation. Use controlled evidence links rather than duplicating the full customer record in every event.
Do not accept an agent-generated person name as proof of the reviewer. The application’s authenticated decision path supplies identity, and the permission service establishes whether that actor could approve the resource.
Audit a fictional contact correction
An AI proposes changing a callback number. A supervisor approves revision two after the caller’s correction. The executor updates the record and stores its authoritative version. The audit should show that revision one was superseded and did not authorise the final value.
If the update fails after approval, keep that failure linked. A decision record cannot be presented later as proof that the customer record changed. Reviewers need the separate execution disposition.
| Audit question | Evidence |
|---|---|
| Who decided? | Authenticated actor reference |
| What was approved? | Proposal revision and relevant scope |
| Was the actor authorised? | Trusted policy decision reference |
| When did the decision apply? | Decision and expiry timestamps |
| What happened afterward? | Authoritative execution result or uncertainty |
Test a forged reviewer name, a direct unauthorised request, a changed proposal, and a failed write. Assert both audit content and actual business state.
Protect the evidence trail
Restrict who can edit proposals, inspect audit records, and delete retained artifacts under the actual policy. Ordinary note editing should not silently rewrite past approval evidence. Corrections to audit metadata need their own accountable process.
Audit detail creates storage and privacy obligations. Keep the minimal data needed for the defined review and preserve source access controls. Do not store secret verification values simply to demonstrate that identity checks occurred.
This audit design is proposed. The HVAC case study documents authenticated staff operations without claiming this approval feature. Pair it with action evidence recording.
Approval evidence FAQ
Is a reviewer’s display name enough?
No. Use the authenticated actor and trusted permission decision under the application’s identity model.
Does approval prove the update completed?
No. Link the separate authoritative execution result.
Should every approved value be copied into broad logs?
Prefer controlled proposal and version references, with sensitive detail accessible only to authorised reviewers.