What are meeting minutes?
Meeting minutes are a short record of what was decided, who owns each decision and by when. Everything else — the date, the attendee list, the links — is scaffolding around those three things. There is exactly one test of quality: minutes work to the extent that someone who missed the meeting can act on them. If they can't, the document has failed, however many pages it runs to.
Minutes get confused with three neighbouring documents. The difference isn't length or formality — it's the question each one answers.
| Document | Question it answers | When you need it |
|---|---|---|
| Minutes | What was decided, who does what, by when | Any meeting where decisions were made or commitments taken |
| Transcript | Who said what, word for word | Negotiations where wording carries cost, interviews, incident reviews. The source minutes are extracted from |
| Personal notes | What matters to me specifically | Always. Not circulated, and never an agreement |
| Follow-up email | What is now required of the recipient | External meetings: clients, vendors, candidates |
That gives you the three jobs minutes actually do, none of which is "prove the meeting happened". They lock in agreements, so nobody re-litigates them a month later. They assign ownership — every action acquires a name and a date. And they carry context to people who weren't in the room, without a corridor briefing.
How do you structure meeting minutes?
The order isn't arbitrary. It runs from what a reader needs fastest to what they'll skim selectively, which is why decisions sit above discussion: the outcome matters more than the route to it. The first two screens have to answer "what am I supposed to do now" — if that takes scrolling, the structure is wrong.
| Section | What goes in it | Common mistake |
|---|---|---|
| Header | Subject, date, start and end time, who chaired | Date only. Without duration nobody can see, six months on, what the question cost — and that's what decides whether you meet again |
| Attendees | Who was there, and who was invited but absent | One merged list. An absentee isn't automatically bound by a decision but must be told about it — this is your distribution list |
| Context | One or two sentences on why the meeting happened at all | Half a page of backstory. Three months later people read those two sentences and nothing else |
| Decisions | What was resolved, on what grounds, who made the call | "Discussed pricing", "talked through the timeline" — a description of how time passed instead of an outcome |
| Actions | Action verb, definition of done, one owner, a calendar date | "The team" in the owner column and "next week" in the date column |
| Open disagreements | One line per unresolved position: whose it is, what's at stake, when you return to it | Dropping the section and dissolving the argument into "we agreed to revisit this" |
| Materials | Links to the documents, mockups and dashboards referenced | Attached files instead of links: the copy diverges from the live version the same day |
Seven sections is a ceiling, not a required minimum. A thirty-minute working call usually keeps four alive: header, decisions, actions, disagreements. Delete an empty section rather than leaving it with a dash — a dash reads as "we never got there", not as "there wasn't any".
How much detail should minutes have?
This is the question most templates never answer. The level is set not by how long the meeting ran or by the note-taker's taste, but by the cost of being wrong: what a misread sentence will cost a month from now.
| Level | What makes it into the text | When to use it |
|---|---|---|
| Resolution minutes | The wording of each resolution and who carried it. No discussion at all | Boards, shareholder meetings, anything where the document has legal weight and a stray sentence becomes evidence |
| Action minutes | Decisions with grounds, actions, disagreements, links | The default. Covers roughly nine working meetings in ten |
| Discussion minutes | All of the above plus each side's position and the arguments that did or didn't land | Negotiations where it matters who pushed for what; incident reviews; meetings you know will be revisited under pressure |
Some things stay out at every level: judgements about people, asides, jokes, and — separately — numbers that were said aloud but confirmed by nobody. A figure spoken in a meeting and written into minutes is treated as agreed within a week, no matter that nobody checked it.
Good action minutes for an hour-long meeting run to about a page. If you have three, you're recording the discussion. If you have five lines and not a single name in them, you're recording that a meeting occurred.
How do you take minutes during the meeting?
Minutes are written during the meeting, not after it — afterwards you only clean them up. The working sequence looks like this.
| When | What the note-taker does | How long |
|---|---|---|
| Five minutes before | Opens the template and pastes the agenda items in as headings — from then on it's filling in, not inventing structure | 5 min |
| The moment a decision lands | Writes the wording immediately and says it out loud: "capturing that — release moves to 12 August". This is the only moment disagreement surfaces cheaply | as it happens |
| When an argument starts | Opens a line under disagreements instead of trying to resolve it into a decision | as it happens |
| Last three minutes | Reads the decisions and actions back, with names. Half the corrections happen here | 3 min |
| Same day | Edits, fills in dates, sends to attendees and absentees, creates the actions in the tracker | 20–30 min |
Who does it is a separate question. The chair can't take the minutes: moderating and recording need different kinds of attention, and attempting both degrades each. Three arrangements work — a designated secretary for recurring meetings, a rotation in a small team (with the useful side effect that people learn to phrase things so they can be written down), and transcribing the conversation and editing afterwards when there is no note-taker in the room at all.
The timing isn't about tidiness. Recall degrades within hours: after two days, contested wording can't be reconstructed and participants start remembering different versions. Minutes sent on day three get discussed instead of acted on.
How should a decision be worded?
The most common failure here is recording the process instead of the result. "Discussed the timeline", "went through the budget" — that describes how time passed. A decision should read as a statement you can check for truth.
The working formula is what was resolved + on what grounds + who decided. Grounds matter because decisions get reopened, and a month later the question won't be "what did we decide" but "why did we decide that". Without them, any newcomer has every right to start the argument over — and will be right to.
Discussed moving the release. Agreed we need to think about it further and come back to this.
Release moves from 5 to 12 August. Grounds: the billing migration isn't ready, and the risk of dropped payments outweighs the cost of the delay. Decided by: Anna, product owner.
The first version can't be checked: it's unclear whether the release moved, who returns to the question, or when. There's a record but no agreement. The second answers three questions at once — the new date, the reason, and the person to take an objection to.
A note on "we agreed to revisit this"
That isn't a decision, it's the absence of one. If something is genuinely deferred, the deferral needs an owner and a date: "Pricing tiers deferred to 15 September; Igor returns to it once the August churn data lands." That line belongs under disagreements, not decisions — there it misleads nobody.
What makes an action item doable?
An action from minutes differs from a ticket in the tracker in one respect: nobody is going to clarify it. So it has to stand on its own — the wording has to make clear what counts as finished.
- An action verb up front. "Send", "sign off", "collect" — not "budget" or "the access question".
- A definition of done. Send where, in what form, for whose review. Without it the action closes whenever the owner feels finished.
- Exactly one owner. "Engineering" means nobody will do it: responsibility split between people belongs to none of them.
- A date, not "next week". Relative deadlines expire the moment the minutes are read later than they were written.
Think about the phase-two budget. Owners: the team. Due: next week.
Post the phase-two budget in #budget, broken down by role. Owner: Igor. Due: 8 August.
"Think about" can't be delivered or verified. "The team" removes responsibility from everyone at once. "Next week" stops meaning anything the moment the minutes are opened on a different Monday. The second version shows where it lands, what form it takes, one name and a calendar date.
Where do disagreements go?
This is the section people drop first, and it's the one that separates minutes from a progress report. An argument dissolved into "we agreed to revisit this" resurfaces a month later as "but we agreed" — with both sides sincerely correct, because each remembers its own half of the conversation.
The format is one line per unresolved position, carrying four things: what the question is, whose positions diverged, when you return to it, and who owns the return.
- Discount depth on annual plans. Positions: Igor — no lower than 15%, or margin breaks; Lena — 25%, or we don't catch the market. Revisit 15.09 with August churn data. Owner: Igor.
The point isn't to preserve a record of the conflict — it's to make the question impossible to lose quietly. An open position acquires a date, so it lands on the next meeting automatically. That, incidentally, is the most reliable source of items for the next call's agenda.
A template you can copy
Markdown, so it drops into an editor, a tracker or a knowledge base without reformatting. Square brackets are what you fill in; everything else can stay as it is.
# Minutes: [subject] **Date:** [dd.mm.yyyy], [start]–[end] **Chair:** [name] **Minutes by:** [name] **Attendees:** [names, comma-separated] **Absent:** [names; "none" if everyone attended] ## Context [1–2 sentences: why this meeting happened] ## Decisions 1. [What was resolved]. Grounds: [why]. Decided by: [name, role]. 2. … ## Actions | What to do | Who | Due | |---|---|---| | [Verb + object + definition of done] | [one name] | [dd.mm] | ## Disagreements and open questions - [Question]. Positions: [who wants what]. Revisit [dd.mm], owner: [name]. ## Materials - [Title](link)
The same shape serves a weekly status and a vendor meeting alike: what changes is the level of detail from the section above, not the structure. If your organisation numbers its minutes, put the number on the first line beside the subject — searching by it later beats searching by date.
Minutes builder
Fill in the fields and the minutes assemble against the template above. Nothing is sent anywhere: it's all computed in the browser, and the page stores nothing you type.
Checklist before you send
Nine checks, each catching its own class of problem. Tick them off — the counter shows how ready you are.
When minutes aren't worth taking
Bad minutes are worse than none: they create the impression that an agreement was captured, and people later cite them as the source of truth. So an honest list of when not to write them matters as much as the template.
Skip them for one-to-ones, for brainstorms that produced no decisions, and for ten-minute status syncs. If nothing was decided, three lines in a shared channel are more honest than a formatted empty document. For meetings about something personal — feedback, conflict, compensation — minutes aren't merely redundant: they change what people are willing to say out loud.
A transcript won't substitute. A verbatim record is source material, not a document: the useful parts are interleaved with clarifications, returns to settled points and a discussion of where to get lunch. Nobody reads it, and a week later the decision can't be dug back out.
Auto-generated minutes won't survive without editing. A model hears an agreement well, but doesn't know which of the two Annas owns billing, and can't tell a decision from a proposal that was voiced confidently and rejected a minute later. One wrong name or date discredits the whole document: having hit a false line once, a reader stops trusting the rest.
Minutes as a weapon won't work. Once people understand the record is being kept in order to be produced against them later, wording turns evasive, contested positions move to direct messages, and the meeting becomes theatre. Minutes are a memory instrument, and they only function while everyone believes that's what they are.
What you don't have to do by hand
Decisions, actions and disagreements are almost always spoken aloud, which means they can be pulled from a transcript. Whisperer transcribes the meeting and, once it ends, builds a meeting map — topics, decisions and action items as separate nodes, which you can copy out as text or save into your knowledge base. What's left is editing the wording, filling in the missing dates, and removing anything that was a proposal rather than a decision. The manual part stays exactly where it should be: deciding what counts as a decision.
The same move transfers to meetings where the point isn't agreement but comparability. In a structured interview the transcript yields answers under identical headings, and in customer discovery it yields the phrasings of a pain point that repeat across twenty conversations.