Assume the launch story will change
Pricing, availability, timing, comparisons: something will move while 100 articles are in motion. Plan for it. Version the brief from day one and tag every article with the version it used. Then any update has one defined blast radius.
Route the fix straight to the affected pages
One changed claim produces one list: every draft, review, and live page that contains it. No all-hands email asking people to search their inboxes. Unreleased work pauses instantly; anything already public gets a logged follow-up.
The fix belongs in the campaign receipt
Your campaign receipt keeps the full trail: what changed, which URLs it touched, what was requested, and what each follow-up check found. One document holds the launch and its corrections, so trust survives the change instead of breaking on it.