A structured field assessment for high-stakes launches. Score each item, capture evidence, and confirm blockers are cleared before go-live.
PurposeConfirm launch blockers are cleared with evidence — docs, tests, metrics, or named owners.
Score: 0 = Not Ready · 1 = Partial · 2 = Ready
| Check | Score | Owner / Notes |
|---|---|---|
| All critical user paths tested end-to-endRequired | ||
| Error messages reviewed for clarity | ||
| Load tested at expected launch traffic volumeRequired | ||
| Rollback plan documented and tested |
| Check | Score | Owner / Notes |
|---|---|---|
| Help docs published before launch dateRequired | ||
| In-product copy reviewed for accuracy | ||
| Pricing and plan details confirmed liveRequired | ||
| Legal and compliance notices in placeLegal |
| Check | Score | Owner / Notes |
|---|---|---|
| On-call rotation set for launch weekRequired | ||
| Monitoring alerts configured and tested | ||
| Support team briefed on launch features | ||
| Customer feedback channel ready to receive |
| Check | Score | Owner / Notes |
|---|---|---|
| Launch announcement drafted and approved | ||
| Sales team knows what changed and when | ||
| Success metrics defined and tracked from day oneRequired |
Thresholds: 85–100 = Launch-ready · 70–84 = Conditional Go · <70 = No-go recommended. Any required critical item scored 0 keeps status at No-go.
Critical points: