Brand Voice and Editorial Style

Brand Example Library

Collect approved writing samples and explain the voice principle, situation, audience need, constraints, and decision each example demonstrates.

Free editable Markdown · Brand editors, copywriters, and content designers · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Example identity

Entry ID: [Durable identifier]
Situation: [What happened?]
Audience need: [What must the reader understand or do?]
Channel and format: [Where it appears]
Source: [Published link, approved draft, or fictional label]
Permission: [Reuse and access status]
Product or policy version: [If facts can change]
Owner: [Brand or editorial role]

Approved sample

Example text: [Insert a short approved passage]
Voice principle: [Rule demonstrated]
Tone choice: [Why it suits this situation]
Annotation 1: [Specific wording and effect]
Annotation 2: [Order, evidence, or qualification]
Deliberate omission: [What was kept out and why]
Use this when: [Context]
Do not copy when: [Boundary]

Contrast and localization

Weak contrast: [Invented unsuitable version]
Why it fails: [Reader effect]
Localization intent: [Meaning, formality, and priority]
Literal-translation risk: [Idiom, humor, or structure]

Names and facts remain current.
The sample includes no unnecessary personal data.
The note teaches a principle instead of cosmetic mimicry.

Lifecycle

Tags: [Situation, channel, audience, principle, language]
Approved by: [Name or role]
Effective date: [YYYY-MM-DD]
Review trigger: [Policy, product, style, or feedback change]
Retirement note: [Complete when obsolete]

How to use this template

Identify a recurring writing decision and select a permitted, accurate sample that demonstrates it.
Record audience, situation, channel, source, constraints, and the governing voice principle.
Annotate the specific language and structural choices that make the example effective.
Add boundaries, a contrasting weak approach, localization notes, approval, and discoverable tags.
Publish the entry, observe how teams use it, and retire or revise it when its trigger occurs.

Select examples that teach a decision

Choose samples that resolve a recurring writing problem: explaining uncertainty, giving an error action, introducing a technical term, refusing a request, or balancing warmth with urgency. Attractive prose without a reusable lesson adds noise. Preserve enough surrounding context to show the audience, channel, consequence, and constraints. Include short passages rather than entire assets unless the full sequence matters. When an example comes from published work, record its source, date, permission, and whether changing product facts make it unsafe to reuse.

Annotate why the wording works

Point to specific choices and connect each to an approved voice or tone rule. Explain order, verbs, evidence, qualification, sentence length, and what the writer deliberately omitted. Add an unsuitable contrast when it reveals a likely failure, but avoid mocking real colleagues. Do not annotate with circular statements such as “This sounds human” or “This is on brand.” A useful note says the message names the user’s saved work before the recovery action because loss is the reader’s first concern.

Curate the library over time

Tag examples by situation, channel, audience, principle, language, and risk so contributors can find the closest case. Keep a balanced collection; success messages should not crowd out errors, apologies, limitations, and complex explanations. Localized examples need their own review because rhythm, formality, and idiom do not transfer mechanically. Assign owners and review triggers. Retire samples when facts, interfaces, policy, audience expectations, or style guidance change, while preserving historic decisions in version history.

See the fields in context

Fictional example: saved draft after an error

The interface and saved draft below are invented.

Approved sample: “Your draft is saved. We couldn’t publish it because the connection ended. Check your connection, then select Publish again.”
Principle: Put the reader’s highest concern before the technical explanation.
Annotation: The passage confirms safety, names the failed action, and gives one recovery step without blame.
Boundary: Do not reuse it if the system cannot verify that a draft was saved.
Tag: Error, recovery, interface, calm-direct.

Frequently asked questions

How many examples should a library contain?

Enough to cover recurring consequential situations, not every possible sentence. Start with gaps writers regularly debate and improve discoverability before adding volume. Remove redundant entries that teach the same decision.

Can competitor copy appear as a negative example?

Avoid copying protected or identifiable material merely to criticize it. Create a short fictional contrast that demonstrates the issue, or discuss the pattern in your own words with appropriate attribution when analysis requires a real source.

Should examples be copied verbatim?

Usually no. Apply the principle to the new facts, audience, and channel. Verbatim reuse can preserve obsolete claims or make unrelated situations sound formulaic.

Who approves a localized example?

A reviewer with language, regional, and brand context should approve it, with subject review for consequential facts. The English entry can explain intent but cannot validate another language’s tone by itself.