What belongs in meeting notes
A meeting notes template earns its place by answering three questions for someone who was not in the room: what did we decide, who is doing what by when, and why did that make sense at the time. Everything else in the template exists to make those three answers trustworthy.
- Purpose line. One sentence about what the meeting needs to produce. If you cannot write it, the meeting is probably a status update that could have been a message.
- Attendees, including who is missing. The absent person is the one who will ask "when was this decided?" Marking them lets you send the note instead of re-explaining.
- Notes by topic. Fragments are fine. Capture numbers, dates, names and disagreements, because those are the details memory drops first.
- Decisions with reasons. The reason is what stops the decision being reopened by the next person who joins.
- Action items with one owner and one date. A task without a date is a wish.
- Open questions with a name. Not every question gets answered in the room. Write down who can answer it so it does not vanish.
What does not belong: a transcript. If you want every word, record the meeting and keep the recording. Notes are the compressed version that people actually read.
Meeting notes vs meeting minutes
The two get confused because both are written during meetings. Minutes are a formal record: attendance, motions, votes, in a fixed order, often required by bylaws or regulators. Notes are a working document for the team. The template on this page is for notes. If a board, committee or HOA needs an official record, the meeting minutes template covers that format, and the board meeting minutes template adds the sections boards expect.
How to take notes during the meeting
Do not try to write the final note live. Keep three habits instead:
- Pre-fill before the meeting. Title, attendees, purpose and agenda take two minutes and mean you are not typing while the first person talks. If you circulate an agenda, start from the meeting agenda template and the notes grow out of it.
- Type fragments under the topic heading. "Ana: refunds if prices shown early" is enough. You will expand it in the close-out.
- Flag decisions and actions as they happen. Put a
D: or a checkbox in front of the line the moment someone commits. Hunting for commitments afterwards is where notes go wrong.
The ten-minute close-out
The value of meeting notes is created after the meeting, in a block most people skip. Within an hour:
- Rewrite fragments under Decisions as full sentences with a because.
- Turn every flagged commitment into an action item with a name and a date. If the owner was not agreed, assign yourself the task of agreeing one.
- Move anything unresolved to Open questions with the name of the person who can resolve it.
- Send or share the note. A note nobody reads within a day is a note nobody will read.
For recurring meetings, start the next note by copying the previous Action items into a "Carried over" section and ticking what is done. The fourth example above shows what that looks like in practice.
Common mistakes
- Writing a transcript. Nobody reads it, and the decisions hide inside it.
- Assigning actions to teams. "Engineering to investigate" means nobody investigates.
- No dates on actions. The item survives three meetings and is then quietly dropped.
- Decisions without reasons. Six weeks later someone asks "why did we do that?" and the note says only that you did.
- One note per meeting, no links. Fifty-two weekly notes with no link between them are an archive, not a memory. Link the project, carry actions forward, and the notes start answering questions.
Meeting notes that still make sense next quarter
Use the Meeting Notes template in Scribelet, turn action items into tracked tasks with due dates, and ask your notes what was decided instead of scrolling for it. Encrypted, free to start.
Free plan, no credit card. See pricing