You decide whether a proposed configuration is ready to become live. Publication changes what the station uses for subsequent work. A draft preview or the Author's statement that the tests passed is not the publication decision.
Before opening a candidate
Get the requirement, change note and candidate reference from the Author. Confirm which station and workflow it affects. Sign in with Reviewer and two-factor authentication. Ask the Owner whether the site requires a second approver or a separate confirmation for every publication.
Review the frozen work
- Open the candidate and read Frozen review. Confirm that the draft, revision and change note are the work you intend to review.
- Inspect the frozen content offered for that candidate: layout, rules, data mapping or form, as applicable.
- Read the independent reference expectations. They should describe intended business behaviour, including cases that must be refused.
- Verify every required reference case. Inspect the resulting label proofs and refusals, rather than relying only on a passed count.
- Resolve any discrepancy with the Author. If the proposal changes, review the new saved and frozen candidate; do not approve an explanation that is absent from the frozen work.
See examples and releases for a detailed review checklist.
Publish deliberately
Check the station, current qualification and any outstanding uncertainty. Complete the proof-review acknowledgements and review note. Confirm your identity when asked, then use the publication action.
When the site requires a second approver, the approval must belong to the exact candidate and verification, and publication uses the required different reviewer. If the page says an approval is missing or stale, obtain a fresh valid approval.
After publishing, read the receipt and confirm the intended release is active. Publication takes effect immediately; agree the timing with the Supervisor before performing it.
If you need to reverse a change
A rollback is a reviewed activation of a retained release, with current checks. Use rollback, inspect its proofs and exclusions and record the reason. Do not assume that older automatically means safe for current work.
A rollback does not recall printed labels or rewrite accepted-run history. Coordinate any affected production work with the Supervisor.
When publication is refused
Read the reason. Common categories include permission or recent-authentication requirements, failed verification, changed candidate evidence, missing printer qualification and uncertain output. Resolve the specific cause and review the current state before trying again.