Testing exit criteria
- All critical and high defects closed or accepted with workaround
- SIT and UAT pass rate at or above agreed threshold
- Regression pack passed on the final transport set
- Performance tests at peak volume passed
- Security and role testing complete, SoD conflicts mitigated
Data readiness
- Two successful mock loads with reconciled counts and values
- Data owners signed off each migration object
- Opening balances agreed by Finance
- Data cleansing backlog below threshold
Cutover readiness
- Runbook frozen with owners and backups
- Final mock cutover within planned window
- Rollback plan rehearsed
- Go/No-Go criteria approved by steering committee
People and support
- End-user training completion above 90%
- Super-users and floor-walkers rostered
- Hypercare team and escalation matrix live
- Business contingency procedures signed off
Executive sign-off
Bring the evidence to one Go/No-Go meeting. A go-live scorecard that rolls these checks into one readiness score makes the decision fast and defensible.
Frequently asked questions
When should we run the go-live readiness assessment?
Start at T-6 weeks, repeat weekly, and hold the final assessment at the T-72h checkpoint.
What readiness score is safe to go live?
Most programmes require every critical criterion to be met and an overall score above 85%. Any open critical item should trigger a No-Go.