A brand voice guide template codifies how your organization sounds across all channels. This walkthrough explains the framework's core components, how to populate each section with defensible choices, and how teams actually use the finished guide to maintain consistency.
A functional brand voice guide template starts with three or four voice attributes—single adjectives or short phrases that describe how the brand sounds. Common choices include conversational, authoritative, witty, empathetic, technical, or irreverent. Avoid vague terms like 'professional' or 'friendly' unless you define them sharply.
Below each attribute, the template should include a definition paragraph explaining what that trait means in your context, followed by a do/don't table. The 'do' column shows a sentence or phrase that exemplifies the attribute; the 'don't' column shows a contrasting alternative that misses the mark. This side-by-side structure removes ambiguity—writers see the boundary, not just the target.
Add a vocabulary section listing preferred terms, banned jargon, and any terminology specific to Canadian English (centre versus center, labour versus labor). If you operate bilingually, note which voice attributes survive translation into French and which require reframing. For example, casual contractions in English may feel too informal in Quebec French professional contexts. Finally, include a channel matrix showing how voice intensity or formality shifts on LinkedIn versus email versus help-center articles.
Filling out the template begins with stakeholder interviews and existing content audits. Pull samples of customer emails, social replies, blog posts, and sales collateral. Identify passages where the brand felt most like itself and passages that felt off-brand, then extract the qualities that explain the difference.
Draft three to five candidate attributes, then test each by writing two versions of the same message—one adhering to the attribute, one violating it. Share both versions with a cross-functional group (marketing, support, product) and ask which version sounds right. This qualitative validation surfaces whether the attribute is defensible or just aspirational.
Document the reasoning behind each choice in the template's definition paragraph. If you chose 'direct' over 'warm', explain the tradeoff: direct serves time-pressed audiences but risks sounding curt in support contexts. If your brand leans technical, note the floor—where expertise tips into jargon that excludes non-specialists. The goal is a guide that explains its own choices so future hires understand not just what the voice is, but why it exists.
Canadian brands serving Quebec face a structural challenge: voice attributes rooted in English idioms often collapse under translation. A brand that sounds 'witty' in English through wordplay or cultural references may need to express wit differently in French, where formal register conventions and audience expectations shift.
The template should include a French voice addendum if applicable, with parallel do/don't examples in both languages. Work with a native French copywriter, not just a translator, to identify which attributes transfer cleanly and which require adaptation. For instance, conversational tone in English might use contractions and sentence fragments, but Quebec French professional norms may favour slightly longer, complete constructions even in casual contexts.
Beyond language, note regional terminology variance. A Vancouver tech startup and a Montreal nonprofit may both target Canadian audiences but face different local references, cultural touchpoints, and regulatory language (CRA versus Revenu Québec). The template's vocabulary section should flag these splits so writers choose the regionally appropriate term without second-guessing.
The do/don't tables are the template's highest-leverage component. Each voice attribute gets its own table with four to six rows, each row showing a paired example. The 'do' example demonstrates the attribute in action; the 'don't' example shows a plausible alternative that diverges in a specific way.
For a 'conversational' attribute, a do example might read: 'We rolled out the update Tuesday—check your dashboard.' The don't version: 'The update was deployed on Tuesday. Please review your dashboard at your earliest convenience.' The contrast isolates the active voice, contraction, and brevity that define conversational here.
Avoid strawman don'ts—exaggerated bad examples that no one would write. The don't column should show reasonable copy that simply prioritizes a different voice trait, making the choice explicit. If your brand is 'empathetic but not apologetic,' the don't example might be an over-apologetic phrase that dilutes the message. The table teaches judgment, not just correctness. Include examples across content types: a landing-page headline, an error message, a social reply, an email subject line. This breadth shows how the attribute scales across contexts.
A rigid voice guide that applies the same intensity everywhere produces robotic copy. The template should include a context matrix: rows for each major channel (blog, email, social, help docs, ads), columns for voice attributes, and cells indicating whether to amplify, maintain, or soften each attribute in that channel.
For example, a brand that is normally 'authoritative' might soften that trait in empathetic support emails but amplify it in thought-leadership blog posts. A 'witty' brand might dial down humor in transactional emails (order confirmations, password resets) where clarity trumps personality. The matrix makes these shifts explicit so writers don't have to guess.
If you serve distinct audience segments—enterprise versus SMB, technical versus non-technical—add a second dimension. An IT infrastructure vendor might use more technical language with DevOps teams but simplify for budget-holding executives. The guide should name these segments and indicate where voice adapts. The goal is controlled flexibility, not blanket rules that flatten nuance.
A brand voice guide only works if it enters the production process. Embed key excerpts—especially the do/don't tables—into content briefs, style-guide wikis, and freelancer onboarding decks. When assigning a blog post, include the relevant voice attribute and a sample sentence rather than expecting the writer to reference a PDF.
Build a review checklist that maps to the guide's attributes. Before publishing, editors ask: Does this piece reflect our conversational tone? Did we avoid the banned jargon listed in the vocabulary section? Is the formality level appropriate for this channel per the context matrix? The checklist turns subjective voice into a series of yes/no checks.
For distributed teams, create a Slack channel or wiki page where anyone can post a sentence and ask whether it aligns with a specific attribute. These micro-discussions reinforce the guide's principles and surface edge cases that refine future versions. The guide is a living document—expect to revisit examples annually as the brand, audience, and market evolve.
Brand voice shifts as organizations grow, enter new markets, or rebrand. The template should include a version number and last-updated date at the top, plus a changelog noting what changed and why. Common evolution triggers include mergers, product-line expansions, negative feedback about tone, or leadership changes that redefine positioning.
Schedule an annual voice audit: pull recent content samples, evaluate adherence to the current guide, and flag any drift. If customer-support teams consistently soften an 'authoritative' attribute to avoid sounding cold, that signals a mismatch between aspiration and reality. Update the guide or adjust training accordingly.
When updating, document the reasoning. If you drop a 'witty' attribute because it felt forced in technical documentation, note that decision so future teams understand the constraint. If you add a French voice addendum after expanding into Quebec, explain the translation challenges you encountered. The guide becomes institutional memory, not just a rulebook.
Three to five attributes is optimal. Fewer than three undershoots the nuance needed to differentiate your brand; more than five overwhelms writers with too many simultaneous constraints. Each attribute should describe a distinct dimension—tone, formality, technical depth, emotional register—so they work together without contradiction. If two attributes feel redundant, combine them or drop the weaker one.
Yes, if you serve Quebec or bilingual markets. Direct translation rarely preserves voice because French and English differ in formality conventions, sentence structure norms, and cultural references. Include a French voice addendum with parallel do/don't examples written by a native French copywriter. Flag which attributes transfer cleanly and which require localized interpretation.
Each table pairs a sentence that exemplifies the voice attribute with a contrasting alternative that misses the mark. The 'don't' example should be plausible, not exaggerated—something a reasonable writer might produce if they prioritized a different trait. Show examples across content types: headlines, error messages, email subject lines, social replies. The goal is to teach judgment by isolating the specific quality that defines each attribute.
Use a context matrix that shows whether to amplify, maintain, or soften each voice attribute per channel. For instance, a brand that is normally witty might dial down humor in transactional emails where clarity matters most. Document these shifts in the template so writers know when to flex. Consistency means recognizable, not monotone—the brand should feel like itself even as intensity varies.
Review annually or when a major change occurs—merger, rebrand, new product line, entry into a new market, or persistent feedback that the current voice feels off. Conduct a voice audit by sampling recent content and checking adherence. If teams consistently deviate from an attribute in practice, update the guide to reflect reality or provide better training. Include a version number and changelog so everyone knows what changed and why.
Embed excerpts into content briefs and review checklists rather than expecting writers to reference the full guide each time. Include the relevant voice attribute and a sample sentence in assignment documents. Build a short checklist that editors use before publishing. Create a Slack channel where teams can ask quick voice questions. The guide should enable faster decisions, not add approval layers.