Handover RACI template
Use this template when you need to broadcast handover roles without exposing internal specifics. Copy the RACI template or Browse the runbooks index. The structure below stays inside the Anti-drift Content Governance guardrails and keeps RACI labels uncluttered.
How to use it
- Duplicate the template table into your handover document.
- Replace the placeholder rows with the concrete activities in scope.
- Stick to role names or generic titles (for example, "On-call engineer") rather than personal identifiers.
- Link to the supporting Runbooks index if you need step-by-step execution support.
- Pair each owner with the transition operating promises so SLA and backup coverage stays visible.
Template
Tip: keep one row per decision or activity so the RACI stays readable.
| Activity / Decision | Responsible (R) | Accountable (A) | Consulted (C) | Informed (I) | Notes |
|---|---|---|---|---|---|
| Publish daily status update | Delivery lead | Product sponsor | Facilitator | Partner teams | Async in #handover-status at 5pm |
| Merge final PR to enable feature | Engineering lead | Tech lead | QA lead | Support team | Attach receipts + rollback plan |
| Approve scope change >10% | Product sponsor | Steering committee | Finance partner | Transition distro | Requires updated SLI + timeline |
Related references
- 20-minute handover drill — Use this before or after the RACI to lock scope.
- Transition operating promises — Pair each RACI line with an explicit SLA or escalation.
- SLI states map — Keep the official state tracker aligned with your RACI owners.