How to take meeting notes that people actually read

Useful meeting notes record three things: what was decided, who owns each action, and by when. Everything else — the discussion, the arguments, the digressions — is context that almost nobody rereads. Write the decisions during the meeting, confirm the owners before it ends, and send the notes the same day.

A transcript is not notes. If the person who missed the meeting has to read four pages to learn what changed, the notes have failed.

A structure that works

• Decisions — what was agreed, one line each, in plain language.
• Actions — owner, action, date. One name per action; “the team” owns nothing.
• Open questions — what was not resolved and who will resolve it.
• Context — links to the documents discussed, for whoever wants the detail.

The steps

1. Before the meeting, paste the agenda into the note. Notes that start as the agenda get taken; notes that start blank do not.
2. During the meeting, write only decisions and actions. Resist transcribing the discussion.
3. When an action appears, say the owner and the date out loud and write them down. Silent assignment is how actions die.
4. In the last two minutes, read the actions back to the room. This is the step that makes notes accurate.
5. Send the notes the same day, while people still remember the meeting.
6. Before the next meeting, open the previous notes and check the actions. Notes nobody revisits stop being written.

If a meeting produced no decisions and no actions, that is worth recording too — it is the clearest signal that the meeting did not need to happen.

Common failure modes

• Writing everything. Long notes are unreadable; nobody opens them twice.
• Actions without dates. “Soon” never arrives — a date creates accountability.
• Notes trapped where others cannot find them. If they live in one person’s app, they may as well not exist.
• A different format every time. A predictable structure means people know where to look.

Doing it in Ettex

Ettex Notes handles the mechanics: tags, checklists, links between notes and documents, and version history if you need to see what changed. Actions can become calendar events or board cards without retyping, since the apps share one account.