# What must be checked before a release?

FICTIONAL TEACHING EXAMPLE — not an approved deployment procedure or a test result.

- Document ID: DOC-OPS-01
- Purpose: Prepare a release-readiness record for an approval decision. This does not authorize deployment.
- Audience: Release engineers
- Owner: Release lead (fictional role; no person assigned)
- Reviewer: Operations reviewer (fictional role)
- Access scope: Internal team
- Status: Revise / awaiting walkthrough
- Last verified: Not yet verified
- Review trigger: Deployment process changes

## Prerequisites

A proposed release record, the team's agreed verification checklist, and an approved rollback reference. These example references must be replaced with actual approved records before use.

## Steps

1. Identify the proposed version in the release record.
2. Attach existing verification evidence; do not create a pass result from an unchecked item.
3. Confirm the role authorized to approve the release.
4. Identify the rollback owner and approved reference. Stop if either is missing.
5. Record unresolved questions and their responsible roles.
6. Submit the readiness record to the designated approver. Record the actual decision when it occurs.

## Completion check

A complete readiness record and a recorded approval decision. This is not evidence that deployment succeeded.

## Current open issue

The rollback owner is missing. The teaching example remains awaiting clarification; no approval or walkthrough result has been invented.

## Related record

DOC-OPS-OLD is the superseded checklist. Retain it according to the organization's policy and point readers to DOC-OPS-01.
