The Difference Between Meeting Minutes and Meeting Notes (And Which One You Need)
Meeting minutes are a formal record of who attended, what was decided and what was voted on, kept as an official account. Meeting notes are a working document of actions, owners and open questions for the people doing the work. Choose by audience; avoid a hybrid that does neither job.
- Minutes: a formal record of attendance, decisions and votes.
- Notes: a working list of actions, owners and open questions.
- Choose by who will read it and why.
- Avoid a hybrid that does neither job.
- Some meetings need no record at all.
Meeting minutes are the official record of a meeting, typical of boards, committees and governed bodies: attendance, motions, votes and decisions, written neutrally and usually approved by members at the next meeting under procedures such as Robert's Rules of Order. Meeting notes are an informal working document for a team, focused on decisions, action items and owners, and circulated quickly. Choose based on who will read it and why.
You've been asked to take notes, or send the minutes, or both. The terms get used interchangeably, but they describe different documents for different readers, and a hybrid often serves neither.
What is the difference between meeting minutes and notes?
Meeting minutes are a formal record of what happened — who attended, what was decided, what was voted on, what motions were made. Their primary audience is future people who weren't in the meeting and may need to refer to the record months or years later: auditors, regulators, board members, legal teams, future employees. Their content is structured, complete, and somewhat dry by design. Meeting notes are a working document — what was discussed, what was decided, what action items came out, what's pending. Their primary audience is the team that was in the meeting and people adjacent to it who need to act on the outcomes in the next days and weeks. Their content is actionable, scannable, and biased toward usefulness over completeness. Both can include the same facts. They're organized for fundamentally different uses, and the same artifact does poorly at both jobs simultaneously.
What goes in meeting minutes versus meeting notes?
The structural difference shows up in what each artifact emphasizes. Minutes lead with attendance and absence, formal motions, votes, and decisions in the order they occurred — because the future reader needs to know that the right people were present, the right process was followed, and the formal record reflects what was officially settled. Notes lead with decisions and action items — because the team reader needs to know what to do next. Minutes are typically reviewed and approved at the next meeting (literally voted on) before becoming the official record; notes are typically circulated within hours and treated as a snapshot the team can revise informally. Minutes are written in past tense, third person, neutral voice ('the committee resolved to'); notes are often written in present tense, more directly ('Tom owns the timeline doc'). The two formats reflect their two purposes: minutes preserve, notes propel.
"Who will read this artifact, for what purpose, and when?"
The single best question to ask before deciding whether to write minutes, notes, or nothing at all. The answer determines the right artifact. 'Compliance auditor, in 18 months, to verify the decision was made properly' = minutes. 'My team, this week, to act on the action items' = notes. 'Nobody, for nothing, ever' = neither — send a three-line Slack message instead and reclaim the forty-five minutes you would have spent on documentation. Skipping this question is how teams end up producing whichever document they always produce, whether or not anyone needs it.
When do you need minutes instead of notes?
Teams often use whichever term their company has historically used, regardless of whether it's the right artifact for the meeting in question. The choice should be made on use case. Use minutes when: there's a regulatory or compliance requirement, the meeting is at board or governance level, the decisions may need to be referred to as the official record at a later date, or attendees include people who might leave the company and the record needs to outlast them. Use notes when: the meeting is operational, the audience is the team and adjacent stakeholders, the goal is to drive action in the next few days, and nobody is going to read this in three years. Most workplace meetings — standups, planning meetings, project syncs, retrospectives, 1:1s — call for notes. A small fraction — board meetings, formal decision-making bodies, regulated industries — call for minutes. Picking the wrong one wastes effort if you over-formalize and creates risk if you under-formalize.
Can one document serve as both minutes and notes?
A common failure mode in meeting documentation is the hybrid: a document that's trying to be both minutes and notes simultaneously. It has the formal attendance list and motions of minutes, but also the action items and tensions of notes. It's longer than notes, more casual than minutes, and serves neither audience well. The future reader looking for the record can't quickly find what was decided. The team reader looking for action items has to wade through formal preamble. The hybrid usually emerges because one person is writing for one audience while the boss is reading for another, and nobody named the mismatch. The fix is to choose explicitly: if this meeting needs minutes, write minutes and skip the action-items section (or move it to a separate operational follow-up). If it needs notes, write notes and skip the attendance and motions ceremony. If it needs both — rare, but it happens — write two documents. Two clean artifacts beat one contaminated one almost every time.
Does every meeting need minutes or notes?
There's a third option most documentation guides skip: no formal artifact at all. Many meetings — quick stand-ups, hallway syncs, brainstorm sessions where the brainstorm document itself is the output, 1:1s where the relevant follow-ups live in private channels — don't actually need either minutes or notes. They need a Slack message ('In our standup: A is unblocked, B at risk on data dependency, C taking customer follow-up'), or an updated calendar entry, or just a verbal recap to the people who weren't there. The signal you've reached this category: are you producing notes or minutes mostly because notes or minutes are what one produces after meetings, rather than because someone will use this specific document for something specific? If yes, the right artifact may be no document. The hour you'd have spent writing notes nobody reads is better spent on the actual work the meeting was meant to drive. The discipline is to ask 'who will use this artifact, for what, when?' before starting to write — and to be willing to skip the artifact entirely when the honest answer is 'nobody, for nothing, never.'
Get the right artifact in seconds — minutes, notes, or a Boss Update
The Debrief takes a meeting transcript and produces the format you actually need: structured notes (decisions, action items, tensions, open questions) for working teams, or a Boss Update (3–5 sentence upward summary) for managers, or full distilled output you can adapt into formal minutes. Pick the artifact that matches the use case rather than producing the hybrid that fails both.
Found this useful? Link to it.
https://deftbrain.com/guides/meetings/the-difference-between-meeting-minutes-and-meeting-notes
Free to read, no account, no paywall — link away.