Quick notes and ideas, all in one place.

How to Take Meeting Notes That People Actually Read

How to Take Meeting Notes That People Actually Read

Most meeting notes fail for a simple reason: they try to record everything. A faithful transcript of a forty-minute conversation is thorough, accurate and almost never opened again. The notes people return to are short, and they answer three questions — what did we decide, who is doing what, and by when.

That is a low bar, and most of us still miss it. We write down the discussion instead of the outcome, we lose the owner of an action somewhere between the third and fourth speaker, and we tidy things up two days later when the details have gone fuzzy. The method below takes the pressure off your memory and puts it into a structure.

Before the meeting: decide what the notes must answer

Spend thirty seconds before anyone speaks working out what someone will need from this meeting in three weeks. Write two or three questions at the top of the page. For a product catch-up, that might be:

  • Are we moving the launch date?
  • Who owns the pricing page?
  • What do we tell the client on Thursday?

Those questions turn you from a stenographer into a filter. Anything that does not help answer them can be left out without guilt. If you genuinely cannot work out why the meeting exists, that is worth raising with whoever called it — before it runs for another six weeks out of habit.

Set up one page with three zones

Draw three headings before the meeting starts, and never change them:

  • Decisions — what we agreed, one line each, written in the past tense: “Launch moves to 12 April.”
  • Actions — who does what, by when.
  • Open questions — anything unresolved that needs to come back.

Everything you write goes into one of those three zones. This is the whole trick. The discussion goes in your ears and out of your pen, because you are listening for outcomes rather than sentences.

What to write down, and what to let go

The signals are fairly consistent once you start listening for them.

  • A decision usually arrives after words like “so”, “let’s go with”, “agreed then”, or a shift in tone from talking to settling. Write it as a finished thing: “We go with the smaller venue.” Not “it was felt that the venue question could potentially be revisited”.
  • An action is a verb with a person attached: “I’ll draft the email”, “Priya will check with finance”. If you hear the verb but not the name, ask before the meeting ends. “Who’s picking that up?” is a perfectly normal question and it saves an email chain later.
  • Numbers, dates and money. Write them down with their context — “budget cap £8k”, “draft by Friday 14 March” — because these are the details people misremember.

Skip anything repeated from a document everyone was sent, anything you cannot attribute to a person, and the long stretches where people think aloud. Your own opinions stay out of it too. If you find a point genuinely interesting but irrelevant, it can go in a margin note; it should not appear in the version you send.

The ten-minute tidy-up

Do this before you leave your desk, not tomorrow morning.

  1. Read your jottings once, without editing anything.
  2. Move each item into Decisions, Actions or Open questions. Delete whatever fits none of them.
  3. Check that every action has a verb, a name and a date. If a name is missing, write “owner to confirm” rather than guessing.
  4. Write one sentence at the top: what this meeting changed.
  5. Send it within a few hours, while everyone still remembers agreeing to it.

Format so it can be skimmed

Small choices do a lot of work here. Put the owner’s name at the start of the line, or in bold, so that scanning down the action list gives each person their own to-do list. Begin every action with a verb: “Confirm the venue deposit”, not “Venue deposit to be confirmed”. Write dates as day then month — Friday 14 March — because “next week” means something different to everybody reading it.

Translate meeting language into plain English. “We agreed to revisit the pricing structure in Q3” becomes “Pricing review before 30 September. Owner: Sam.” Keep the whole thing to roughly a page. If it will not fit, you are still writing a transcript.

Send them while they still matter

Put the substance in the covering message, not only in the attachment or the shared document. Three lines will do:

Three decisions and four actions from this morning. Launch moves to 12 April. Actions below — tell me if I have misrecorded anything by end of day.

Invite corrections openly. It is much easier to fix “I have written that you are doing the pricing page” than to discover the confusion three weeks later. Keep one home for notes — a shared folder or the notes app your team already uses — and keep the structure identical every time, so people learn where to look rather than searching through email.

Make it stick

Save the template so setting it up takes seconds: date, attendees, then Decisions, Actions and Open questions. Keep the tidy-up to ten minutes and do it straight after the meeting, before the detail fades. If your day is back-to-back, book the last five minutes of each meeting for it. People rarely object to five minutes spent getting the actions right.

Not every meeting needs notes. If nothing was decided and nothing was assigned, send one line saying so. It takes ten seconds, it is honest, and it gives everyone the evidence they need to ask whether that recurring meeting should exist at all.

Photo: RDNE Stock project / Pexels