Create a controlled inventory before replacing assets
List every place customers and partners encounter the current identity. Include high-visibility digital routes, routine operational messages and assets managed by suppliers. Record the owner, platform, login or supplier dependency, replacement file, review status and planned change date.
Mark each item as launch-critical, replace soon, replace when current stock ends, or retire. That prevents a launch plan from treating a printed item, a customer portal and a social avatar as if they have the same cost or operational risk.
Fictional example: a two-location heating firm changes its trading name and website. One launch-critical tracker row could read: item, main boiler-service page; owner, web lead; dependency, confirmed service wording and logo; URL mapping, `/boilers` to the matching new boiler-service page; checks, the old address redirects to that relevant page and the enquiry form and confirmation work on phone and desktop; detail, checked URLs and a saved screenshot; status, verified. The row shows what completion means without treating every asset as an equal launch risk.
- Website, redirects, metadata and forms
- Domain, email and account profiles
- Proposal, invoice and presentation templates
- Product interface, help centre and transactional messages
- Partner, directory and supplier assets
Prepare a complete and licensed asset package
Store confirmed logo variants, colour and type specifications, image files, templates and usage notes in one controlled location. Identify the file for each use, such as a small digital mark, a print-ready logo or an editable presentation asset. Keep source files and export files clearly labelled.
For third-party images and other creative files, record the licence and the uses it permits. For commissioned work, record whether copyright was assigned or what licence the contract grants; commissioning a work does not by itself establish copyright ownership. The person updating a channel should not have to infer which file is confirmed or whether a supplier may adapt it.
Sequence the digital work around customer journeys
Update the routes that explain the offer and accept enquiries before lower-priority decorative placements. For a website, check the page title, logo, navigation, service content, contact details, forms, confirmation messages, favicon and social-sharing image. Where a URL changes, map the old address to its relevant new destination, plan the redirect and update internal links before launch. Avoid sending unrelated old pages to one generic destination.
Test the complete journey on a phone and desktop: arrive from a search result, understand the offer, submit a form, receive the expected confirmation and reach the right next step. A visually consistent header does not prove the underlying enquiry path still works.
Give each change one accountable owner
Assign a person to approve identity files, one to coordinate channel updates and one to verify each critical journey. Use a shared tracker with dependencies and detail of completion, such as a checked URL or an confirmed screenshot. Keep supplier and stakeholder approvals visible before the launch date is fixed.
Prepare the announcement only after the service wording, contact details and support answers are ready. If customers may ask whether contracts, invoices or support channels have changed, write an accurate answer for the team before the public post goes live.
Run a short post-launch reconciliation
After launch, revisit the inventory and check that the live website, social profiles, email templates and key documents show the confirmed version. Search the site for the old name and review redirected routes. Record unresolved items with owners and dates instead of assuming that a deployment updated every external platform.
Keep the prior assets and change record according to the business's retention needs. The record helps the team distinguish an intentional transition from an overlooked inconsistency and gives future contributors a plain source of truth.