# Final Publish Readiness Check

Verify approvals, sources, assets, metadata, links, disclosures, accessibility, technical behavior, scheduling, monitoring, and ongoing ownership before release.

## Usage note

Run this check on the exact release candidate in its real publishing environment. It confirms that assigned reviews and operational controls are complete; it does not redo specialist work or turn unchecked boxes into approval. Stop release when a required owner, source, action, or rollback path is missing.

## How to use this template

1. Identify the exact approved release candidate, destination, accountable publisher, and release window.
2. Confirm editorial, factual, specialist, accessibility, legal, and other required approvals against that version.
3. Test content, metadata, assets, links, actions, language signals, and relevant states in the rendered environment.
4. Verify schedule, audience, monitoring, correction, rollback, maintenance, and retirement owners.
5. Record publish, hold, or cancel, then capture the live URL and complete immediate post-release checks.

## Blank template

### Release identity

- **Content title:** [Title]
- **Release candidate:** [Version or commit]
- **Destination:** [URL, channel, audience, or placement]
- **Scheduled time and zone:** [Date, time, zone]
- **Publisher:** [Name or role]
- **Accountable owner:** [Final decision role]
- **Rollback or hold owner:** [Role]

### Content and approval

- [ ] Purpose, audience, action, and scope match the approved brief.
- [ ] Material claims match current sources and final wording.
- [ ] Quotations, names, dates, numbers, and labels are verified.
- [ ] Required editorial and specialist approvals name this version.
- [ ] Disclosures, limitations, consent, and credits appear appropriately.
- [ ] No unnecessary personal, confidential, or restricted data is present.
- **Open exception:** [Approved record or None]

### Rendered and technical checks

- [ ] Title, description, canonical, language, and sharing metadata are correct.
- [ ] Heading order, keyboard operation, focus, labels, alternatives, and captions are checked.
- [ ] Links, downloads, forms, and primary actions work in relevant states.
- [ ] Images and assets are licensed, optimized, and display as intended.
- [ ] Dates, time zones, prices, availability, and dynamic details are current.
- [ ] Structured or machine-readable data matches visible content.
- **Preview evidence:** [Link, screenshot, or test record]

### Release and aftercare

- **Decision:** [Publish / Hold / Cancel]
- **Blocking issue:** [Owner and due date]
- **Live URL or message ID:** [Complete after release]
- **Immediate live check:** [Owner and time]
- **Monitoring signal:** [Specific feedback, error, or behavior]
- **Correction path:** [Who can edit, pause, or notify]
- **Maintenance owner:** [Role]
- **Review trigger:** [Date or source change]
- **Retirement condition:** [When it should leave service]