What makes a summary useful
A summary has one job: to save the reader time without misleading them. That means it is short, it says what was decided and by whom, it lists what happens next, and it admits what is still uncertain.
The five steps
1. Start from the purpose
Ask what the meeting was meant to achieve. The summary should answer that first: "We agreed the launch date and the scope for phase one."
2. Pull out decisions
Scan your notes for moments of agreement, and write each as a full sentence. If nobody clearly agreed, it is not a decision.
3. List the actions
For each follow-up write the action, the owner and the date. If any is missing, mark it.
4. Capture what is still open
List questions that were raised but not answered, and who will answer them.
5. Cut everything else
Remove discussion that did not lead to a decision, an action or an open question. Keep a link to the full notes for anyone who wants detail.
A before-and-after
Before (raw notes):
"Talked about the homepage a lot, Priya thinks fine, Dev wondering about speed. Pricing page needs redo, Dev can do Thursday. Maybe customer portal later? Budget 40k I think, Priya to check."
After (summary):
- Purpose: review progress on the website build.
- Decisions: the homepage stays as is.
- Actions: Dev redoes the pricing page by Thursday. Priya confirms the budget figure.
- Ideas, not agreed: a customer portal later.
- Open: whether the budget is 40,000.
Notice that "I think" stayed uncertain instead of becoming a fact.
A quick checklist
- Can a stranger understand it in a minute?
- Does every action have an owner and a date?
- Are ideas and decisions kept apart?
- Did you keep numbers exactly as stated, or flag them as unconfirmed?
- Is anything in it you cannot trace back to the discussion?
Summarizing with AI
AI can do the first draft of these steps quickly. The risk is that it smooths over uncertainty. A good tool keeps decisions apart from suggestions and flags what is unclear, as MeetMemo's summaries do, but you should still check names, numbers and decisions against the transcript. See AI meeting summaries. For the document format, see the meeting minutes template and how to write meeting minutes.
How long should a summary be?
A rule of thumb that works: one line of summary per ten minutes of meeting, plus the decisions and actions. A 30-minute call might yield a three-line overview, two decisions and three actions. If your summary is longer than the notes it came from, you are transcribing, not summarizing.
Summaries for different readers
The same meeting needs different summaries depending on who reads them.
- For attendees, list actions first. They already know the discussion.
- For a client, list decisions and next steps first, in neutral language, and leave out internal commentary.
- For a manager or sponsor, list outcomes, risks and decisions needed from them.
- For your future self, include context: why a choice was made, and what alternatives were rejected.
You can keep one set of notes and write a short summary for each audience.
A second example: a client call
Raw notes: "Priya wants everything by the autumn campaign, which starts around November 15 I think. Five pages. Maybe a blog. Hosting? She'll ask IT. We said we'd send revised scope Friday. Budget not discussed properly, she said 'let's see the proposal'."
Summary:
- Purpose: agree scope and timing for the new website.
- Timing: target launch before the campaign, which starts around 15 November (date to confirm).
- Scope: five pages. A blog is an idea for later, not agreed.
- Actions: we send the revised scope on Friday. Priya asks IT about hosting.
- Open: budget, to be addressed in the proposal.
Notice how "I think" became "to confirm" and "maybe" became "an idea, not agreed".
Mistakes that make summaries useless
- Summarizing the topics instead of the outcomes. "We discussed pricing" tells the reader nothing. "Pricing page to be redone by Thursday" does.
- Dropping the owners and dates.
- Smoothing over disagreement. If two people disagreed and it was not resolved, say so.
- Adding information that was not said. A summary is not the place for your interpretation.
- Making it too long to read.
Frequently asked questions
Should I summarize during or after the meeting?
Capture decisions and actions during, and write the summary within a few hours after, while you remember the context.
Is an AI summary good enough to send to a client?
Treat it as a draft. Check every decision, name and number, and remove anything internal before sending.
What is the difference between a summary and minutes?
A summary is a short overview for understanding. Minutes are the formal record. See how to write meeting minutes.