“Make it confident, warm and distinctive.” The instruction sounds reasonable until another writer has to use it. Should they make a promise? Add a joke? Shorten the explanation? Two people can follow the same adjectives and produce very different drafts.
A usable brand voice brief helps the next person make a writing decision. It gives them a reader, a situation, a small set of observable rules and examples showing why a choice fits. The aim is a working reference they can apply to the next piece of content.
You can start with one page. This guide develops that page through an original teaching example: a team preparing an educational checklist and later correcting a link to it. The team and messages are hypothetical; no customer result is implied.
Begin with the job the words need to do
Before choosing personality traits, write what the reader needs from this message. “Help a colleague prepare a clear handover” gives the writer a concrete task. “Sound premium” leaves the important decisions open.
Add what the reader already knows and what may be uncertain. Someone discovering a resource needs a reason to open it. Someone facing a broken link needs the corrected destination and an explanation of what changed. The brand may be the same while the immediate writing task differs.
Separate voice from situational tone
Mailchimp’s official Voice and Tone guide distinguishes a relatively stable voice from tone that changes with context and the reader’s state of mind. It is a useful editorial distinction from one brand’s own practice, not evidence that its personality should become yours.
For your brief, decide which principles should survive a change of situation. For example, a teaching voice might consistently name the action and explain unfamiliar terms. Its tone can be inviting when introducing a resource and more direct when correcting an error.
Do not prescribe how the reader must feel. “The reader may be unsure which version to use” is a working hypothesis to consider. “Our audience is frustrated” requires evidence if presented as a finding about real people.
Turn each adjective into an instruction
Choose a few rules that a writer can recognise in a sentence. The following set is an original example for the hypothetical educational team; it is not Ovydo’s approved voice charter.
| Intention | Observable writing rule | Question during review |
|---|---|---|
| Clear | Name the thing the reader can prepare or check | Can someone identify the task without opening another document? |
| Considerate | Give enough context to act without blaming the reader | Does the instruction explain what changed or what is needed? |
| Precise | Keep a claim within its evidence and conditions | Does the sentence promise more than the source establishes? |
Source: original editorial template, 16 October 2026. These are proposed rules, not measured causes of engagement or conversion.
“Clear” now has something to mean. A reviewer can point to an unnamed task rather than asking for another abstract round of “more clarity”. The writer can also disagree usefully: perhaps the title names the task, while the next sentence needs an example.
Microsoft’s official style and voice tips provide another reference: lead with important information and make next steps evident. That is guidance for Microsoft content. Here it supports a question to consider, not a requirement to adopt its full style system.
Show a choice and preserve its reason
Examples teach more when the brief explains what the writer should notice. An isolated approved sentence may otherwise become a phrase copied into situations where it no longer fits.
Situation one: introduce a resource
Initial teaching draft: “Transform your content forever with our ultimate checklist.”
Proposed revision: “Use the checklist to record the version, reviewer and next action before handing over a post.”
The revision names the work the reader can do. It replaces an unlimited promise with the actual purpose of the teaching resource. The reason is precision, not a claimed improvement in click-through rate. No campaign has been sent and no response has been measured.
Notice that the revised sentence could still be wrong if the checklist did not contain those fields. A voice rule never removes the need to inspect the resource being described. Attach the content reference or source the writer should use.
Situation two: correct a link
Initial teaching draft: “Oops! Looks like someone clicked the wrong thing.”
Proposed revision: “The earlier link pointed to the previous checklist. Use the updated link for the current version.”
The second message gives the reader a next step and describes the error without assigning blame. It assumes, within this hypothetical exercise, that the destination has been verified. In real copy, verify the old and new links before making that statement.
The voice rules remain recognisable across both situations. The correction uses less promotional energy because the reader’s immediate task is recovery. You do not need a wholly different brand personality to explain a mistake plainly.
Give factual claims their own boundary
A brief should distinguish three kinds of instruction: a style preference, an approved public phrase and a factual statement requiring evidence.
“Use everyday words” is a writing preference. An exact brand signature is controlled wording. “Every colleague can publish to every account” is a capability claim. Making the last sentence sound more confident cannot resolve whether it is true.
Record the limits alongside the example. If availability depends on account type or permission, the writer needs that condition. If the evidence is missing, leave a question for the responsible owner or remove the claim. Do not ask a voice document to settle a product question.
For Ovydo-specific work, the retained signature is Give your ideas the world. Keep that phrase in English. The surrounding explanation can be localised; using the signature does not establish legal clearance or product availability.
Assemble a brief someone can pick up
Here is a filled teaching brief. Its content and roles are examples, not an approval record.
| Field | Example entry |
|---|---|
| Reader | A colleague preparing a social content handover |
| Situation | Introducing an educational checklist |
| Purpose | Help the reader identify what to record before review |
| Voice rules | Name the task; explain what the reader needs; bound factual claims |
| Tone for this situation | Inviting, direct and free of artificial urgency |
| Original example | “Use the checklist to record the version, reviewer and next action before handing over a post.” |
| Why this wording | It describes the task rather than promising an unspecified transformation |
| Terms to preserve | Names of actual fields and any separately approved brand wording |
| Claim boundary | No guarantee of time saved, performance or software automation |
| Working reference | Link to the real resource and its current revision, to be supplied |
| Review owner and version | Real assignment and revision to be completed by the team |
Source: original teaching example, 16 October 2026. The blank assignment is intentional; it is not a fictional review.
Keep the brief close to the content rather than making people search through several documents. A longer style guide can still hold grammar, naming conventions and specialist rules. The short brief selects what matters for this task and points to those references when needed.
Adapt the decision into another language
An adaptation should preserve the task, strength of the claim and reason for the wording. It does not need to preserve English sentence order.
For example, “Record the next action before you hand over the post” can become “Avant de transmettre le contenu, notez la prochaine action attendue.” The French instruction changes the rhythm while keeping the same responsibility. It should not become “Automatisez tous vos passages de relais”, which introduces a new capability claim.
Mailchimp’s Writing for Translation guide advises avoiding idioms and other expressions that complicate translation. For your brief, preserve an explanation of the intended meaning so the translator can choose natural phrasing without strengthening the promise.
Revise the rule when the example exposes a gap
During ordinary editorial review, note where the brief fails to answer a real writing question. Perhaps “direct” works for a checklist but needs a clearer boundary in a correction. Update the rule, add a relevant example and retain the reason for the change.
Distinguish mandatory corrections from preferences. A broken link or unsupported claim needs resolution. Two equally accurate openings may be a style choice. This distinction helps the next writer understand whether they are fixing an error or exploring an alternative.
Ovydo’s public Brand Kit presentation and Studio presentation can be read with this handover in mind: which references would the next person need beside the content? These public pages do not prove that a voice rule is stored, enforced or available in a particular workspace.
Checklist for a usable voice brief
- ☐ The reader, situation and writing task are explicit.
- ☐ Each selected trait has an observable rule.
- ☐ Examples are original and match the actual resource.
- ☐ The reason for each important revision is preserved.
- ☐ A correction has a usable next step.
- ☐ Product facts and style preferences are distinguished.
- ☐ Approved exact wording is identified separately.
- ☐ Translation preserves the meaning and claim boundary.
- ☐ A real review owner and revision will be assigned.
- ☐ Unanswered questions remain visible rather than becoming invented rules.
Frequently asked questions
How many voice traits should a brief contain?
Use a small set that the writer can apply to the task. Three are used in this teaching example, not prescribed as a universal optimum. Add a rule when it resolves a concrete ambiguity.
Should the voice change on every social network?
Review the situation, reader and format. You can adapt length and tone while retaining the same principles. No universal platform personality or engagement benefit is established here.
Can AI use this brief?
It can receive the rules and examples as working context, where the team’s data policy allows. Its output still needs factual and editorial review. Supplying a brief does not certify the draft’s accuracy or originality.
Does an approved example remain approved forever?
Preserve its scope and revision. A new fact, product condition or context can require a new decision. Keep the example’s reason so people can judge when it still applies.
Sources and limits
Official guidance consulted 16 October 2026; high confidence in the attributed guidance, no experimental validation of this template.
- Mailchimp — Voice and Tone, update date not established; the distinction between voice and contextual tone is attributed to Mailchimp.
- Microsoft — Top 10 tips for style and voice, displayed update 6 July 2026; public body readable despite an authorisation banner.
- Mailchimp — Writing for Translation, update date not established; used for the limited advice on translatable language.
- Ovydo Brand Kit and Studio, public presentations retrieved on the consultation date; update dates not established. The exact Ovydo signature is a PO decision supplied to this editorial work, not a supplier claim.
The brief, messages and revision reasons are original recommendations. They establish no customer research finding, performance effect or approved Ovydo voice charter.
Sources and editorial references are included in the guide.
