Daily article operations guide
Freeze the publish candidate at the end of the content VA shift
Give the reviewer one identifiable draft instead of a moving target assembled from late edits.
Where the work breaks
When copy, metadata, and assets change during review, two people can approve different versions while believing they checked the same page.
A routine the team can repeat
At cutoff, label one version the publish candidate. Record its identity, source packet, image, unresolved items, and reviewer. Later changes create a new candidate.
What to keep in the record
Use a version or commit reference the reviewer can recover. Keep the superseded candidate long enough to explain the difference.
Who decides
Freezing a candidate does not approve it. The publisher releases only the version accepted after all required gates pass.
Use this in the daily queue
Apply the check to one named article and keep the result with that article’s release record. A short, specific entry is more useful than a generic "done" status.
See the research library or plan a research support workflow.