brand voice templates

Standard Operating Procedure: Establishing and Maintaining Corporate Communication Personas

Document Control

• Document ID: SOP-COMMS-001
• Version: 1.0.0
• Effective Date: [__________]
• Review Cycle: Annual

1. Purpose & Scope

This document outlines the systematic process for defining, documenting, and implementing a unified linguistic framework for [Company Name]. This procedure applies to all internal and external communications, ensuring consistency across marketing, support, and executive outreach.

2. Prerequisites

• Access to the [Company Name] central repository or [Document Management System].
• Current strategic vision statement and core values document.
• Stakeholder access to [Collaborative Writing Platform].

3. Roles & Responsibilities

4. Step-by-Step Procedure

Phase 1: Discovery and Archetype Definition

• Conduct stakeholder interviews to identify the desired emotional resonance for [Company Name].
• Select a core archetype (e.g., The Sage, The Hero, The Caregiver) that aligns with [Company Name] values.
• Define the three primary pillars of the corporate tone (e.g., "Professional yet accessible").

Phase 2: Linguistic Documentation

• Draft the "Voice Matrix" defining what the brand is (e.g., "Empathetic") and what it is not (e.g., "Condescending").
• Create a "Vocabulary Lexicon" identifying preferred terminology and prohibited jargon.
• Document syntax preferences (e.g., active vs. passive voice, sentence length averages).

Phase 3: Implementation and Training

• Distribute the finalized guide to all departments.
• Conduct a workshop for [Department Name] to review practical application exercises.
• Integrate the guide into the onboarding process for new hires.

Phase 4: Maintenance and Audit

• Schedule a quarterly review of high-impact communications to ensure alignment.
• Update the document based on shifts in [Company Name] market positioning.

5. Quality Assurance, Pro-Tips, and Pitfalls

• QA Checklist: Does the document provide enough examples for a non-writer to replicate the tone? Is there a clear escalation path for tone-related disputes?
• Pro-Tip: Include a "Before vs. After" section in your documentation. Showing a rewritten paragraph is more effective than explaining abstract adjectives.
• Common Pitfall: Over-complicating the guidelines. If the document exceeds [__________] pages, it will not be read. Keep the core requirements to a one-page summary.

6. FAQs

Q: How often should we update these guidelines? A: Review the document every 12 months or immediately following a significant pivot in [Company Name] business strategy.

Q: What if a specific department needs a different tone? A: Use a "Core vs. Context" model. The core persona remains constant, while secondary attributes can be adjusted for specific channels (e.g., social media vs. technical documentation).