- 0:00–0:06
Choose one version • Give all application owners the same approved reference. • V1 · approved identity reference • Website owner · V1 • Campaign owner · V1 • Document owner · V1 • Late change? Reopen every affected check
One illustrative approved identity reference, V1, branches to the website, campaign and document owners. All use the same version. A late change reopens every affected application check; distributing the reference does not mean those applications already pass.
- 0:06–0:12
Walk the customer task • Include messages, downloads and saved templates. • Campaign • Website + enquiry form • Confirmation + next link • Also inspect saved proposals, downloads and signatures • Hypothetical visual refresh: name, domain, prices and URLs stay
The inventory follows campaign to website and enquiry form, then confirmation and the next link. Saved proposals, downloads and signatures are also inspected. This hypothetical visual refresh retains the name, domain, prices and public URLs; naming and URL migration are separate decisions.
- 0:12–0:18
Follow dependencies • A campaign needs its checked destination. • Approved copy + usable fonts • Destination • Destination evidence required • Campaign release depends on this check • Release dependency, not a traffic direction
Approved copy and usable fonts feed the reviewed destination illustration. The destination evidence requirement appears before the conditional campaign-release dependency. This arrow describes release order, not customer traffic. No passing test or completed release is asserted.
- 0:18–0:24
Hold a broken release • Visual approval does not resolve a wrong-language link. • Approved artwork • Wrong language • Hold • Arabic campaign link opens English page • Correct link + recheck; release still pending
In the article’s hypothetical launch, approved artwork has an Arabic campaign link that opens the English page. The wrong-language finding leads to a closed hold gate. Correcting the link leads to another check, not an automatic release; the release remains pending on evidence.
- 0:24–0:30
Check after publication • Repeat the task and find remaining old assets. • After publication: repeat enquiry + destination task • Superseded download • Labelled archive • Defect location + owner + remaining exceptions • Procedure illustration; no launch or sales lift is claimed
An explicitly instructional post-publication sequence repeats the enquiry and destination task. A superseded download moves out of the normal working area to a labelled archive, while the record names defect location, owner and remaining exceptions. No actual launch or sales improvement is claimed; before-and-after differences do not prove rebrand causation.
A silent 30-second explanation in five six-second beats. A versioned identity feeds linked campaign, website and confirmation changes that need release checks.
Read the article: Rebranding Rollout Plan: Coordinate Your Website and Campaigns