How to Write a Presentation Summary - Steps, Examples, and Templates
Most decks get read once and remembered badly. The presentation summary is the part people keep, forward, and quote back to you three weeks later.
It is also the part most people write last, at speed, after the slides are done. That order is backwards, and it shows in the result.
This guide covers what a presentation summary is and the three forms it takes. It then gives a three-step method that works for your own deck or someone else's.
What a presentation summary is
A presentation summary is a short piece of writing that carries the argument of a presentation without the presentation.
That definition has a hard edge. If the reader needs the slides to follow it, it is not a summary. It is a caption.
Three things separate a real presentation summary from a table of contents:
- It states conclusions, not topics. "Churn rose in the enterprise segment" beats "Churn analysis."
- It carries the numbers that matter. Two or three, not twenty.
- It says what happens next. A summary ending without a decision leaves the reader to invent one.
Three kinds, and which one you need
The term covers three different jobs. Writing the wrong one is the most common failure. It usually happens because nobody asked which was wanted.
| Kind | Length | Written when | Reader |
|---|---|---|---|
| Summary slide | 1 slide, 30–60 words | Before you present | Everyone in the room |
| Abstract or preview | 50–150 words | Before you present | People deciding whether to attend |
| Post-presentation summary | 200–500 words | After you present | People who missed it, and future you |
The summary slide lives inside the deck. If that is what you need, our guide to the executive summary slide covers the slide-specific layout.
The post-presentation version is a document, not a slide. It has to survive being read cold, six weeks later, by someone who was not in the room. Our walkthrough of the post-presentation recap covers that format.
The writing method below is the same for all three.
What belongs in a presentation summary
Strip a good one down and you find five components. Not all five appear every time, but their absence should be a decision rather than an oversight.
- The question the presentation answered. One sentence. If you cannot write it, the deck did not have one.
- The answer. Also one sentence. This is the line people will quote.
- The evidence. Two or three figures, each with its source.
- The caveat. What the analysis does not cover, or where confidence is low.
- The next step. Who does what, by when.
The caveat is the one people cut for length. Keep it. A presentation summary that reads as more certain than the underlying work is worse than none at all. It travels further than your qualifications do.
How to write a presentation summary
Three steps. The order matters more than the speed.
Step 1: Write the answer before you write anything else
Open a blank document, not the deck. Write one sentence answering the question the presentation set out to answer.
Do this before rereading your slides. Rereading pulls you toward summarizing structure, and structure is not the point. The finding is.
If the sentence runs past about 25 words, the presentation probably made two arguments. Write both sentences, then decide which one leads.
Test it on its own. Hand the sentence to someone who was not in the room. If their first response is a clarifying question rather than a reaction, it is not carrying its weight yet.
This step is where a presentation summary is won or lost. Everything after it is assembly.
One warning. If the answer sentence keeps changing as you write, the analysis is not finished. Stop writing and go back to the data.
Step 2: Pull the three numbers that hold it up
Now go back to the deck with a specific job. Find the smallest set of figures that makes your sentence credible.
Three is usually the ceiling. Readers stop absorbing numbers after that. A wall of figures also signals that you could not decide which ones mattered.
For each number, record where it came from. Not "from the dashboard" but the actual table, file, or query. This takes an extra minute and saves an hour the first time someone challenges a figure.
Round for readability, but never round to a different conclusion. A shift from 4.2% to 4% is fine. Rounding 4.6% to 5% in a summary about crossing a 5% threshold is not.
If your figures come from a spreadsheet, the mechanics are covered in our guide to summarizing Excel data without pivot tables.
Step 3: Add the caveat and the next step, then cut
You now have an answer and evidence. Two things remain.
The caveat goes immediately after the evidence, in one sentence. Name the boundary of the analysis. A date range, an excluded segment, or a data quality issue you worked around all qualify.
The next step goes last, and it needs a name attached. "We should review pricing" is not a next step. "Pricing review, owned by Dana, before the October board meeting" is.
Then cut. Read the draft and delete every sentence not doing one of the five jobs listed above. Most first drafts lose about a third here and improve.
Cut adjectives first. Words like significant, substantial, and notable feel like emphasis but carry no information. If a number is large, the number says so.
A worked example
Here is the same finding written badly, then written well.
Before, 84 words:
This presentation covered our quarterly churn analysis. We looked at churn across segments and time periods. The analysis included data from multiple sources. We found some interesting patterns in the enterprise segment that may warrant further investigation. There were also findings related to the mid-market. We discussed several possible explanations. We also covered potential next steps the team could consider taking in the coming weeks, depending on priorities.
After, 79 words:
Enterprise churn rose to 4.2% in Q3, up from 2.8% in Q2. Mid-market and SMB held steady.
Three figures carry it. Of 14 lost enterprise accounts, 11 had no executive sponsor on file (CRM export, Sept 18). Average time-to-first-value for those accounts ran 47 days against a 21-day target (onboarding log). Nine of the 14 had support tickets open longer than 30 days.
This excludes accounts lost to acquisition. Dana owns a sponsor-coverage review before the October board meeting.
Nearly the same length. The second one can be forwarded to someone who missed the meeting, and they can act on it.
Notice what the second version does not do. It never describes the presentation. It delivers the finding.
The sourcing is doing quiet work too. Each figure names where it came from, in four words or fewer. That costs almost nothing to write and removes the most common follow-up question.
How long a presentation summary should be
Match length to the reader's decision, not to the length of the deck. A 60-slide deck can produce a 40-word summary if the finding is simple.
| Context | Target |
|---|---|
| Summary slide | 30–60 words |
| Email body | 100–200 words |
| Shared document or wiki | 200–500 words |
| Board pre-read | 300–500 words, plus the deck attached |
Above 500 words you are writing a report. That is a different deliverable with different conventions.
There is a practical reason to stay under the ceiling. Summaries get read on phones, in hallways, between meetings. Anything that needs scrolling twice gets saved for later and then not read.
Language that survives the read
Plain language guidance from the US federal government applies directly here. It is also more specific than most writing advice.
Use active voice. As Digital.gov's plain language guide puts it: "Active voice makes it clear who should do what. It eliminates ambiguity about responsibilities." In a summary that assigns a next step, that is the whole game.
Use present tense. The guide is direct about why: "The simplest and strongest form of a verb is present tense."
Watch for hidden verbs, the habit of turning an action into a noun. The guide's example is exact: write "We analyze data," not "We conduct an analysis of the data." Summaries attract this problem because the nominalized version sounds more formal. Formality reads as padding.
One more test costs nothing. Read the presentation summary out loud. Any sentence you stumble over will trip a reader too.
Common mistakes
- Summarizing the deck instead of the finding. The tell is an opening line that begins "This presentation covered."
- Burying the answer in the third paragraph. Readers stop early. Lead with the conclusion.
- Dropping the caveat. The summary travels further than the deck, so unqualified claims travel with it.
- Numbers without sources. The first challenge you cannot answer costs you the room.
- No owner on the next step. Actions without names do not happen.
- Writing it last, at speed. Draft the answer sentence before you build slide one. It improves the deck too.
- Reusing last quarter's wording. A recycled presentation summary hides the thing that changed, which is usually the point.
Summarizing someone else's presentation
Writing up a deck you did not build is a different problem. You have the slides but not the reasoning, and the two are rarely the same thing.
Work backwards from the ending. Presenters put their real conclusion in the last three slides, or say it out loud and never write it down. Start there rather than at slide one.
Then check the conclusion against the evidence yourself. A presentation summary you sign your name to becomes your claim, regardless of who made the slides. If the numbers do not support the closing slide, that gap belongs in your caveat line.
Ask the presenter one question before you publish: what did you leave out? The answer is usually the most useful sentence in the whole summary, and it almost never appears on a slide.
Attribution matters here too. Name the presenter and the date at the top. Six months later, nobody will remember whose analysis it was, and the summary is what survives.
One habit worth adopting for recurring meetings. Keep summaries in one place with consistent structure, so a reader can scan four of them and see the trend. A folder of inconsistent write-ups is barely better than no write-ups, because comparison becomes manual work.
A reusable template
Copy this and fill it in. Five slots, in this order.
Finding: [One sentence. The answer, not the topic.]
Evidence: [Figure 1, with source.] [Figure 2, with source.] [Figure 3, with source.]
Caveat: [What this does not cover.]
Next step: [Action, owner, date.]
Detail: [Link to the deck or the underlying data.]
The last slot matters more than it looks. A presentation summary that links back to its source gets trusted on the second reading, not just the first.
Keep the template in whatever tool your team already opens. A format nobody can find is a format nobody uses, however good it is.
Where the work actually goes
Writing the summary is fast. Finding the three numbers that hold it up is slow, especially when they live in different places.
That is the part worth automating. When figures sit across a spreadsheet, a database, and a PDF, assembling them by hand is where the afternoon goes. It is also where transcription errors get introduced.
Powerdrill Bloom handles that half. Ask across your documents and databases in natural language, and every number comes back with the page, the row, and the figure behind it. That last part is what lets you write the source note without going back to look.
The judgment stays yours. Which finding leads, what the caveat says, and who owns the next step are decisions no tool makes for you. Before you send, our deck review checklist is a useful last pass.
Frequently asked questions
What is a presentation summary?
It is a short piece of writing that carries a presentation's argument without the presentation itself. A good one states the finding, gives two or three supporting figures, names a caveat, and assigns a next step.
How long should a presentation summary be?
Between 30 and 60 words for a summary slide, and 100 to 200 for an email. A shared document runs 200 to 500. Length follows the reader's decision, not the size of the deck.
What is the difference between a summary and an abstract?
An abstract is written before the presentation, to help people decide whether to attend. A presentation summary is usually written after, to carry the finding to people who were not there.
Should a presentation summary include recommendations?
Yes, as the closing element, with an owner and a date attached. A summary that stops at the finding leaves the reader to invent the next step. They usually invent nothing.
Can I write the summary before building the deck?
You should. Drafting the answer sentence first forces you to know your conclusion, and it tends to shorten the deck. If you cannot write that sentence, the deck is not ready to be built. Our data deck outline guide covers what comes next.
Sources: Digital.gov, Writing for understanding, part of the plain language guide series adapted from PlainLanguage.gov.