# Customer operation and handover checklist

Demonstrate that the agreed operating team can run a specific release. A training attendance record is insufficient by itself.

**Workflow, environment and release:** ____________________  
**Customer service owner:** ____________________  
**Technical owner:** ____________________  
**Handover date:** ____________________

| Task to demonstrate | Exercise | Evidence and owner | Ready / gap |
|---|---|---|---|
| Review operating health | Locate an aged queue and identify its next owner. | ______ | ______ |
| Resolve a normal exception | Inspect evidence, record a decision and verify continuation. | ______ | ______ |
| Maintain a source | Identify an outdated record and follow the approved update process. | ______ | ______ |
| Manage access | Confirm the correct role and remove an expired support permission. | ______ | ______ |
| Recover from a failure | Pause affected work, verify system state and follow the recovery procedure. | ______ | ______ |
| Evaluate a supported change | Inspect cases, decide whether to release and identify the rollback path. | ______ | ______ |
| Review value | Reconcile attempts, accepted outcomes, remaining effort and costs. | ______ | ______ |

**Transferred materials:** Configuration reference, operating runbook, evaluation set, incident procedure, change process, support contacts and agreed export documentation.

**Customer-operated scope:** ____________________  
**Software maintenance/support scope:** ____________________  
**Optional Managed Operations scope:** ____________________  
**Outstanding conditions and due dates:** ____________________

**Decision:** Accepted / Conditional / Not ready.  
**Acceptance owners:** Customer process owner, technical/control owners and Wildchild delivery owner, as agreed for the engagement.

---
Wildchild · Applied AI. Built around your business.
https://www.wildchild.ai
https://www.wildchild.ai/contact