Tone of Voice Guide Template

Purpose

This recipe produces a complete Tone of Voice Guide that defines your brand's voice attributes and positions your tone across four measurable dimensions — formal/casual, serious/playful, respectful/irreverent, and enthusiastic/matter-of-fact. The output includes slider positions for each dimension, do/don't writing examples, a content-type tone mapping matrix, and before/after writing samples — ready for team distribution and AI tool configuration. [src1]

Prerequisites

• Brand mission and values — documented positioning statement or at minimum a clear articulation of what the brand stands for and who it serves
• Target audience profiles — at least 2-3 audience personas with demographics, communication preferences, and emotional needs
• Existing content samples — 5-10 representative pieces across content types (marketing page, product UI text, support email, social post, error message)
• Document editor — Google Docs, Notion, Confluence, or Word
• Stakeholder access — ability to get feedback from marketing, product, support, and leadership teams

Constraints

• Voice is constant; tone adapts. The brand voice (personality attributes) never changes. Tone shifts based on context, audience emotional state, and content type. Conflating the two produces inconsistent writing. [src3]
• Abstract scales without concrete examples are worthless. Every tone dimension position must include at least 3 do/don't pairs with real sentences. [src1]
• Content type coverage must include at minimum: marketing copy, product UI microcopy, error messages, customer support, and legal/compliance text. [src4]
• Tone guides require validation against real content. Build the guide, then rewrite 5-10 existing pieces using it.
• Humor in error states is high-risk. Users in distress need clarity and empathy, not jokes. [src2]

Tool Selection Decision

Which path?
├── Solo creator or small team, no existing guidelines
│   └── PATH A: Lean Guide — 1-page tone card + examples
├── Small-to-medium team, some informal guidelines
│   └── PATH B: Standard Guide — full document with all 4 dimensions
├── Large team, high content volume, needs governance
│   └── PATH C: Comprehensive Guide — full guide + decision matrix + training materials
└── Enterprise, multiple sub-brands or regions
    └── PATH D: Scalable System — modular guide + per-channel tone profiles + AI tool config

Execution Flow

Step 1: Voice Attribute Discovery

Duration: 45-60 minutes · Tool: Document editor

Define 3-5 core voice attributes that describe your brand's personality. Voice is the constant — it does not change across content types or situations. [src3]

Voice Attribute Workshop:
──────────────────────────────────────────────────

1. List 5 adjectives that describe how your brand SHOULD sound:
   _________, _________, _________, _________, _________

2. List 5 adjectives your brand should NEVER sound like:
   _________, _________, _________, _________, _________

3. "We are _________ but not _________" (complete 3-5 pairs):
   • We are confident but not arrogant
   • We are _________ but not _________
   • We are _________ but not _________

4. If the brand were a person, how would colleagues describe them?
   _____________________________________________

Example outputs:
  Mailchimp: "plainspoken, genuine, has a sense of humor"
  Slack: "clear, concise, human — like a friendly, intelligent coworker"
  GOV.UK: "direct, informative, authoritative but never bureaucratic"

Verify: Voice attributes pass the "but not" test — each attribute has a clear boundary. · If failed: Interview 3 team members about what makes the brand's communication different from competitors.

Step 2: Position on the Four Tone Dimensions

Duration: 45-60 minutes · Tool: Document editor + visual slider

Position your brand on each of the four NN/g tone dimensions. Each dimension is a spectrum from 1-10. Most brands do not sit at extremes. [src1]

TONE DIMENSION POSITIONING
══════════════════════════════════════════════════

Dimension 1: FORMAL ←──────────→ CASUAL
Position: ___/10  (1 = very formal, 10 = very casual)

  1-3 (Formal): "We regret to inform you that your transaction
                  could not be processed at this time."
  4-6 (Neutral): "Your transaction didn't go through.
                  Here's what you can do."
  7-10 (Casual): "Hmm, that didn't work. Let's try again —
                   here are your options."

Dimension 2: SERIOUS ←──────────→ PLAYFUL
Position: ___/10  (1 = very serious, 10 = very playful)

Dimension 3: RESPECTFUL ←──────────→ IRREVERENT
Position: ___/10  (1 = very respectful, 10 = very irreverent)

Dimension 4: MATTER-OF-FACT ←──────────→ ENTHUSIASTIC
Position: ___/10  (1 = very matter-of-fact, 10 = very enthusiastic)

Verify: Each dimension has a specific numerical position AND at least one example sentence written in your voice. · If failed: Collect 10 existing content samples and independently rate each on all four dimensions. Average the ratings.

Step 3: Build Do/Don't Examples for Each Dimension

Duration: 60-90 minutes · Tool: Document editor

For each dimension, create 3-5 paired examples showing what your tone sounds like versus what it does not sound like. Use your actual products, features, and scenarios. [src3]

DO/DON'T EXAMPLE FORMAT
══════════════════════════════════════════════════

DIMENSION: [Formal/Casual — Position: 7/10 (casual)]

Context: Welcome email
  ✓ DO: "Hey [Name]! Welcome aboard. Here's the quick
         tour to get you started."
  ✗ DON'T: "Dear [Name], Thank you for registering your
            account. Please find enclosed your onboarding
            documentation."
  WHY: We're casual and direct. Formal language creates
       distance we don't want with new users.

Context: Payment failure notification
  ✓ DO: "Your payment didn't go through. Update your card
         details and we'll try again."
  ✗ DON'T: "Whoopsie! Your payment took a tumble.
            No worries though!"
  WHY: Even at position 7/10 casual, payment issues require
       clarity over personality.

Verify: Every do/don't pair references a real content type you actually produce. · If failed: If examples feel forced, your dimension positions may be wrong. Return to Step 2.

Step 4: Create the Content-Type Tone Map

Duration: 45-60 minutes · Tool: Spreadsheet or table

Different content types require different tone positions. An error message and a marketing email should not sound the same. [src4]

CONTENT-TYPE TONE MAP
══════════════════════════════════════════════════

Baseline tone: F:7 S:6 R:4 E:7

Content Type        │ F/C │ S/P │ R/I │ M/E │ Notes
────────────────────┼─────┼─────┼─────┼─────┼──────────────
Marketing landing   │  7  │  6  │  4  │  8  │ Enthusiasm up
Blog post           │  8  │  6  │  5  │  7  │ Most casual
Social media        │  8  │  7  │  5  │  8  │ Most playful
Product UI copy     │  6  │  4  │  3  │  5  │ Clarity first
Onboarding flow     │  7  │  5  │  3  │  7  │ Warm, guiding
Error messages      │  5  │  2  │  2  │  3  │ Serious, clear
Support emails      │  6  │  3  │  2  │  5  │ Empathetic
Legal/compliance    │  2  │  1  │  1  │  2  │ Formal, precise
API documentation   │  3  │  2  │  2  │  3  │ Technical
Press releases      │  3  │  3  │  2  │  5  │ Professional
Sales proposals     │  4  │  3  │  2  │  6  │ Confident

Key: Tone adapts to user emotional state.
 • User is happy → enthusiasm OK
 • User is frustrated → serious + empathetic
 • User is deciding → clear + confident
 • User is worried → respectful + precise

Verify: Every content type in the map corresponds to content your team actually produces. · If failed: Write the same message three ways and ask 3 team members which feels right.

Step 5: Write Before/After Samples

Duration: 60-90 minutes · Tool: Document editor

Take 5-10 real pieces of existing content and rewrite them using your new tone guide. This validates the guide and creates training material. [src7]

BEFORE/AFTER REWRITE FORMAT
══════════════════════════════════════════════════

Content type: [Error message]
Tone position: F:5 S:2 R:2 E:3

BEFORE (existing):
"Error 404: The requested resource was not found on this
server. Please verify the URL and try again."

AFTER (new tone):
"We couldn't find that page. It may have been moved or
the link might be outdated. Try searching for what you
need, or head back to the homepage."

WHAT CHANGED:
- Removed technical jargon
- Added helpful next action
- Shifted from passive to active voice
- Kept serious tone — no jokes in error states

Verify: Show before/after pairs to someone unfamiliar with the project. They should identify the tone difference without explanation. · If failed: If rewrites feel indistinguishable, push dimension positions further from center.

Step 6: Assemble and Distribute the Guide

Duration: 30-60 minutes · Tool: Document editor

Compile all components into a single, accessible document with sections: introduction, voice attributes, tone dimensions, do's and don'ts, content-type tone map, writing samples, word lists, and quick reference card.

DISTRIBUTION CHECKLIST:
  [ ] Share with all content creators
  [ ] Present to marketing/product/support leads
  [ ] Pin in team communication channels
  [ ] Add to onboarding materials
  [ ] Configure AI writing tools with tone settings
  [ ] Schedule quarterly review (set calendar reminder)

Verify: At least 3 people from different teams have reviewed and confirmed the guide reflects the brand accurately. · If failed: Run a calibration workshop with 10 content samples rated independently.

Output Schema

{
  "output_type": "tone_of_voice_guide",
  "format": "document",
  "sections": [
    {"name": "voice_attributes", "type": "object", "description": "3-5 brand personality attributes with but-not boundaries", "required": true},
    {"name": "tone_dimensions", "type": "array", "description": "4 dimensions with position (1-10), rationale, and example sentences", "required": true},
    {"name": "do_dont_examples", "type": "array", "description": "3-5 do/don't pairs per dimension with context and reasoning", "required": true},
    {"name": "content_type_map", "type": "table", "description": "Matrix of content types x 4 dimensions with numerical positions", "required": true},
    {"name": "writing_samples", "type": "array", "description": "5-10 before/after rewrites demonstrating the tone in practice", "required": true},
    {"name": "word_lists", "type": "object", "description": "Preferred and avoided words with context", "required": false},
    {"name": "quick_reference", "type": "document", "description": "One-page summary card for daily use", "required": true}
  ],
  "expected_sections": "7",
  "sort_order": "logical flow (voice then dimensions then examples then application)",
  "deduplication_key": "voice_attributes"
}

Quality Benchmarks

If below minimum: The guide is too thin to be useful. Prioritize adding do/don't examples and content-type mapping — these are the sections teams reference daily.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Defining voice and tone as the same thing

Many guides use "voice" and "tone" interchangeably, producing documents that either change personality per channel (inconsistent) or apply the same rigid tone everywhere (robotic error messages, inappropriately cheerful billing warnings). [src3]

Correct: Voice is personality (constant); tone is mood (adaptive)

Define voice attributes once. Then map tone adaptations per content type and user emotional state. Mailchimp exemplifies this — their voice is always plainspoken and genuine, but tone shifts from enthusiastic in onboarding to serious in account issues.

Wrong: Building scales without concrete examples

A slider showing "formal to casual" at position 7 is meaningless without sentences showing what position 7 actually sounds like. Teams interpret abstract scales differently, producing inconsistent output. [src1]

Correct: Every scale position paired with 3+ real examples

Each dimension position must include do/don't sentence pairs using your actual product names, features, and scenarios.

Wrong: Ignoring context-specific tone adaptation

Applying the same playful tone to a marketing landing page and a payment failure notification alienates users. Inappropriate humor in error states significantly damages brand perception. [src2]

Correct: Map tone to user emotional state, not just content type

Error states require seriousness and empathy regardless of overall brand playfulness. Build a content-type tone map that accounts for the user's likely emotional state at each touchpoint.

When This Matters

Use this recipe when a brand needs to create or overhaul its written communication guidelines. It produces a structured, actionable tone guide — not a branding document. The output is designed for daily use by writers, designers, product managers, and AI writing tools. Essential when scaling content production beyond one writer, onboarding new team members, or configuring AI content generation tools to match brand voice.