How to write meeting notes people actually read

Most meeting notes fail for a simple reason: they are written in the order things were said. A reader has to scroll through the discussion to find out what was decided, and by the time they reach the part that concerns them, they've stopped reading.

Notes people actually read are written in the order a reader needs them. What did we decide? What do I have to do, and by when? What is still open? Everything else is context, and most readers can skip it.

The 30-second test

Before you send your notes, imagine someone who missed the meeting and has thirty seconds. Could they answer these three questions from the top of your notes alone?

• What changed because of this meeting?
• Is there anything I have to do, and by when?
• Is there anything waiting on me to decide?

If the answers are buried in paragraph four, move them up. That single change does more for your notes than any tool.

The structure

1. Decisions: what was agreed, one line each, written as a statement. “The menu page launches before the logo refresh.”
2. Actions: one line each, owner first, then the task, then the date. “Sam: send the new menu prices by Wednesday.”
3. Open questions: what wasn't settled, and who will settle it. End each line with a question mark so it stands out.
4. Context: only what a reader needs to understand the decisions. Skip who said what, unless it matters later.

[Meeting name], [date]
Attendees: [names]

Decided
- [statement]
- [statement]

Actions
- [Owner]: [task] by [day or date]
- [Owner]: [task] by [day or date]

Open
- [question]? (who settles it, by when)

Context
- [only what explains the decisions]

During the meeting

Good notes are easier to write during the meeting than after it, if you capture the right things. You don't need to write fast. You need to write the lines that matter in a form you won't have to rewrite.

• Write the owner first. “Sam: prices by Wednesday” is a task with an owner and a date. “Prices need sending” is a wish nobody owns.
• Keep the day or date on the same line as the task. A date in a separate sentence gets lost when someone copies the line into a task list.
• When someone says a decision out loud, write it down in their words, then read it back: “So we're launching the menu page first?” It costs five seconds and saves a week of misunderstanding.
• For your own tasks, write “I'll” or “me to”, then replace it with your name before you send.
• Mark anything unresolved with a question mark as you go, so the Open list writes itself.

After the meeting

1. Send the notes the same day, ideally within the hour. Notes sent the next morning are already competing with people's memories, and memories win.
2. Put the actions at the top of the message itself, not only in an attachment or a linked doc. Many people read only the message preview.
3. Use a subject line that says what's inside: “Kickoff notes: 3 decisions, 4 actions (Sam: prices Wed)”.
4. Address actions to people by name. If an action has no owner, don't send it as an action. Put it under Open with a question mark.
5. Copy the actions into wherever your team tracks work, so the notes aren't the only place a task lives.

A worked example

Here is the difference in practice. The first version follows the conversation. The second follows the reader.

We talked about the menu page and the logo. Sam thinks the prices should be ready this week. Alex mentioned the photos from the shoot. Budget for extra pages came up.

Kickoff call, Tuesday

Decided
- The menu page goes live before the logo refresh.
- We keep the current fonts.

Actions
- Sam: send the new menu prices by Wednesday.
- Alex: send two homepage layouts by Friday.
- Sam: share the photos from the shoot next week.

Open
- Are extra pages in the budget? (Alex asks the client by Thursday)

Common mistakes

• Recording everything. A transcript is a record, not notes. If you have one, link it, and still write the four sections.
• Vague owners. “The team will look into it” means nobody will. Pick a name, even if it's “Alex to find the right person by Friday”.
• Dates like “soon” or “next sprint”. Use a day or a date a reader can put in a calendar.
• Hiding disagreement. If something was argued and not settled, it belongs under Open, not quietly dropped.
• Sending notes nobody asked to receive. Keep the list to attendees and anyone with an action.

Make it a team habit

Rotate the note-taker so the job doesn't fall to the same person every week, and agree on the template once, so every set of notes looks the same. After a month, people stop asking “what did we decide?” because they know exactly where to look.