Handing over a social account without losing the voice

An account changes hands. The new strategist reads the last three months of posts, the brand doc if there is one, and starts writing. Nothing obviously breaks. Six weeks later the client says something vague about the posts not feeling like them lately, and cannot point at a single one.

They are right, and the cause is structural. Reading published posts teaches you the output, not the reasoning: which angles were rejected, which words are banned, what the client reacted badly to in March, why the account stopped doing the Friday format. All of that lived with the person who left.

Voice does not survive a handover by default. It survives because someone captured the part that was never written down.

What is actually lost

Four categories, in rough order of how much damage their loss causes.

1. Rejections. The single most valuable and least recorded artefact. Every angle the client killed, every phrasing that came back marked up, every topic that turned out to be sensitive. The published archive shows what passed; it says nothing about what was tried. A new writer without the rejection history will re-propose the same rejected ideas within a month, which is what a client experiences as "they don't know us."

2. The forbidden list. Claims they cannot legally make, competitors they will not name, words banned internally. Usually held in memory after the first time someone got told off.

3. Fact provenance. Which numbers are current, which were true in March, which need legal review. Undated facts in an old post are how a stale claim gets recycled into a new one — the second-order version of publishing a wrong claim.

4. Relationship texture. Who actually approves versus who comments, how blunt you can be, whether they want to be consulted or informed. Not voice exactly, but it determines how much friction the next three months carry.

The published posts capture none of these. That is why "read the last quarter and you'll pick it up" fails reliably.

Capture it before you need it

The only version of this that works is continuous. A handover document written during a handover is written by someone already mentally gone, under time pressure, from memory that is already degrading.

Four artefacts, maintained per account as a matter of course:

• The voice definition, concrete enough that two writers produce similar posts from it. Three real sample posts beat any list of adjectives — the standard is in keeping several brand voices straight.
• The fact file, with dates. Every citable number, when it was true, where it came from.
• The forbidden list. Claims, comparisons, words, customers who may not be named.
• The rejection log. One line per killed angle, with the reason. This is the one nobody keeps and the one that matters most. It costs ten seconds at the moment of rejection and is unreconstructable afterwards.

If these exist, a handover is a week. If they do not, it is a quarter, and the client pays for the difference in quality without being told.

The two-week handover

Assuming the outgoing person is still available. Compress it if they are not, and accept a worse result.

Days 1–2 — Written transfer. The four artefacts above, updated to current. Plus one page the outgoing strategist writes from memory: what the client actually cares about, what they say they care about, and where those differ. That page is worth more than the rest combined.

Days 3–4 — The walkthrough. Go through the last quarter's posts together, outgoing person narrating: why this angle, what got cut, what the client said. Record it. This is the reasoning layer that the archive does not contain, and an hour of it saves a month.

Days 5–8 — Shadow drafting. The incoming writer drafts; the outgoing one edits with reasons attached. Nobody sends anything new to the client yet. Three or four rounds is usually enough for the register to transfer, and the edits themselves become additions to the voice definition.

Days 9–10 — Introduce, deliberately. Tell the client, before they notice. Frame it as continuity with a name and a date, not as an apology. Clients handle a planned handover well and an unannounced one badly, and the difference is entirely in whether they found out from you.

Days 11–14 — Supervised solo. Incoming writer runs the account; outgoing person reviews before release. Then stop.

The drift check

The failure is gradual, which is why it is caught late. Two cheap checks catch it inside a month.

The blind test. Take three new posts, strip the logo and any product names, and ask someone who knows the brand which client they belong to. If the answer is "could be any of them," the voice has already flattened toward the writer's default. This is the same check that catches voice bleed across clients, and it works for the same reason.

The rejection replay. Pull five angles from the rejection log and ask the new writer whether they would propose them. If they would propose three, the reasoning did not transfer, and the client is about to feel it.

Run both at week two and week six. After that, drift is usually the normal kind that any account has, not handover damage.

Why this keeps happening

Because the artefacts live in the wrong place. A brand doc in a shared drive gets updated during onboarding and never again; a rejection log in someone's notes app leaves with them; the fact file is a spreadsheet three versions behind whatever the client last confirmed.

The structural fix is that brand knowledge should live attached to the brand rather than to the person, and it should be updated as a side effect of the work rather than as a separate chore nobody does. That is what SelfSM holds per brand: voice profile, confirmed facts with their history, constraints, and the record of what was proposed, edited and rejected. The next strategist inherits the account rather than reverse-engineering it from published posts.

It also removes the incentive that quietly damages agencies — when knowledge lives with a person, the account is hostage to their retention, and everyone knows it.

FAQ

How do you hand over a social media account to a new manager? Transfer four written artefacts first — voice definition, dated fact file, forbidden list and rejection log — then walk through the last quarter's posts with the outgoing person narrating why each angle was chosen, then shadow-draft for a week before the new writer sends anything to the client.

Why does a brand's voice change when the writer changes? Because published posts show the output, not the reasoning. A new writer cannot see which angles were rejected, which words are banned or what the client reacted badly to, so they default toward their own register within a few weeks.

What is a rejection log and why does it matter? A one-line record of every angle a client killed and why. It is the most valuable handover artefact and the least commonly kept — without it, a new strategist re-proposes rejected ideas within a month, which clients experience as not being understood.

Should you tell the client the account is changing hands? Yes, before they notice, framed as planned continuity with a name and a date. Clients handle announced handovers well and unannounced ones badly, and the difference is almost entirely in who told them first.

How long should a social media account handover take? About two weeks with the outgoing person available: two days of written transfer, two of walkthrough, four of shadow drafting, then a supervised solo period. If the brand artefacts were maintained continuously it is closer to a week; if they were not, expect a quarter of degraded quality.