Free script

All guides · Meetings

Meeting minutes template for managers (with a filled-in example)

Good meeting minutes record four things: what was decided, who does what by when, what was left open, and when you meet next. Everything else is optional. Copy the template below, fill it in during the meeting, and send it within the hour. One page is enough for most team meetings; if it is longer, you are probably writing a transcript.

Free · one email

Today's script for the talk you're putting off.

The words to open, the pause and the next step, from a 10-minute lesson. Day 1 is free; plans are $9.99 a month or $39.99 a year after.

Get today's script free

This guide is for managers who now run the team meeting and have to decide what gets written down. Below: the template, a filled-in example, what to record and what to leave out, how to take notes while you run the room, how to send them, and how to make sure the actions happen.

The meeting minutes template (copy this)

Paste this into a doc your team can all open. Keep the same file for every meeting of the same kind, newest at the top, so anyone can scroll back through what was decided.

PartWhat goes in it
HeaderMeeting name, date, start and end time, who ran it, who took notes, who was there, who was absent
PurposeOne line: what this meeting was for ("Weekly sync on the Q4 launch")
DecisionsNumbered list. Each is one sentence a stranger could understand later ("We will ship on 12 December, not 5 December")
ActionsA small table: action, owner (one name), due date
Discussion notesA few lines per agenda item: the main point, any view that was overruled and why. Not a transcript
ParkedTopics raised that were not on today's agenda, with who will pick each up
Next meetingDate, time, and the first two agenda items already known

Put decisions and actions first when you send it. Most readers will read only the top ten lines, so the top ten lines should be the part that matters.

Running a team for the first time? Get today's script free, then see your leadership style and get a 10-minute lesson and one ready script a day.

A filled-in example: a weekly team meeting

Here is what the template looks like after a real 30-minute meeting. The details are invented, only to show the level of detail.

Support team weekly meeting · Tuesday 4 November · 10:00–10:30
Ran by: Dana. Notes: Priya. Present: Dana, Priya, Omar, Jess, Sam. Absent: Lee (leave).

Purpose: weekly sync; decide how to cover the holiday rota.

Decisions

  1. Holiday cover will be two people per day, 22 December to 2 January, chosen by sign-up; the manager breaks ties.
  2. We stop sending the daily backlog email. The dashboard replaces it from Monday.

Actions

ActionOwnerDue
Create the holiday sign-up sheet and share itPriyaWed 5 Nov
Tell the sales team the backlog email is endingDanaFri 7 Nov
Add the "waiting on customer" count to the dashboardOmarMon 10 Nov

Discussion
Backlog: down from 41 to 33 tickets this week. Jess raised that old tickets are mostly waiting on customers; agreed to track that separately.
Rota: Sam would rather work the holiday and take leave in January. Noted for the sign-up.

Parked: new macro for refunds (Jess to bring to next week).

Next: Tuesday 11 November, 10:00. Agenda so far: sign-up results; dashboard check.

That page took about five minutes to tidy after the meeting. Notice what is missing: no list of every thing each person said, no minute-by-minute record, no adjectives. A decision, an owner, a date.

What to write down, and what to leave out

The question to ask for each line is: would someone who missed the meeting need this to do their job? If not, cut it.

Always record

Usually leave out

Minutes or notes?

People use both words for the same thing in everyday work. Strictly, "minutes" are the formal record of a meeting that has rules, such as a board or committee, and may be needed for legal or governance reasons. A team meeting usually needs only short notes with decisions and actions. If you run a formal body, such as a board, a union branch or a homeowners' association, check what its rules require; for an ordinary team, the template above is enough.

How to take notes while you run the meeting

If you lead and write at the same time, you will do both badly. You have three options, in order of preference:

  1. Ask someone else to take notes, and rotate. Each person takes a turn, with the template open. Say it at the start: "Priya has notes today, Omar next week." It spreads the work and gets everyone reading the notes more carefully.
  2. Take notes on a shared screen. Write the decisions and actions where everyone can see them, and read each one back before you move on: "Decision: we ship on 12 December. Right?" Errors get fixed in the room.
  3. Write them yourself, in the last five minutes. If you must, jot only a keyword per item during the meeting, then spend the last five minutes writing out decisions and actions and reading them aloud.

Whichever you choose, the habit that does the most good is the read-back in the last five minutes. It catches the "I thought you were doing that" before it happens. Our guide on how to lead a meeting with confidence has a closing script that includes it.

If you record the meeting or use an AI note-taking tool, tell the team before you start and follow your company's rules and any local law on recording. Even then, check the output yourself: summaries tend to miss who owns an action, and they can get a decision wrong.

How to write decisions and actions so they hold

WeakBetter
Discussed the launch dateDecided: launch moves to 12 December because testing finishes on 5 December
Someone to update the planOmar updates the plan by Wednesday noon
Look into refundsJess drafts a refund macro and brings it to the 11 November meeting
Team agreed to communicate betterDana sends the weekly priorities email every Monday by 9:00
OngoingOwner and date of the next check, or the item comes off the list

The test is simple: could the owner be late? If you cannot tell whether an action was done, it is not written yet.

How to send the notes

  1. Send them the same day, ideally within an hour, while people remember. A day later it is already a reminder, not a record.
  2. Put decisions and actions in the message body, not in an attachment. A link to the full page can sit underneath.
  3. Use a subject line that works alone: "Notes: support weekly, 4 Nov. 2 decisions, 3 actions."
  4. Name each owner in the email. People act on a message with their name in it.
  5. Invite corrections once: "Reply by end of day if I've got anything wrong." Silence then counts as agreement.

A short email template:

Subject: Notes: support weekly, 4 Nov. 2 decisions, 3 actions
Hi all. Decisions: (1) holiday cover is two people a day, sign-up by 12 Nov; (2) the daily backlog email stops on Monday. Actions: Priya, sign-up sheet by Wed; Dana, tell sales by Fri; Omar, dashboard count by Monday. Full notes: [link]. Reply by end of day if I've missed something.

Make the actions happen

Notes nobody uses are the main way meetings lose their value. Three habits fix most of it:

If one person misses their actions again and again, that is a conversation for a one-to-one, not for the group. See how to manage an underperforming employee for how to open it.

Variations for other kinds of meetings

MeetingChange the template like this
Daily stand-upUsually no minutes. Record only blockers and who will help. See stand-up meeting format
Project meetingAdd a status line per workstream (on track, at risk, late) and a risks list
One-to-onePrivate notes only: topics, agreed actions, things to follow up. Share the actions, not the notes. See the one-on-one meeting template
Decision meetingAdd the options considered and the reason for the one chosen
Problem or incident reviewAdd a timeline of what happened, what went well, and what changes
Large or cross-team meetingAdd a distribution list and send a five-line summary on top

For how to plan the meeting itself, see the team meeting agenda template; the agenda items become your notes' headings, which saves you work.

Common mistakes with meeting minutes

Questions about meeting minutes

What should meeting minutes include?

The date, time and attendees; the purpose; decisions; actions with an owner and a due date; short discussion notes where a view was overruled; parked items; and the next meeting. Decisions and actions matter most.

How long should meeting minutes be?

For a weekly team meeting, one page or less. A 30-minute meeting rarely needs more than 150 to 300 words of notes once the header is set.

Who should take the minutes?

Not the person leading, if you can avoid it. Rotate the role among team members, or have the leader write only decisions and actions in the last five minutes.

What is the difference between minutes and meeting notes?

Minutes are a formal record, often needed by rules for boards and committees. Notes are informal and written for the team. For most team meetings you want notes with the structure above.

How soon should I send meeting notes?

The same day, ideally within an hour. The sooner they arrive, the more likely people act on them and correct mistakes.

Do I need to keep meeting notes?

For ordinary team meetings, keep them as long as they are useful, for instance a quarter or a project. Regulated or formal meetings may have required retention periods; check your company policy or the body's rules.

Sources

Next: take the free leadership style quiz, or browse all our guides for new managers.

The notes are the easy part. The talks aren't.

  • A 10-minute lesson a day for 30 days, in the order your quiz answers set
  • One ready script a day: the words to open, the pause, the next step
  • $39.99 a year or $9.99 a month · cancel in one tap · a receipt your employer can expense
Get today's script free

Or read a sample lesson first