Brand Voice and Editorial Style

Message House Workbook

Organize a supportable core promise, message pillars, proof, conditions, audience relevance, approved language, and claims that must not be made.

Free editable Markdown · Message strategists, product marketers, and brand teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Foundation

Audience: [Specific group]
Situation and decision: [What are they trying to decide?]
Observed need: [Research evidence]
Alternative considered: [What else may they choose?]
Core promise: [One supportable sentence]
Applicability: [Who and when it covers]
Limitation: [What it does not promise]
Message owner: [Accountable role]

Pillar record

Pillar name: [Short distinct idea]
Audience question answered: [Why it matters]
Supporting message: [One clear statement]
Proof point: [Feature, process, result, source, or example]
Evidence source and date: [Link]
Condition: [Where the claim applies]
Claim owner: [Role]
Evidence gap: [What remains unproven?]

Language controls

Approved phrases: [Wording and context]
Terms to define: [Audience-friendly treatment]
Claims not to make: [Unsupported or overbroad language]
Short-form rule: [What cannot be removed]
Long-form order: [Promise, pillar, proof, limitation, action]

Pillars are distinct rather than synonyms.
Evidence supports the exact level of certainty.
The framework leaves an appropriate non-action choice.

Test and maintenance

Comprehension result: [What participants believed]
Credibility question: [Proof they requested]
Unintended implication: [What needs revision]
Approved by: [Brand, product, editorial, and specialist roles]
Effective date: [YYYY-MM-DD]
Derived assets: [Pages, decks, scripts, campaigns]
Review trigger: [Product, evidence, audience, or market change]

How to use this template

Define the audience situation, decision, evidence base, and communication outcome.
Draft a narrow core promise with explicit applicability and limitations.
Create distinct supporting pillars and attach current proof, sources, and owners to each.
Record approved language, claims to avoid, channel adaptation rules, and unresolved evidence gaps.
Test comprehension and credibility, approve the framework, and schedule review and downstream updates.

Put one audience decision at the center

Define who faces which situation and what the message should help them understand or decide. A core promise should express relevant value the organization can deliver, not a collection of adjectives. Keep it narrow enough that pillars explain the same proposition. If one framework tries to serve buyers, employees, partners, and regulators simultaneously, the promise often becomes empty. Preserve distinct stakeholder needs in separate adaptations while maintaining one factual base. State what the promise does not mean so enthusiastic writers cannot expand it beyond evidence.

Build pillars as reasons to believe

Each pillar should answer a different material question supporting the promise, such as capability, experience, control, or evidence. Avoid three synonyms for quality. Beneath each pillar, list verified proof: current features, documented process, relevant research, limits, or a clearly labeled example. Testimonials and popularity may illustrate experience but do not prove a universal outcome. Link claims to a source, date, and accountable owner. If evidence is weak, change the wording or record a research need rather than filling the gap with confidence.

Test the structure outside the workshop

Ask intended readers to explain the core promise, conditions, and differences in their own words. Check whether pillars are distinct, credible, and relevant and whether any phrase creates an unintended guarantee. Give channel teams approved and prohibited language plus rules for shortening the hierarchy. A small placement may carry the core and one proof point, while a detailed page can show all pillars. Review the house when the product, market, evidence, audience, or legal position changes, and propagate revisions through derived assets.

See the fields in context

Fictional example: volunteer scheduling service

Gatherline is an invented service; no real capability or result is claimed.

Core promise: Help small volunteer teams coordinate confirmed shifts without maintaining separate spreadsheets.
Pillar 1: Shared availability, supported by the fictional role-based calendar.
Pillar 2: Clear confirmation, supported by timestamped acceptance records.
Limitation: The service does not verify professional qualifications or guarantee attendance.
Test result: Readers understood coordination but initially inferred automatic background checks, so that implication was removed and the limitation moved earlier.

Frequently asked questions

How many pillars should a message house have?

Use the fewest distinct reasons needed to support the promise, commonly two to four. More pillars often indicate several propositions have been combined. Remove anything irrelevant to the audience decision.

Is a slogan the same as the core promise?

No. A slogan may be memorable but omit audience, value, and conditions. The core promise is an internal and external meaning anchor; a slogan derived from it still needs separate review.

Can one message house serve several audiences?

Only when they share the same situation and value. Otherwise maintain a consistent fact base and create audience-specific houses or message maps so relevance is not purchased with vague language.

What happens when evidence expires?

The claim owner should revise or withdraw the proof and every dependent message. Record dates and derived assets so an old statistic or feature does not remain in campaigns after the source changes.