Define operational ownership before client handover

A runbook without owners is reference material, not handover. AI services divide responsibility across platform health, task quality, source data, integration contracts and business decisions. One generic “support team” cannot own all of them credibly.

Build the decision artifact

For every service, name who operates it, who owns quality and evaluation, who owns data and permissions, and where incidents escalate. Add SLOs, dashboards, alert routes, access, backups, rollback, vendor dependencies and known limitations. Have the receiving team execute a recovery exercise before acceptance.

The enterprise delivery lab makes this reasoning executable with synthetic data:

from enterprise_cases import ownership_case

result = ownership_case()
assert result["complete"] is True
assert result["fde_owns_everything"] is False
assert result["handover_signed"] is False
assert len(result["services"]) == 2

The fictional matrix assigns those four responsibility types for workflow and connector services. The FDE owns neither everything nor an imaginary signed handover. That protects the article from converting a document fixture into a claim of operational transfer.

Test the failure path

Handover fails when access is granted after the final workshop, alerts still point to delivery engineers, or quality drift has no owner. Time-box transition support and define what falls under a defect, operational support or new scope.

Save evidence that another reviewer can inspect:

• service ownership matrix
• runbook and access verification
• receiver-led recovery exercise
• signed acceptance and transition-support boundary

This exercise aligns with the enterprise delivery, secure integration, operations and leadership work in the FDE for Professionals course. The course link describes the pathway; this local draft and its synthetic verifier do not claim that a client deployment, security approval or production result occurred.

Practice task

Ask the future operator to restore a synthetic failed job using only the handover pack. Record every question as a missing artifact or unclear owner.

Continue learning

This article is part of the Enterprise AI delivery and architecture sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Plan a controlled rollout across business units.
• Continue with Create an enterprise integration acceptance matrix.

Reference: GOV.UK Service Manual: operating a service.