How to Write Meeting Minutes (Step-by-Step With Examples)

The One-Line Definition

Meeting minutes are a short, structured record of what was decided and committed to in a meeting — written for people who weren't there (and for the ones who were, when their memory fades).

Notice what isn't in that definition: transcript, opinions, sidebars, chronological account. Minutes are a compression of a meeting, not a recording of it. If your minutes read like a transcript, they aren't minutes yet.

Before the Meeting: Two Minutes of Prep

Most bad minutes are written under time pressure because the minute-taker walked in cold. Two minutes of prep saves twenty at the end.

1. Get the agenda. Even rough bullets beat nothing. Create a heading in your document for each agenda item.
2. Know who's coming. List attendees, apologies and absent people in a block at the top.
3. Have a shared template open. The free meeting minutes template we publish takes about 30 seconds to copy into a new doc.
4. Pick one tense and stick to it. Past tense is the convention: "The team agreed", not "The team will agree".

During the Meeting: The Four-Column Method

Open your notes in four mental columns. Every sentence you hear goes into exactly one column — or gets discarded. This prevents the most common failure mode, which is writing down everything equally.

1. Decisions — "We're going with option B."
2. Actions — "Sam will send the proposal by Friday."
3. Risks / open questions — "We don't know if legal will approve this."
4. Context — a single line explaining why a decision or action was taken.

Anything else — anecdotes, digressions, opinions, back-and-forth — goes into a mental bucket you don't transcribe. You can add a single summary sentence if a discussion genuinely shifted the outcome, but most don't.

Capturing decisions cleanly

A decision is the moment where the meeting converges. Listen for phrases like "OK, let's do that", "Agreed?", "Sounds like a plan". The second someone says one of these, stop taking notes on the discussion that led to it and write the decision as a single sentence in the present tense.

Good: "The team approved the Q3 billing rework as the quarterly priority."

Bad: "After much back and forth Dana suggested billing should be the priority but Priya wasn't sure and said mobile might be better then Alex pointed out that revenue impact was higher for billing so we all agreed."

Capturing action items cleanly

Three fields, always. Task, owner, due date. An action item missing any of the three isn't an action item — it's a wish. If you notice a missing field during the meeting, stop and ask: "Who owns that?" or "When by?"

Good: "Draft Q3 billing spec — Sam — 2026-06-25"

Bad: "Sam to think about billing spec soon"

After the Meeting: The 24-Hour Rule

Share the minutes within 24 hours. The longer you wait, the more the attendees forget, and the less useful the minutes are for catching errors. If you can't finalise them in 24 hours, send a draft with a clear note that corrections are welcome.

1. Tidy up. Spell out acronyms, remove filler, fix typos.
2. Highlight actions. Bold or list them at the top — attendees should be able to spot their own commitments in five seconds.
3. Send to everyone who attended, plus anyone who was meant to. Apologies and absent people need the output too.
4. Archive. Minutes should live somewhere searchable — a shared doc folder, Notion, or a meeting knowledge base that lets you find decisions months later.

Seven Mistakes to Avoid

1. Writing a transcript. If the minutes are the same length as the meeting, they're not minutes.
2. Attributing everything. "Dana said, Priya replied, Alex responded" — attendees read minutes to find what was agreed, not who talked most.
3. Mixing decisions and discussion. Keep them in separate sections so readers can scan the outcome.
4. Burying action items. Surface them. Bold, numbered, at the top or end.
5. Writing in the moment, then never editing. Raw notes are not minutes. The edit pass is the point.
6. Forgetting the "why". A one-line reason next to a decision makes the minutes searchable a year later.
7. Hoarding. Unshared minutes are worse than no minutes, because they breed misremembered decisions.

When You Shouldn't Be Writing Minutes At All

Honestly? Most of the time. If you're an active participant and the meeting is longer than 20 minutes or has more than three people, you cannot take good minutes and contribute well at the same time. You'll end up doing both badly.

The practical answers are:

1. Rotate a dedicated minute-taker. Someone not needed as a voice. Rotate weekly so no-one gets stuck with it.
2. Use an AI meeting assistant. Tools like Beaver listen to the meeting, fill in a structured template, and produce the draft minutes automatically. You review and publish. Your attention stays on the conversation.

For the step-by-step of how the AI side actually works, see how AI notes generators work. For the debate between manual and AI approaches, see meeting notes: manual vs AI.

FAQ

How do you start writing meeting minutes?

Start before the meeting. Open a new document using a meeting minutes template, fill in the date, attendees and agenda, and you're already halfway done. During the meeting, only record decisions, actions and a one-line context for each.

What should be included in meeting minutes?

Meeting title, date and time, attendees (present / apologies / absent), agenda, decisions, action items with owners and due dates, and the next meeting's date. That's it. Anything else belongs in a transcript, not in minutes.

Should meeting minutes be word-for-word?

No. Word-for-word is a transcript. Minutes are a compression — the decisions and commitments, with enough context to understand them later. A 60-minute meeting usually produces about half a page of minutes.

How soon should meeting minutes be sent?

Within 24 hours. Longer and memories fade, which makes it hard for attendees to spot errors or missing items.

Can AI write meeting minutes?

Yes — an AI meeting assistant can listen to a meeting, fill in a template, and produce a first draft automatically. A human should still review before publishing, because AI can miss the one-line "why" context that makes decisions searchable a year later.