No launches yet — .
No products yet
Create your first product, then add launches to it.
Every launch for this product. They can run at the same time at different stages and dates — and a later launch (say a discrete feature) can record that it follows on from an earlier one.
| Launch | Type | Follows on from | Target | Progress | Blockers | Status | |
|---|---|---|---|---|---|---|---|
| {{ l.name || 'Untitled launch' }} | {{ l.type }} | {{ l.predecessorId ? launchName(l.predecessorId) : '—' }} | {{ l.targetDate || '—' }} | {{ l.pct }}% | {{ l.blockers }} | {{ l.label }} |
No launches yet for this product. Create the first one.
Answer these once. They decide which readiness areas this launch must clear — and which it may skip. Each answer is explained; hover the ⓘ for the detail behind it.
{{ q.group }}
{{ g.intent }}
Nothing matches “{{ gateFilter }}” in {{ g.name }}. .
{{ g.code }} · {{ g.name }} — sign-off
{{ excludedSections(g).length }} section(s) not applicable to this launch (by qualifiers)
Readiness at a glance. A launch is ready for the go/no-go when every area is clear of outstanding blockers.
Open blockers
{{ openBlockers.length }}The blocking items still holding this launch — click any to jump straight to it.
No open blockers
0Every applicable blocking item is passed or declared N/A. Sign off each area below to complete the go / no-go.
Readiness by area
Overall readiness
All applicable blockers are cleared. This launch can proceed to a formal go/no-go decision.
{{ totalBlockers }} blocker(s) remain across the areas. Resolve or formally except them before launch.
Where you choose to launch with a known gap, record it here — with an owner, an expiry, and a remediation plan. An exception is a decision, not an oversight.
No exceptions logged.
No product yet
Create a product first, then add launches to it.