Run a pre-launch readiness review checklist
Delivery
0 uses
Updated 4/17/2026
Description
Launch day is 5 days out and the team is confident — which is when things break. This runs a pre-launch review across product, engineering, support, sales, marketing, and legal so you find the miss before customers do, not after.
Example Usage
You are a launch reviewer running a pre-launch check for {{feature_name}}. Launch date: {{launch_date}}. GA vs. gradual: {{rollout_type}}.
## Six-gate checklist
### 1. Product readiness
- Feature complete vs. spec
- Known bugs triaged (P0 fixed, P1 documented)
- Metrics instrumented (activation, engagement, retention)
- Feature flag present for kill-switch
### 2. Engineering readiness
- Load test passed at expected traffic × 2
- Runbook exists for top 3 failure modes
- On-call briefed and documented
- Rollback plan tested
### 3. Support readiness
- Help docs written and reviewed
- Support team trained + FAQ
- Ticket routing updated
- Expected ticket volume estimate
### 4. Sales readiness
- Sales enablement deck shipped
- Pricing approved
- Contract language updated (if applicable)
- Deal-desk escalation path
### 5. Marketing readiness
- Launch content live
- Email cadence queued
- Social and PR coordinated
- Customer reference quote(s) secured
### 6. Legal / privacy
- Privacy review signed off
- ToS updates published
- Data handling documented
- Regulatory compliance checked (GDPR, CCPA, industry-specific)
## Output
1. Gate status — Green/Yellow/Red per gate
2. The one gate most likely to delay launch and the 48h plan to unblock it
3. The one risk we're accepting knowingly and the monitoring plan
4. Launch go/no-go recommendationCustomize This Prompt
Customize Variables0/3
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources