Cutover Readiness Checklist (Go/No-Go)
In financial services, the cutover is a controlled risk event. This checklist defines objective gates, required evidence, and the accountable owner for each readiness area.
| Gate | Readiness criteria | Evidence required | Owner | Go/No-Go rule |
|---|---|---|---|---|
| G1 — Data integrity | Reconciliation within tolerance across all account types and ledgers | Signed reconciliation report + independent QA validation | Data Migration Lead | No-Go if tolerance breached or exceptions untriaged |
| G2 — Channel stability | Login, account view, and critical journeys stable under peak load | Performance test results + monitoring dashboards + error budget thresholds | Channels Lead | No-Go if critical journey fails or sustained error rate above threshold |
| G3 — Payments continuity | Payments scenarios validated end-to-end (incl. retries and exceptions) | Test evidence; reconciliation; contingency plan for failed processing | Payments Lead | No-Go if any critical payment scenario remains unproven |
| G4 — Monitoring & incident response | War-room staffed, runbooks validated, escalation paths clear | Incident drill outcome report + on-call rota + severity triage matrix | Ops Lead | No-Go if staffing gaps or runbooks unvalidated |
| G5 — Rollback safety | Rollback plan tested, timeboxed, and decision authority explicit | Rollback rehearsal report + decision log + “point of no return” definition | Programme Director | No-Go if rollback untested or authority unclear |
| G6 — Customer communications | Customer messaging, scripts, and fallback channels ready | Comms pack + branch scripts + contact centre FAQ + update cadence plan | Comms Lead | No-Go if customer comms is incomplete or unapproved |
“Ready” is not a milestone. It’s a body of evidence.
← Back to Pack overview