Summary, minutes, transcript and notes are four different documents
They get used interchangeably, and that is where most of the disappointment comes from: people expect one thing and receive another. The difference is not length — it is the question each one answers.
| Document | Question it answers | Who reads it |
|---|---|---|
| Meeting summary | What came out of this meeting | Participants and anyone affected |
| Minutes | What was formally decided, by whom | Those who need the record later |
| Transcript | What was said, word for word | Almost nobody — it is raw material |
| Personal notes | What I need to remember | Their author |
The summary is the only one of the four written for someone who was not in the room. That single constraint decides everything about its shape: no in-jokes, no "as we discussed", no pronouns without names. Minutes are a neighbouring document with its own rules — we covered them in the piece on meeting minutes.
What goes into a summary people actually read
1. Decisions
Each decision as a finished sentence with the reason attached. "We ship tier B first — it unblocks two enterprise deals." Without the reason the decision gets re-litigated in three weeks by someone who was not there; with it, the argument ends before it starts.
2. Commitments: who, what, by when
Three fields, all mandatory. A commitment without a name belongs to nobody; without a date it never happens. This is the part that turns a summary from a document into something that changes work — and it is also the part most often written as "the team will look into it". What to do with that list afterwards is in the piece on action items after a meeting.
3. Open questions
What was raised and deliberately left unresolved, with the date you return to it. An open question that is not written down does not disappear — it resurfaces at the worst possible moment, and by then nobody remembers what the disagreement was about.
4. Context for those who were not there
Two or three sentences: why the meeting happened and what changed as a result. This is the part everyone skips and the part the absent reader needs most.
WHY WE MET
[one sentence]
DECISIONS
· [what was decided]. Reason: [why]. Decided by: [name].
COMMITMENTS
· [name] — [what], by [date]
OPEN
· [question]. Back to it on [date], owner: [name].
NEXT MEETING
[date, or "none planned"]
Automatic summaries: what to expect and where they stop
Most conferencing platforms now generate summaries automatically, and the value is real. The limits are worth knowing before you rely on one.
They live inside one platform. A summary feature belongs to the service the call ran on. Move the meeting elsewhere — a client's Zoom, a partner's Teams, a phone call — and the feature is simply absent.
They usually require a paid business plan. On personal accounts the function is often unavailable entirely, which is the single most common reason people search for why their summary never arrived.
They have to be switched on at the start. Recognition is streaming: if nobody pressed the button in the first minute, the meeting cannot be summarised retroactively.
Delivery is narrower than people assume. The result typically goes to the organiser, not to every participant — so "the summary did not arrive" often means "it arrived, to somebody else".
Yandex 360 measured this on their own users: wrapping up a meeting takes about 17 minutes — 7 during the call and 10 after it. After automatic summaries launched, the share of meetings where nobody ever sent the outcome fell by 27 percentage points. The exact figures matter less than the order of magnitude: a quarter of an hour per meeting, and it is the part people most often skip.
Writing the summary by hand
The five-line rule
Write it in the last five minutes of the meeting, out loud, while everyone is still there. "So: we decided X, Anna takes Y by Friday, the pricing question goes to next week." Two benefits at once — the disagreements surface immediately rather than in the reply thread, and the writing is already done when the call ends.
The follow-up email
Send it the same day. A summary that arrives two days later has already been overtaken by three other conversations, and nobody corrects it because nobody remembers precisely enough. Same day, five lines, plain text in the body — not an attachment.
Five mistakes that make a summary useless
- Retelling instead of extracting. A chronological account of who said what is a transcript with extra steps. Decisions and commitments only.
- Commitments without names. "We need to check the integration" is a wish, not a task.
- Writing for those who attended. They already know. Write for the person who reads this in a month.
- Sending it late. After 24 hours it is an archive document, not a working one.
- Length. Past one screen it stops being read, and the parts that mattered are lost inside the parts that did not.
Where Whisperer fits
Everything above runs into one step: somebody has to capture while the meeting is happening, and during a meeting everyone is busy with the meeting. Built-in summaries solve this inside a single platform and under its plan conditions. Whisperer solves the same problem from the other side — from your computer rather than from the conferencing service.
It keeps a streaming transcript during the conversation across two independent audio streams — microphone and system audio — so replies are labelled by speaker and it is clear who proposed what. That works on top of any call and on a personal account: no corporate domain and no paid plan on the platform's side. The limit is firm and worth stating plainly: it listens to a live conversation, and a finished recording cannot be uploaded.
From the conversation it assembles a meeting map — topics, decisions and tasks as separate nodes; tasks go to the tracker with an assignee and a date, and the history stays searchable in one place regardless of which service the call ran on. For cross-language conversations there is real-time translation.
If the idea of capturing without a bot joining the room is what appeals, it is covered in meeting notes without a bot; the wider picture of this tool category is in AI meeting assistants. The free tier is 60 minutes — enough for one real meeting.
Frequently asked questions
What is the difference between a meeting summary and minutes?
A summary answers "what came out of this meeting" and is written for people who were not there. Minutes are the formal record: what was decided, by whom, on what basis. A summary is read the same day; minutes are consulted later, when something needs to be proven.
Why did my automatic summary never arrive?
Four usual reasons, three of them about access rather than failure: the feature was never switched on at the start of the call; the account is personal rather than corporate; the organisation has no paid plan; or the summary did arrive — to the organiser, not to you. Check the organiser's inbox before assuming it failed.
Can I get a summary for free?
On most conferencing platforms the built-in feature requires a paid business plan. Tools that work from your side of the call, independent of the platform, usually have a free tier — enough to test on a real meeting before deciding.
Do I have to record the meeting to get a summary?
Not necessarily. There are two approaches: processing a finished recording afterwards, and recognising speech live during the conversation. The second needs no file at all — the text exists by the time the call ends.
Who should write the meeting summary?
Not the person chairing — running a discussion and writing it down at the same time does not work, and the writing is what suffers. Either a designated note-taker, or automatic capture with a two-minute review afterwards. Reviewing beats writing from scratch: the facts are already there, only the emphasis needs correcting.
How quickly should the summary go out?
The same day, ideally within the hour. After that, participants have moved on to other conversations and stop correcting errors — not out of indifference, but because they no longer remember precisely enough to be sure.
How long should a summary be?
One screen. Decisions, commitments with names and dates, open questions, two sentences of context. Anything longer stops being read, and the parts that mattered get lost inside the parts that did not.
The bottom line
A summary is not a shortened transcript — it is the answer to "what came out of this meeting", written for someone who was not there. Decisions with reasons, commitments with names and dates, open questions with return dates, two sentences of context, sent the same day and fitting on one screen.
The reliable part to automate is the capture, because it is the first thing to fall away under time pressure. Create an account — 60 free minutes a month — turn on the transcript at your next call and compare two versions: the one you would have written from memory, and the one assembled from what was actually said.