19 August 2026 · By Heni Hazbay
How to Summarize a Meeting (With an Email Example)
A meeting summary is not the same as minutes. The five-part structure, a recap email you can copy, and where AI-generated summaries reliably get things wrong.
The short answer: Five parts — purpose, decisions, actions with owners and dates, open questions, next meeting. Send it the same day, keep it under 200 words, and put the actions where they are visible without scrolling. A summary is not minutes and should not try to be.
Most meeting summaries fail the same way: they recount the discussion in order, at length, and bury the two decisions somewhere in paragraph four. Here is the structure that works and the email that goes with it.
A summary is not minutes
Worth settling first, because people conflate them and then write the wrong document.
| Meeting summary | Minutes | |
|---|---|---|
| Purpose | Get the right people acting | Create an official record |
| Audience | Attendees and action owners | The organisation, and its future self |
| Structure | Loose, five parts | Fixed, conventional |
| Style | Plain, direct, can use “you” | Third person, past tense |
| Approved later | No | Yes |
| Typical length | 150–200 words | Half a page to several pages |
If your meeting has governance obligations — a board, a committee, anything with bylaws — you need minutes, and a summary is an optional extra. For an ordinary team meeting, a summary is usually the only document worth producing.
The five parts
1. What the meeting was about. One line. Not the agenda, the point. “We needed to decide whether to delay the launch.”
2. What was decided. The decisions, stated as decisions. This goes second because it is why anyone opens the email.
3. What happens next. Actions, each with a name and a date. Formatted as a list or table so they are scannable — this is the part people come back to.
4. What is still open. The questions the meeting did not resolve, and who is expected to resolve them. Leaving this out is how the same discussion happens again in a fortnight.
5. When you meet next. One line, with the date.
That is the whole structure. Notice what is missing: a chronological account of the conversation. Nobody reads that, and writing it is where most of the effort goes in a bad summary.
The recap email
Subject: Recap — Launch date decision — 19 Aug
Hi all,
We met to decide whether to move the launch. Short version: we are moving it
two weeks, to 14 October.
DECIDED
- Launch moves to 14 October.
- The pricing page ships with it, not before.
ACTIONS
- Priya — update the launch plan and tell the partner team — by Thu 21 Aug
- Dan — confirm the new date with support staffing — by Mon 25 Aug
- Me — redraft the announcement copy — by Wed 27 Aug
STILL OPEN
- Whether the October date affects the conference demo. Dan is checking with
events and will confirm this week.
Next: Tuesday 26 August, 10:00.
Shout if I have got any of this wrong.
[Name]Four things in that are doing work. The decision is in the second line, before anyone has scrolled. Every action has a name and a date — an action with neither is a wish. The open item names who is closing it, so it does not evaporate. And “shout if I have got any of this wrong” invites correction while people still remember, which is how errors get caught.
If your meeting also produces a formal record, how to send meeting minutes covers the more structured version of this email.
Writing it from a recording
The reliable way to produce an accurate summary is to work from what was actually said rather than what you remember — particularly if you were chairing, which means you were listening least attentively at exactly the moments that mattered.
The workflow that works:
- Record the meeting. Tell the room at the start.
- Skim the transcript for decision language. “So we’ll…”, “Let’s go with…”, “Agreed”, “I’ll take that”. Decisions announce themselves with a small set of phrases, and searching for them is faster than reading.
- Pull the actions. Anything phrased as a commitment by a named person.
- Write the five parts. Ten minutes, from an accurate source.
Record and Transcribe (our app, for iPhone and Apple Watch) records and transcribes automatically, with a label on every line — which matters a great deal here, because a summary that attributes a commitment to the wrong person is worse than no summary. Audio is written to disk as it captures, so a meeting that overruns or a phone that locks does not cost you the record.
Three transcriptions free, no card. The longer walkthrough is in recording and transcribing in-person meetings.
Where AI summaries go wrong
Automatic summarisation is genuinely useful and has three failure modes worth knowing, because they are consistent.
It confuses proposals with decisions. The most common and most costly error. Someone says “we could push it to October” early on, the group rejects it, and the summary reports that the launch is moving to October. Machines are good at extracting topics and poor at tracking whether a thing was agreed or discarded.
It misattributes. Without reliable speaker labels, a summary will assign a commitment to whoever spoke nearby. Check every name against an action before you send.
It flattens emphasis. Forty minutes of hedging and one decisive sentence get equal weight, so the thing everyone actually cared about can end up as bullet six.
The working rule: an AI summary is a first draft to correct, not a document to forward. Read it against your own memory of the meeting, fix the decisions and the names, and send your version. That is still far less work than writing it from scratch — which is the whole point.
The one-line test
Before sending, ask: could someone who missed the meeting act correctly on this alone?
If they would not know what was decided, who is doing what, or by when — the summary is not finished, however long it is.