Release go/no-go checklist: 24 checks before you deploy
Most failed releases don't fail because of one big mistake. They fail because several small things were assumed: someone thought testing was finished, nobody checked the rollback, support wasn't told. A go/no-go checklist turns those assumptions into a short, honest conversation before you deploy.
Below are 24 checks across 8 areas, the decision rules that keep the meeting short, and an agenda you can use next week.
The 24 checks
1. Scope and change
- Release scope is frozen and matches the approved list.
- Every change has an approved change request.
- Late changes after code freeze have been reviewed and approved.
2. Testing and quality
- Regression testing is complete with no open critical or high defects.
- User acceptance testing (UAT) is signed off.
- Performance testing is complete wherever load or data volumes change.
- Known issues are documented with workarounds.
3. Deployment readiness
- The deployment runbook is written and peer-reviewed.
- The deployment has been rehearsed in a production-like environment.
- The deployment window is agreed and people are rostered.
- Database and configuration changes are scripted and reviewed.
4. Rollback
- A rollback plan exists with clear trigger criteria.
- Rollback has been tested, or proven in a previous release.
- Backups are taken and a restore has been verified.
5. Operations and support
- Monitoring and alerts cover the new features.
- The support team is briefed with release notes and FAQs.
- The hypercare roster and escalation path are confirmed.
6. Communications
- Customer release notes are approved.
- Customers are told about any downtime or visible change.
- Internal stakeholders know the release time and impact.
7. Security and compliance
- A security review or scan is complete with no high findings.
- Access, data and privacy changes have been reviewed.
8. Business sign-off
- The business owner approves the release timing.
- Dependencies on other teams or vendors are confirmed.
Mark the critical checks
Not every check is equal. Mark the ones that must be ready, no exceptions. A sensible starting set: regression testing, UAT sign-off, the deployment runbook, the rollback plan, backups, support briefing, customer notification and the security review. Keep the list short. If everything is critical, nothing is.
Four decision rules
| If… | Then |
|---|---|
| Any critical check is Not ready | NO-GO |
| Any check has no status yet | INCOMPLETE: finish the checks before deciding |
| Only non-critical checks are Not ready | GO WITH CONDITIONS: write down each condition, owner and deadline |
| Everything is Ready or N/A | GO |
Agreeing these rules in advance is the point. On release day, under pressure, people argue. With the rules agreed, the checklist decides and the meeting just confirms.
A 30-minute go/no-go meeting
Hold it one to two working days before release, so there is time to fix gaps.
- 5 minutes: confirm scope and any late changes.
- 10 minutes: walk through every check that is Not ready or pending.
- 5 minutes: confirm the rollback plan, its triggers and who decides.
- 5 minutes: confirm support, hypercare and customer communications.
- 5 minutes: make and record the decision.
Common mistakes
- No single decision owner. A group never quite decides. Name one person.
- Checking boxes without evidence. Ask for a link to the test results, not just a "yes".
- Changing the checklist every release. Run it as-is for three releases, then improve it.
Get the Release Go/No-Go Kit
A ready-to-use checklist with an automatic GO / NO-GO decision, a release calendar, rollback plan, change request form and release notes template. Word and Excel.