# Launch readiness checklist · [Launch name] · Stage: [ ] · [Date] Status: Green = ready · Amber = at risk, with a plan and date · Red = not ready Definitions of ready are agreed by [date], before work is graded against them. | Function | Owner | Ready means | Evidence link | Status | Note | |---|---|---|---|---|---| | Product | | Scope frozen for this stage; metrics and baselines set; customer FAQ approved | | | | | Engineering | | Rollout plan, flags and kill switch; capacity tested against the marketing plan; rollback rehearsed | | | | | Documentation | | Docs for every supported platform at this stage; release notes drafted; limitations stated | | | | | Support | | Runbooks and macros; staff trained; launch ticket tag live; escalation path | | | | | Sales | | Enablement complete; talk track states the stage; quoting works | | | | | Legal | | Terms match the stage label; claims substantiated; AI disclosure reviewed | | | | | Billing | | SKUs and meters live; test invoice correct; dispute path defined | | | | | Security | | Review passed; audit logging and access controls verified; security docs ready | | | | | Marketing | | Artifacts approved; channels and timeline set; spokespeople and references confirmed | | | | | Behavior review (AI) | | Named reviewer has used the feature on real tasks and signs off on behavior | | | | ## Capacity inputs from marketing Announcement channels and expected traffic: [ ]. Event demo load: [ ]. Confirmed with engineering on [date].