Brand Voice and Editorial Style

Tone-by-Situation Matrix

Adapt tone consistently for success, error, urgency, apology, uncertainty, refusal, sensitive news, and recovery without changing the underlying facts.

Free editable Markdown · Content designers, brand teams, and customer communications teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Situation profile

Situation: [Success, error, delay, urgency, apology, uncertainty, refusal, sensitive news, or another]
Reader context: [What has happened?]
Consequence: [Low, moderate, or high, with explanation]
Organization’s responsibility: [What it owns or controls]
Reader’s immediate need: [Information, action, remedy, reassurance, or time]
Urgency: [Action window]
Channel: [Interface, email, status page, support, public statement, or another]
Required reviewers: [Editorial or specialist roles]

Tone direction

Emphasize: [Calm, direct, candid, respectful, encouraging, or another]
Reduce: [Playfulness, celebration, detail, persuasion, or another]
First message element: [What comes first]
Required facts: [What must be stated]
Action or remedy: [Specific next step]
Uncertainty treatment: [Known, unknown, and next update]
Do not use: [Blame, false certainty, jokes, euphemism, or another]
Voice allowance: [Where brand personality is still suitable]

Examples

Suitable example: [Draft]
Why it works: [Order, responsibility, clarity, and tone]
Unsuitable example: [Draft]
Why it fails: [Implication or reader burden]
Revised example: [Improved version]

The tone does not minimize the consequence.
Essential action is visible before promotional language.
Responsibility is stated accurately.
The message does not assume or instruct an emotion.

Localization and review

Formality note: [Relationship and locale]
Idiom or humor risk: [What should not be translated literally]
Length or interface constraint: [Space and accessible alternative]
Approval owner: [Role]
Calibration sample: [Real content to test]
Review trigger: [Incident, feedback, channel, or audience change]

How to use this template

Inventory recurring situations where audience need, urgency, power, or consequence changes the appropriate tone.
For each, record facts, required action, emotional risk, channel constraints, and voice qualities to emphasize.
Define message order, mandatory elements, wording to avoid, and legitimate room for personality.
Create positive and negative examples, then review for accuracy, accessibility, culture, and specialist requirements.
Calibrate with real drafts, publish the matrix, and revise it using feedback and incident evidence.

Diagnose the reader’s situation first

Tone should respond to what happened, what the reader needs now, and how much power the organization holds. A success confirmation can be warm and brief; a payment failure needs clarity without blame; a safety alert needs direct action before brand personality; an apology needs responsibility and remedy rather than cheerful reassurance. Avoid guessing a reader’s emotion. Describe the observable situation, consequence, urgency, and information need, then choose qualities such as calm, candid, focused, respectful, or encouraging. The same voice principles can remain recognizable while emphasis changes.

Define order and boundaries, not adjectives alone

“Friendly but professional” gives writers little help. For each situation, specify what comes first, what must be stated, what can wait, and what language is unsuitable. In an error, name what happened, whether work was saved, and the next action before adding empathy. In uncertainty, separate confirmed facts from estimates and give the next update time. In an apology, identify responsibility, effect, repair, and prevention without using passive voice to hide the actor. Provide contrasting examples and explain why one works.

Calibrate channels and cultures

Space, timing, privacy, permanence, and reply options affect tone. A button label, public incident update, personal email, support chat, and formal letter cannot use identical wording. Localization should preserve communicative intent rather than copying humor, idiom, formality, or sentence length. Test sensitive messages with relevant reviewers and affected perspectives where appropriate. Audit real content periodically because teams often become playful in failures or bureaucratic in apologies despite written rules. Update the matrix after incidents, repeated feedback, or new channel constraints.

See the fields in context

Fictional example: delayed file conversion

The file service and incident below are invented.

Situation: A conversion is delayed, but the original file remains safe.
Emphasize: Calm clarity and next action; reduce celebration and humor.
Suitable message: “Your original file is safe. Conversion is taking longer than expected. You can wait here or download the original now; we’ll update this page by 14:00 UTC.”
Unsuitable message: “Oops! Our robots are having a slow day,” because it hides status and trivializes lost time.
Trigger: If files become unavailable, move to the incident tone and qualified review path.

Frequently asked questions

Is tone different from brand voice?

Voice is the durable character and principles of communication. Tone adapts those principles to a situation. A candid voice may sound celebratory after success and restrained during harm while remaining truthful in both.

Should error messages apologize?

Apologize when the organization caused meaningful inconvenience or harm, but do not use apology as filler. State what happened, impact, next action, and remedy. Avoid blaming the reader for a system condition.

Can humor appear in interface content?

Only where it cannot obscure action, trivialize failure, exclude readers, or age poorly through repetition and translation. High-stress, sensitive, or consequential moments usually need direct respectful language.

How should uncertainty sound?

Separate confirmed facts, estimates, and unknowns. Avoid false precision or vague reassurance. Give the next update time or decision point and name what the reader can safely do now.