Most meeting minutes get written twice: once during the meeting, badly, and again the next morning from memory, worse. By Friday nobody agrees on what was decided, and the one person who typed a stray sentence is now the official memory of the room.

That's the whole problem in one image. Minutes are not a transcript, and the second you try to make them one, you've lost.

This is the short version of how to write meeting minutes people actually open: what to capture, what to throw away, and what to do when you're also the person leading the discussion.

Minutes are not a transcript

The word "minutes" has nothing to do with time. It comes from the Latin minutus, small — small notes, not a court record.

Robert's Rules of Order puts the same idea plainly: minutes record what was done at a meeting, not what was said. That one rule decides nearly everything else.

A record of what was done stays short, survives review, and takes a reader thirty seconds. A record of what was said runs for pages, invites arguments about phrasing at the next meeting, and buries the three things anyone actually needs.

Record	Purpose	What goes in it
Minutes	The agreed, official record	Decisions, action items, owners, dates, attendance
Notes	One person's working memory	Ideas, reminders, half-thoughts
Transcript	Proof of exactly what was said	Every word, with speaker and timestamp

Minutes are the first row. Notes and a transcript are inputs to it, not replacements for it.

The three fields that actually matter

Strip a set of minutes down and three things do all the work:

The decision, written as a complete sentence. "We discussed pricing" is not a decision. "Decision: we hold the annual price and move the increase to March" is.
The owner, one name. "The team will follow up" is an unowned task wearing a disguise. One person, one name.
The date. Not "soon", not "ASAP". A date somebody said out loud in the room.

Every action item is just those three in a row: owner, verb, deliverable, due date. "Priya will send the revised budget to Finance by Friday." If an item is missing an owner or a date, the minute-taker has one job — interrupt for ten seconds and ask, "Who's taking that, and by when?"

Before the meeting: build the skeleton

Half your minutes can be written before anyone speaks.

Take the agenda and paste each item into your document as a heading. Now every topic is an empty section waiting for a decision, and you're filling blanks instead of facing a blank page. Pre-fill the header too: meeting name, date, time, location or call link, chair, and who's taking the minutes.

Two more things to settle up front:

Who's recording. Agree it before the meeting. If the minute-taker is also expected to talk a lot, that's two jobs and one of them will be done badly.
How formal this needs to be. A weekly team check-in needs decisions and actions. A board meeting needs motions, movers, seconds, and vote counts. Ask the chair before the meeting, not after.

During: capture outcomes, not sentences

Listen for the words that signal a decision, not the ones that fill the time: "we've decided", "the consensus is", "let's go with", "action item".

When you hear a decision, write it as one. When a task lands without a name, ask who owns it. Note attendance as people join, and mark late arrivals and early exits — in a formal meeting, those change a vote.

Resist the instinct to grab the argument. A new minute-taker captures the back-and-forth "in case someone needs it later". Nobody ever does. What they need is the outcome, the owner, and the date. The argument lives in the recording if a dispute ever comes up.

After: write it up within 24 hours

Memory decays fast. The shorthand that made sense at 10 a.m. is unreadable by Friday. Turn the skeleton into clean sentences the same day, while the meeting is still fresh.

Then run the one check that separates minutes people trust from minutes people argue about: the timestamp trace.

For every action item, find the moment in the recording where the commitment was actually made. Each item needs three anchors:

a timestamp — the moment someone committed to it,
a named owner — a person, never a department,
a confirmed date — a date someone said out loud.

If you can't find the timestamp, the commitment was inferred, not made. Flag it instead of publishing it. The trace takes about five minutes on a half-hour meeting, and it catches the two ways minutes go wrong: an action nobody agreed to, and an action nobody owns.

When you're the participant too

Here's the part most guides skip. A minute-taker who's also in the discussion cannot listen, talk, and write all at once. Something gives, and it's usually the minutes.

Three honest options:

Hand it off. Rotate the job so the person running the meeting isn't the one writing it down.
Write less. Decisions and action items only, live; fill context in afterward from the agenda.
Record, then write from the record. Tell everyone you're recording, then write the minutes from the transcript and summary afterward instead of from memory.

That third option is where an AI notetaker earns its place. Meetbook records the meeting from the browser tab — no bot joins the call — and hands you a transcript with a speaker and timestamp on every line, plus a summary and action items with owners when the call ends. Every point in the summary links back to the quote it came from, so the timestamp trace isn't five minutes of scrubbing through audio. It's clicking the line in the summary and landing on the exact second. You still decide what matters. You just stop transcribing while you're trying to think.

A template you can copy

Copy this into a doc, and delete the lines marked "formal only" if this is a weekly team meeting.

Meeting: [name] Date and time: [day, date, start–end, time zone] Where: [room, or the call link] Chair: [name] · Minutes by: [name] Present: [names] · Absent: [names]

[Agenda item] Decision: [what was agreed, or "not decided — back on the agenda (date)"] Action: [owner] — [verb + deliverable] — [due date]

Formal only: Motion: [exact wording] — moved by [name], seconded by [name]. Carried or failed [for]–[against]–[abstain].

Open items: [questions carried forward, each with an owner] Next meeting: [date and time] Adjourned: [time]

What to leave out

This is where most minutes bloat:

word-for-word quotes and who said what in a debate,
your own commentary — "a heated exchange", "a great idea",
side conversations, jokes, and off-topic remarks,
ideas that were floated but never agreed, unless someone owns a follow-up,
anything you're not sure was said, until you've checked it.

Minutes are the room's record, not the minute-taker's opinion. If a sentence only helps you remember your own reaction, it doesn't belong.

Sending and approving

For a team meeting, send the minutes the same day. Put the decisions and action items in the body of the message, because most people won't open the attachment. Give a correction deadline and say what happens after it passes: "After Friday this becomes the record."

For formal meetings, the draft goes to the chair first, then out, and the group approves it at the next meeting — as presented, or as corrected. Corrections get recorded in the new minutes, never silently edited into the old file.

Minutes that people use are short, owner-first, and verifiable. Everything else is a transcript nobody reads.

How to Write Meeting Minutes