Meeting notes template: what to capture, who writes them now, and where they live after the call (2026)

Meeting notes are the working record of a meeting: what was said that matters, what was decided, who does what by when, and what was raised but not resolved. They are written during the call, by one person, and they are read afterwards by everyone — including the people who weren't there. Notes are lighter than minutes and fuller than a recap; they are the document the other two are made from.

This guide is the craft first — what to capture, a template you can copy, two filled-in examples — then the mechanics: where the notes live in the tools your team already uses, and what happens to them after the call. The second half matters more than it looks. The notes' real test is not the meeting; it is three weeks later, when someone asks whether item 2 was ever done.

Meeting notes, minutes and the recap

Three records come out of a meeting, and people use the words interchangeably. They aren't the same document:

Notes are the raw material. A meeting with a chair and votes turns them into minutes; a working call turns them into a recap. If there are no notes, the other two get written from memory, which is how a decision becomes three different decisions by Friday.

One thing notes are not: a transcript. Writing down what everyone said is a different job, and in 2026 it is a machine's job. The note-taker writes down what the meeting meant.

What to capture: the format

A usable page of meeting notes carries six elements. Most templates you'll find are a subset of this list, and the ones that fail usually leave out the last two:

1. The header. Meeting name, date, the link, who was there and who sent apologies. Thirty seconds, before anyone speaks.
2. The purpose, in one sentence. Copied from the agenda if there is one; written on the spot if there isn't. It is the line against which the notes are judged at the end: did the meeting produce this?
3. One block per item, in agenda order. Two or three lines of what was said — positions, not a play-by-play, attributed only when it matters. Then the outcome, marked: decided, open or deferred to a date.
4. Decisions, each in one sentence. The sentence starts "we agreed" and contains the thing agreed, not the discussion that led to it. A decision buried inside the discussion text is a decision nobody will find.
5. Action items — owner, task, date. One line each. An action with no owner is a wish; an action with no date is a hope. Both go in the parking lot instead.
6. The parking lot. Anything raised that the meeting did not resolve, with the name of the person who raised it. It feeds the next agenda. This is the element most templates drop, and the reason the same question gets asked in three consecutive meetings.

What stays out: verbatim quotes unless someone asks to be quoted, tone, the note-taker's opinion, and anything said off the record. A reader should not be able to tell whose side the note-taker was on.

How to take meeting notes: before, during, after

Before the meeting, build the skeleton. Take the agenda and turn it into headings: one block per item, the header pre-filled from the invitation, the previous session's open actions pasted at the top. Ninety percent of the formatting happens before the call. If there is no agenda, the first note of the meeting is that there wasn't one.

During the meeting, write outcomes, not dialogue. For each item you need the positions raised, the decision, and the actions. The habit that does most of the work: when a decision is made, read it back aloud — "so I'm noting: two languages for the Q4 campaign, Lena owns the brief by the 12th" — and let the room correct it while everyone still remembers. Reading the outcome back is what turns a conversation into a record while the people who had it are still in it. If an item runs out of time, it is not resolved; it goes to the parking lot with a date.

After the meeting, publish the same day. Clean up the notes while the context is fresh — ten minutes, not an evening — and send them to everyone invited, including, especially, the people who missed the meeting. Then put them where the next meeting will find them. Notes that live in one person's notebook are notes the team doesn't have, and the parking lot in them is a parking lot nobody will empty.

A meeting notes template

[Team] — [Meeting name] — notes
Date: [date] · Time: [start]–[end] · Link: [meeting link]
Present: [names] · Apologies: [names] · Notes: [name]
Purpose: [one sentence — what this meeting is for]
Open from last time: [action] — [owner] — [done / not done]

1. [Item] — [owner]
[Two–three lines: what was said that matters, positions attributed only where it matters.]
Outcome: decided / open / deferred to [date]
Decision: [one sentence — "we agreed …"]
Action: [name] — [task] — by [date]

2. [Item] — [owner]
[Summary.]
Outcome: [decided / open / deferred]
Action: [name] — [task] — by [date]

Decisions (all items, one line each)
– [decision]
– [decision]

Action items
– [name] — [task] — by [date]
– [name] — [task] — by [date]

Parking lot: [question] — raised by [name] — to the next agenda
Next meeting: [date] · Record: [link to recording / document]

The two lists at the bottom repeat what is already in the item blocks. That is deliberate: the blocks are for the people who were there, the lists are for the people who weren't.

Two filled-in examples

Weekly team meeting — 30 minutes

Product — Weekly — notes
Date: 6 October 2026 · Time: 10:00–10:30 · Present: Mateusz, Priya, Lena, Tomás (notes) · Apologies: Ana
Purpose: unblock this week's work and decide what we don't ship.
Open from last time: Priya — interview slots to the two finalists — done.

1. Blockers raised in the channel — everyone
Two blockers: the export job fails on files over 50 MB (Mateusz); the staging login loops on Safari (Lena). Lena has a fix in review.
Outcome: open
Action: Mateusz — reproduce the export failure with a 60 MB file — by 7 Oct

2. Scope cut for the release: drop the export or ship it unpolished? — Mateusz
Mateusz would ship the export behind a flag; Priya would drop it and avoid a support wave. Lena noted the two enterprise trials asked for it.
Outcome: decided
Decision: we agreed to ship the export behind a flag, on for the two trials only.
Action: Mateusz — flag and trial allowlist — by 9 Oct

3. Hiring: finalists — Priya
Both finalists interviewed; Priya recommends the second. No objections.
Outcome: decided
Action: Priya — offer to the second finalist — by 8 Oct

Parking lot: should the 50 MB limit be raised? — raised by Mateusz — to next week's agenda
Next meeting: 13 October 2026, 10:00

Client call — 45 minutes

Aster GmbH — scope call — notes
Date: 7 October 2026 · Time: 14:00–14:45 · Present: L. Ortega, K. Sato (Aster); J. Lindqvist, P. Nowak (notes)
Purpose: agree the scope change and its price before the end of the month.

1. What changed since the last call — J. Lindqvist
The pilot ran in three countries instead of two; Aster wants Japanese support in the first phase.
Outcome: information

2. The scope change: what is in, what is out — K. Sato
In: Japanese support, the third country. Out: the custom report, which moves to phase two. Ortega wants the phase-two date in writing.
Outcome: decided
Decision: we agreed phase one is three countries plus Japanese support; the custom report is phase two.

3. Price and timeline options — J. Lindqvist
Two options presented; Aster prefers the fixed-price one but needs the finance sign-off.
Outcome: deferred to 14 October
Action: J. Lindqvist — revised statement of work with both options — by 10 Oct
Action: L. Ortega — finance sign-off on the fixed-price option — by 14 Oct

Parking lot: phase-two start date — raised by L. Ortega — to the 14 October call
Next call: 14 October 2026, 14:00 · Record: the current statement of work

Notice what both examples have in common: every item ends in one of three words, every action has a name and a day, and the parking lot is not empty. Forty-five minutes of talking became a page a person who wasn't there can act on — that is the whole job.

Where the notes live in the tools you already use

Each major platform has a place for the notes, and each stops at a different point. Documented behaviour only, from the vendors' own pages, with the month each page was checked:

Two things are the same everywhere. The notes are a document next to the meeting, kept in the one language the room used; and whether last week's action items were done is a question the document does not answer — a person goes and checks.

Who writes them now — and where they live afterwards

InterMIND is a communication space where a meeting lives in a channel, so the notes have an obvious home: the channel's chat. The skeleton goes in the day before as a note; during the call, the note-taker can put it on everyone's screen next to the video tiles with Share to conference, edit it live while the room watches, and every participant reads it in their own language. Notes drafted somewhere else land in the channel by email — every channel has its own address, and a message sent to it appears as a regular message with the sender named and attachments kept.

When the call ends, the recap is written from the meeting itself — a summary, the points marked agreed, open or disputed, the action items with owners, each line keeping its timestamp — so the note-taker edits a draft instead of writing one. It arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it in their own language: the record is translated per reader, not written once in the language the room happened to use. Any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session, so item 2 from three weeks ago is one click away.

The parking lot and the action list are where the notes usually die, and where the channel's recurring meeting does the checking instead: when the next recap is written, the open action items of the previous session are read back and judged against what was said — an item someone reported finished is marked done, anything else is marked not done with the reason in the words of the meeting, or "not discussed" — and at the start of the next session Mia names the open items and their owners. This part runs for selected accounts while it is being refined.

Where the notes need to end up in a system of record, the host adds a recap copy to any address — a CRM or tracker inbound mailbox — and every recap of the meeting or channel is also sent there, after a one-time confirmation of the address; the mechanics are in a copy of every meeting recap in your CRM, by email. A decision taken in the hallway afterwards goes into the channel as a voice note — it arrives as text within seconds, read by each member in their own language.

A participant who joins by link without an account gets the fully translated meeting live, but no record afterwards — the account is free, and it is what makes the record reachable.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

Notes as a craft survive every tool: somebody still has to decide what the meeting meant. What doesn't have to survive is the second job — retyping the outcomes after the call, in one language, and checking by hand whether anyone did what the last page said.

FAQ

What should be included in meeting notes?

Six things: the header (meeting name, date, link, who was there); the purpose in one sentence; one block per item with two or three lines of what was said and the outcome marked decided, open or deferred; each decision in one sentence; action items with owner, task and date; and a parking lot of what was raised but not resolved, with the name of the person who raised it.

How do you write meeting notes?

Build the skeleton from the agenda before the call — one heading per item, header pre-filled, last session's open actions at the top. During the call, write outcomes rather than dialogue, and read each decision back aloud so the room corrects it on the spot. Afterwards, clean up for ten minutes, send the notes the same day to everyone invited, and put them where the next meeting will find them.

What is the difference between meeting notes and meeting minutes?

Notes are the working record taken during the call — plain, same-day, for the people who were invited. Minutes are the formal record written from the notes afterwards: attendance, each item, decisions with how they were reached, votes, and actions, in neutral language, and in boards and associations usually the document the organization is required to keep and approve. A working call needs notes and a recap; a meeting with a chair and votes needs minutes — the minutes guide covers that format.

Is there a meeting notes template in Google Docs?

Google documents Take notes for me for Google Meet on eligible Workspace editions: switched on in Calendar when the event is created, it writes the notes into a Google Doc after the meeting and shares it per the configured setting, one language per meeting. The template in this guide is plain text, so it pastes into a Google Doc, a Word file, a Slack canvas or a chat message without reformatting.

How do I take meeting notes in Microsoft Teams?

According to Microsoft's documentation, select Notes in the meeting controls during a meeting, or Add an agenda in the meeting's Details when scheduling. The notes are a Loop component that any attendee or organizer can edit, with tasks assigned by tagging people; they are saved automatically and reachable from the Teams calendar and the meeting recap. External attendees cannot access or edit them.

Who should take notes in a meeting?

Someone who is not running the discussion: the facilitator is busy with the room, and a note-taker who is also chairing writes down their own side. In working meetings the duty rotates or sits with a designated person; in formal bodies it is the secretary. In 2026 a growing share of the first draft is written by the meeting platform from the meeting itself, and the human role shifts to editing — checking decisions, owners and dates before the notes circulate.

Should meeting notes be sent after every meeting?

Yes, the same day, to everyone who was invited and not only to those who attended — the people who missed the meeting are the ones who need them most. Notes that are not sent are notes that exist for one person; the action items in them have no witnesses and the parking lot never reaches the next agenda.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Zoom — Using Meeting Summary with AI Companion; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Meeting agenda template (canvas). Microsoft, Google and Slack pages checked October 2026; the Zoom meeting-summary page checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state.