Most meeting notes are written for the person who missed the meeting and read by nobody. They run to six hundred words, list who said what, and contain almost nothing you could act on. A fortnight later, someone asks why the pricing page still hasn't been rewritten, and the answer is sitting in paragraph four of a document no one opened.
Useful notes do one job: they tell you what was decided, who is doing what, and by when. Everything else is optional. The template below takes about ninety seconds to set up before a meeting and saves everyone a follow-up call afterwards.
Decide what the notes are for before you start
Two minutes before the meeting begins, answer one question: what should a reader be able to do after spending two minutes with these notes? For most meetings the answer is narrow. They should know the decisions, be able to find their own tasks, and see what is still unresolved.
That single question is a filter. It tells you to ignore the long anecdote about a customer complaint, unless it produced a change of plan, and to ignore the debate about the office move, unless it ended in a decision. If a line in your notes doesn't help someone decide or act, it belongs in a recording, not in a document.
A one-page template that covers the essentials
You don't need special software. A blank document with five headings works everywhere, from a notes app to the back of a printed agenda.
- Header. Meeting name, date, and the names of everyone present. Add one line on why the meeting happened.
- Decisions. A short numbered list. Each one is a full sentence.
- Actions. A table or list with three columns: task, owner, due date.
- Parked items. Anything raised that the group agreed not to settle today, plus who will bring it back.
- Next meeting. A date, or "none scheduled".
The order matters. Decisions come first, because that's what most people scan for. Actions come second, because that's what they're looking for. Parked items sit at the bottom, where they can't be mistaken for either.
Write decisions as sentences, not topics
"We discussed the free tier" tells a reader nothing except that time passed. "We will keep the free tier free for individuals and charge teams per seat" tells them everything. If the second version feels too blunt, that is usually a sign the meeting didn't actually decide anything — worth knowing while you can still fix it.
Add a short reason where it is likely to be questioned. "We will pause the newsletter until the new site launches, because the sign-up form is moving." Six extra words, and nobody reopens the argument in a month. Where a decision was contested, say so plainly: "agreed, with two objections on timing". Honest notes are more useful than tidy ones.
Never record an action without an owner and a date
Three things belong on every action line: a verb, a name and a date. "Marketing to look at the homepage" is not an action. "Priya to draft new homepage copy by 14 March" is.
A few habits that keep this honest:
- One owner per task. Two names means nobody. If the work genuinely needs two people, split it into two lines.
- Real dates, not moods. "Soon", "next week" and "after the launch" are not dates. If nobody will commit, write down the date you'll chase it.
- Start with the verb. "Book the venue", "send the contract", "check the figures". It makes the task easier to tick off.
- Mark unassigned work clearly. "Unassigned — Sam to find an owner by Friday" is better than quietly leaving it out.
Keep up in the room
You are taking notes, not transcribing. Paraphrase. If you type every sentence, you will capture a lot of words and miss the moment the group actually changed its mind.
A routine that works:
- Capture decisions and actions live, in your template. Nothing else.
- Keep a separate scratch area for anything you didn't follow. Ask about it in the last five minutes rather than interrupting mid-flow.
- If you are also a participant, say "let me note that down" out loud. People pause for it, and it signals that what they just said matters.
- Tidy the notes straight afterwards, while you still remember who "she" was.
That last step takes ten minutes and is the difference between notes people trust and notes people quietly correct.
Send them within a day, and invite corrections
Notes lose most of their value by the following afternoon. Send them the same day if you can, and keep the message short: a couple of lines summarising the decisions, then the notes themselves pasted into the body of the email rather than hidden in an attachment. People read what they can see without clicking.
Invite corrections explicitly — "reply if I've got your action wrong" — and mean it. Someone who welcomes fixes ends up with a better record and fewer awkward conversations later. If something changes, correct it in the document and note that it changed, so nobody keeps working from a stale version.
The two-minute test
Before you send, read your notes as if you had missed the meeting. Can you say what was decided? Can you find your own name and know what to do next? Is it obvious what is still open?
If yes, you are done. Notes that pass that test get read, and notes that get read get acted on — which is, after all, the only reason to write them.
Photo: Felicity Tai / Pexels
