Talking points are a short internal document that sets out what an organisation will say about a topic: one main message, a small set of supporting points with proof, approved wording for sensitive parts, and clear notes on what not to claim. The direct answer is this: a talking points document is useful when anyone on the team can pick it up, understand the position in two minutes, and repeat it accurately in their own words without inventing, exaggerating or drifting into a different position. This guide is about the document itself: what it contains, how it is structured, how to write it, and how to keep it current. It is not a guide to interview technique or presentation skills; those begin only after the document exists and is right.
Table of Contents
- What is a talking points document?
- Talking points, scripts, press releases and Q&A documents: the differences
- What should a talking points document contain?
- How to write talking points, step by step
- What is message discipline in a document?
- One page or several? Choosing the right length
- An example talking points outline
- How to keep the document current and controlled
- Common mistakes in talking points documents
- Frequently asked questions
What is a talking points document?
A talking points document is an internal, written summary of an agreed position, organised as a main message supported by a few provable points, written to be read quickly and used consistently by everyone who speaks or writes for the organisation on that topic.
Think of it as the single source of truth for one subject. Sales staff answering a customer, a support agent replying to an email, a manager briefing a partner and a director writing a comment for a trade publication should all be able to start from the same document and land in the same place. The document does not make them sound identical; it makes them agree on the facts, the emphasis and the limits. That agreement is the whole value. Without a written document, a position lives in meetings and memory, and it changes a little with every retelling until the organisation is saying several slightly different things at once, each of them quotable.
Talking points are normally internal. They may contain context, sensitivities and instructions that are not for publication, such as why a topic is delicate, which claim legal has not cleared, or which question must be referred to a named person. That internal character is a feature: it lets the document be candid about limits in a way a public document cannot be. It also creates a responsibility to label, store and circulate the document properly, which this guide covers below.
Talking points, scripts, press releases and Q&A documents: the differences
- Talking points document. Internal. Points and proof in note form, written to be absorbed and reused in the reader’s own words across many situations.
- Script. Exact words to be spoken verbatim, used for recordings, ceremonies and tightly timed announcements. A script fixes wording; talking points fix meaning.
- Press release. External and publishable. A finished news document written for journalists to quote and republish; the structure in how to write a press release shows how different its shape is from internal notes.
- Q&A document. Anticipated questions with agreed answers, usually paired with talking points for difficult topics. Talking points state the position proactively; a Q&A handles challenges reactively. Many teams keep both in one file, with the talking points first.
- Briefing note or fact sheet. Background and data for understanding. Talking points draw on the facts but add the decisions: what to emphasise, what to phrase carefully and what to leave out.
Confusing these documents causes real problems. Reading talking points aloud verbatim makes a speaker sound stilted, because notes are not sentences. Sending the internal document to a journalist exposes context that was never meant to travel. Publishing a Q&A answer as the main message buries the position under defensive detail. Name the document correctly at the top, state who it is for, and half of those errors disappear.
What should a talking points document contain?
A header that controls the document
Start with the unglamorous lines that prevent most mistakes: the topic, the date and version, the owner (the person who can approve changes), who the document is for, and its status, for example internal only, or cleared for use in external replies. A reader should know in five seconds whether they are holding the current version or last month’s.
The main message in one or two sentences
The position, stated plainly, at the top. If the document has no main message, it is a pile of facts, not talking points. The main message answers the reader’s silent question: if I remember only one thing, what is it? Everything else in the document exists to support, prove or protect these two sentences.
Three supporting points, each with proof
A small set of supporting points, ordered by importance, each carrying its evidence in the same line or the line beneath: the figure with its source and date, the example with its name and place, the commitment with its deadline owner. Proof inside the document is what stops confident misuse, because a user who can see where a claim comes from will repeat it at the right strength, and will know which claims have no proof yet and must be softened or dropped.
Approved wording for the sensitive lines
Some sentences need to be exact: a legal description, a safety instruction, an apology, a statement about an ongoing process. Mark those lines clearly as use-as-written, and keep the rest of the document in note form. Mixing the two without labels invites people to improvise the one sentence that had to be precise, while reading the flexible notes like a script.
What not to say, and why
A short, explicit list: claims not yet substantiated, topics outside this document’s scope, speculation to avoid, and questions to refer onward, each with a one-line reason and a destination (the named person or team who handles it). This section is not negativity; it is the document’s safety rail, and experienced writers treat it as seriously as the messages themselves.
Audience and usage notes
Close the document with brief notes on where it will be used: which audiences, which channels, and any timing that matters, such as an announcement date or the handling described in our guide to the embargoed press release, where material is shared early on strict conditions. Usage notes stop a document written for one moment being reused carelessly in another.
How to write talking points, step by step
Step 1: Define the job of the document
Write one line, for yourself, stating the situation, the audience and the decision the document must support. A document for a product delay, a document for a funding announcement and a document for a recurring industry question are different instruments even inside one company. Most weak talking points fail here: they try to cover every situation and end up guiding none.
Step 2: Gather facts before phrases
Collect the verified material first: dates, figures with sources, names, commitments and their owners, and the questions people are actually asking, drawn from inboxes, support tickets, sales calls and previous coverage. The contrast between grounded and invented material is the same one visible in media pitch examples of what works and what fails: specifics persuade, adjectives do not.
Step 3: Draft the main message, then argue with it
Write the position in plain sentences. Then test it: is it true at the strength stated? Would we say it to the most sceptical reader? Does it promise anything we do not control? Rewrite until the answers are comfortable. Only then build the supporting points underneath, each one answering the reader’s natural follow-up: why, how do you know, what happens next?
Step 4: Order for the reader, not for the writer
Put the point the audience cares about most first, not the point the organisation is proudest of. Inside each point, lead with the claim and follow with the proof, so a skimming reader still absorbs the structure. Use headings a busy colleague can scan, short lines instead of dense paragraphs, and consistent terms for the same thing throughout; a document that calls one product by three names teaches confusion.
Step 5: Write the limits section honestly
List what the document does not cover, which claims are not cleared, and where hard questions go. Base it on the hardest questions you can imagine being asked, not the easiest. If a limit feels awkward to write down, that is usually the sign it is exactly the limit the team needs written down.
Step 6: Get one accountable approval
Route the draft to the people who own the facts and the risks (the subject owner, and legal or compliance where the topic needs it), then to one named approver who settles disagreements. Committee editing by circulation produces documents with everyone’s fingerprints and no one’s judgement. Record the approval in the header: version, date, approver.
Step 7: Publish internally like you mean it
Put the approved document in the one place the team is told to look, announce it in one message that links to that place only, and withdraw or archive superseded versions the same day. A brilliant document that exists as five email attachments with similar names will be quoted in its oldest form by someone, somewhere, at the worst moment.
What is message discipline in a document?
Message discipline, at the level of this document, means the written position does not contradict itself, does not quietly change between versions, and is not diluted by every user adding a favourite claim. The document enforces it in practical ways: one main message that other points must support or leave, defined terms used consistently, numbers given once with their source rather than repeated in varying forms, and a change process that edits the master document instead of letting branches grow. The long tradition of persuasive communication, from the early practitioners described in our profile of Edward Bernays and the shaping of modern PR, is a reminder that consistency is powerful precisely because audiences compare what an organisation says over time. A disciplined document respects that comparison instead of hoping nobody checks.
One page or several? Choosing the right length
Length should follow risk and complexity, not habit. For a routine topic, a single page (main message, three points, limits, header) is ideal because it will actually be read in the moment of need. For a complex or sensitive topic, use a layered document: the one-page summary first, then fuller supporting sections with deeper proof, approved wording and a paired Q&A. What matters is that the first page can stand alone accurately; if the summary needs its footnotes to avoid misleading the reader, the summary is wrong. Resist the opposite failure too: a twenty-page document for a simple announcement tells the team the topic is more dangerous than it is, and guarantees the document will be skimmed, misread or ignored.
An example talking points outline
The following skeleton is fictional and simplified, included to show the structure rather than finished wording. Imagine a community transport charity announcing a schedule change.
- Header. Topic: spring timetable change. Version 2, dated, owner named. Internal; approved wording may be quoted.
- Main message. From the first of next month, our buses move to a spring timetable that adds two evening services and removes one little-used midday service, so that more working passengers can rely on us.
- Supporting point 1. Evening demand is the reason; proof note: cite the charity’s own published passenger review, with date.
- Supporting point 2. What changes for riders, stop by stop; proof note: link to the published timetable.
- Supporting point 3. Help for affected riders; proof note: the named contact and the alternative service.
- Use as written. The line about the removed service’s last running date.
- Do not say. Do not speculate about funding for next year; refer those questions to the named trustee.
Notice the proportions: most of the skeleton is proof notes and limits, not slogans. That is what a working document looks like.
How to keep the document current and controlled
Talking points decay. Figures age, commitments land or slip, and a position written for an announcement is wrong for the follow-up. Build the maintenance into the document itself: a review date in the header, an owner who is a person rather than a department, and a simple rule that anyone who finds an error reports it to the owner instead of editing a private copy. When facts change, issue a new version with a new number, change the master, and announce the change in the same channel as the original. Keep the internal document internal: store it in controlled systems, think before forwarding it outside the team, and mark its status on every page if your tools allow. If an old version surfaces publicly, the header, date and version lines are what let you show calmly which document was current and what it actually said.
Common mistakes in talking points documents
- No main message. A fact dump that forces every reader to invent their own position, which they promptly do, differently.
- Claims without proof inside the document. Users repeat the claim at full strength in places where its missing source matters.
- Written as a script but labelled as points. Readers either read notes aloud, awkwardly, or improvise around sentences that were meant to be exact.
- No limits section. The team learns the boundaries by crossing them in public.
- Multiple live versions. The fastest way to have two departments quoting two positions on the same day.
- Approved by everyone and no one. Endless circulation, no decision, and a document that arrives after the moment it was for.
- Marketing adjectives in place of evidence. Words like leading and world-class inside an internal document teach the team to say things it cannot support outside it.
Frequently asked questions
What are talking points in simple terms?
They are the written, internal summary of what your organisation says about a topic: one main message, a few supporting points with proof, exact wording where wording matters, and notes on what not to claim.
How many talking points should a document have?
One main message and usually three supporting points a reader can hold in mind. More than that usually means the document is covering two topics and should be split.
Are talking points the same as a script?
No. Talking points fix the meaning and the facts so people can speak in their own words. A script fixes the exact words. Good documents label clearly any line that must be used word for word.
Who should approve a talking points document?
The person accountable for the topic, with factual checks by the people who own the facts and legal or compliance review where the subject needs it. One named approver should settle the final version.
Should talking points be shared outside the organisation?
They are written for internal use, with internal candour about limits and sensitivities. Share the public materials built from them (releases, statements, published Q&As), not the internal document itself.
A talking points document earns its keep quietly: fewer contradictory quotes, fewer invented claims, fewer panicked calls asking what we say about this. Write the document with a clear message, visible proof and honest limits, keep one current version, and your team will sound like one organisation because, on paper, it is one.
