How to take better meeting notes
In short: Most meeting notes fail because they try to be a transcript. This guide covers what to write down live, what to let a recording handle, and the four-part structure that makes a note worth rereading.
Meeting notes have one job: to make the meeting useful to someone who is not currently in it — including you, next week. Almost every problem with them comes from confusing that job with a different one, which is recording what was said. Those are separate tasks, and once you stop trying to do both at once, both get easier.
Decide what the note is for before the meeting starts
A note written for a decision log looks nothing like a note written for a handover, and neither looks like the note you take when you are the one who has to do the work afterwards. Choosing before the meeting removes most of the in-the-moment hesitation about whether something is worth writing down.
In practice three purposes cover nearly everything: a record of decisions, a list of what you personally owe, and context for people who were not there. Write the purpose at the top of the note. It takes five seconds and changes what you notice.
Capture live, structure later
Trying to produce a clean, organised note during the meeting is the single most common mistake, because organising costs attention you need for listening. Capture roughly and in order; impose structure afterwards, when you know how the discussion ended.
If the session is recorded and transcribed, the live capture layer becomes even smaller. You are no longer responsible for the words — only for the markers: a line at each moment you will want to return to.
- Write decisions the moment they land, in the speaker's own words
- Mark disagreements — they predict what will come back
- Note anything assigned to you, with the deadline if one was said
- Leave the rest to the transcript
The four-part structure that survives a busy week
Whatever happened in the room, a useful note ends up in four parts. Put them in this order, because it matches the order people read in: they want the outcome first and the reasoning only if they disagree with it.
- Decisions — what was settled, stated so it makes sense out of context
- Actions — one owner each, with a date where one exists
- Open questions — what was not settled, and who needs to settle it
- Context — the discussion, or the transcript, kept underneath
Write decisions so they survive without you
"Agreed to go with option B" is meaningless in three weeks. "Agreed to ship the import feature without CSV support in v1, because the parser work would delay the release by a month" still works, and prevents the same discussion from happening again.
An action item without an owner is a wish
If nobody's name is attached, the item will not happen, and the note will quietly become inaccurate. When an action has no obvious owner, that itself is worth recording as an open question.
Let AI do the first pass, then correct it
An AI write-up is very good at the mechanical part: pulling candidate decisions and action items out of a transcript, and grouping a rambling discussion by topic. It is unreliable at knowing which of two contradictory statements was the one that stuck.
So use it as a first draft and read it against the transcript once. The correction pass takes a couple of minutes and is what makes the difference between a note people trust and a note people quietly stop reading.
- Generate the summary, then verify each decision against the source
- Fix names and attributions first — those errors propagate
- Delete anything the model added that nobody actually said
Send the note the same day
A meeting note's value decays fast. Sent within a few hours, it corrects misunderstandings while everyone still remembers the discussion; sent three days later, it mostly documents a disagreement that has already started.
Send the decisions and actions in the body of the message rather than as a link. The people most likely to have misunderstood something are the least likely to click through.
Key points
- Write the purpose of the note at the top before the meeting starts.
- Capture markers live; let a recording and transcript carry the words.
- End with decisions, actions with owners, open questions, and the transcript underneath.
- Treat any AI summary as a draft, and check it against the source once.