# Release-readiness checklist

A practical starting point from Benchform. Adapt this checklist to your product,
organization, and required acceptance criteria. It does not establish certification
or approval for official quality use.

Guide: https://benchform.app/resources/release-readiness-checklist/

## Release scope

- Product/configuration:
- Release identifier:
- Baseline identifier and revision:
- Technical reviewer:
- Quality reviewer:
- Review date:

## Review checks

- [ ] Scope is defined: identify the included product configuration and record revisions.
- [ ] Requirements are reviewed: inspect applicable requirements, ownership, and approval history.
- [ ] Risk decisions are current: inspect assessments, controls, and required human decisions.
- [ ] Traceability is current: inspect missing links, changed endpoints, and retired records.
- [ ] Verification is applicable: inspect approved protocols, exact revisions, results, and evidence.
- [ ] Failures are resolved: inspect failed/inconclusive runs, linked retests, and dispositions.
- [ ] Quality work is addressed: inspect open findings, CAPAs, changes, and required follow-ups.
- [ ] Documents and training are ready: inspect approved document revisions and required completion.
- [ ] Release decisions are recorded: retain named technical and quality decisions.
- [ ] The package is inspectable: include documents, evidence, a manifest, and checksums.

## Open findings

| Record and revision | Condition | Owner | Required action/evidence | Disposition |
| --- | --- | --- | --- | --- |
| | | | | |

## Release decision

- Decision:
- Supporting record references:
- Remaining conditions, if applicable:
- Sign-off recorded in:
- Frozen package location and digest:

Keep the approved baseline and evidence intact after the next development revision.