brand voice template examples

Standard Operating Procedure: Establishing Organizational Tone and Style

Document Control

• Document ID: SOP-BRAND-VOICE-001
• Version: 1.0.0
• Effective Date: [YYYY-MM-DD]
• Review Cycle: Annual

1. Purpose & Scope

This document provides the framework for defining, documenting, and implementing a consistent linguistic identity for [Company Name]. The scope includes all internal communications, external marketing assets, and customer support documentation.

2. Prerequisites

• Access to the [Central Document Repository].
• Current [Company Name] Mission Statement and Core Values.
• Stakeholder access to the [Brand Strategy Workspace].
• [Software Name] for collaborative editing and version control.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Discovery and Audit

• Gather existing collateral from [Department Name].
• Identify recurring linguistic patterns in current communications.
• Define the [Company Name] "Personality Archetype" (e.g., The Sage, The Hero, The Creator).

Phase 2: Defining the Linguistic Pillars

• Establish the Primary Tone: [e.g., Authoritative vs. Approachable].
• Establish the Secondary Tone: [e.g., Technical vs. Conversational].
• Create the "We Are / We Are Not" matrix:
  • We are [Adjective 1], but we are not [Adjective 2].
  • We are [Adjective 3], but we are not [Adjective 4].

Phase 3: Drafting the Style Guide

• Document specific vocabulary preferences: [List preferred industry terms].
• Document forbidden jargon or prohibited phrases: [List banned terms].
• Define grammatical standards (e.g., Oxford Comma, Active vs. Passive voice).
• Create three distinct examples of the voice applied to:
  • [Example 1: Customer-facing announcement]
  • [Example 2: Internal policy update]
  • [Example 3: Social media engagement]

Phase 4: Implementation and Governance

• Distribute the approved guide to all [Department Name] leads.
• Schedule a training session for [Date].
• Set a recurring audit date for [Date] to ensure adherence.

5. Quality Assurance, Pro-Tips, and Pitfalls

• QA Checklist: Ensure all examples pass the "Read Aloud" test; if it sounds robotic, adjust for natural cadence.
• Pro-Tip: Focus on the "Why" behind the voice. Employees adopt standards faster when they understand the psychological impact on the customer.
• Common Pitfall: Over-complicating the guide. Keep it under [Number] pages to ensure it remains a practical reference rather than a theoretical document.

6. FAQs

Q: How do we handle changes to the tone as the market evolves? A: Treat the guide as a living document. Submit proposed changes to the [Brand Lead] for review during the quarterly [Name of Meeting].

Q: What should I do if a specific channel requires a different tone? A: You may add an "Adaptive Tone" section to the guide, provided it maintains the core [Company Name] values. Document these variations as "Sub-Voices."