Meeting Notes People Actually Use: Templates and a 24-Hour Workflow
Write meeting notes around decisions, owned actions and open questions, with three copyable templates, a 24-hour follow-up message and a filing scheme.
Ask this guide
Answers come straight from this guide’s text. Nothing is generated, and nothing you type leaves your browser.
Open the notes from your last meeting and look for three things: what was decided, who owes what, and by when. Say the page reads "Priya raised concerns about timing; Sam suggested a phased approach." It answers none of them: it says who spoke, not what was settled. Notes like that are hard to reread, so people fall back on memory, and the meeting is sometimes held again.
After reading, you can run any meeting from one structure: decisions, owned actions and open questions, with everything else optional. You get three copyable templates, a 24-hour follow-up message, a filing scheme, and four checks for AI-drafted summaries.
Why transcript-style notes are hard to use: they record talk, not outcomes
A transcript-style note makes every reader do the editor's job: find what concerns them, and guess whether a remark was a decision or a thought out loud.
Robert's Rules of Order treat minutes as mainly a record of what was done, not what was said; a City of Madison attorney's guide puts it as "what was done at the meeting, not what was said at the meeting". It also warns against acting as a stenographer: you will be selective, and people may disagree about what was said.
We found no controlled study of note formats and follow-through, so here is adjacent evidence and its limits.
- Meeting behaviour. Kauffeld and Lehmann-Willenbrock (2012) videotaped 92 regular team meetings. Teams with more problem-solving and action planning were more satisfied, and better meetings went with higher team productivity. The study is correlational: it cannot show that writing actions down causes follow-through.
- If-then plans. A 2025 synthesis of 642 tests (Sheeran, Listrom and Gollwitzer) found a modest average effect on behaviour change (effect size d = .27 across 301 tests) and substantial publication bias. It mostly concerns people's own goals; a smaller line of work has tested plans made by groups, but we did not find it tested on actions assigned in meetings.
The three-part structure: decisions, actions and open questions
Every useful line in a note is one of three things.
- Decision: a choice that changes what someone will do, written as a full sentence naming who made it.
- Action: a commitment with one owner, a verb, a due date and a done-when.
- Open question: something the room could not settle, with who will find the answer and by when.
Anything else is context; keep a line of it only if a reader would otherwise misread a decision.
Steven Rogelberg, author of The Surprising Science of Meetings (Oxford University Press, 2019), advises building agendas from questions rather than topics; a 2019 TED Ideas summary quotes him on when such a meeting can end: "the questions have been answered in a compelling way". So each agenda question should end as a decision, an action or an open question, and one with none of the three was not answered.
| Weak line | Rewritten |
|---|---|
| "Discussed launch timing" (talk, not outcome) | Decision: Launch moves from 8 Dec to 15 Dec. Decided by Priya. |
| "Someone to check the VAT question" (no owner) | Action: Lena confirms whether Vendor B issues reverse-charge VAT invoices, by 24 Nov. |
| "Follow up with finance ASAP" (no date, no done-when) | Action: Sam sends finance the signed quote and gets a PO number, by 26 Nov. |
| "Security concerns" (resolved or not?) | Open question: Is a penetration test required before launch? Omar asks the security lead, reports 24 Nov. |
If you cannot name who decided, name how: "Agreed by consent" or "Vote, 3 to 1". If the room cannot say, it is not a decision: write an open question with an owner and a date. "We should look into X" is an action with an owner, never a decision.
An action passes if a stranger could tell a week later whether it is done: one person (a team is not an owner), a verb, a date, and what finished looks like. For actions that tend to slip, add a cue such as "when Friday's stand-up ends": the 2025 synthesis found contingent plans stronger than schedule-style ones (d = .43 against .29; see our if-then planning guide), though cues are untested on team actions.
Three templates: decision meeting, weekly project sync, one-on-one
Copy the one that fits the meeting and fill in the top before it starts. The example content is invented.
Decision meeting
Borrowed from Michael Nygard's architecture decision records: short, with a status, and a changed decision is marked superseded, not deleted. The options section is our addition: "why not the other one?" gets asked six months later.
# 2026-11-17 Decision: invoicing vendor
Decider: Priya | Present: Priya, Sam, Lena, Omar | Notes: Sam
## Question
Which vendor takes over invoicing before the contract ends on 31 January?
## Options considered
- Vendor A: stay as is. Rejected: renewal costs more.
- Vendor B: chosen.
- Do nothing: not possible.
## Decision
We will move to Vendor B, on the lower quote. Decided by Priya on 2026-11-17.
## Consequences
- Invoices are produced by hand for about a week during the migration.
## Actions
- [ ] Sam | rebuild invoice templates in Vendor B | by 2026-12-18, done when Priya approves a test invoice
## Open questions
- ? Does Vendor B issue reverse-charge VAT invoices? | Lena asks, reports 2026-11-24
Status: accepted (revisit if the answer above is no)
Weekly project sync
# 2026-11-17 Sync: checkout redesign
Present: Priya, Sam, Lena | Absent: Omar
## Last week's actions
- [x] Lena | usability script | done
- [ ] Omar | payment sandbox access | slipped 1x to 2026-11-24 (waiting on bank)
## Decisions (copy each to the decision log today)
- D-003. Single-page checkout ships first; address book later. Priya.
## New actions
- [ ] Sam | draft error-state copy | by 2026-11-20, done when Lena has reviewed it
- [ ] Lena | update usability script for the new flow | by 2026-11-24
## Open questions
- ? Do we need guest checkout? | Priya, 2026-11-24
The carry-over list is the engine: start every sync with last week's actions and mark each done, slipped (new date, one-line reason) or dropped. Our rule, judgment not research: an action that slips twice is renegotiated or dropped.
One-on-one
# 2026-11-17 1:1 Sam and Priya
Editors: Sam and Priya only
## Carried over
- [ ] Priya | intro to the finance lead | slipped 1x to 2026-11-24
## Topics (the report's first)
- Sam: wants to lead the invoicing migration
## Decisions and open questions (only if any)
- D. Sam leads the migration. Priya.
## Actions (both lists, same format)
- [ ] Sam | ... | by ...
- [ ] Priya | ... | by ...
The person reporting owns the agenda, and the manager's actions go in the same list, so follow-through is visible both ways. Keep one running document and limit who can edit it: it is the template most likely to hold sensitive content.
From meeting to inbox: live capture and the 24-hour message
Capture live without leaving the conversation
Split roles once a meeting passes about four people (our rule of thumb): one person facilitates, another writes. Rotate the note-taker on a fixed rota instead of asking for volunteers.
- During. Write only three things, each with a one-letter prefix:
Ddecision,Aaction (owner, verb, date),?open question. Everything else gets a few words at most. In a remote meeting, type into a shared document so owners can correct their own line. - Three minutes before the end. Read the decisions and actions aloud. Each owner answers "mine, by then" or corrects the line. An action nobody accepts is not an action yet: assign it or drop it. If time runs out, send the read-back as the first lines of the follow-up.
- Within 15 minutes. Turn the shorthand into the template while it is fresh, then send the message below the same day.
An invented example of step 1:
D launch -> 15 Dec (Priya)
A Lena VAT? by 24/11
? pen test needed? Omar asks sec
fin - quote
The first three expand into the table's rewritten lines. The last has no owner or date, so the read-back is where someone says "mine, by Thursday" and it becomes Sam's action. The read-back is our recommendation, not researched.
The 24-hour follow-up message
Daryl Chen's 2019 TED Ideas summary of Rogelberg's research gives a 24-hour rule in her own voice, for people left out of a meeting because they are not essential: "circulate meeting notes within 24 hours if you want people to truly feel in the loop". We found no study testing the timing for attendees, so our reasons are judgment: corrections are easiest while the meeting is fresh, and every action's clock is already running.
Put the outcome in the body, not only a link, so it shows in the preview.
Subject: Notes 17 Nov, checkout sync: 1 decision, 3 actions
Decisions
- Single-page checkout ships first; address book later (Priya).
Actions
- Sam: draft error-state copy, by Fri 20 Nov
- Omar: get payment sandbox access, by Tue 24 Nov
- Lena: update the usability script for the new flow, by Tue 24 Nov
Open questions
- Do we need guest checkout? Priya answers by Tue 24 Nov.
If I got anything wrong, reply by noon tomorrow and I'll fix the
notes. Otherwise this is the record.
Full notes: <link>
Put the owner's name first on each action line, because people scan for their own name, and include absent owners.
Where to file notes so you can find them in six months
Name by date, type and topic. Put the ISO date first so a plain file list sorts chronologically, and skip spaces and special characters.
2026-11-17_sync_checkout-redesign.md
2026-11-17_decision_invoicing-vendor.md
2026-11-17_1on1_sam-priya.md
Keep one home per project, not per person. One folder or page holds the project's notes and decision log, and the recurring calendar event links to both.
Keep the decision log append-only. One line per decision, newest first. Never delete or reword one: when it changes, add a line and mark the old one superseded, as in Nygard's rule. Copy each decision from the note to the log the same day.
D-014 | 2026-11-17 | Move invoicing to Vendor B | Priya | notes: 2026-11-17_decision_invoicing-vendor
D-009 | 2026-08-03 | Keep Vendor A for invoicing until the contract ends on 31 January | Priya | superseded by D-014
Give each action one record of status. Once an action is in the task list you check daily, the list holds its status and the note keeps the commitment as made; a checkbox in a note goes unseen.
Test it. Ask someone who was not there to find why you chose Vendor B. If it takes more than a couple of minutes, fix the file name or the log line.
AI transcripts and summaries: a draft, never the record
A transcript captures words, not which statements the room treated as decisions. An AI note-taker can do the part of the job people dislike, getting the words down; deciding which statements were decisions, and who owns them, is still yours.
A 2024 study of OpenAI's Whisper speech-to-text model as it stood in 2023 (Koenecke and colleagues) found many transcriptions highly accurate, but about 1% contained entire phrases not in the audio, and 38% of those included explicit harms. The comparison was speakers with aphasia against a control group, so 1% is not a rate for your team calls; it shows that a fluent transcript can contain words nobody said.
Summaries add omission. In a five-week 2024 trial for the Australian regulator ASIC, five assessors scored human summaries 81% and a Llama2-70B summariser 47%, citing incorrect information, missed key points and odd emphasis. ASIC said a week of tuning likely hindered the model, so read it as a failure pattern, not a current rate.
Before sending an AI-drafted summary, check four things:
- Owners. Each action names the right person, not "the team" or the wrong Sam.
- Numbers and dates. Every figure and deadline matches the recording.
- Strength. A "could" has not become a "will".
- Omissions. Search the transcript for "I'll", "by Friday" and "let's" to find dropped commitments.
Paste the draft at the bottom of your note and fill the three sections from it, so the transcript is backup; our guide to checking AI output before you trust it sorts checks by stakes. Tell attendees before you record or transcribe, and follow your organisation's policy (our AI usage policy template counts meeting recorders as AI tools); consent rules differ by country and, in the US, by state.
Review open actions weekly, then start with one meeting
Notes get used when their actions get revisited: in the carry-over list at each sync, and in your weekly review. In the 20-minute weekly review, the "waiting for" scan and the calendar look-back are where meeting actions surface. Add one question: which actions from this week's meetings have no owner or no date in my system?
To start, pick one recurring meeting, paste the matching template, run the read-back and send the message within 24 hours. After two weeks, count actions closed by their due date against actions made, counting only those with an owner and a date. A low ratio is a prompt, not a score: sort each miss by cause (our reading, not research).
| What you see | Likely cause | Fix |
|---|---|---|
| Actions close late and nobody warned | No date or no done-when | Rewrite it with the stranger test |
| "I never agreed to that" | The owner was absent, or the read-back was skipped | Message the owner; it counts once they reply |
| Same action carried a third week | It is a project, not an action | Split off the first physical step, or drop it |
| Note says done, task list says open | Two records of status | The task list wins; the sync reads from it |
| A settled decision gets reopened | Reasons and rejected options were never recorded | Add the options section and link the log entry |
Frequently asked questions
Do I need notes for every meeting?
No. A meeting with no decisions, actions or open questions needs no note, which is a hint to ask whether it needed to happen.
Should I record the meeting instead of taking notes?
A recording is an archive for people who missed the meeting, and nobody can scan it for the decision. The three-part note is what people will read. If you record, tell attendees first.
What if people ignore the follow-up message?
Keep it to one screen, put the owner's name first on each action, and ask owners to reply "ok" or send a correction. The next sync's carry-over list is the backstop.
Sources and further reading
- Bad meetings drain time and energy — here are 6 ways to lead ones that engage and inspire — Daryl Chen, TED Ideas, 2019. Rogelberg on question-based agendas; the 24-hour advice is Chen's own.
- Meetings Matter: Effects of Team Meetings on Team and Organizational Success — Kauffeld and Lehmann-Willenbrock, Small Group Research, 2012. The 92-meeting study.
- The when and how of planning: Meta-analysis of the scope and components of implementation intentions in 642 tests — Sheeran, Listrom and Gollwitzer, European Review of Social Psychology, 2025. Effect sizes and publication bias.
- Point of Order: Taking Committee Minutes — City of Madison Attorney's Office, 2020. What minutes should record.
- Documenting Architecture Decisions — Michael Nygard, Cognitect, 2011. The decision-record format.
- Careless Whisper: Speech-to-Text Hallucination Harms — Koenecke et al., ACM FAccT 2024. Hallucinated phrases in Whisper transcripts.
- Humans outperform AI in Australian government trial — Tom Williams, Information Age, 2024. The ASIC trial.