Most meeting notes fail in one of two ways. Either they are a near-transcript that nobody rereads, or they are so sparse that a week later nobody can tell what was actually decided.
The fix is not writing faster. It is being clear about what notes are for.
Notes have exactly three jobs
Good meeting notes answer three questions:
- What did we decide?
- Who is doing what, by when?
- What's still open?
Almost everything else can go. The path to a decision is rarely worth recording once the decision is made. Restated background, discussion that circled and resolved, general agreement — none of it survives contact with a reader a week later.
The test: if someone who missed the meeting read only your notes, would they know what was agreed and what they owe?
A template that works for most meetings
[Meeting name] — [date]
Present: [names]
DECISIONS
- We're going with X, not Y. (Reason, if it isn't obvious.)
ACTIONS
- [Owner] — [what] — by [date]
OPEN
- [Question still unresolved] — who's resolving it, by when
NOTES
- Anything genuinely worth keeping that isn't the above
Two rules make this work:
- Every action has a name and a date. "Someone should look into pricing" is not an action. "Priya — draft the pricing options — by Thursday" is.
- Decisions are written as decisions. Not "we discussed whether to delay the launch" but "we're delaying the launch to March."
Three structures, and when each fits
The three-part structure above — decisions, actions, open — fits working meetings, stand-ups, planning, and client calls. It is the right default.
Cornell notes — a narrow cue column beside a wider notes column, with a summary at the bottom — suits learning: lectures, training, conference talks. It is built for material you will revise later, not for decisions you need to act on.
Chronological with headers suits long, multi-topic meetings such as board or committee sessions, where the sequence matters and people need to find the section on one particular agenda item. Use agenda items as headings.
Do not use a heavier structure than the meeting deserves. A fifteen-minute stand-up does not need a Cornell layout.
The real problem: you cannot listen and transcribe at once
This is the thing most advice skips. Taking detailed notes actively degrades your participation, because writing down what was just said uses the attention you would otherwise use to think about it.
If you are running the meeting, or you are there because your judgement is needed, detailed note-taking is working against you.
Three ways out:
Rotate the note-taker. Whoever is least central to a given discussion takes notes for it.
Note only decisions and actions, live. Skip everything else. This is fast enough to do without losing the thread — you are writing one line every few minutes, not continuously.
Record it, and write the notes afterwards. The most complete option, and increasingly the default.
Working from a recording instead
Recording changes the job from capture to editing, which is much easier and much more accurate.
The practical workflow:
- Record the meeting. Conferencing platforms have this built in; for in-person, a phone is enough. (How to record a meeting covers both, including consent.)
- Transcribe it. Upload the recording and get back text with each distinct voice grouped under its own editable label. The labels mark where the speaker changes rather than identifying anyone, so name them once and the transcript tells you who said what.
- Pull out decisions and actions. Skim the transcript, lift the three sections into your template. An hour-long meeting takes a few minutes to work through as text.
- Send it the same day. Notes that arrive a week later do not get read.
The transcript is the part that makes this fast. A recording is not a shortcut — nobody replays a two-hour meeting. A transcript is searchable and skimmable, so finding the moment a number was agreed takes seconds.
You can transcribe a meeting recording free, with no signup, on our meeting transcription page — voices are grouped automatically, which matters here specifically because "who committed to this" is the thing notes most often get wrong. Check any commitment you're going to write down against the recording.
Sending them out
- Same day. Momentum is most of the value.
- Actions at the top, not buried under discussion. Most people read the first three lines.
- Tag owners directly wherever your team works, rather than relying on people to find their own name.
- Keep them somewhere findable. Notes that live only in one person's inbox are notes nobody can check.
Common mistakes
- Writing everything. A near-transcript reads like nothing; the decisions are buried.
- Actions without owners. Anything assigned to "the team" is assigned to nobody.
- No dates. "Soon" never arrives.
- Recording someone's exact words in a way that misrepresents them. If a phrasing matters, check it against the transcript before circulating it.
- Confusing a transcript with notes. A transcript is the raw material. Notes are what you make from it.
Related reading
- How to record a meeting — in person and online, including consent
- Meeting transcription — speaker-labeled transcripts from a recording
- Zoom transcription · Teams transcription · Google Meet transcription