What is a launch tier?

Silent ships with no announcement, Limited goes to a subset or beta, GA is announced to everyone

Do I need every section?

Delete what truly does not apply, but write why so reviewers know it was considered

When is the go or no-go call?

One or two days before launch, by the DRI, using the timeline below

Templates · Product

Launch checklist template

Everything to ship a feature: eng, docs, support, marketing

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

A feature has a launch date and several teams (eng, support, marketing, sales) must be ready on the same day

Who it's for

Product managerManager

Part of a kit

Product launch, step 4 of 6. From brief and PRD through experiment, launch checklist, release notes and the customer newsletter.

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Launch checklist: Shared calendars

Author: Hannah Cole · Date: 2026-09-28


Feature	Shared team calendars in Northwind Planner
Launch date	2026-10-20
Launch tier	GA
DRI	Hannah Cole

Timeline

Mermaid diagram (drawn as a picture in reph)

gantt
    title Shared calendars launch
    dateFormat  YYYY-MM-DD
    section Build
    Code complete      :a1, 2026-09-29, 10d
    QA on staging      :a2, after a1, 5d
    section Ready
    Docs and support briefing :b1, after a1, 7d
    Go or no-go call   :milestone, m1, 2026-10-16, 0d
    section Launch
    Launch day         :milestone, m2, 2026-10-20, 0d
    Metrics review     :c1, after m2, 7d

Engineering

Feature flag shared_calendars created and defaulted off
Rollback plan documented and tested (flag off hides shared views, data kept)
Monitoring wired: sync lag and invite error rate on the Calendars dashboard
Load tested at 3x expected traffic (scheduled 2026-10-13, owner: Sam Ortiz)

QA

Test plan executed on staging
Cross-browser and iOS/Android pass (in progress, 2 open bugs)
Regression suite green

Security & legal

Security review completed (new sharing surface, ticket SEC-882)
Privacy review: shared calendars expose event titles only to invited members
DPA wording updated for calendar data sharing (legal, due 2026-10-14)

Docs

Help center article drafted
Public changelog entry written
Internal runbook updated with sync failure steps

Support readiness

Support team briefed (session booked 2026-10-15)
Escalation path: Calendars on-call channel during launch week

Marketing & comms

Launch blog post drafted
In-app announcement configured for all workspaces
Email to admins scheduled for launch morning

Sales enablement

Talk track updated: shared calendars included on every paid plan
No pricing change, confirmed with finance

Post-launch

Metrics review booked for 2026-10-27
Retro booked for 2026-11-03

Go or no-go

Function	Owner	Ready?
Engineering	Sam Ortiz	Yes, pending load test
Support	Leila Haddad	After 10-15 briefing
Marketing	Chris Nakamura	Yes

Decision: Go, conditional on the load test passing · Decided by: Hannah Cole · Date: 2026-10-16

The template

Show the blank template

Launch checklist

Author: [your name] · Date: [date]


Feature
Launch date
Launch tier	Silent / Limited / GA
DRI	[your name]

Timeline

The few dates every team plans against. Adjust durations to your launch tier.

Mermaid diagram (drawn as a picture in reph)

gantt
    title Launch timeline
    dateFormat  YYYY-MM-DD
    section Build
    Code complete      :a1, 2026-01-01, 10d
    QA on staging      :a2, after a1, 5d
    section Ready
    Docs and support briefing :b1, after a1, 7d
    Go or no-go call   :milestone, m1, after a2, 0d
    section Launch
    Launch day         :milestone, m2, after m1, 0d
    Metrics review     :c1, after m2, 7d

Engineering

Everything that has to be true in the code and infra before this ships.

Feature flag created and defaulted off
Rollback plan documented and tested
Monitoring/alerts wired for the new path
Load/perf tested at expected traffic

QA

Verification a build did what it was supposed to, not just that it compiled.

Test plan executed on staging
Cross-browser / cross-device pass (if user-facing)
Regression suite green

Security & legal

Anything that touches new data, a new surface area, or a contractual obligation needs sign-off here before launch, not after an incident.

Security review completed (if new data or surface area)
Privacy/ToS/DPA implications reviewed
Data retention/deletion path confirmed

Docs

What a customer or API consumer needs to read to use this without filing a support ticket.

Help center article published
API/changelog entry written (if applicable)
Internal runbook updated

Support readiness

Support shouldn't learn about the feature from the first ticket about it.

Support team briefed with FAQ / known issues
Escalation path defined for launch-week issues

Marketing & comms

How customers and prospects find out this exists, sequenced against the launch tier above.

Launch post / email drafted
In-app announcement or changelog entry
Social/blog scheduled

Sales enablement

What sales needs to know or say differently starting launch day. Silence here means reps improvise.

Sales deck / talk track updated
Pricing/packaging implications communicated

Post-launch

The follow-through that turns a launch into a learning instead of a one-time event.

Metrics review scheduled (T+1 week)
Retro scheduled (T+2 weeks)

Go or no-go

Who signs off, and the call they made. A no-go needs a new date and a reason.

Function	Owner	Ready?
Engineering
Support
Marketing

Decision: Go / No-go · Decided by: · Date:

Questions

What is a launch tier?: Silent ships with no announcement, Limited goes to a subset or beta, GA is announced to everyone
Do I need every section?: Delete what truly does not apply, but write why so reviewers know it was considered
When is the go or no-go call?: One or two days before launch, by the DRI, using the timeline below

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Launch checklist" with search_docs, then read it with read_doc. Fill the header and tick or annotate each item from the linked PRD, release ticket board, help center drafts and marketing calendar, with owner and evidence (link or ticket) for every ticked item. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (unticked items blocking the date, unknown owners) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Start with this template →Sign in

Launch checklist template

Use it when

Who it's for

Part of a kit

Filled example

Launch checklist: Shared calendars

Timeline

Engineering

QA

Security & legal

Docs

Support readiness

Marketing & comms

Sales enablement

Post-launch

Go or no-go

The template

Launch checklist

Timeline

Engineering

QA

Security & legal

Docs

Support readiness

Marketing & comms

Sales enablement

Post-launch

Go or no-go

Questions

Fill it with your agent

Related templates

Feature brief

PRD / requirements doc

Experiment (A/B) plan

Release notes

Customer product newsletter

Analytics request