The Brand Voice Playbook: A Step-by-Step Process for Rules Writers Will Actually Use
Most brand voice documents get written once, admired in a Slack thread, and then ignored by everyone who touches the company's content. Here's the process for building one people actually open before they hit publish.
Why Most Voice Guides Die in a Shared Drive
Somebody on the marketing team writes a one-page PDF: three adjectives, a logo, a color palette, done. It gets emailed around once, collects a few nice reactions in Slack, and then nobody opens it again. Six months later a support agent, a freelance blogger, and whoever runs the company's LinkedIn are all writing in three different voices, and nobody notices until a customer points it out in a review.
The issue isn't that people don't care about how the brand sounds. It's that most guides describe a personality instead of giving instructions. "Friendly, confident, a little witty" tells a writer nothing they can act on at nine in the morning with a deadline. A guide that actually gets used works like a style sheet, not a mood board. What follows is the process for building that kind of document — one people check before publishing, not one they skim once during onboarding and never open again.
Start By Reading What You Already Have
Before writing a single rule, pull together twenty or thirty pieces of writing the company already published: the highest-traffic blog posts, a handful of support replies that got a genuinely good customer reaction, the last quarter of social captions, a few sales emails that actually closed deals. You're not chasing what marketing wishes the brand sounded like. You're documenting what it already sounds like when things go well.
Read them side by side and mark the patterns. Do sentences run short or long? Does anyone use contractions, or does everything sound like a press release? Is there a recurring phrase or house joke that keeps showing up? Do writers address the reader directly as "you," or stay at arm's length? This audit takes an afternoon, and it's what keeps the finished guide honest — it records behavior that's already working instead of aspirational traits somebody invented in a conference room.
Turn Adjectives Into Rules
| Vague Trait | Concrete Rule | Example |
|---|---|---|
| Friendly | Address the reader as "you," contractions allowed everywhere | "You'll get an email once it ships" instead of "The user will receive a confirmation email" |
| Confident | State the claim first, then the reason — never lead with a hedge | "This plan works for teams under ten people" instead of "This might be a good fit for smaller teams" |
| Clear | One idea per sentence, no sentence over 25 words in body copy | Break compound claims into two sentences instead of joining them with "and" or "which" |
| Witty | One aside per 300 words, never in an error message or refund notice | A joke belongs in a blog intro, not in "Your payment failed" |
Write the Document, Step by Step
- 1Tag the patterns from your audit
Go through the sample writing and label recurring habits: sentence length, point of view, punctuation quirks, words that show up often and words that never do. This becomes the raw material for every rule you write next.
- 2Convert each pattern into a testable rule
For every tagged pattern, write an instruction a stranger could check a sentence against without asking you what it means. If a rule needs a follow-up question to apply, rewrite it.
- 3Build a banned-and-preferred word list
List the industry jargon, filler phrases, and corporate tics the brand avoids, paired with what to say instead. This is usually the single most-used page in the whole document.
- 4Map the rules to channels
Note where each rule bends — a support reply might drop the humor rule entirely, while a blog post leans into it. Keep this as a short table, not a separate document per channel.
- 5Test it on someone who didn't write it
Hand the draft to a writer who had no part in creating it and have them rewrite three real pieces using only the document. Wherever they guess or ask questions, the rule wasn't concrete enough.
- 6Publish it somewhere people actually work
Drop it into the CMS, the support macro tool, or wherever writers already spend their day — not a folder three clicks deep in a shared drive nobody remembers exists.
A single voice doesn't mean identical language everywhere. It means the same underlying rules — sentence rhythm, banned phrases, how you address the reader — hold steady while formality, length, and humor dial up or down depending on the channel. A support reply and a blog intro can sound related without sounding interchangeable.
Where the Voice Can Flex
- Formality: a help-center article can be looser than a pricing page, even though both follow the same sentence rules
- Length: social captions compress the same voice into a fraction of the words a blog post uses
- Humor: asides that work in marketing copy get stripped out of anything transactional, like billing or account notices
- Directness: sales emails front-load the ask more than editorial content does, without breaking the house rules on tone
a content ops lead describing what changed after their second attempt at a voice guideThe guide didn't get used because it was well-written. It got used because every rule in it was something you could check a sentence against without calling the person who wrote it.
Keep the Document Alive
A guidelines document that ships and never gets touched again slowly stops matching how the brand actually writes, because language drifts and new channels show up that the original authors never planned for. Treat the rollout like a product launch with its own maintenance schedule, not a one-time deliverable you check off and forget.
Train new writers against it during onboarding by having them rewrite a few sample pieces and get feedback measured against the rules, not just by handing over the PDF. Pull five recent pieces every quarter, one per major channel, and score them against the rule list the same way you'd run any other quality check. Revisit the document itself after a rebrand, a new product line, or any real shift in audience — the rules should describe the brand as it writes today, not as it wrote two years ago.
If your finished guidelines reference any stats about tone preference or reader trust — the kind of claims that tend to get repeated in brand decks without a source attached — it's worth running them through AI Humanizer Lab's Citation Checker before the document goes out the door, just to confirm the numbers still trace back to something real.
Make your writing sound human
Humanize AI-generated text in one click with AI Humanizer Lab.
Try for free