How to Take Meeting Notes That People Actually Read

Most meeting notes are written once and read never. They sit in a shared folder, a few hundred words long, and the only person who opens them again is whoever has to write the next set. That is not a failure of effort. It is a failure of purpose. Notes written as a record of a conversation are hard to use; notes written as a list of decisions and jobs are easy to act on. The difference comes down to a handful of choices you can make before, during and just after the meeting.

Decide who the notes are for

Before anyone speaks, answer two questions: who will read these, and what will they do differently because of them? If the honest answer is nobody and nothing, skip the notes entirely and send a one-line summary instead.

There are usually two audiences. The people who were there need reminding what was agreed once the detail has faded. The people who were not there need to catch up quickly, without reading a transcript. A finance colleague wants the figure you settled on. A designer wants the specific change requested. Write for the second group and the first will still be well served.

Record decisions and actions, not the discussion

This is the single biggest upgrade you can make. Most notes capture who said what, in the order they said it. Readers do not need the journey; they need the arrival point.

A decision sounds like this:

• Decision: The launch moves to 14 March so the printed materials arrive in time.

Not like this:

• There was a long discussion about timing. Several options were considered and various concerns were raised.

An action sounds like this:

• Priya to send the revised quote to the client by Tuesday 12 September.

Not like this:

• Quotes were mentioned and someone will look into it.

Every action needs three things: an owner (one name, not a team), a verb that describes the work, and a date. "The marketing team will review the copy" fails all three tests. "Sam will review the homepage copy by Thursday" passes.

Give every set of notes the same skeleton

Consistency saves time twice over: once when you write, and again every time somebody reads. A structure that works for almost any meeting looks like this.

1. Header. Meeting name, date, start and finish times, attendees, and apologies.
2. Purpose. One line explaining why you met.
3. Decisions. What was agreed, stated plainly.
4. Actions. Owner, task, deadline — one line each.
5. Key points. Only the context someone will need later. Options ruled out, figures quoted, constraints mentioned.
6. Open questions. Anything parked, with a note of who is picking it up.

Notice what is missing: the running order, the small talk, and the points everybody already agreed with. If a line of your notes would not change anyone's behaviour, it is probably taking up space that a decision could use.

Keep discussion notes short

When you do record discussion, compress it to the reason behind a decision. "Chose the smaller venue because the deposit is refundable" is useful six weeks later. A summary of who argued for what is usually not.

Capture rough, then tidy

Trying to write polished notes while a meeting is happening is the fastest route to missing the important bit. Work in two passes instead.

During the meeting, capture roughly: names, numbers, dates, decisions and verbs. Do not worry about full sentences. Mark anything you are unsure about with a question mark so you can check it before you send.

Afterwards, spend five minutes editing. Turn fragments into short sentences, group the actions together, delete the padding. This second pass is where good notes are actually made — it is also the point at which you will notice the decision you did not quite catch.

Make the page easy to scan

People read meeting notes the way they read a train timetable: looking for one specific thing. Help them find it.

• Keep sentences under about twenty words.
• Use names, not pronouns. "She will follow up" becomes unreadable a week later.
• Replace vague timing with dates. "Next Friday" becomes "Friday 12 September".
• Bold owners and decisions so the eye catches them.
• Put actions in a separate section rather than buried in the discussion.
• Leave white space. A wall of text gets skimmed at best.

Spelling out numbers and names matters more than it sounds. "Around twenty-five per cent" is clearer than "about 25%" when the figure is being quoted back to a client at some later date.

Share them while they still matter

Notes sent three days later are history. Notes sent the same afternoon are a working document, because people still remember the meeting and will correct anything you got wrong. Aim to send within a few hours, or by the end of the working day at the latest.

Then keep them in one predictable place. A single shared folder, a project page, or a channel — it matters less which one you choose than that you always choose the same. Put the actions somewhere they will be seen, such as a task list, rather than leaving them to be rediscovered in a document nobody opens.

One habit that closes the loop: at the top of each new set of notes, add a short line about what happened to the actions from last time. It takes thirty seconds and it makes people take the list seriously.

A ten-minute routine that sticks

Before the meeting, write the header and the purpose line. During it, note decisions, actions and figures in rough. Straight afterwards, give yourself five minutes to tidy, check your question marks, and name an owner and a date against every task. Send it to everyone who was there, plus anyone who should have been.

The notes that get read are rarely the longest or the most detailed. They are the ones where a reader can find, in under a minute, what was decided, what happens next, and whose name is against it.

Photo: Sarah Blocksidge / Pexels