The Baton, Not the Binder: Passing On Your Website's Voice Without Losing It

There's a particular kind of silence that follows a marketing lead leaving a company. It's not awkward. It's more like the pause after someone switches off a desk lamp. The laptop goes back to IT, the Slack account is deactivated, and somewhere in a shared drive there's a folder called Website — final FINAL v3. Nobody opens it for six months.

Then a new person arrives, reads the homepage, and thinks: why does it say that? They rewrite it. And the brand voice quietly shifts a few degrees, like a picture hung slightly crooked by someone who meant well.

That's the gap worth closing.

Logins are the easy part

A standard handover covers the plumbing. CMS access, hosting, the agency contact, the next campaign deadline, the fact that the cookie banner is managed by someone in legal whose name nobody is quite sure of. All useful. None of it explains why your About page opens with a sentence about a bloke in a garage in 1998, or why the pricing page refuses to use the word "cheap".

Those choices aren't accidents. Or at least, they shouldn't be. They're editorial decisions — small bets about how the brand wants to sound — and they're the first thing to get flattened by a newcomer with good intentions and a blank page.

Handing over the why is the difference between a new starter continuing a voice and a new starter inventing one from scratch.

The phrases that are load-bearing

Every website has a handful of sentences doing structural work. They might look ordinary. They might even look slightly odd. One might be a deliberately blunt line on a services page that the sales team fought for. Another might be a piece of jargon the founder insists on because a key client uses it. A third might be a piece of plain English that replaced a much more impressive-sounding phrase, on purpose, after someone noticed that newcomers kept asking what it meant.

None of this survives a handover unless someone writes it down.

A good test: if a sentence would take more than thirty seconds to explain to a new colleague, it belongs in the handover. If explaining it requires a story about a customer complaint from years ago, a competitor's ad campaign, or a very specific regional reference, it definitely belongs in the handover.

What happens when the memory goes

The pattern is predictable. New person joins. New person wants to make their mark. The homepage gets a light refresh. The refresh is competent, well-written, entirely reasonable — and subtly wrong. The dry humour gets smoothed out. The short sentences get longer. The local references get genericised until the copy could belong to a company anywhere in the UK, which is another way of saying it belongs nowhere.

Three months later, someone in sales mentions that enquiries have dipped and the site "feels less like us". Nobody can quite say why. The original writer is now working somewhere else and has forgotten the details anyway.

This isn't a failure of talent. It's a failure of paperwork.

A handover note that actually earns its keep

The good news is that this doesn't need to be a forty-page document. Nobody reads those. What you want is something closer to a one-page briefing that a new starter can skim in ten minutes and return to when they're stuck.

Here's a template that works. Adapt the headings, bin the ones you don't need, and keep it short enough that people actually maintain it.

1. The voice in one paragraph

Not an adjective list. A description of how the brand actually sounds when it's writing well. "Warm but not gushing. Direct, occasionally dry. Never uses exclamation marks outside of genuine good news." Include one sentence that sounds exactly right and one that sounds exactly wrong. Examples do more than rules.

2. The deliberate quirks

A short list of choices that look like mistakes but aren't. Lowercase headings on the blog. The fact that the brand says "we" on product pages and "I" in emails. The refusal to use the word "solutions". Every one of these will be "fixed" by a well-meaning newcomer unless it's flagged as intentional.

3. The untouchables

Phrases that must not be rewritten without a conversation. Legal lines, regulated claims, the founder's origin story, the exact wording of a guarantee, the name of a product that legally can't be shortened. Be specific about why — "because compliance" is a reason; "because [name] will be cross" is a better one.

4. The pages with history

A quick note on any page that has been through something. The pricing page that was rewritten after a wave of confused support tickets. The careers page that was rebuilt because candidates kept asking the same three questions. The 404 page that exists because a broken link went viral on a forum in 2023. Context turns a strange page into a sensible one.

5. The open questions

Things nobody has resolved. The tone of voice on the help centre. Whether the newsletter should sound like the homepage or like the founder's LinkedIn. Flagging an open question is far more useful than pretending it's settled.

6. The people

Who to ask about what. Not a full org chart — just the two or three names attached to the decisions above, plus a note on who owns the brand voice day to day.

Where to keep it

Somewhere the next person will actually find it. A pinned doc in the marketing channel. A page in the CMS itself, if the CMS allows it. A file in the website folder with an obvious name, not a cryptic one. The best handover note in the world is worthless if it's buried three folders deep behind a login nobody has.

And update it. Not in a big annual push — just when something changes. A sentence added after a rewrite. A quirk removed because it's no longer true. Handover notes rot faster than websites do.

The point of all this

Brand voice isn't held in a PDF. It lives in the heads of the people who made the decisions, and it evaporates the moment they move on. A handover note is just a way of making sure that when the keys change hands, the thinking goes with them.

It won't stop every rewrite. It won't make every new starter read it. But it will save someone, somewhere, a month of second-guessing — and it will keep your website sounding like itself, which is harder than it looks and worth more than it costs.