How to take meeting notes people actually read

A meeting ends and five minutes later three people remember three different things. Good notes fix that. Bad notes are a transcript that nobody reads. The trick is to capture outputs, not conversation.

What to write: the four things that matter

Both sources we read for this guide, Fireflies and Jamie (each a blog for an AI note-taking product, so we used only the manual advice), agree on the same core:

1. Decisions. Write them as plain statements: "We will launch on the 12th." Not "we talked about launching".
2. Action items. Each needs a task, an owner and a due date. Fireflies puts it sharply: without all three, it is a suggestion.
3. Open questions. Anything unanswered that someone has to chase.
4. Changes. Scope, deadline or ownership that moved.

Everything else (the tangents, the opinions, the exact words) can stay in the room. Note the objection and the outcome, not who said what.

A copy-paste template

Paste this into any notes app or document before the meeting starts. Prefer to choose your own sections? The meeting notes template builder makes a plain text or Markdown version for your type of meeting.

MEETING: [name]
DATE / TIME: [ ]
ATTENDEES: [ ]
GOAL (one line): [ ]

TOPIC 1: [ ]
- Key points:
- Decision:

TOPIC 2: [ ]
- Key points:
- Decision:

ACTION ITEMS
- [task] | [owner] | [due date]
- [task] | [owner] | [due date]

OPEN QUESTIONS
- [ ]

NEXT MEETING: [ ]

It follows the fields Fireflies and Jamie both describe: meeting details, a one-line objective, a block per agenda item with a decision, an action list and open questions. Strip it down for short calls. A five-minute check-in only needs the decision and the action items.

Different meetings, different notes

Meeting	What to capture	Skip
One-to-one	Agreements, feedback you want to remember, follow-ups for each side	Small talk
Daily stand-up	Blockers and who can help	Status everyone can read elsewhere
Project review	Decisions, risks, changes to scope or dates, owners	Long debates; note the outcome
Client call	Requests, promises you made, deadlines, questions to answer	Your internal opinions
Brainstorm	The ideas that got energy, the chosen direction	Ideas that went nowhere, unless asked

The pattern repeats: if something changes what people will do next, write it down. If not, let it go.

An example of good notes

Here is an invented set of notes from a 25-minute project review. It is short on purpose.

Website relaunch, review, Tue 3 Dec
Present: Priya, Sam, Lena
Goal: confirm launch date

DECISIONS
- Launch moves from 5th to 12th (checkout bug)
- Keep old homepage banner until launch

ACTIONS
- Priya: final copy to Lena | Fri
- Sam: fix checkout bug, retest | Mon
- Lena: book launch-day cover [CHECK date]

OPEN
- Do we need a redirect plan? Sam to ask Dev.

Anyone who missed the call knows what changed, who owns what and by when.

During the meeting

• Read the agenda first so you can prepare the topic headings.
• Type fragments. "Launch 12th, Priya owns copy, Fri" is a perfect note.
• Mark gaps instead of stopping. If you miss a name or a number, type [CHECK] and keep going. Fireflies recommends exactly this.
• Ask for clarification out loud when an action item is vague. "Who is taking that, and by when?" takes five seconds and saves a follow-up thread.
• Do not try to be neutral and complete. You are writing for the reader who was not there.

After the meeting: the 30-minute routine

1. Fill the [CHECK] marks within about half an hour, by messaging the right person.
2. Reorganise by topic, not by chronology.
3. Pull the action items into their own section, with owner and due date.
4. Write the subject line as an outcome: "Launch moved to the 12th, Priya owns copy" beats "Meeting notes 6/3".
5. Send it the same day to attendees and to anyone affected by a decision.

Jamie adds a habit for recurring meetings: review the last notes before the next one, weekly for fast-moving projects and monthly for slower ones.

Mistakes to avoid

• Typing everything. You miss the conversation and produce a document nobody wants.
• Vague actions. "Look into pricing" has no owner and no end. "Sam sends three competitor prices by Thursday" does.
• Notes that stay private. Notes that nobody else sees cannot settle a disagreement.
• Only one person ever takes notes. Rotating the role is a common suggestion in the sources, and it spreads the load.

The follow-ups that do not belong in the notes

Meetings also produce personal loose ends: a thing you promised to look at, a link someone dropped in the chat, a worry you do not want to forget. They do not belong in the shared notes, and they should not live in your head either.

Do a one-minute brain dump as soon as you stand up, then choose the next step with the cut-and-shrink routine. On a phone, quick capture gets it done between meetings.

Nom is a good place for this moment, although it does not record meetings. Share the link someone dropped in the chat, snap the whiteboard, or speak the thing you promised to look at. Nom puts it away and picks one to three tiny quests for today. Later you can ask for it in your own words, like "the numbers Sam sent", and it brings the note back with its source.

If you do not want a template, even a single line per meeting helps. The habit of writing the decision and the owner is what people notice. For notes you want to look back on, see organising notes without a heavy system.