Most voice guides fail because they describe personality, not production. Friendly, bold, human. Writers nod and produce the same generic SaaS tone as everyone else. A guide that works fits on two pages, shows before and after sentences, and answers disputes editors actually see.
Voice is not tone of one campaign
Voice is stable across channels. Tone shifts with context: a product release note can be tighter than a blog essay. Define voice as the underlying habits that stay constant. Tone notes belong in individual briefs when a piece needs extra restraint or warmth.
If leadership wants different voices for executive bylines and support docs, document two registers under one brand, not two brands. Writers need to know which register a format uses by default.
Start from real drafts, not workshops
Collect ten pages you are proud of and ten you are not. Mark sentences that sound right and lines that make you wince. Patterns emerge faster from actual copy than from a whiteboard session. Include web copy, blog posts, and emails customers receive.
Interview sales and support for phrases customers use and misunderstandings they hear. Voice should meet the reader's language without parroting jargon unless the audience expects it. For regulated categories, legal may need a parallel list of approved and banned claims.
The four parts of a usable guide
| Part | Contents | How writers use it |
|---|---|---|
| Traits with examples | 3 to 5 traits, each with do and do-not sentences | Calibrate new drafts quickly |
| Vocabulary | Preferred terms, banned hype, product naming | Replace wrong words in pass one |
| Syntax habits | Sentence length, person, contraction use | Match rhythm across pages |
| Boundaries | Humor, politics, competitor mentions | Avoid approvals that stall publishing |
Keep traits behavioral. Instead of innovative, try names the mechanism in plain language and shows proof before adjectives. Traits should be testable. An editor can ask does this section follow trait three without a debate.
Examples beat adjectives
For each trait, show a wrong line and a fixed line from your domain. Wrong: Our platform revolutionizes workflow synergy. Fixed: Your team sees open tasks by owner and due date, without switching tools. Writers pattern-match faster than they interpret adjectives.
If the guide does not include sentences from your product category, writers will import voice from whatever they read last.
Link the guide from every content brief instead of pasting voice notes repeatedly. Briefs should flag exceptions: this post uses first-person CEO voice, or this landing page must match legal-approved wording.
Person, point of view, and formality
Decide default person: first person plural we, second person you, or third person for formal reports. Mixing we and you in the same paragraph sounds sloppy unless intentional. State contraction policy. Contractions often help blog posts; product UI copy may avoid them.
- Pick a reading level target using a sample paragraph score, not a number alone.
- Say whether jokes, rhetorical questions, or metaphors are in bounds.
- Define how to address competitors: by name, by category, or not at all.
- Note accessibility: plain language, defined acronyms, no idioms that do not translate.
Roll voice out through editorial
Train editors first. They enforce voice on every draft and feed back recurring mistakes into the guide. Writers external and internal get the guide plus one annotated example post. For website copywriting, pair the guide with page templates so heroes and CTAs inherit the same rules.
Review the guide quarterly. Product positioning shifts. New features introduce new terms. Retire rules that editors never enforce. A stale guide gets ignored; a living guide gets opened.
Voice on SEO content without sounding robotic
SEO articles still need headings that match queries and answers that satisfy intent. Voice should not fight clarity. Put keywords in titles and H2s where natural; keep body sentences in your register. Avoid stuffing brand slogans into every section.
When ghostwriting for executives, capture their actual phrasing in interviews. See how to interview a subject matter expert for question techniques that pull voice-rich quotes. Editors reshape for clarity without sanding off personality.
Signs the guide is working
Revision comments shift from this does not sound like us to factual or structural fixes. External writers need fewer rounds. New hires publish acceptable drafts within two assignments. Sales recognizes blog posts without seeing the byline.
If every draft still arrives in generic marketing voice, the guide is too abstract or not linked from briefs. Fix the examples before you add more traits.
Maintaining voice across formats
Blog posts, landing pages, and support articles can share traits while differing in tone. Document format defaults: blog allows first-person stories from SMEs; landing pages stay second person and imperative; support stays neutral and step-based. Writers should not guess per assignment.
When legal requires specific wording on claims, add those strings to the vocabulary section as required phrasing, not as optional examples. Editors then treat deviations as errors, not style preferences.
Run a quarterly voice audit on five random live URLs. Mark drift early before the archive sounds like five different companies. Small glossary updates beat annual rewrites nobody reads.
When onboarding new writers, assign one calibration edit: they revise a paragraph to match two traits using the guide examples. That exercise catches misunderstanding faster than a thirty-minute brand presentation.
Rules writers can execute under deadline
Voice docs fail when they only list personality adjectives. Writers need do and do-not examples: sentence length ranges, humour boundaries, formality, banned claims, and sample rewrites. Keep the guide short enough that people open it.
Test the guide on a real draft. If two editors still disagree, the rule is unclear. Tighten until disagreement is rare. Then share it with freelancers and agencies the same way you share it in-house.
Version the guide when traits change. Writers working from an old PDF is how voice drift starts quietly.
Link the current guide from your CMS template or brief tool so outdated copies are harder to circulate by accident.
Assign one owner to approve guide changes so writers always know which version is current.