How to write meeting minutes people will actually read

What meeting minutes are for

Meeting minutes are a short written record of what a meeting decided and what people agreed to do. They are not a transcript. Someone who missed the meeting should be able to read them in two minutes and know what changed, who owns each next step, and when it's due.

That idea is old. Robert's Rules of Order, the parliamentary manual many boards and associations follow, puts it plainly, as quoted in a City of Madison guide for its committees (City of Madison, 2020):

University governance offices say the same. The University of Manchester's guidance says minutes should not attempt to be a verbatim record of discussion, and should be action focused and indicate responsibility for actions, key deliverables and timescales (University of Manchester). York University in Toronto encourages its governing bodies to use executive-style minutes, which it describes as a concise record that consists only of actions taken (York University).

What to include in meeting minutes

• The basics: meeting name, date, time, who chaired, who attended and who sent apologies.
• Each agenda item as a short heading, in the order discussed.
• The decision for each item, in one or two sentences, with the main reason if it isn't obvious.
• Each action with an owner, a verb and a target date. Manchester's guidance says actions should normally include a target date for completion.
• Exact figures and wording where they matter: the budget agreed, the launch date, the text of a motion.
• Items deferred to a later meeting, so they don't disappear.

Formal committees also record motions, who proposed and seconded them, and the vote. For a weekly team meeting, decisions and actions are usually enough. York's guidance notes that for informal groups, a summary of tasks assigned and items agreed is normally sufficient.

What to leave out of meeting minutes

• Back-and-forth discussion. Summarize the points raised in a sentence if the decision needs context.
• Who said what, attached to their opinion. York recommends against identifying individual participants together with their opinions.
• Speculation, jokes and side conversations.
• Anything you couldn't hear clearly. Ask, or leave it out.

Leaving these out isn't about hiding anything. Long minutes don't get read, and a decision buried in paragraph six might as well not be written down.

How to write meeting minutes, step by step

1. 1Before the meeting, copy the agenda into your minutes template. Each item becomes a heading with empty Decision and Actions lines underneath.
2. 2During the meeting, listen for three things: a decision, a task, and a number. Write those in full. Everything else gets a few words at most.
3. 3When a decision is fuzzy, ask the chair to restate it before the group moves on. "So we're agreed the launch moves to the 14th?" saves an argument later.
4. 4Right after the meeting, write the clean version while you still remember the context. Manchester says minutes should be drafted as soon as possible following the meeting, and York gives the same advice.
5. 5Send the minutes to attendees, with the actions at the top or in the message itself.
6. 6At the next meeting, start by checking last time's actions. That's what makes people read them.

Before and after: the same meeting in two versions

Here is an invented example: a team of five planning a customer webinar.

Before: a transcript in disguise

"Maya opened by saying registrations were lower than expected. Tom said he thought the date clashed with a conference and suggested moving it. Priya disagreed at first because the slides were nearly done, but then said a week's delay was fine. There was a long discussion about whether to email the list again. Tom said he could probably do it. Someone mentioned the landing page needs updating."

It's accurate, but the reader still has to work out what was decided. Nobody owns the landing page, and "probably" isn't a commitment.

After: decisions and actions

• Item 1, webinar date. Decision: move the webinar from 7 November to 14 November, because 7 November clashes with a major industry conference.
• Item 2, registrations. Decision: send one reminder email to the full list.
• Action: Tom to send the reminder email, by 31 October.
• Action: Priya to update the date on the landing page and slides, by 29 October.
• Action: Maya to report registration numbers at next week's meeting.

It's about the same length, but a reader can scan it in seconds, the reason for the date change survives, and every task has a name and a date.

A meeting minutes template you can copy

• Meeting: name, date, time. Chair. Attendees. Apologies.
• Actions from last time: done, in progress or dropped.
• For each agenda item: Decision (one or two sentences). Reason (if needed). Actions (owner, task, date).
• Deferred items: what, and to when.
• Next meeting: date and time.

Small habits that get minutes read

• Put the decisions in the email subject or first line, not just "Minutes, 22 October".
• Keep the same template every week, so readers know where to look.
• Use names, not "the team" or "someone", for every action.
• Store minutes in one place with a consistent name, such as "Webinar planning 2026-10-22", so the history is searchable.

If you take rough notes during the meeting, dictating a quick summary right after works well when typing is slow. With Lumyo, you can dictate that note, and later ask which notes mention a decision. Answers cite the note they came from, and tapping the source opens the exact line. For the wider problem of tracking down what was said in a call, see how to find what was said in a meeting.