Build a brand voice brief an AI writer can follow
Turn vague brand adjectives into useful writing guidance with approved examples, audience context and a simple review checklist.
“Friendly, bold and human” can describe almost any brand. An AI writer needs to know what those words mean in an actual sentence.
A good voice brief combines the audience, the job of the message, examples and boundaries. It should help someone choose words without forcing every piece of writing into the same template.
Start with the reader's situation
Explain who is reading and what they are trying to do. A first visit to your homepage, a failed payment notice and a release announcement need different tones even when they come from the same company.
State the desired action and what the reader already knows. This prevents the assistant from repeating background or introducing jargon before it is useful.
Replace adjectives with examples
For each principle, give an approved example and explain the choice. If “direct” means leading with the action, show that:
Your invitation expired. Request a new one to join the workspace.
Then explain why a longer version would get in the reader's way. The reason helps the writer apply the principle in a new situation rather than copying a sentence mechanically.
Include examples across a few formats. A product page alone does not teach an assistant how to write a helpful support reply.
Separate voice from factual permission
The brief should not become an accidental source of product claims. Link to current product information, approved positioning and any wording that needs review. Mark hypothetical example claims as examples.
Add a short list of phrases you avoid, but explain the underlying concern. “Avoid unsupported superlatives” is more transferable than banning one word and leaving its synonyms untouched.
Review for usefulness
A practical review asks:
Does the opening address the reader's task?
Is every factual claim supported?
Does the tone fit the situation?
Can a sentence be removed without losing meaning?
Is the next action clear?
Save approved edits back into the examples collection with their context. A rejection without an explanation teaches very little. A few well explained revisions can make the next draft easier for both people and AI to get right.