Brand rollout: planning the change beyond launch day

The new identity has been approved. There is a launch date, a presentation everyone likes and a folder of artwork ready to go.

There is also a warehouse of packaging, a website connected to several systems and a supplier who needs six weeks to replace the signage. Someone in sales is still using the presentation from two rebrands ago.

I see rollout as part of the branding work itself. It is where the proposed identity meets the people, systems and materials expected to carry it.

Planning that transition early gives the business a chance to resolve dependencies before they become expensive surprises.

Establish what is changing

An updated visual identity has different implications from a new name, a merger or a change in the service itself.

List the agreed changes and their consequences. A typeface may require licences and document updates. A name may affect domains, email addresses, contracts and customer recognition. A new promise may require changes to how teams deliver the service.

The rebranding process should establish the reasons for the change. The rollout plan turns those decisions into work someone can own, cost and schedule.

Where legal, regulatory or contractual changes are involved, assign those checks to the appropriate people. Artwork approval does not resolve them.

Find out where the existing brand lives

I’d start with an inventory, including the ordinary materials that rarely appear in a launch presentation.

• Websites, apps, emails, social accounts and business listings.
• Proposals, presentations, forms and internal documents.
• Packaging, uniforms, signage, vehicles and physical spaces.
• Advertising, partner materials and supplier-held files.

Record each item’s owner, replacement cost, production lead time and dependencies. Include quantities where existing stock needs managing.

Ask teams to contribute examples from their actual work. The central asset folder may be immaculate while everyone is using something else.

Decide what needs to change first

Some touchpoints need to change together. Others can wait until the next sensible replacement cycle.

Prioritise according to customer importance, visibility, operational risk and timing. A payment confirmation carrying an unfamiliar name may create more confusion than an old notebook in a meeting room.

I’d separate the work into three groups:

• Required for launch: applications customers and teams need to understand and use the changed brand, such as core website pages, customer communications and sales tools.
• Planned transition: items that can change during an agreed period, including packaging stock, branch signage and partner materials.
• Replace when needed: materials that create little confusion if retained temporarily, such as low-visibility internal stock and non-essential print.

These categories need judgement. Existing packaging may be acceptable during a visual refresh and inappropriate after a significant product change.

Record the reasoning behind exceptions. Otherwise, a temporary decision can quietly become permanent.

Choose a realistic launch approach

A coordinated switch makes sense when several things need to change together for customers to recognise continuity. A new name, for example, needs alignment across communications and the places people encounter it.

A phased rollout may suit multiple locations, large inventories or long supplier cycles. The business can also combine approaches, coordinating key digital and customer communications while replacing physical materials in stages.

Agree the transition period and any temporary explanations connecting old and new identities. Give those messages an expiry date.

An optimistic launch date becomes expensive when every dependency is treated as someone else’s problem.

Give each deliverable an owner

For each application, identify who is responsible, what they need, when it must be ready and how completion will be checked.

For a website, that might mean a digital lead coordinating approved content, assets and development, then checking key journeys on mobile and desktop. For packaging, an operations lead may need to review existing stock, secure a printer’s production slot and approve a physical proof.

The same principle applies to sales materials, partner listings and signage: give someone responsibility for the finished application, including the steps beyond producing the artwork.

I’d keep the working plan straightforward, with an owner, deadline, budget, dependencies and status for each deliverable. Include testing and installation time. A file being delivered does not mean the application is finished.

Prepare people to use it

People need to understand what changed and what they should do differently.

Customer service needs an explanation for callers. Sales needs usable proposals. Procurement needs specifications. Leadership needs enough understanding to make decisions consistent with the direction.

I’d test the materials with those teams before the announcement. Ask someone to prepare a presentation, update a page or brief a supplier. Watch where they hesitate.

Useful brand guidelines should support those tasks with relevant examples. File access, font licences and template compatibility deserve attention too.

Manage the overlap

Decide what happens to existing stock before ordering replacements. Can it be used up, adapted or withdrawn? Who approves that decision?

Archive superseded assets and remove outdated templates from the places teams normally use. Confirm that suppliers have received the replacements and understand when to start using them.

During a phased transition, make the acceptable exceptions clear. People should not have to guess whether an old application has been approved or overlooked.

Give partners specific instructions: what to replace, where to find the files and when the change should be complete.

Check the experience

Follow representative customer journeys through the updated materials. Submit an enquiry, request a quote and read the confirmation messages.

Check names, contact details, language versions and visual assets across those steps. Look for broken links, missing fonts and documents that fail in everyday software.

If a domain is changing, assign the migration its own technical plan. Redirects, email continuity, analytics and search visibility require appropriate expertise and verification.

Keep responsibility after launch

Schedule reviews that suit the scale of the transition. Early checks can catch immediate problems; later ones can address supplier replacements and applications that were missed.

Can teams find the right files? Are customers confused? Are exceptions being resolved? Give people one place to report issues and someone responsible for making decisions.

The handover needs to make independent use possible. The rollout is complete when the priority applications work, the agreed exceptions are resolved and the business can carry the identity forward.