A rebrand rollout plan is the part that starts after the rebrand is decided. It lists every place the old brand still lives, one person's name beside each, and the order they change in.
That sounds like admin. It's also where a rebrand quietly comes apart.
Say a customer reads your announcement on Monday, then gets an invoice with the old logo at the top on Friday. To them, the rebrand isn't finished. They're right, and one missed line was enough to show it.
What would it take for no customer to meet the old brand halfway through? Every line caught, a name beside each one, and the changes made in order.
All of this starts once the rebrand is settled. If you haven't decided whether to rebrand, or what the new brand will be, that's a different job, and it comes first. Still deciding what the business should be? That's my business design work.
First, know how big your rebrand is
Rebrands come in two sizes, and they make very different lists. A refresh changes the look and the words: a new logo, new colors, new messaging, and the same name. A full rebrand changes the name too.
The name is what makes the list long. A logo lives mostly in files someone designed. A name lives in places nobody designed at all: a bank account, a contract, a directory listing someone else wrote. So a full rebrand adds every place the name is written, usually the domain and email addresses, and wherever your business is registered.
The list below is the long version. If yours is a refresh, read it with a pen and cross out the lines a refresh doesn't touch. What's left is your list.
Every place the old brand lives
Here is the business rebrand checklist, grouped by where each thing lives. Work down it once with your own business in mind.
Your people and partners. Your team, your business partners, and anyone who answers the phone or email for you.
Your website and addresses. The website's words as well as its logo, including the headlines and the calls to action. If the name changes, the domain and every email address on it. Moving the site to a new platform at the same time? Plan the people side of the website migration too.
Social profiles. On every profile: the name, the username, the bio or about text, the profile and cover images, the website link, and the buttons.
Listings and mentions. Your Google Business Profile, other local listings and directories, and other sites that mention you or link to you.
Email. Signatures, templates, newsletters, and automated email sequences.
Documents and templates. Invoices, letterheads, envelopes, business cards, proposals, presentations, document templates, brochures, flyers, and internal forms.
The words, wherever they appear. Every mention of the old brand, your short "about" summaries, and your address, phone number, and website URL if any of them change.
Sales and support material. Sales scripts, pitch decks, onboarding documents, and support documents.
Proof and ads. Testimonials, case studies, ads, and photographs that show the old brand.
Physical things, if you have them. Signage, packaging and labels, name badges, and your voicemail and hold messages.
Money, legal, and contracts. Your bank, your insurers, and wherever your business is registered. Your privacy policy and terms. Contracts with customers, suppliers, and employees.
Then add the places only your business has. This list is where yours starts, not the whole of it.
Give every line on the list one owner
Every line on that list is a change somebody has to make. So every line gets one person's name beside it, and that person makes that change.
Then put two more names at the top of the page. One is whoever approves the new version before it goes out. That's usually you. The other is whoever keeps the whole list and knows what's done. That can be you too, but it doesn't have to be.
Most lines fall into one of three groups:
- What only you decide or approve. The calls only the owner can make and the sign-off on what goes out under the new brand.
- What each person changes in the things they use every day. Their own email signature, their own profiles, and the templates they send.
- What outside people change. Whoever runs your website, your designer, and whoever handles your bank and registrations.
A line with no name beside it stays the old brand. Everyone who sees it assumes it belongs to someone else. And the lines that end up with no name are predictable. They're the ones nobody uses on a normal day: the hold message, the directory listing set up years ago, the brochures in a drawer. Nobody notices them, so nobody claims them.
Any big list of changes works the same way. For a list that comes out of strategy work, here's how a business implementation plan gives each change a finish line and one owner.
Right now I'm doing a rollout like this with all my companies, individually and as a full entrepreneurial support ecosystem. When businesses point to each other, the old brand lives in more places than anyone remembers, so every line needs a name.
Just need a website or blog content, and nothing else? FableForge and its Tech Team handle that.
Change it in order: your people first, then the switch, then the announcement
Order is what keeps a rollout from leaking. If a customer asks about the new name before your own people have heard it, that question gets a blank look.
- Settle the name before anything changes. If the name is changing, it's final, and you've checked it's available to protect. Every line on the list spells it out, so a name that moves later sends you back through all of them.
- Tell your people first. They hear about the change, and why, before any customer does. Give them answers to the questions customers will ask and the updated scripts and templates they'll be using. Then ask what they think. They'll spot places your list missed, because they work in those places every day.
- Set up the new addresses early, if the name changes. The new domain and email addresses need to be ready before the switch. Setting them up is a tech job, and it belongs with the website line above.
- Make the switch. Your website and your online profiles change together. A customer who clicks from one to the other should find the same brand on both. You can switch everything at once or in planned stages. A slow rollout can raise more questions than it answers, which is the case for one coordinated switch.
- Announce it. Tell customers directly: an email, then a follow-up that gives the date of the change, and in person where you can. Bring your loyal customers in rather than surprising them. Keep service running normally, so the change feels like an improvement to the people it affects.
- Work through the long tail. Documents, physical things, and contracts change as they come up, each one still with the name you gave it.
Written down, with a name on every line and this order beside it, the list is your rebrand implementation plan.
After launch day, the list is still the plan
Once the switch is done, go back through the list line by line. What gets missed is what nobody sees daily, like the directory listing or the hold message. Those are the lines to check by hand.
Your people will also keep reaching for the old templates for a while. Getting a change used is its own job. That's the subject of rolling out new systems so your people use them.
Now the name at the top of your rebrand rollout plan matters most: whoever keeps the whole list. A rollout this size is a project in its own right, and it has to fit around the work that pays the bills. If you're running it yourself, get the whole rollout onto one plan first. The overview of planning launches, rebrands, and migrations shows where a rebrand fits among the others.
If your people are already stretched, a rebrand rollout is exactly the kind of project Sparkitive takes on. We can keep the whole list and work it down while you run the business.
Weeks after switch day, something like the hold message will still say the old name. If you'd rather someone else chased the whole list down, a free 30-minute discovery call with me is the place to start. Whoever ends up doing the chasing, you'll go away knowing what comes next for your rollout.
