The handover pack should allow someone other than the builder to understand, operate and stop the service. Use this proposed minimum set:
| Document | Minimum contents |
|---|---|
01-pilot-charter |
Objective, scope, exclusions, owners and stop conditions |
02-baseline-and-alternatives |
Demand, current outcomes, costs, assumptions and non-AI options |
03-policy-register |
Approved answers, booking rules, exceptions and revision owners |
04-data-flow-and-controls |
Processing parties, access, retention and sensitive-data boundaries |
05-contract-and-price-register |
Order forms, agreements, inclusions, minimums and exit terms |
06-integration-specification |
Tools, field mappings, permissions, transaction states and duplicate prevention |
07-routing-and-handoff-runbook |
Destinations, coverage, acceptance and failure paths |
08-test-pack-and-results |
Cases, expected system states, evidence and unresolved defects |
09-outcome-ledger |
Unique tasks, verified completions, human rescue, failures and recontacts |
10-release-and-incident-log |
Changes, approvals, incidents, remediation and rollback history |
11-economics-and-decision-memo |
Fully loaded costs, alternatives, sensitivity analysis and decision |
12-exit-and-recovery-plan |
Number control, exports, deletion, credential rotation and return routing |
For an outsourcer, add client-specific approvals, tenant separation and the treatment of automation under the client’s commercial agreement. For a multi-location operator, add a signed exception sheet for each location rather than assuming one branch’s rules apply everywhere.