Stakeholder Launch Approval Checklist
Collect the right sign-offs.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a launch approval checklist. Product and risk level: [PRODUCT_AND_RISK]. Approving functions: [FUNCTIONS]. Regulatory context: [REGULATORY_CONTEXT]. Produce a checklist table: Area | Question | Evidence required | Approver | Status | Date. Cover product quality, security review, privacy and data protection, legal (terms, claims, intellectual property), accessibility, finance (pricing, billing), support readiness, operations (monitoring, capacity), and marketing (claims substantiated). Mark legal and regulatory items as [VERIFY] with the responsible specialist. Add rules: no verbal approvals, define who can waive an item, record conditions, and escalate disagreements. Include a one-page summary for the final go/no-go meeting. Present the checklist as a table with columns for area, question, evidence, approver, status, and conditions, and add a summary line that counts approved, conditional, and outstanding items so the final meeting can focus on the gaps. Where an approver gives a conditional yes, record the condition, the owner, and the date it must be satisfied. Define which items are blockers (security, legal) and which can be accepted as known risks, and who may accept them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.