In this article

When a new identity is approved, attention often moves immediately to announcement graphics. Yet a campaign can display the new mark while proposals, websites or signage continue using inconsistent information. A launch depends on people being able to use the system as well as on the moment the change becomes visible. This guide goes beyond preparing a celebratory post. It addresses how an approved identity reaches employees, suppliers and customers in a practical sequence. It is distinct from deciding the strategic scope of a rebrand: the focus is carrying completed decisions into reliable use.

Quick answer

Clarify what changes and what remains stable before announcing a new identity. Give employees current files and application examples, and assign owners for websites, profiles, documents and physical material. Explain the meaning of the change as well as showing its appearance. If touchpoints cannot all change simultaneously, document temporary arrangements and review dates so the transition does not become an indefinite mixture of unrelated versions.

Define what the announcement needs to explain

A logo, palette or type system may change while the company name and services remain stable. Describe those distinctions clearly. Customers should not infer that an agreed service or contact route has changed merely because the appearance is new. The guide comparing brand renewal and logo changes can support the scope discussion. Prefer an accurate explanation of what actually changed over unsupported claims of transformation added simply to make the announcement sound more significant.

Prepare internal users before the external announcement

Employees need more than recognition of the new mark. They should know which file to use, what happens to old templates and how to respond to questions. Prepare a concise internal explanation with relevant examples. Sales, operations and customer-facing teams may need different material. Instead of sending everyone one long presentation, provide examples connected to their tasks. An unresolved internal decision will not automatically become clear when a public post announces that the new identity has arrived.

Use a touchpoint inventory to establish the sequence

List the website, profiles, email signatures, proposals, packaging and signage. Record the update owner, required source material and review status for each. The most visible surface is not always the most urgent: incorrect information or a broken customer route may deserve priority. Identify the approved version used for new outputs. This prevents several teams from publishing different files during the same period while each assumes its own copy represents the final identity.

Make temporary coexistence an explicit arrangement

Physical stock, production schedules and separate publishing owners may prevent a single-day change. Explain where old and new identities can coexist, for how long and under whose review. A temporary exception should not become permanent uncertainty. An old brochure carrying the correct current address presents a different problem from one directing customers to an obsolete contact. Assess the transition through information accuracy as well as appearance, and record the conditions under which each retained item will be replaced.

Test the announcement through a hypothetical customer question

Imagine a customer seeing the new logo and asking whether the business itself has changed. Does the announcement explain who you are and what matters to that person? Is an appropriate contact route available alongside the design images? This scenario is not reported customer feedback. It is a review exercise reminding the team that information obvious to the designers may not be known by someone outside the project, and exposing questions the launch wording leaves unanswered.

Continue the consistency review after launch

Publication of the announcement does not complete every transition task. Review old download links, profile images and frequently used documents. Establish one current source to reduce the return of retired files. Clarify with BOCW which identity, application and launch-support tasks are included in the project. Examine whether teams can use the system correctly alongside reviewing visual engagement. A sustainable launch is assessed through the consistency of later applications as well as the appearance and reach of its first public post.

Key takeaways

  • Explain appearance changes separately from stable company and service information.
  • Prepare employees with current artwork and realistic application examples.
  • Record touchpoint owners, temporary arrangements and final review responsibilities.

Frequently asked questions

Must everything change on the same day?

That may not be practical. Plan the sequence, exceptions and final checks explicitly, and prioritise material containing incorrect customer information.

Is showing the new logo enough for an announcement?

It shows the visual change. Customers may also need a concise explanation of what changes and what remains stable.

What should be reviewed after launch?

Check access to current files, reuse of retired templates and consistency of information. Views of the first announcement alone do not establish that the transition is complete.