Prepare a launch-readiness review packet

A readiness packet should expose missing approvals and evidence. It should not declare readiness just because every checklist row has a confident sentence.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: Launch checklist, test results and named approval records.

Work through the task

1. Map each requirement to evidence.
2. Keep missing evidence and unresolved risks separate.

A brief you can adapt

Create readiness.md with requirement, evidence location, status and owner when supplied. Use Not verified for checks without evidence.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Open the evidence for the most consequential checks and verify it covers the intended release.

Where this approach can fail

An AI-generated readiness report is not release authorization.

For the related desktop setup, see review results.