AI Agent Client Handover Checklist for Agencies.

Before the review

Write down the version being reviewed, the workflow scope, the business rules, the test data and the people responsible for the review. State what is outside the review so a finite check is not mistaken for a general safety or compliance assessment.

• Change: prompt, model, tool, configuration or workflow version.
• Scope: the workflow, actions and systems included.
• Rules: expected actions, approval boundaries and “must never happen” cases.
• Evidence plan: what request, action, result and resulting state will be retained.

During the review

Record the exact request, starting state, actions taken and final state for each check. A report can use clear words such as “met the rule”, “needs a fix” or “inconclusive”. Avoid turning an unavailable external system into a pass.

This example is invented and does not report a customer result.

After the review

Separate open issues from accepted limitations. Assign an owner and next action for each open item. Record whether the client decision is to hold, fix and recheck, or accept a stated limitation within the agreed process.

1. Share the summary and evidence.
2. Discuss the change and required client input.
3. Repeat the agreed checks after a fix.
4. Record reviewer, decision and date.

What to retain

Keep the agreed rules, version/settings, starting records, requests, actions and results, open issues, owners and decision. Redact customer information before public sharing and agree access and retention before a real engagement begins.

The sample report and editable checklist illustrate this structure. The report is fictional; the checklist example rows are intentionally marked “not checked”.