A launch checklist gathers, by area, everything that must be ready to put a product or feature in customers’ hands: tests, support, communication, legal matters, metrics and a rollback plan. Each item has an owning role and a deadline relative to the date. Go/no-go criteria turn the checklist into an explicit decision, taken the day before with the owners of each area.
How to use
- Say what is launching and choose the type: major, minor or beta.
- Tick the areas involved: each one gets items with a deadline and an owning role.
- Mark what is already done and see how many go criteria are still missing.
- Enter the metric to watch and the rollback trigger to complete the launch day timeline.
- Export as Markdown or CSV to track it in your task manager.
What each field asks for
| Field | What to enter |
|---|---|
| What is launching | Product, version or feature. |
| Launch type | Sets how strict the checklist is and the release on the day. |
| Planned date | Optional. Deadlines count back from it (D-5 = five days before). |
| Areas involved | Each area gets items and an owning role. |
| Items already done | Mark what is complete; the rest stays pending. |
| Metric to watch | The number that shows whether the launch worked. |
| Rollback trigger | The condition that makes you roll back, agreed beforehand. |
Example
A fictional booking app for hair salons prepares a major launch for 12 November, with all eight areas involved. Of 24 items, 10 are done, but only 2 of the 9 go criteria are met: the rollback still needs rehearsing and support still needs training, for example. On the day, the release starts with 10% of the audience, widens to 50% two hours later if the indicators are stable, and the rollback decision follows the agreed trigger: error rate above 2% for 15 minutes.
When to use
- A few weeks before a launch, to spread the work across areas with deadlines.
- In the go/no-go meeting, to decide on criteria rather than gut feeling.
- Before opening a beta, so you do not forget the support channel and participant feedback.
- After a difficult launch, to turn what was missing into a checklist for next time.
Frequently asked questions
What should a launch checklist include?
Items by area (product, engineering, support, marketing, sales, legal, data and rollback), each with an owning role and a deadline. Without an owner and a deadline, an item is just a wish.
What is a go/no-go meeting?
It is the meeting, usually the day before, where the owners of each area confirm whether the agreed criteria are met. The decision to launch or postpone is recorded, with the reasons.
Why are owners shown as roles and not names?
Because the checklist must work for any launch and any team. When you use the result, each role gets the name of the person who will look after that item in your organisation.
What is the difference between a major, minor and beta launch?
A major launch changes a lot for many customers and calls for gradual release, a rehearsed rollback and legal review. A minor one calls for regression tests and an in-product notice. A beta goes to a limited group and needs a support and feedback channel.
Do I really need a rollback plan?
For a major launch, yes. Agreeing beforehand which number triggers a rollback, and rehearsing it, stops the decision being made in the middle of the problem, under pressure.
How do I follow up after launch day?
Compare the chosen metric with the baseline a week later and record what you learnt. The tool’s timeline already sets that review for day seven.