Before the window opens
A production cutover should start only when the approved release, plan, people, evidence requirements and decision model are aligned.
- Approved plan version and release identity are locked
- Critical owners, validators and approvers are available
- Dependencies and environment eligibility are confirmed
- Rollback triggers and authority are unambiguous
- Command-centre communications are active
During execution
Run from current operational state, not from static status reports. Exceptions should identify impact, owner, decision deadline and escalation route.
- Actual start and finish are captured
- Automated outcomes are verified at the provider
- Blocked work prevents dependent execution
- Forecast impact is visible
- Gate decisions preserve rationale and evidence
After deployment
Completion requires technical validation, business confirmation, reconciliation, operational handover and a preserved record. A successful deployment workflow alone is not go-live completion.
Questions transformation teams ask
Who should approve a production go-live?
The organisation should name an authorised decision-maker or decision group. The accountable authority should be recorded separately from task execution.
When should rollback be triggered?
Triggers should be defined before execution using measurable technical, business and timing thresholds, with a named authority and latest viable decision time.