How to write meeting minutes

Published · Updated

A record the meeting approves, not a summary of what was said — and the difference decides almost everything else.

Minutes are not a summary of the discussion. They are a record that the meeting itself approves at its next sitting, and in a dispute they are read as evidence of what happened. That changes how you write them: a detailed retelling of the argument is a liability, not a virtue. Record what was decided, who moved and who seconded it, how the vote went, and what happens next. Leave out the adjectives, the reasoning you did not hear stated, and the names of people who were simply speaking.

Three documents, and what makes them different

Three things get called the same thing, and the confusion is where most of the trouble starts.

Notes are yours. They exist to help you, nobody checks them, and they can be as partial as you like. A transcript is what was said, in order, with no judgment applied — useful precisely because nobody edited it. Minutes are the meeting’s own record, written afterwards and approved by the people who were present.

Only the third one is approved by anyone, and that single fact decides everything else about how it is written. A document that a group has to agree to is written narrowly on purpose: the less of it that nobody agreed to, the less of it there is to argue about.

It follows that minutes are not written during the meeting. During the meeting you take notes, and that is its own skill with its own problems. The minutes come after.

What belongs in the minutes

The list is short, and shortness is the point.

  • The date, the time, where it was held, and who was present — with apologies from those who were not.
  • Each item considered, in the order it was taken.
  • Decisions, in the words the meeting settled on rather than your paraphrase.
  • Who proposed a motion and who supported it, and how the vote went.
  • Actions, each with a name and a date attached.
  • The time the meeting closed, and when the next one is.

The format for all that lives on a meeting minutes template, which is a separate matter from what this page is about.

What to leave out, and why

This is the part almost nobody writes down, and it is what separates minutes that hold up from minutes that cause trouble.

The discussion itself. Who argued which way, and how heated it got, is exactly the material a disagreement six months later will be fought over.

Adjectives and adverbs. “A lively debate” and “a productive exchange” are your assessment, and your assessment is not something the meeting voted on. Neutral wording is not bureaucratic dullness; it is the absence of claims nobody approved.

Reasons you inferred. If someone did not state why they voted as they did, writing your guess into an approved record attributes a motive to a person who never offered one.

Names outside procedural roles. A record of decisions and a record of who said what are different documents. The second one changes how people speak in the room, and usually not for the better.

Draft, circulate, approve

The document goes through three stages, and skipping the middle one costs more time than it saves.

Write the draft while it is fresh, then send it round with a deadline for corrections. Corrections raised in writing beforehand are settled quietly; corrections raised at the next sitting take up the meeting’s time and make everyone present pick a side.

At the next sitting the minutes are approved. After that they are not edited. If something in them turns out to be wrong, the later meeting decides the correction and that decision is recorded there — so the record shows both what was approved at the time and what was amended afterwards. A document that people approved is not something one person quietly rewrites later, and the procedure exists to make that impossible rather than merely impolite.

Formal minutes and working minutes

Not every meeting needs the full procedure, and pretending otherwise is why minute-taking has a reputation for pointlessness.

A board, a committee, a body with members and votes needs all of it: motions, seconds, the count, the approval at the next sitting. A working meeting of a handful of colleagues needs three things — decisions, actions with owners and dates, and anything deliberately postponed. Everything else is ceremony borrowed from a room that is not yours. There is a layout for board minutes, part by part with each part marked by who fills it in.

The mistake to avoid is the reverse of the obvious one. Most people worry about being too informal; the more common failure is a small team spending twenty minutes on the form of a document that two people will read once.

Making it easier on yourself

One habit does more than any template. Write the minutes from a record rather than from memory.

The gap between the meeting and the writing is where accuracy goes. If you have the transcript in front of you, the question “did they say two weeks or two months” is answered in a few seconds instead of by an email exchange that makes everyone re-litigate the point.

One caution that matters more here than anywhere else: check who said what before you write it down. Automatic speaker labelling is good and it is not perfect, and an error about which of two people proposed a motion is worse than having no record of the motion at all. It is the one thing on this page worth verifying by hand every time.

Where an automatic summary stops being enough

An automatic summary is not minutes, and it is worth being exact about why rather than treating it as a matter of taste.

A summary is judged on how well it reflects what was said, so it is complete on purpose. Minutes are judged on how little is in them that nobody agreed to, so they are incomplete on purpose. The two are optimised against each other, which is why a good summary makes poor minutes and good minutes make a poor summary.

There is also the approval, which no tool can supply. A summary is produced; minutes are agreed. Nothing that runs automatically can do the second thing, because the second thing is people accepting a version of events.

What we make, and what it does not replace

We make a Mac app that records the meeting, recognises the speech on your Mac and by default sends no audio anywhere; the transcript syncs to our servers, and when a summary is assembled, that text goes to a language model. Every quote shows you where it was said — open it and the transcript opens at that place. Notes you type during the meeting stay in their own layer, separate from what was said, which is the separation the minutes need anyway. If you choose server recognition in Settings, the audio is sent to Dalm and our speech recognition providers and deleted once the text is ready.

It gives you a draft of the minutes and the ability to check a wording in seconds. Approving them stays with the meeting.

The free plan covers recording, transcription and search, and asks for no card. Where the text goes afterwards is on privacy, and how the recognition works is on how it works. If recording a conversation raises a question about what you are allowed to do, that belongs on recording consent laws rather than here.

Questions

What is the difference between meeting minutes and meeting notes?
Notes are yours and answer to nobody; minutes are the meeting's own record and are approved by the people who were there. That approval is the whole difference. Notes can be wrong in private and cost you nothing, while minutes that are wrong get corrected in public, at the next sitting, in front of everyone who disagrees with them.
Should meeting minutes record the discussion word for word?
No, and this is where most advice goes wrong. A detailed retelling of an argument gives everyone who was in the room something to dispute, and gives anyone reading later a version of events nobody agreed to. Record what was decided rather than how the room got there. The reasoning is worth keeping in your own notes, which belong to you.
Should I name people in the minutes?
Only in their procedural roles — who proposed something, who supported it, how the vote went, who took on an action. Naming someone for simply speaking turns a record of decisions into a record of who said what, and that is a different document with different consequences for the person named.
Who approves the minutes?
The meeting itself does, usually at its next sitting, and until then the document is a draft however finished it looks. This is why circulating a draft early is worth the effort: corrections raised in advance are easier than corrections raised out loud.
Can approved minutes be corrected?
Not by editing the old text. A correction is itself a decision of the later meeting and is recorded there, so the record shows both what was approved and what was later amended. Quietly fixing a document that a group has already approved defeats the reason it was approved at all.
Can an AI summary be used as meeting minutes?
Not as they stand, and we make one, so we are saying this against our own interest. A summary reflects what was said; minutes are what the meeting agrees happened, and the two are not the same thing — a summary is judged by how complete it is, minutes by how little is in them that nobody agreed to. What a summary and a transcript are genuinely good for is the raw material: you write the minutes from them instead of from what you remember.