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 freeThis 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.
| Part | What goes in it |
|---|---|
| Header | Meeting name, date, start and end time, who ran it, who took notes, who was there, who was absent |
| Purpose | One line: what this meeting was for ("Weekly sync on the Q4 launch") |
| Decisions | Numbered list. Each is one sentence a stranger could understand later ("We will ship on 12 December, not 5 December") |
| Actions | A small table: action, owner (one name), due date |
| Discussion notes | A few lines per agenda item: the main point, any view that was overruled and why. Not a transcript |
| Parked | Topics raised that were not on today's agenda, with who will pick each up |
| Next meeting | Date, 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
- Holiday cover will be two people per day, 22 December to 2 January, chosen by sign-up; the manager breaks ties.
- We stop sending the daily backlog email. The dashboard replaces it from Monday.
Actions
Action Owner Due Create the holiday sign-up sheet and share it Priya Wed 5 Nov Tell the sales team the backlog email is ending Dana Fri 7 Nov Add the "waiting on customer" count to the dashboard Omar Mon 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
- Decisions, in a full sentence, with the date if it matters ("from Monday", "until the end of Q1").
- Actions, each with one owner and one date. "The team will look into it" is not an action.
- Numbers that were agreed or reported, with what they refer to.
- Reasons for a decision when it was contested, in one line, so nobody reopens it in two weeks.
- Anything promised to someone outside the room.
Usually leave out
- Who said what, unless an owner or a commitment depends on it.
- Small talk, jokes and side discussions.
- Back-and-forth that ended in a decision. Record the decision.
- Personal or sensitive material about a person (performance, health, pay). Keep that in a private note, not in minutes the whole team can read.
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:
- 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.
- 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.
- 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
| Weak | Better |
|---|---|
| Discussed the launch date | Decided: launch moves to 12 December because testing finishes on 5 December |
| Someone to update the plan | Omar updates the plan by Wednesday noon |
| Look into refunds | Jess drafts a refund macro and brings it to the 11 November meeting |
| Team agreed to communicate better | Dana sends the weekly priorities email every Monday by 9:00 |
| Ongoing | Owner 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
- Send them the same day, ideally within an hour, while people remember. A day later it is already a reminder, not a record.
- Put decisions and actions in the message body, not in an attachment. A link to the full page can sit underneath.
- Use a subject line that works alone: "Notes: support weekly, 4 Nov. 2 decisions, 3 actions."
- Name each owner in the email. People act on a message with their name in it.
- 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:
- Start the next meeting with last week's actions. Two minutes, each owner says done or not done. It is the cheapest accountability you have, and it removes the need to chase people privately.
- Carry forward, don't forget. An action not done is moved to the new notes with its date, and you ask why in one sentence. Two carry-overs on the same item means the action is too big or has no real owner.
- Close the loop on parked items. If a topic is parked three times, either schedule it or drop it, and say so.
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
| Meeting | Change the template like this |
|---|---|
| Daily stand-up | Usually no minutes. Record only blockers and who will help. See stand-up meeting format |
| Project meeting | Add a status line per workstream (on track, at risk, late) and a risks list |
| One-to-one | Private notes only: topics, agreed actions, things to follow up. Share the actions, not the notes. See the one-on-one meeting template |
| Decision meeting | Add the options considered and the reason for the one chosen |
| Problem or incident review | Add a timeline of what happened, what went well, and what changes |
| Large or cross-team meeting | Add 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
- Writing too much. Long notes are unread notes. If your page runs past one screen, cut the discussion section.
- Actions without owners or dates. The single most common failure.
- Sending them days later. By then people have forgotten, and the notes record what you remember rather than what was agreed.
- Putting sensitive things in shared notes. Keep performance and personal matters out.
- Doing it all yourself every time. Rotate the note taker.
- Never looking back at them. If you don't start the next meeting from the last notes, people learn the notes don't matter.
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
- Asana, meeting minutes template: asana.com/templates/meeting-minutes
- Zapier, meeting minutes template: zapier.com/blog/meeting-minutes-template
- Reclaim.ai, meeting minutes template: reclaim.ai/blog/meeting-minutes-template
- The Muse, meeting minutes templates and tips: themuse.com/advice/meeting-minutes-templates
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