Meeting minutes are a record of decisions, not a transcript of conversation: who attended, what was agreed, who owns what and by when. Draft them inside the meeting itself, tidy them within the hour, and send them while people still remember the room. The part most guides skip is that the record is only ever as accurate as what you could actually hear. If half the call was crosstalk, a dropping remote line and a keyboard under somebody's microphone, no amount of careful editing recovers the sentence you missed. This page covers what to include and a format you can copy, then the harder half: writing from a rough call or a messy transcript.
What the record must contain, and what to leave out
The test for any line in your meeting minutes is whether somebody who missed the room could act on it without asking a follow-up question. That rules out most of what gets typed in real time. Nobody needs the discussion; they need the outcome, the owner and the date. Attribution earns its place where a decision was contested or where a named person committed to something, and almost nowhere else.
- Header: meeting name, date, start and end time, location or platform.
- Attendees, apologies, and anyone who joined late or left early.
- Agenda items in order, each with a one-line summary of the discussion.
- Decisions written as decisions: what was agreed, and on whose authority.
- Action items: owner, task, due date. One line each, no prose.
- Anything deferred, with the reason and the point at which it returns.
- Date of the next session, and who is taking the notes.
That skeleton is deliberately plain, and plain is the point: a reader should find the actions in the same place every time, which is what makes a template or a worked sample worth keeping. Two habits carry most of the quality. Write decisions in the past tense and in full sentences, so they still parse a year later, when the shorthand means nothing. And never log a discussion point without saying how it ended; deferred is a perfectly good example of an outcome.
A format that survives a real meeting
Build the document before the meeting starts, not after. Paste the agenda in as headings, pull the attendee list from the invite, and leave an empty action table at the bottom. During the call you are then filling gaps instead of composing, which is the difference between meeting minutes that get finished and notes abandoned at lunchtime. Type outcomes, not the sentences people said. When you miss something, mark it with a bracket and the clock time and carry on: a gap you resolve in ten minutes beats a confident guess that turns out wrong.
When you are the secretary and a participant
Doing both jobs badly is the default outcome, so protect the record first. Ask at the top that decisions be restated once they are agreed. A plain line such as so we are going with option B, and Priya owns it by the 14th, hands you a clean sentence to capture. If you need to contribute to an item, say so and stop typing for it; a thirty-second gap you have flagged is honest, while a paraphrase written while you were talking is not. Best practice is admitting which moments you could not cover.
Working from a rough call or a messy transcript
The biggest improvement to your meeting minutes happens before anybody speaks. Speech is easier to follow, for you and for any transcription tool, when the signal reaching the call is clean, so treat audio as part of your preparation. Work through a pre-meeting audio checklist, and if you are hosting, ask anyone in a noisy room to use a headset. The comparison of laptop mics, headsets and software explains why that choice matters more than the room does.
During the call, log the clock time whenever you lose a passage. Two timestamps and a note naming the item will find that section in a recording in seconds. If a speaker is unintelligible, ask them to repeat the decision for the record; that interruption is cheap. When another room is bleeding in, a line about background voices is useful context later, and anyone whose input sounds wrong should test the microphone before rejoining.
Afterward, read the transcript against your skeleton rather than the other way round. Search it for the exact wording of decisions, figures and dates, and leave the rest alone. Krisp ships an AI meeting note taker alongside its noise cancellation and processes audio on-device; our Krisp review covers the split between the desktop app and the mobile apps, which do transcription and notes only. The owners and dates still need a human pass.
Edge cases that wreck the record
Crosstalk you could not untangle
Write what was decided and leave out who said what. If the decision was contested, note that two positions were argued and record the outcome rather than rebuilding the argument. Where people overlapped so badly that even the recording is ambiguous, ask them to confirm in writing. One short message beats an invented quotation.
A remote line that kept dropping
Flag it: name the item, the participant and the fact that their audio was intermittent. That protects everybody if the decision is questioned later. Then deal with the cause before the next session, because a mic picking up background noise is often the same device struggling on a weak link, and echo has its own set of fixes.
Names, figures and acronyms
Transcripts guess at proper nouns, and they guess confidently. Check every name, number, date and acronym against the attendee list, the agenda or the shared document before you send. If you cannot verify a figure, write the range you are sure of and ask in the covering message. A wrong number outlives the meeting it came from.
Frequently asked questions
How soon should the notes go out?
Within a day, and sooner when actions start immediately. Accuracy falls away once your memory of the room fades, and late meeting minutes stop being useful to anyone who has to act. Draft during the call, tidy in the half hour afterward, and send once every action has a named owner and a date.
Do they need to be approved?
In formal bodies, yes: the record is reviewed and accepted at the following meeting, with corrections logged rather than edited in silently. For internal teams, approval is informal. Send the draft, invite corrections for a day, then treat it as final. Keep one canonical version rather than competing copies.
Is a recording enough on its own?
No. A recording is evidence, not a record, and nobody rewatches an hour to find a decision. Record only where participants have agreed and your policy allows it, then use the file to check the passages you were unsure about. The written summary is still the thing people read and act on.
Does a transcript replace the notes?
No. A transcript is raw dialogue with no judgment applied: it keeps every false start and buries the outcome. Use it to search for exact wording and numbers, then write the summary yourself. Automated note takers give a workable first draft, but decisions, owners and dates need checking by somebody who was there.
Will noise cancellation improve transcription?
It can. Speech recognition works from the same signal your ears do, so a microphone carrying a fan, a keyboard and a second conversation leaves the model less to work with. Cleaning the input before it reaches the call, with a headset, a quieter room or software, helps more than later editing.