PRISMWORKS | AI OPERATING HANDOVER
Companion: https://prismworks.ai/resources/owning-ai-after-launch/
Version: 2026-11-02 | Adapt with the receiving team. No submission required.
Record evidence references, not credentials or sensitive source content.

RESPONSIBILITIES
Business acceptance owner / backup:
Technical release owner / backup:
Source and access owners:
Incident response and escalation:
Support coverage and supplier responsibilities:
Cost owner and operating review cadence:

OPERATING ASSETS
For each item record: location, owner, current version, receiving-team access,
and any unresolved dependency.
- Workflow scope, permitted actions, and human approvals
- Source inventory, refresh/removal rules, and access design
- Code, configuration, deployment, and environment instructions
- Customer-owned, licensed, and supplier-operated components
- Evaluation cases, rubrics, results, and known limitations
- Monitoring, case evidence, and retention rules
- Service accounts, licenses, and renewal responsibilities
- User training, reviewer guidance, and feedback process
- Pause, recovery, reconciliation, and manual operating procedures

DEMONSTRATION WITH THE RECEIVING TEAM
For each exercise record: operator, date, observed result, evidence, and gap.
1. Explain and complete a normal case within the accepted scope.
2. Recognize missing or conflicting evidence and escalate appropriately.
3. Locate a failed case and its permitted source observations.
4. Pause new work and account for work already in flight.
5. Establish an unknown outcome before retrying a consequential action.
6. Use the manual operating path during an outage.
7. Evaluate a model, source, or integration change.
8. Restore a known configuration and identify effects needing reconciliation.
9. Remove or revoke a source and verify the intended access behavior.

ACCEPTANCE AND FOLLOW-UP
Open action / accountable owner / review date / required evidence:
Dependencies that still require the original implementer:
Accepted operating boundary and limitations:
Support and escalation agreement reference:
Release or handover decision, owners, and date:
Evidence needed before expansion:
Conditions for redesign or retirement:

Restoring configuration does not reverse emails sent or records changed.
Verify recovery and reconciliation separately. Ownership is demonstrated
operating ability, not simply receipt of a repository or checklist.