How to Write a Brand Voice Guide Writers Actually Use

Most brand voice documents share the same fate. Someone spends a weekend writing three pages about being "approachable yet authoritative," the file goes into a shared drive, and six months later every article still sounds like a different person wrote it. The document exists. Nobody uses it.

The problem is almost never effort. It is that the document was built to describe a feeling instead of to guide a decision. A writer staring at a blank draft cannot do anything useful with the word "authentic." They can do a lot with "we say 'you' and 'we,' never 'the customer' or 'our company.'" One is a mood. The other is a rule you can check.

This is a practical guide to writing voice documentation that changes what actually gets published. It works whether you write everything yourself, hand it to a freelancer, or run it through an AI drafting tool.

Why most brand voice guides get ignored

Brand voice guides get ignored because they are written as inspiration rather than instruction. The typical guide lists four or five personality adjectives, maybe a mission statement, and a paragraph about the audience. None of that survives contact with a real sentence.

Consider what a writer does when they finish a paragraph. They ask: is this right? A good voice guide answers that question in specific terms. A bad one forces the writer to interpret an adjective and hope. Two writers will interpret "confident" in opposite directions, and both will believe they followed the guide.

There are three recurring failures:

• Abstraction. Adjectives with no rule attached. "Warm" tells you nothing about contractions, sentence length, or whether you can open with a question.
• No examples. A rule without a before-and-after is a rule people misread. The example is where the meaning actually lives.
• Length. A 14-page guide is a guide nobody rereads. If it does not fit on two pages, it will not be consulted mid-draft, which is the only moment that matters.

The parts of a voice guide that actually do work

A working guide is a set of decisions a writer would otherwise have to make from scratch on every piece. Strip out everything that does not change a sentence. Keep these.

1. Point of view and address

Decide, in one line, who "we" is and who "you" is. State whether you use first person plural ("we recommend"), whether you address the reader as "you," and what you never call them. A dental practice might write: "We say 'you' and 'your family.' We never say 'patients' when speaking to the reader directly, and never 'clients.'"

2. Formality level, pinned to real choices

Do not write "semi-formal." Write the actual mechanics: "We use contractions (it's, you'll). We start sentences with And or But when it reads better. We avoid slang and emoji. We use one exclamation point per article at most." Those are checkable.

3. Sentence and paragraph rhythm

State your defaults. "Most paragraphs run two to four sentences. We vary sentence length on purpose. We break up any paragraph over five lines." This is the single biggest driver of whether two pieces feel like the same voice.

4. Vocabulary: words we use, words we ban

A two-column list does more work than any amount of description. Put your industry-specific preferences here, your banned marketing clichés, and how you refer to your own product or service.

5. Before-and-after rewrites

Three to five paragraphs shown "generic version" next to "our version." This is the part writers actually copy the feel from. It is worth more than the rest of the document combined.

A worked example: turning adjectives into rules

Suppose an HVAC company in Tucson describes its voice as "trustworthy, straightforward, and local." Useless as written. Here is the same intent converted into a table a writer can apply.

Now add one before-and-after so the tone is unmistakable:

Generic: "Regular maintenance is important to ensure your system operates efficiently throughout the year."

Our version: "In Tucson, dust is the thing that kills a system early. Change the filter monthly from May through September and you'll dodge most of the summer breakdown calls we get."

A freelancer who reads that pair understands the voice in ten seconds. No adjective could have transmitted it.

How long should a brand voice guide be?

A brand voice guide should fit on two pages, because a document longer than that stops being a reference and becomes something people read once and forget. The goal is a page a writer keeps open in a second tab while drafting. If you have more material — full editorial standards, formatting rules, legal disclaimers — put those in a separate operations document. The voice guide is only the part that shapes tone and word choice.

If yours is already long, cut everything that does not change a sentence. Brand history, mission statements, and audience personas belong elsewhere. Keep point of view, formality mechanics, rhythm, the word lists, and the examples. That is the whole job.

How do you make writers actually follow the voice guide?

You make writers follow the voice guide by building it into the workflow at two points — before drafting and during review — instead of hoping people remember it. A document that lives only in a folder gets used once. A checklist attached to every assignment gets used every time.

Here is a sequence that works for a small content operation:

1. Attach the two-page guide to every brief. Not a link to find it. The actual text, at the top of the assignment.
2. Add a five-item voice check to the review step. Reviewer confirms each before approving. Example: point of view correct, no banned words, paragraph length varied, at least one concrete local or specific detail, opening leads with the answer.
3. Feed the before-and-after examples into any AI tool you use. If you draft with an LLM, paste the word lists and two rewrite pairs into the prompt. Models match demonstrated examples far better than they match adjectives.
4. Update the guide when you catch a recurring miss. If three drafts in a row overuse a word, add it to the ban list. The guide should get sharper over time, not sit frozen.

The review checklist is the piece most teams skip, and it is the one that enforces everything else. A rule with no checkpoint is a suggestion.

Keeping the guide alive as you scale

Voice drifts when the number of people writing goes up and the feedback loop stays informal. The fix is to treat every edit you make on a draft as data. When you rewrite a writer's sentence, ask whether the reason is already in the guide. If it is not, add it. Over a few months the document stops being your guess about the voice and becomes a record of the decisions you actually make.

This is also where outside help either fits or fights your voice. A program that produces articles in your voice should be working from documentation like this, and should be showing you before-and-after samples early — not delivering ten pieces before anyone checks the tone. At ClearPath Content we build the two-page guide and the review checklist together with a client before writing anything, because a voice document nobody uses is the same as no document at all.

The practical takeaway: rewrite your voice guide so every line is a decision a writer can check, cap it at two pages, and staple a five-item version to your review step. If a rule cannot be checked against a finished sentence, it is not a rule — it is a wish, and it will not survive your next draft.