Brand voice guidelines become useful when they tell a writer what to do, what to avoid and how to adapt to the reader’s situation. A list such as “bold, human, expert” is not enough. Teams need observable principles, language rules, before-and-after examples, tone guidance and a clear way to resolve new questions.
Define voice as a set of behaviours
Voice is the consistent character of the organisation’s language. Tone is how that voice adjusts to context. The distinction prevents two common mistakes: making every message sound identical, or letting each writer invent a different personality.
Choose three or four voice principles. For each one, describe:
- what the principle means for your audience;
- two or three writing behaviours;
- what it does not mean;
- a short example in context.
“Confident” might mean lead with a clear recommendation, use direct verbs and explain the basis for a claim. It should not mean certainty where evidence is limited, dismissing a customer’s concern or using inflated language.
“Warm” might mean acknowledge the reader’s situation, use natural language and make the next step feel manageable. It should not mean forced humour, excessive exclamation marks or pretending a serious problem is easy.
When a principle contains a tension, preserve it. “Expert but plain-spoken” is more instructive than “expert” because it makes clear that expertise should reduce complexity for the reader rather than display it.
Show how tone changes with the situation
A stable voice can support different tones. A launch announcement, payment failure and security notice should not carry the same energy.
Build a small tone matrix around situations the team writes for regularly. Useful dimensions include:
- routine or high stakes;
- positive, neutral or difficult;
- early exploration or committed customer;
- marketing, product, support or legal context.
For each situation, explain what to increase and reduce. During onboarding, the tone may be encouraging and concise. During an outage, it should become calm, factual and accountable. In a sales page, it may be energetic but still specific. In an overdue-payment message, it should be direct without becoming cold or accusatory.
Do not create a different personality for every channel. The customer may move from an advert to a demo, product interface and support conversation in one day. The tone can change; the organisation should remain recognisable.
Write rules that remove everyday friction
Voice principles guide judgement, while editorial rules settle repeat questions. Keep the rules focused on choices that affect clarity, trust and recognition.
Include guidance for:
- whether to use “we”, the company name or another form;
- how to address the reader;
- contractions and level of formality;
- active and passive voice;
- sentence and paragraph length;
- technical terms and acronyms;
- capitalisation and punctuation;
- inclusive language;
- numbers, dates and currencies;
- calls to action, error messages and claims;
- preferred and avoided terminology.
Explain the reason when it helps people apply the rule elsewhere. “Use sentence case for headings because it is easier to scan” is more transferable than a bare instruction.
Avoid turning the guide into a general grammar handbook. Link to an established house style for low-value edge cases, and keep the brand-specific decisions easy to find.
Illustrative example
Imagine a business finance platform with the voice principle steady clarity.
The guideline might say:
Lead with what happened, state the consequence in plain English and give the safest next action. Do not use playful language when money is delayed or access is restricted.
Before:
Oops! Your transfer hit a little snag. Hang tight while our wizards work their magic.
After:
Your transfer has not been sent. We are checking the issue now. You do not need to try again; we will update this screen by 14:00 GMT.
The second version is not “less branded”. It expresses steadiness through useful information. In a lower-stakes success message, the same brand could sound lighter without abandoning clarity.
Build examples around real work
Generic examples are difficult to transfer. Collect material from the places where your team writes most often:
- homepage and landing-page copy;
- sales emails and proposals;
- product labels, empty states and errors;
- support responses;
- social posts;
- reports or insight pieces;
- recruitment and internal communications.
For each, show a weak draft, a stronger draft and a short explanation. The explanation matters: it teaches the choice instead of encouraging imitation.
Add message patterns rather than fixed scripts. A useful service-recovery pattern might be: acknowledge the impact, state what is known, explain what happens next and give a time for the next update. Writers can adapt that pattern to different incidents while preserving the voice.
Include examples of what not to do carefully. Avoid exaggerated bad copy that nobody would write. Use realistic mistakes—too much jargon, a buried action, unsupported enthusiasm or a tone that ignores the reader’s circumstances.
Make the guide fast to use
The best voice guide is not the most comprehensive one; it is the one people consult while working. Create layers:
- A one-page summary for everyday use.
- A fuller guide with principles, tone and examples.
- A terminology list for searchable decisions.
- Templates or checklists inside the tools where writing happens.
Give each principle a memorable name, but prioritise clarity over cleverness. Add navigation and descriptive headings. Keep examples copyable. If a team uses a content management system or design system, place relevant guidance beside components such as buttons, form errors and notifications.
Test the guide by giving the same brief to several people. If their drafts vary in ways that contradict the intended voice, the problem may be the guidance, not the writers. Ask what they could not decide and revise the guide around those gaps.
Govern the voice without creating a bottleneck
Assign an owner who maintains the guide, but do not require that person to approve every sentence. The goal is distributed confidence.
Create a lightweight process:
- writers flag unanswered questions;
- the owner records decisions and useful examples;
- recurring issues become guidance;
- high-risk content receives appropriate review;
- the team reviews the guide when the audience, product or brand changes.
Separate voice review from personal taste. Feedback should name the relevant principle, audience need or context: “The key action appears after the explanation” is actionable; “This does not sound punchy enough” is not.
Your useful next step
Choose three pieces of current copy from different customer moments. Highlight where they sound inconsistent or create unnecessary effort. Draft one voice principle that would improve all three, with two behaviours, one boundary and a before-and-after example. If colleagues can apply it to a fourth piece without further explanation, you have the start of a usable guide.