What it is

A framework for building FAQ documents that work for different audiences – employees, journalists, board members, customers, and partners – from a single set of facts. Rather than writing five separate documents, this template shows how to adapt tone, depth, and emphasis for each audience while keeping the underlying facts consistent.

The most common failure in communications under pressure is that different teams produce different answers to the same question. This template prevents that by establishing a single source of truth first, then translating it by audience.

When to use it

Use when:

You are preparing for a significant announcement, restructure, or change programme
A news story or issue is emerging and you need to brief multiple audiences quickly
Your organisation is launching a product, campaign, or initiative with external and internal components
Spokespeople need to be briefed across multiple channels simultaneously
You need to prepare a board or leadership team for questions they haven’t anticipated

Don’t use when:

You have a single audience and no translation is needed – a simpler Q&A document will do
The situation is still evolving and the facts are not yet settled – wait until you have answers you can stand behind
Legal proceedings are active and answers require legal sign-off at each step (this template does not replace legal review)

Inputs needed

Before starting, gather:

The core narrative: What is the situation, announcement, or issue in plain language?
The known questions: What will each audience actually ask? (Run a pre-mortem – don’t just guess the easy ones)
The facts you can confirm: What is true, verified, and approved to share?
What you cannot say, and why: What is confidential, legally constrained, or still unclear?
Who owns each audience: Which team or person is responsible for employee comms, media, customer comms, board briefings?
Timing: When does each audience need to know, and in what order?

The template

Step 1: Core narrative block

Write this before drafting any audience-specific FAQs. Every answer across every audience should be consistent with this block.

The situation in one sentence:

[WHAT HAS HAPPENED / IS HAPPENING / IS BEING ANNOUNCED] – [WHEN] – [AFFECTING WHOM].

What we know (confirmed facts only):

What we don’t know yet (be honest internally – this prevents contradictions):

What we are doing:

What we are not doing (sometimes as important):

When we will provide more information:

[DATE/TIME/MECHANISM FOR NEXT UPDATE]

What must not be said (legal, HR, or sensitivity constraints):

Step 2: Question bank

List every question each audience is likely to ask – including the ones you’d rather not answer. Uncomfortable questions left out of the FAQ are the ones that cause problems.

Technique: For each audience, ask: What does this person need to know to do their job, make a decision, or feel informed? Then ask: What would they ask if they felt they weren’t being told the full story?

Employee questions (typical):

Does this affect my job?
Will my pay or terms change?
Who made this decision and why?
When will I find out more?
Who can I speak to if I have concerns?
What is the company’s view on [TOPIC]?

Media questions (typical):

What exactly has happened?
Why now?
Who is responsible for this decision?
What does this mean for [customers / employees / market]?
Have you spoken to [AFFECTED PARTY]?
What is your response to [CRITICAL FRAMING]?

Board / leadership questions (typical):

What is the financial impact?
What is the reputational risk?
What is the timeline?
What decisions do we need to make, and by when?
What are we doing that we haven’t done before?
What could go wrong?

Customer questions (typical):

Does this affect my product / service / contract?
What do I need to do?
Who can I contact if I have a problem?
Is my data / order / account safe?
Will pricing change?

Partner / supplier questions (typical):

Does this affect our agreement?
Who is my point of contact going forward?
What do I need to communicate to my own stakeholders?
Is there anything you need from us?

Step 3: Answer matrix

For each question in the bank, write the core answer first – then adapt for each audience that needs a version of it.

Format for each answer:

QUESTION: [Q]

CORE ANSWER (internal working version – not for distribution):
[Full, honest answer including what you know and don't know]

EMPLOYEE VERSION:
[Warm, direct, human. Acknowledge impact on people. Use "we".]

MEDIA VERSION:
[Precise, factual, attribution-ready. Avoid "no comment" – use "we are not in a position to confirm X at this stage".]

BOARD VERSION:
[Analytical, risk-focused, decision-oriented. Include numbers and timelines where available.]

CUSTOMER VERSION:
[Practical, reassuring where truthful, clear on what action (if any) is needed. Plain English.]

PARTNER VERSION:
[Professional, relationship-preserving, specific about implications for the partnership.]

Audience-specific tone guide

Audience	Primary need	Tone	What to lead with
Employees	Certainty and honesty	Warm, direct, human	Impact on them personally
Media	Accuracy and quotability	Precise, factual	The news – not the organisation’s view of it
Board	Risk and decision-making	Analytical, structured	Financial and reputational impact
Customers	Reassurance and clarity	Plain English, practical	What this means for them specifically
Partners	Continuity and relationship	Professional, bilateral	What changes and what doesn’t

Step 4: Distribution and version control

Before sending any FAQ document:

Version number every document so you know which is current if updates are needed
Name documents clearly: FAQ_Employees_v1_[DATE] not FAQ_FINAL_FINAL
Record who received what version and when – this matters if facts change
Agree an update trigger: at what point does a new fact require a new version?
Assign a single owner per audience document who is responsible for updates

AI prompt

Base prompt

You are a communications strategist helping build a stakeholder FAQ pack.

The situation: [DESCRIBE IN 2–3 SENTENCES – WHAT HAS HAPPENED / IS HAPPENING]

Confirmed facts:
- [FACT 1]
- [FACT 2]
- [FACT 3]

What we cannot confirm yet: [LIST]
What must not be said: [LIST ANY CONSTRAINTS]

Audiences needed: [CHOOSE: Employees | Media | Board | Customers | Partners – select all that apply]

For each audience, write answers to the following questions:
[LIST THE QUESTIONS FROM YOUR QUESTION BANK]

Format each answer clearly by audience. Keep employee answers warm and human. Keep media answers precise and quotable. Keep board answers analytical with risk focus. Keep customer answers plain and practical. Keep partner answers professional and relationship-preserving.

Do not include any confirmed facts beyond what I have listed above. If a question cannot be answered with confirmed information, state what you can say: "We are not in a position to confirm this at this stage. We will provide an update by [DATE]."

Prompt variations

Variation 1: Crisis FAQ – rapid build

We are managing [BRIEF DESCRIPTION OF ISSUE]. I need a rapid FAQ for two audiences: employees and media. Questions employees will ask: [LIST]. Questions media will ask: [LIST]. Facts confirmed: [LIST]. What we cannot say: [LIST]. Write 8–10 answers per audience. Employee tone: honest and steady. Media tone: precise and attributable. Under 30 minutes to produce.

Variation 2: Announcement FAQ – multiple audiences

We are announcing [ANNOUNCEMENT] on [DATE]. I need FAQ documents for [AUDIENCES]. The core message is: [1–2 SENTENCES]. The questions each audience is most likely to ask are: [LIST BY AUDIENCE]. Write full Q&A sets for each. Flag any question where our answer is weak or likely to invite follow-up.

Variation 3: Board briefing Q&A only

Prepare a board Q&A briefing for [TOPIC/SITUATION]. The board will want to understand: financial impact, reputational risk, decision points, and timeline. Write 10 questions they are likely to ask and full answers for each. Where the answer involves uncertainty, say so directly and state what we are doing to resolve it. Analytical tone throughout.

Variation 4: Customer FAQ – plain English

We need to explain [SITUATION/CHANGE] to customers. They will not have technical or industry knowledge. Write a 10-question FAQ in plain English. Each answer should be under 60 words. Lead with what this means for the customer, not for the organisation. Avoid passive voice. Where action is required from the customer, make it the first sentence of the answer.

Human review checklist

Core narrative consistent: Are the facts in every audience version identical? Run a side-by-side check on key facts before distribution
No gaps in question bank: Has someone played devil’s advocate and asked the questions you’d least like to answer?
Tone appropriate per audience: Read each version aloud – does it sound right for that audience?
Unanswerable questions handled honestly: Where you can’t answer, does the document say that clearly rather than evading?
Update mechanism in place: Who owns each document, and what triggers a new version?
Legal or HR review completed: If any answers touch on employment, contract, or regulatory matters, have they been cleared?
Plain English check for customers: No jargon, no passive voice, clear on what (if anything) the customer needs to do
Media version quotable: Could a journalist lift any answer and use it accurately as a quote? That is the test.
Version numbers applied: Every document distributed should have a version number and date
Spokesperson briefed: Has the person who will actually answer questions seen and approved this document?

Example output

Employee FAQ example – restructure announcement

Q: Does this affect my job?

The restructure affects roles in [SPECIFIC TEAMS/FUNCTIONS]. If your role is affected, you will hear from your manager directly today. If you do not receive a conversation today, your role is not at risk in this process.

We know that uncertainty is difficult. We are committed to communicating clearly and promptly at every stage, and to treating everyone involved with respect.

Q: Who made this decision and why?

This decision was made by the [LEADERSHIP TEAM / BOARD] following a review of [BRIEF CONTEXT – e.g. our cost base / our market position / our operating model]. The review concluded that [PLAIN LANGUAGE REASON]. This was not a decision taken lightly, and it was not taken quickly.

Q: When will I find out more?

Your manager will follow up with you [TODAY / THIS WEEK] with more detail relevant to your specific situation. A further all-staff update will be shared on [DATE]. In the meantime, if you have questions you need answered sooner, please speak to [CONTACT / HR].

Message House – Build the core narrative that all FAQ answers should be consistent with
Media Pitch Builder – Develop media-facing communications alongside the FAQ
All-Staff Update – Formal internal communication that the employee FAQ should align with
Crisis Preparedness Toolkit – Full crisis communications workflow including stakeholder FAQs

Stakeholder FAQ Builder with Audience Variants