What should be reviewed?
A go/no-go decision determines whether an organisation should proceed into the new operating environment. It should be based on defined acceptance criteria, evidence, known risk and accountable authority, not treated as a ceremonial calendar meeting.
- Cutover plan and rehearsal readiness
- Critical defects and migration controls
- Infrastructure, integration and access readiness
- Business and operational readiness
- Support and hypercare readiness
- Contingency and rollback viability
- Outstanding decisions and accepted risks
Readiness gates
Define gates according to the organisation's risk, scope and governance model. A gate should state the criterion, required evidence, accountable owner, assessment time and consequence if unmet.
Do not adopt arbitrary universal thresholds or assume every amber condition is acceptable.
Evidence, not optimism
Use test results, reconciliations, approvals, rehearsal findings, operational acceptance and current risk information. A verbal assurance can provide context but should not replace evidence for a critical control.
Expose gaps directly so the decision authority can understand residual risk.
What does conditional go mean?
A conditional go can be legitimate when the remaining condition is bounded and controllable. Each condition needs an owner, deadline, acceptance criterion and stated consequence if it is not met.
It should not be used to re-label a blocking prerequisite or defer unclear risk beyond the decision meeting.
Who makes the decision?
The accountable authority depends on the programme governance model and impact. It may be a sponsor, steering body, business owner or delegated executive. Contributors advise and present evidence; authority to decide should be explicit before the meeting.
Where several approvals are required, document how they combine into the final release decision.
Go/no-go decision record
Record the outcome so teams know what was authorised and under which conditions.
| Field | Purpose |
|---|---|
| Date and time | Establish the decision point |
| Decision and authority | State outcome and accountable decision-maker |
| Readiness summary | Reference current evidence |
| Exceptions and accepted risks | Make residual exposure visible |
| Conditions | Define owner, deadline and consequence |
| Evidence references | Connect supporting records |
| Next checkpoint | State when the decision is reviewed |
Go/no-go anti-patterns
Avoid practices that create the appearance of governance without accountable control.
- Voting without defined authority
- Creating readiness evidence at the last minute
- Treating amber as automatically acceptable
- Hiding critical blockers in appendices
- Ignoring rollback or contingency
- Leaving the decision undocumented
- Confusing percentage complete with readiness
After GO
Move from planning assurance into operational execution. Confirm conditions, activate the command model, preserve the approved baseline and monitor the assumptions behind the decision.
After NO-GO
A no-go is a controlled risk decision, not automatically a programme failure. Stabilise the current state, communicate clearly, resolve blockers, update the plan and establish new readiness and decision points.
Preserve evidence and rationale so replanning begins from facts rather than blame.
Make readiness and decisions traceable
CutoverCenter connects readiness, governance and execution so go-live decisions can use structured programme evidence.