How to write meeting minutes people will actually read

Good meeting minutes record what was decided and who will do what by when, not a transcript of who said what. A reader who missed the meeting should be able to learn the outcome in a minute. Everything else is optional. I built the meeting minutes template around that structure, with an actions table that flags any action without an owner, and this guide explains how to take minutes that are quick to write and useful to read.

What minutes are for

Minutes do three jobs: they remind attendees what they agreed, they tell people who were absent what happened, and they create a record you can point to later when someone asks "when did we decide that?". Robert's Rules of Order, the widely used guide to formal meetings, puts it plainly: minutes are mainly a record of what was done, not of what was said. That principle is just as useful for a weekly team meeting as for a board.

What to include

• Meeting name, date and attendees, plus apologies from those who could not come.
• The agenda items, in order, so the minutes follow the meeting's structure.
• Key discussion points, briefly, only where the reasoning matters later.
• Decisions, each stated as a clear sentence: "Agreed to move the launch to 14 May."
• Actions, each with one owner and a due date.
• The next meeting, if there is one.

Formal minutes for companies, charities, councils and clubs often have extra requirements set by law or by the organisation's own rules, such as recording motions and votes, declarations of interest, and approval of the previous minutes. If you are minuting that kind of meeting, check your governing document first.

Taking minutes during the meeting

• Prepare the skeleton beforehand. Copy the agenda in, list expected attendees, and you only need to fill gaps. The meeting agenda generator produces the agenda to start from.
• Listen for decisions and actions. When a discussion ends without one, it is fine for the minute-taker to ask, "So what have we decided?"
• Confirm owners out loud. "Sam, that is yours by Friday?" takes five seconds and saves a week of confusion.
• Do not take minutes and chair at the same time if you can avoid it. Both jobs need full attention.
• Write in plain, neutral language. Record what the group agreed, not who argued hardest. If a disagreement matters for the record, note that views differed and what was finally decided.

A worked example

Here is an invented example from a school parents' association planning a summer fair:

• Attendees: Amira (chair), Ben, Chloe, Dev, Ella. Apologies: Fiona.
• Agenda: 1. Date and venue. 2. Stalls. 3. Budget. 4. Volunteers.
• Discussion: the school field is booked for sports day in early July, so the playground is the only option for June.
• Decisions: fair on Saturday 20 June in the playground; budget capped at £400; no glass bottles on site.
• Actions: Ben to confirm the date with the head teacher by 2 May; Chloe to contact last year's stallholders by 9 May; Dev to set up the volunteer sign-up sheet by 9 May.
• Next meeting: Tuesday 12 May, 7pm.

That is about a hundred words, and anyone who missed the meeting now knows everything they need. Each action has one name and one date, so there is no doubt at the next meeting about whether it was done. The two-hour debate about bouncy castles does not need to be in there, only the outcome.

After the meeting

Send the minutes quickly, ideally the same day, while people still remember what they agreed and can correct mistakes. The template copies everything as Markdown for email, chat or a wiki, or prints it as a clean page. At the next meeting, start by going through the previous action list: that single habit does more for follow-through than anything else. If ownership keeps getting fuzzy across a bigger project, a RACI matrix settles who is responsible for what, and the meeting timer helps keep each agenda item to its slot. For the other half of a well-run meeting, see How to write a meeting agenda with timings that hold.