Loading...
content

Message House Key Message Framework

A one-page message house for aligning an umbrella message, supporting pillars, and proof points across channels. Use it to keep executives, managers, and comms teams saying the same thing.

Trusted by frontline teams 15 years of frontline software

Built for: Technology · Healthcare · Financial Services · Education · Manufacturing

Overview

This Message House Key Message Framework template is a one-page internal communications site for defining what people should remember, repeat, and reinforce. It organizes the message into an umbrella statement, supporting pillars, proof points, audience guidance, spokesperson notes, and channel usage so the same idea can travel cleanly from leadership to managers to employee-facing channels.

Use it when you need alignment across multiple voices or formats: a company announcement, a policy change, a transformation update, a launch, or any internal message that can easily drift if people improvise. The template helps you decide what the one sentence is, which supporting points matter most, what evidence backs them up, and what each audience should hear first. It also gives you a place to document approval workflow so updates do not happen informally.

Do not use this as a substitute for a full project plan, editorial calendar, or crisis response playbook. If the message is still being shaped, or if the audience, timing, or policy implications are unresolved, this page should stay draft until the owner and approvers agree on the final language. It is also not the right place for long-form narrative or a large FAQ library; the value here is clarity, consistency, and fast reuse across channels.

Standards & compliance context

  • For employee-facing policy or HR topics, route the message house through the appropriate legal, HR, or compliance approver before use.
  • Keep proof points aligned with source documents so the page does not introduce claims that conflict with official policy or regulatory language.
  • If the message touches accessibility, benefits, safety, or other regulated employee topics, use plain language and avoid ambiguous wording.
  • Document who approved the final message and when, so audits and internal reviews can trace the version in circulation.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

No items.

  • Umbrella message
  • Supporting pillars
  • Proof points
  • Audience guidance
  • Spokesperson notes
  • Channel usage

  • {{umbrella_message}}

  • What we want people to understand, feel, and do after hearing this message.

  • Keep the language clear, confident, and audience-friendly. Avoid jargon, acronyms, and competing claims.

  • {{pillar_1_summary}}

  • {{pillar_2_summary}}

  • {{pillar_3_summary}}

  • {{pillar_4_summary}}

  • {{proof_point_1}}

  • {{proof_point_2}}

  • {{proof_point_3}}

  • {{proof_point_4}}

  • Lead with strategy, business impact, and the decision behind the message.

  • Focus on what changes for teams, how to answer questions, and where to send follow-ups.

  • Explain what is happening, why it matters, and what action is needed now.

  • What is the one sentence we want people to repeat?
  • Which pillar should be emphasized first?
  • What should we avoid saying?
  • Who approves updates to this message house?

  • Executive talking points

    Short guidance for leadership briefings and town halls.

  • Manager toolkit

    Conversation prompts and team-ready language for people managers.

  • Channel copy guide

    Approved language for email, intranet, chat, and presentation decks.

  • Approval workflow

    Review path for updates, exceptions, and final sign-off.

How to use this template

  1. Start by writing the umbrella message as one sentence that captures the core idea people should repeat after reading the page.
  2. Add 3-5 supporting pillars that explain the message from different angles without repeating the same point in new words.
  3. Attach proof points, source notes, or approved facts under each pillar so spokespeople can speak confidently without improvising.
  4. Fill in audience guidance and spokesperson notes to show what executives, managers, and other communicators should emphasize or avoid.
  5. Map each channel to the approved version of the message, then route the page through the approval workflow before publishing or sharing.
  6. Review the page after rollout feedback, update any language that is being misquoted, and retire outdated proof points as the initiative changes.

Best practices

  • Keep the umbrella message short enough that a manager can repeat it without reading from the page.
  • Limit the number of pillars so the message stays memorable and the hierarchy of ideas is obvious.
  • Use proof points that are specific, approved, and easy to cite in conversation or in a slide deck.
  • Write audience guidance by role, not by vague group labels, so executives and managers know exactly what to say.
  • Include explicit 'do not say' language for sensitive topics to prevent accidental drift in live meetings or chat.
  • Match channel usage to the level of detail each format can support, with shorter copy for banners and fuller copy for manager toolkits.
  • Treat the approval workflow as part of the content, not an afterthought, so changes are traceable and controlled.

What this template typically catches

Issues teams running this template most often surface in practice:

The umbrella message is too broad and reads like a slogan instead of a usable internal directive.
Supporting pillars overlap, which makes the page feel repetitive and weakens recall.
Proof points are missing, so managers have no evidence to use when answering questions.
Audience guidance is generic, causing executives and frontline managers to deliver the same message in the wrong tone.
Channel copy is written once and reused everywhere, even where the format or audience needs a shorter version.
Approval ownership is unclear, so teams keep editing the page after it has already been shared.
The page is updated in one place but not propagated to downstream decks, emails, or intranet posts.

Common use cases

Executive change announcement
A communications lead prepares a leadership message for an organizational change and uses the template to keep the CEO, HR leader, and managers aligned on the same core wording. The proof points and spokesperson notes help each leader speak in their own voice without changing the substance.
Policy rollout for managers
An HR or compliance team uses the page to define the policy summary, the reasons behind it, and the exact language managers should use in team meetings. The channel usage section helps translate the same message into email, intranet, and live Q&A formats.
Product launch inside the company
An internal comms owner uses the framework to explain what is launching, why it matters, and what employees should do next. The audience guidance section helps tailor the message for support teams, sales teams, and leadership updates.
Crisis or issue-response alignment
A communications team uses the template to lock down the approved message, the facts that can be shared, and the phrases that should be avoided. This keeps spokespeople consistent when questions start coming from multiple channels.

Frequently asked questions

What is included in this message house template?

This template includes an umbrella message, supporting pillars, proof points, audience guidance, spokesperson notes, and channel usage. It also includes approval workflow and practical copy guidance so the message can be used, not just written. The goal is to give teams one source of truth for internal communications.

When should I use a message house instead of a longer comms plan?

Use this template when you need a single, repeatable message that will be shared across multiple channels or by multiple spokespeople. It works well for launches, organizational changes, policy rollouts, leadership updates, and recurring internal campaigns. If you need a full campaign calendar, editorial plan, or issue-response playbook, this should sit inside that broader plan.

Who should own and update the message house?

Typically, internal communications, corporate communications, or a program owner drafts it, with approval from the relevant executive sponsor. Managers and spokespeople should use it, but not rewrite it ad hoc. The approval workflow section helps define who can edit, who can approve, and when updates are needed.

How often should this framework be reviewed?

Review it whenever the underlying initiative changes, a new audience is added, or feedback shows the message is being interpreted inconsistently. For time-sensitive announcements, it may need daily or weekly updates during rollout. For stable programs, a lighter monthly or quarterly review is usually enough.

What are the most common mistakes when using a message house?

The biggest mistake is making the umbrella message too broad, so it stops guiding anyone. Another common issue is collecting too many pillars, which makes the message hard to remember and repeat. Teams also get into trouble when channel copy drifts away from the approved proof points or when spokesperson notes are too vague to be useful.

Can this template be customized for different audiences or channels?

Yes, that is one of its main uses. The audience guidance and channel usage sections let you tailor the same core message for executives, managers, frontline staff, or different internal channels. You can also add role-based notes so each audience gets the right level of detail without changing the core message.

How does this connect to other internal communication tools?

This template can feed manager toolkits, FAQ pages, announcement drafts, intranet landing pages, and leadership talking points. It works especially well as the upstream source for channel-specific copy, so every downstream asset stays aligned. If your team uses a content hub or intranet page, this can serve as the canonical message source.

Is this useful for regulated or sensitive communications?

Yes, but it should be reviewed carefully by legal, HR, compliance, or security when the topic has policy, employee-relations, or regulatory implications. The proof points and approval workflow sections help document what can be said and who must sign off. For sensitive topics, keep the language precise and avoid unsupported claims or informal paraphrasing.

Go deeper on the topic

Related concepts
  • A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Related guides

Ready to use this template?

Get started with MangoApps and use Message House Key Message Framework with your team — pricing built for small business.

Get Started
Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?