How to Write Meeting Minutes (And How to Never Do It Manually Again)

If you have sat in a meeting and realised, three days later, that nobody wrote up what was decided, you understand why knowing how to write meeting minutes properly matters. Minutes are the single record of what happened, who is responsible and what comes next.

Without minutes, decisions evaporate and action items stall in everyone's inboxes. With them, a sixty-minute discussion produces a concrete, searchable, accountable output that drives work forward.

This guide walks through what to capture, how to structure it, and the approach UK teams are using to stop spending time on the problem altogether.

What meeting minutes are actually for

The phrase "meeting minutes" comes from the Latin minuta scriptura, small writing. The original idea was a concise record, not a transcript. Good minutes are a structured summary of:

• Who attended, and who was expected but absent
• What decisions were made, and the reasoning behind them
• What actions were agreed, by whom, and by when
• Any information shared that people will need to refer back to
• The date, time and location or meeting link

A board uses minutes as a record of governance decisions. A project team uses them to keep delivery on track, and a sales team uses them to capture client commitments. The purpose is the same: a single source of truth for what was agreed.

Key PointMinutes record the destination, not the journey. If a line does not help someone understand what was decided or what they need to do, it does not belong in the minutes.

The standard structure for meeting minutes

Whether you are minuting a board meeting, a team check-in or a client call, the structure follows the same pattern. Here is what each section should contain.

Meeting header

Start with the basics: meeting name, date, start and end time, location or video platform, and who is taking the minutes. Minutes that lack a date or a clear name become impossible to file and find later.

For example: Product Team Weekly, 12 September 2026, 10:00 to 11:00, Microsoft Teams. Minutes: Sarah Okafor.

Attendees

List everyone who attended, with their role or team if the minutes will be read outside the meeting. Note any apologies from people who were invited but could not attend. This matters when a decision is challenged later or when someone needs to catch up.

Decisions

This is the heart of the document. For each decision, capture:

• What was decided (the outcome, not the discussion)
• Who proposed or championed it, if that context matters
• Whether it was unanimous or by majority
• Any conditions attached to the decision

Write decisions in past tense and plain language. "The team agreed to pause the feature build until the discovery sprint concludes" beats "Feature build: decision pending discovery". The first can be understood by anyone.

Action items

Action items are where minutes drive real change. Each one needs three things: what it is, who owns it and when it is due. Without all three, an action item is a hope, not a commitment.

• Finalise the Q4 budget proposal: James Whitfield, due 19 Sep 2026
• Share the vendor shortlist with procurement: Priya Sharma, due 15 Sep 2026
• Schedule a follow-up with the Edinburgh team: Mark Davies, due 16 Sep 2026

Pro TipIf your minutes go out by email, put the action list in the email body, not only in an attachment. People act on what lands in front of them.

Items deferred or tabled

Any agenda item that was not resolved deserves a note. Record what it was, why it was deferred and when it will be picked up, so nothing falls through the gaps between meetings.

Next meeting

Confirm the date, time and location of the next meeting. If it has not been scheduled yet, record that it needs to be arranged and by whom.

How to write meeting minutes in real time

Writing minutes while a meeting happens is harder than it sounds. The conversation moves fast, people interrupt each other, and decisions sometimes emerge gradually rather than arriving cleanly. These practices help:

• Prepare the template in advance. Have the header, expected attendees and agenda headings ready, so you fill in boxes rather than build a document while listening.
• Capture decisions and actions, not discussion. When someone says "I will handle that by Friday", write it down as an action before the conversation moves on.
• Use shorthand, then clean up. Rough notes during the meeting and fifteen minutes of sharpening afterwards beat trying to write perfect prose live.
• Clarify ambiguity before you leave. "Just to confirm, we have agreed to proceed with Option B?" costs ten seconds and prevents a confusing record.

Distribute within 24 hours. Minutes lose value quickly, because people start acting on their own interpretations of what happened. Send them the same day if you can, and certainly before the next working day.

Common mistakes when writing meeting minutes

Even experienced minute-takers fall into these traps.

Too much detail. Minutes that read like a transcript are not read. If yours routinely run past two pages for a one-hour meeting, you are capturing discussion rather than decisions.

Vague action items. "Follow up on the supplier issue" is not an action item. "Confirm the revised delivery schedule with Henderson Logistics by 18 September" is.

Watch OutAn action owned by "the team" is owned by no one. Every action needs a named individual, and minutes need to make sense to the people who were not in the room.

Storing minutes where nobody looks. A shared drive nobody uses, a buried email list or a tool half the team cannot open all mean the record exists and has no effect. Decide where minutes live and tell every attendee.

The UK context: board minutes and legal requirements

For UK companies, minutes have a legal footing. Under section 248 of the Companies Act 2006, every company must record minutes of all directors' meetings and keep them for at least ten years.

Minutes of general meetings and members' resolutions must also be kept for ten years. Under section 358, those member records are open to inspection by any member free of charge.

The requirement applies regardless of company size. A dispute over a director's authority or a challenged transaction can turn on what the minutes do or do not record. GOV.UK sets out the wider duties in running a limited company.

Key InsightMost operational meetings, such as stand-ups, project reviews and client calls, carry no legal requirement to keep minutes. The practical benefit is the same, though: a record that decisions were made and responsibilities assigned.

How to stop writing meeting minutes manually

Knowing how to write meeting minutes is useful. Not having to write them manually is better.

Most of the effort in minute-taking, capturing decisions, pulling out actions and noting who said what, is pattern recognition applied to spoken language. It is exactly the kind of task that AI meeting tools now handle well. Our guide to the best AI note takers in 2026 compares the options.

Keel produces a structured meeting summary the moment the meeting ends:

• Decisions, written as outcomes
• Action items, each with an owner and a due date
• A full transcript for reference

Keel also works without a bot joining the call, which matters for client calls where a third-party participant raises questions about confidentiality. If you record meetings, read GDPR meeting recording: what UK teams need to know alongside the ICO's UK GDPR guidance.

If you have read this far, you are already thinking about the right things: capturing decisions, assigning owners, distributing promptly and storing accessibly. The next step is removing the manual work in between. Try Keel for your next meeting, or see how Keel works.