What are meeting notes?

Meeting notes are a written record of what a group discussed, what it decided, and what happens next. They usually list the date, the people present, the agenda topics, a summary of the discussion, and the actions people committed to. Unlike a transcript, notes capture the substance rather than every word spoken.

What's an example of good meeting notes?

A useful note is short and specific. A weekly engineering standup might record one decision, cut scope on the release, plus two action items with names against them. A client kickoff records who sends the revised statement of work and by when. A hiring debrief records a no-hire and why, which matters when that candidate reapplies. Discussion gets a paragraph. Decisions get their own line.

Who takes notes in a meeting?

Whoever isn't leading the discussion. In a board or committee setting that's the secretary, whose minutes become the official record. In a team meeting it's usually a rotating role, because the person facilitating can't chair and write at the same time. Naming the note taker at the start avoids everyone assuming someone else was writing.

How do you take meeting notes during a fast discussion?

Capture decisions and action items live, then summarise the discussion afterwards. Most people try to write everything in real time and end up with a transcript nobody rereads. Type the agenda in advance so you're filling a structure instead of starting from a blank page, and flag anything unresolved so you can chase it later.

How should you structure meeting notes?

Start with the date and the purpose of the meeting, then list who attended. Put the agenda next as a numbered list and write the discussion under it. Keep decisions and action items in separate sections at the end, because those are the two parts people come back to. That outline suits most meetings, and the format matters less than keeping decisions apart from discussion.

TemplatesRetrospectives & meetingsMeeting Notes

Meeting Notes Template

Meeting notes are a written record of what a group discussed, what it decided, and what happens next. The template has a date and purpose header, a participant list, a numbered agenda, a free-form notes area, a separate decisions list, and an action item checklist. Teams use it for weekly standups, project check-ins, and client calls where someone has to remember who owns what.

Use this template

Meeting notes template with a date and purpose header, a bulleted participant list, a numbered agenda, a free-form notes block, a decisions list, and an action item checklist with checked and unchecked boxes. — A blank meeting notes doc with agenda, discussion, decisions, and a checkbox action list.

What's included

Date and purpose fields. Two lines at the top that fix when the meeting happened and why it was called.
Participant list. A bulleted roster of who attended, so anyone reading later knows whose account this is.
Numbered agenda. An ordered list of topics you paste in beforehand and work down during the meeting.
Free-form notes block. An open prose area for the discussion itself, kept apart from the decisions below it.
Decisions list. Its own bulleted section, so what the group agreed doesn't get buried in the discussion.
Action item checklist. Checkboxes you tick as work lands, so the next meeting starts from what's still open.

Why write meeting notes?

A decision record you can search. Decisions sit in their own list, so you can find what was agreed in March without rereading everything.
Follow-ups with a name on them. Each action item is a checkbox with an owner, which makes an unassigned task obvious at a glance.
Context for whoever missed it. Purpose, agenda and decisions together give an absent colleague the thread in about a minute.
Fewer repeat arguments. A written decision with a date on it tends to stop the same debate restarting three weeks later.
Fewer status pings. Ticked and unticked boxes answer "is that done yet" before anyone has to ask.

How to use this template

Duplicate the template. Copy it into your workspace and rename it with the meeting date, so the file is findable later.
Fill in the date and purpose first. Write both before anyone joins, so the note has context even if the meeting runs short.
Paste the agenda as numbered items. Drop each topic into the ordered list, then work down it during the discussion.
Keep decisions out of the notes block. Write the discussion in the notes area and move anything the group agreed into the decisions list.
Give every action item an owner and a date. Add one checkbox per task with a name and a deadline, so nothing sits unassigned.
Share it while the meeting is fresh. Send the link the same day. Collaborative editing means corrections land in the note itself instead of a reply chain.

Open in Whimsical

Meeting notes vs meeting minutes

Meeting minutes are the formal record of a meeting, kept for governance and approved at the following session. They follow a fixed structure and carry weight in legal, financial and compliance contexts. Meeting notes are informal and written for the team itself: what was said, what was decided, who owns the next step. Use minutes for boards and committees, notes for internal work.

Frequently asked questions

Meeting notes are a written record of what a group discussed, what it decided, and what happens next. They usually list the date, the people present, the agenda topics, a summary of the discussion, and the actions people committed to. Unlike a transcript, notes capture the substance rather than every word spoken.
A useful note is short and specific. A weekly engineering standup might record one decision, cut scope on the release, plus two action items with names against them. A client kickoff records who sends the revised statement of work and by when. A hiring debrief records a no-hire and why, which matters when that candidate reapplies. Discussion gets a paragraph. Decisions get their own line.
Whoever isn't leading the discussion. In a board or committee setting that's the secretary, whose minutes become the official record. In a team meeting it's usually a rotating role, because the person facilitating can't chair and write at the same time. Naming the note taker at the start avoids everyone assuming someone else was writing.

Capture decisions and action items live, then summarise the discussion afterwards. Most people try to write everything in real time and end up with a transcript nobody rereads. Type the agenda in advance so you're filling a structure instead of starting from a blank page, and flag anything unresolved so you can chase it later.
Start with the date and the purpose of the meeting, then list who attended. Put the agenda next as a numbered list and write the discussion under it. Keep decisions and action items in separate sections at the end, because those are the two parts people come back to. That outline suits most meetings, and the format matters less than keeping decisions apart from discussion.