last updated: april 28, 2026 · written by shashank · holdyourvoice.com
how to build a brand voice style guide
ai
shashank · with ai as his sidekick7 min read · updated apr 29, 2026
in short: most brand guides are useless. to make one that works, you have to stop talking about "brand personality" and start counting things. find the real patterns in your best writing—sentence length, word choice, punctuation habits. turn those patterns into hard rules. put them in a living doc, not a pdf. then use a tool like hold your voice to enforce them automatically, so you don't have to argue about it later.
a style guide is a technical schematic, not a mood board.
a brand voice guide isn't a list of adjectives like "bold" or "innovative." that's a mood board. a real guide is a technical document. it turns your writing style into a set of measurable rules that anyone—a new hire, a freelancer, an ai—can follow to sound like you.
a good one is built on data, not feelings. it answers questions like:
what's our target sentence length?
oxford comma: yes or no?
what are the five transition words we overuse?
what three corporate buzzwords are banned on sight?
this is your source of truth for your company's verbal identity. it's the document that stops brand voice drift, especially as you hire more people or start using ai tools to write.
find your voice by analyzing, not brainstorming.
you don't find your voice by brainstorming adjectives. you find it by analyzing your best writing. it's a forensic process. this grounds your voice in what you actually do, not what you think you do. get this step wrong, and the whole thing is useless.
step 1a: assemble your source text
collect 5 to 10 pieces of your best writing. this is your gold standard. don't pick things you wish you sounded like. pick things that actually worked. good candidates include:
a blog post that did well.
a newsletter that got replies.
your website's about page.
a sales page that converted.
a founder's linkedin post that got real engagement.
put it all into one document. you need at least 5,000 words for the patterns to show up. this text is the raw material for your voice profile.
step 1b: look for the patterns
now you analyze that text. you can use a basic tool for readability, but you'll need to go deeper, either manually or with a tool like ours. look for these specific metrics:
sentence length variation: calculate your average sentence length, but more important is the variation. do you mix long, winding sentences with short, sharp ones? a high variation is a voice signature. low variation is a classic sign of ai writing.
vocabulary choices: what words do you lean on? what words do you avoid? are you a "use" person or a "leverage" person? make a list of your go-to terms. make another for words that are banned. this is where the personality really lives.
punctuation habits: track your punctuation tics. are you addicted to em-dashes? do you use the oxford comma? these small choices are huge voice signifiers.
structural patterns: how do you build an argument? do your posts always start with a single-sentence paragraph? do you follow a specific formula in your emails? map these blueprints out.
this data gives you the objective facts about your voice. it's not up for debate. it's the fingerprint of how you write.
the anatomy of a useful style guide.
a good guide has rules you can measure. it leaves no room for interpretation. we've seen that guides built on concrete rules—like "use contractions 90% of the time"—cut voice drift by over 80% compared to guides that just say "be conversational." your guide should be a checklist, not a poem.
the core sections:
1. rhythm and pacing
this is about the music of your writing. it's the thing people feel before they notice it.
average sentence length: "our target is 12-15 words per sentence."
sentence length variation: "at least one sentence per paragraph needs to be under 6 words. no more than two sentences in a row over 20 words."
paragraph length: "paragraphs are 2-4 sentences. single-sentence paragraphs are for making a point."
2. vocabulary and diction
this is your company's lexicon. it reflects who you are and who you're talking to.
core vocabulary (use often): a list of 20-30 words that are yours. for us, it's words like "quantifiable," "linguistic," "drift," "corpus," and "fidelity."
banned vocabulary (never use): a list of 10-15 forbidden words. this is often more important than the "use" list. think corporate jargon ("synergy," "optimize") or clichés ("think outside the box").
audience terminology: what do you call your people? "users," "clients," "readers," "members"? pick one and stick with it.
3. grammar and punctuation (the house rules)
this section stops the dumb arguments before they start.
serial comma (oxford comma): "we always use the oxford comma." (or "we never do.")
contractions: "use contractions like 'you're' and 'it's' everywhere. avoid clunky ones like 'should've'."
formatting: "use bold for emphasis. never italics. use h2s for sections, h3s for sub-points. never h4s."
4. structural blueprints
give people templates for common writing tasks. it helps them apply the voice correctly.
blog post introductions: "start with a contrarian opinion in a short first sentence. follow with a 3-sentence paragraph on the status quo. end the intro with a question."
email call-to-action: "the last paragraph has one clear call to action. put the link on its own line. like this: 'click here to check your voice score'."
the persona trap.
the single biggest mistake is the "brand as a person" exercise. asking "if our brand was a celebrity, who would it be?" is a trap. the answers are un-measurable, un-enforceable, and lead to total chaos.
the problem is obvious. one writer hears "dwayne 'the rock' johnson" and writes confident, motivational copy. another writer hears the same thing and writes informal, funny copy with a lot of slang. both are right, but the outputs are completely different. the persona is a rorschach test for the writer's own bias, not a clear instruction.
you don't need a persona. you need a profile, built from the data you gathered in step one. it replaces vague adjectives with objective rules.
don't: "our voice is helpful and authoritative, like justin welsh." do: "our posts use short, declarative sentences (avg. 11 words) and address the reader directly as 'you', like justin welsh."
don't: "our brand is a knowledgeable mentor." do: "our paragraphs start with a claim, followed by 2-3 sentences of proof. we don't use rhetorical questions or hedge with words like 'maybe'."
when you swap the persona for a linguistic profile, your voice becomes testable. you can check a draft against the rules. did the writer follow the sentence length rule? did they use a banned word? it's a yes/no question, not an opinion. this is how a tool like our own ai drift detector works. it's math, not magic.
build a living document, not a pdf.
your guide has to be a living document, not a pdf that dies in a dropbox folder. teams that use something like notion or slab for their guides actually follow them. teams that use google docs or static files don't. the tool shapes the behavior.
structure your guide for scannability
people will use this as a quick reference, not read it cover-to-cover. design it for speed.
use clear hierarchies: use headings and bullet points. a writer needs to find the rule on commas in five seconds.
create a "quick start" section: put the 5 most important rules at the top. for a new freelancer, that might be all they need.
use "do / don't" tables: for every major rule, show an example. a two-column table with a "do this" and "don't do this" is the fastest way to make a point.
example "do / don't" table for vocabulary:
do (on voice)
don't (off voice)
use hold your voice to analyze your drafts for linguistic patterns.
leverage hold your voice to optimize your drafts for brand synergy.
the tool helps you prevent voice drift.
the tool empowers you to avoid voice drift.
make it a living document
your voice will change. so should your guide. make it clear that it's a work in progress. set up a process to update it—maybe a quarterly review where the team can suggest changes. in notion, you can use comments to manage this.
enforcement without arguments.
the only way to make a style guide stick is to automate enforcement. frame it as a support tool, not a weapon. in our analysis of voice profiles, we’ve found that the biggest cause of voice drift in teams isn’t a lack of talent; it’s the absence of a low-friction, objective feedback loop. manual reviews create friction and make writers defensive.
the goal is to make writing in-voice the easy path. creativity works best inside constraints. by defining the rules of the game—sentence structure, vocabulary—you free up writers to focus on the hard part: the ideas.
the enforcement stack
the guide (source of truth): your notion doc is the constitution. it's where the rules live.
automated checking (first line of defense): this is where a tool like ours comes in. you build a voice profile from your best writing. then anyone can check a draft and get an instant, objective score. it gamifies the process and takes the personal sting out of feedback. it happens before a human editor ever sees it.
peer review (the collaborative check): use the score to start a conversation. instead of "this feels off," a reviewer can say "the voice score is a 65. looks like sentence length variation is the issue." the feedback becomes specific and actionable.
training and onboarding (proactive education): don't just send a new writer a link to the guide. walk them through it. show them how the automated checker works. give them a few gold-standard examples and have them break down why they work.
this system turns enforcement from a punishment into a real-time part of the workflow. it's the difference between a speed trap and guardrails on a highway. the guardrails don't tell you where to go. they just keep you on the road so you can move faster.
turn your style guide into a real feedback loop
build a voice profile from your best writing, then check every new draft against it before voice drift turns into editing debt.
founder of hold your voice. writes about brand voice, ai writing patterns, and the craft of sounding like yourself.
co-written with ai as sidekick. shashank drafts the voice; the ai pressure-tests the structure. anything that sounds wrong is shashank's fault — anything that sounds suspiciously generic is the ai's.