How to Write a Brand Voice Guide People Actually Use

RedHub AI Editorialupdated September 7, 20265 min read

A bound guide buried under a stack of loose sheets with only its red-lit edge showing
Jump to a section10

TL;DR

  • What it is: a brand voice guide is a short document that turns your voice rules into something a new hire, a freelancer, or an AI tool can follow without you in the room.
  • Who it's for: any team whose voice guide exists but nobody opens it — see the Brand Voice Engine for a spec built to actually get used.
  • How it works: build it from rules and do/don't examples, not adjectives, and keep it to one page.
  • Bottom line: a guide people don't open might as well not exist. Usability is the whole design goal.

What is a brand voice guide?

A brand voice guide is a short document that captures how your brand writes, in a form specific enough that someone who's never written for you can follow it correctly on the first try. The best guides skip long adjective lists in favor of checkable rules, contrast pairs ("direct, not blunt"), a banned-words list, and do/don't examples for each rule. A guide people actually use is short — often one page — because a document nobody opens has zero effect on what actually gets published.

Best for: teams handing writing off to new hires, freelancers, or AI tools. The Brand Voice Engine ships an 8-section Voice Spec template built for exactly this.


Most companies have a brand voice guide sitting somewhere in a shared drive that nobody has opened in six months. That's not a writing problem — it's a design problem with the guide itself. A guide built from vague adjectives and long paragraphs doesn't survive a real deadline. A guide built from checkable rules and quick examples does, because it answers the question a writer actually has: "what do I do right now?"

Why most guides don't get used

Two failure modes show up over and over. First, the guide is too long — twenty pages of brand philosophy that nobody has time to read before a Tuesday deadline. Second, the guide is too vague — full of words like "authentic" and "empowering" that don't tell a writer what to actually change in the next sentence. Fix both and the guide gets used: keep it short, and make every rule specific enough to check.

What actually goes in a usable guide

Skip the brand-philosophy preamble. A usable guide is built from a small number of sections that each answer one concrete question:

SectionWhat it answers
Voice in one lineThe north star. If a draft violates this, nothing else matters.
Voice attributes (contrast pairs)"We are X, not Y" — marks exactly where the line is.
Vocabulary — signature + bannedPhrases you actually use, and the filler and clichés to hunt for.
Sentence & rhythmLength, structure, openers, what to avoid.
Formatting & mechanicsHeaders, lists, emoji policy, punctuation habits.
Point of viewPerson (I / we), tense, how you address the reader.
Signature movesThe 2-4 recognizable tics that make it unmistakably you.
Hard rules (never do)The non-negotiables — "never overpromise," "never bury the point."

Do/don't examples are non-negotiable

A rule without an example is still an abstraction. "No corporate filler" means little on its own; showing the filler version next to the fixed version makes it instantly clear. For every rule in your guide, write a short do/don't pair — a sentence that breaks the rule, and the same sentence rewritten to follow it. This is the single highest-leverage addition you can make to any existing guide, and it takes less time than most teams assume.

Keep it to one page

Length is the enemy of use. If your guide runs past one page, most people will skim it once and never open it again. The discipline of fitting a real voice onto one page forces you to cut anything that isn't a rule someone can act on — which, not coincidentally, is exactly what makes the guide better.

How to write one, start to finish

  1. Pull 3-5 samples of your best existing writing — the evidence your rules will come from.
  2. Draft your one-line voice statement first; everything else supports it.
  3. Write 4-5 contrast pairs for any attribute that could be misread.
  4. List your banned words and your signature phrases side by side.
  5. Add one do/don't example per rule, and stop once it's one page.

Key insight: a guide that fits on one page and gets opened every week beats a twenty-page brand bible that gets opened once. Design for use, not for completeness.

Skip the blank page — extract your guide from real samples

The Brand Voice Engine's Voice Extractor turns 3-5 writing samples into a structured, one-page Voice Spec automatically — contrast pairs, banned words, and hard rules included.

Get the Brand Voice Engine — $59 →

Make the guide reach every tool, not just your writers

A guide that only lives in a PDF misses half the writing that happens today, because a growing share of first drafts come from an AI assistant. A Voice Spec built the same way as a written guide can be pasted into any prompt, installed as a Claude Skill, or dropped into a shared Claude Project so a whole team's AI drafts inherit the voice automatically. See how to keep AI writing on-brand for the deployment side of this.


Decision Guide

Rewrite your guide if: it's longer than one page, full of adjectives, or nobody on the team can name the last time they opened it.

Keep your current guide if: it's already built from checkable rules with do/don't examples and people actually reference it.

Best first step: pull 3-5 of your best samples and draft your one-line voice statement before touching anything else.

Common Questions

What should a brand voice guide include?

A one-line voice statement, contrast pairs, a vocabulary list (signature and banned), sentence and formatting rules, point of view, signature moves, hard rules, and a do/don't example per rule.

How long should a brand voice guide be?

One page, if possible. A guide people don't open has no effect on what gets published, no matter how thorough it is.

Why doesn't my current voice guide get used?

Usually because it's too long, too vague, or both. Long adjective-heavy guides don't survive a real deadline — checkable rules with examples do.

Do I need examples in a voice guide?

Yes. A rule without a do/don't example is still an abstraction. Examples make every rule instantly clear and checkable.

Can a brand voice guide work with AI tools?

Yes, if it's built from specific rules rather than adjectives. A rule-based guide can be pasted into any AI prompt or installed as a reusable Claude Skill.

Who should be involved in writing the guide?

Whoever holds the voice today should supply the samples, but the guide should be tested by someone who's never written for the brand — if they can follow it, it works.