Most meeting notes are never read again, because they are too long, too late, or do not say what happens next. Useful notes are short and organized around three things: what was decided, who will do what, and by when.
Decide what the notes are for
Notes can serve different purposes: a record for people who were absent, a reminder of commitments, or a history of why a choice was made. Think about who will read them and why. A one-page summary for a project team differs from detailed minutes for a formal committee.
Prepare before the meeting
A little preparation makes the notes easier:
- Get the agenda in advance, and use it as the headings of your notes.
- Note who is attending, and who is absent.
- Know the purpose: what should be different after this meeting?
A simple structure
This structure works for most meetings:
Title, date and attendees
Agenda: the topics covered.
Key notes: a few bullets per topic, covering what was discussed and any reasoning that matters.
Decisions: what was agreed, in plain words.
Action items: who does what, by when.
Put decisions and actions where they are easy to find, since those are what people return to.
Capture the right things
You do not need to record everything. Focus on:
- Decisions, and the reason behind them if it is not obvious.
- Actions, each with an owner and a date.
- Open questions that need answers.
- Numbers and dates that were agreed.
Skip small talk, repeated points and anything off-topic. If you are unsure whether to write something down, ask whether anyone would miss it later.
Make actions clear
An action like "Look into pricing" will not happen. A useful action has:
- an owner: a named person,
- a task: a specific thing,
- and a date.
"Lina to update the support docs by Friday" is something a person can do and check.
If an owner or a date is missing at the end of the meeting, ask for it before everyone leaves.
Send them quickly
Notes lose value fast. Send them the same day, or the next morning at the latest, while everyone remembers the meeting. Put the actions at the top of the message so they cannot be missed. Ask people to reply with corrections within a day.
Be careful with sensitive information
Think before you record personal or confidential details, and share notes only with people who should have them. If you use a tool that processes text on a server, such as an AI service, do not paste material that is confidential or personal.
Using a tool to tidy rough notes
If you take quick, messy notes, a Meeting Notes Generator can organize them into this structure. It only knows what you give it, so:
- Check every decision against what was actually agreed.
- Fill in missing owners and dates.
- Delete anything that was not said.
- Share it promptly.
Checklist
- Are decisions and actions easy to find?
- Does every action have an owner and a date?
- Is it short enough to read in two minutes?
- Did I send it today?
Notes people use are notes that make the next step obvious.