How-to

How to Write Meeting Minutes

Minutes are the official short record of a meeting: who was there, what was decided and who does what next. Here is a clear way to write them.

What meeting minutes are for

Minutes are not a transcript. They are a short, accurate record that lets someone who was absent, or who attended but forgot, understand what was decided and what happens next. Good minutes prevent arguments, because they show what was agreed.

What to include

  • Basics: meeting title, date, time, location or link
  • Attendees and apologies
  • Agenda items discussed
  • Decisions, each in a full sentence
  • Action items, each with an owner and a date
  • Unresolved questions and who will answer them
  • Next meeting date

Leave out side conversations, who said what unless it matters, and anything off the record.

Step by step

Before the meeting

Get the agenda and the attendee list. Pick a note-taker, ideally not the person leading the discussion. Our meeting agenda template helps.

During the meeting

Capture decisions and actions as they happen. When something is unclear, ask: "Can I confirm: we agreed to launch on 14 November?" Stating it aloud creates a shared record in the room.

Straight afterwards

Within a few hours, tidy the notes into the structure above. Replace vague phrases ("discuss pricing") with outcomes ("pricing page to be redone by Dev, due Thursday").

Send and confirm

Send the minutes within 24 hours and invite corrections. After a short window, treat them as the record.

A short example

Website kickoff, 12 Oct 2026, 11:00-11:30
Attendees: Priya (Northwind), Alex, Dev

Decisions
- Launch on 14 November.
- Northwind supplies copy by 24 October.

Actions
- Alex: send revised scope, Fri 16 Oct.
- Dev: share design options, Tue 20 Oct.

Open
- Hosting access: Priya to confirm by 19 Oct.

Use the full meeting minutes template for a longer format.

Common mistakes

  • Writing a transcript. If minutes are long, nobody reads them.
  • Vague actions. "Look into it" has no owner, no date and no end.
  • Mixing ideas with decisions. Someone suggested something. Did anyone agree?
  • Waiting a week. Details fade, and so does the value of the document.
  • Never following up. Start the next meeting by reviewing last time's actions.

How long should minutes be?

As short as will carry the decisions and actions. For a 30-minute meeting, one page is usually plenty.

Using software

If you record the meeting, a tool can draft the minutes for you. MeetMemo can create minutes from a meeting's notes, flag anything it could not confirm and export a PDF with your branding. You still review and edit them. See meeting notes to PDF. MeetMemo is in early access.

Minutes for different kinds of meeting

The structure stays the same, but the emphasis changes.

  • Client meetings. Lead with decisions and the client's commitments. These minutes are often the record in a later disagreement, so keep wording precise and send them to the client for confirmation.
  • Internal project meetings. Emphasize actions, owners, blockers and dates. Skip the background everyone knows.
  • Recurring status meetings. Keep a running list of open actions at the top, and record only what changed since last time.
  • Workshops and brainstorms. Record the questions explored and the options considered, then clearly mark what was selected and what was parked.
  • Formal or governance meetings. Follow the conventions your organization or governing document requires, which may include motions, votes and quorum. Take advice if the minutes have legal weight.

Style rules that make minutes easier to trust

  • Use past tense and neutral wording. "The team agreed to move testing to the 3rd", not "We had a great discussion about testing".
  • Attribute decisions to the group, and name individuals for actions.
  • Quote numbers exactly and mark uncertain ones: "budget of about 40,000 (to be confirmed)".
  • Write full sentences for decisions so they make sense out of context six months later.
  • Leave out opinions about people. Minutes are shared.

Approval, distribution and storage

Decide in advance who receives the minutes and who approves them. A common approach is to circulate within 24 hours, allow a short window for corrections, then treat the minutes as final and file them where the team can find them. Name each document consistently, such as "2026-10-12 Northwind kickoff minutes", so they are easy to search later. Keep minutes for as long as your obligations, client contract or policy require.

A quick checklist before you send

  1. Are the date, attendees and purpose correct?
  2. Does every decision read as a full sentence?
  3. Does every action have an owner and a date?
  4. Are unresolved questions listed with an owner?
  5. Have you removed anything that was off the record?
  6. Would someone who missed the meeting understand it?

Frequently asked questions

What is the difference between minutes and notes?

Notes are for you. Minutes are a shared record that others can rely on. Notes feed the minutes.

Should minutes include who said what?

Only where it matters, such as a commitment or a formal decision. Otherwise record outcomes, not speakers.

How long should I keep minutes?

As long as a contract, policy or law requires, and at least until the actions are complete. Ask your organization or a professional if unsure.

Can I record the meeting to write the minutes?

Yes, with the consent of the people in it. See the recording consent guide.

Related on MeetMemo

More to read

Be first to try MeetMemo

Join the early-access list and we will email you when the Android app is ready. No spam.