Last reviewed on 2026-04-24
Meeting notes usually fail in one of two ways. Either they are a full transcript that nobody reads, or they are so skeletal that a week later nobody can remember what was agreed. The useful middle ground is a short, structured record — enough that people who missed the meeting can catch up in two minutes, and people who were in it can find the decisions again.
Here is a lightweight format that holds up well for everyday team meetings, project syncs, and small-group discussions.
A good meeting note has four sections, always in the same order.
The order matters. Decisions come first because they are the most important thing a reader needs. Actions come second because they determine what happens next. Notes go last because they are supporting context, not the main event.
# [Topic] — [Date]
Attendees: Name, Name, Name
Purpose: One line — why we met.
## Decisions
- Decision one.
- Decision two.
## Actions
- [Owner] Action — by [date].
- [Owner] Action — by [date].
## Notes
- Context point.
- Open question we did not close.
Copy this into a note at the start of every meeting. Fill the header before anyone joins the call. Fill the Actions section as soon as someone commits to something — do not wait until the end. Fill Decisions once you are sure the decision has actually been made, not merely discussed. Leave Notes for the last five minutes or a quick tidy-up afterwards.
A decision is something the group has actively concluded and now treats as settled. If you find yourself writing "we talked about X" in this section, it does not belong there. Move it to Notes.
Good decision lines:
Bad decision lines:
Every action line must have an owner, a verb, and a date. Without all three, the line is a wish, not an action.
Good action lines:
Bad action lines:
When in doubt, write actions in the form "[Owner] will [verb] [object] by [date]." It reads stiffly, but it forces you to have all four pieces before you commit it to the page.
Do not try to write down everything that is said. You are making notes, not a transcript. Listen for three things:
Everything else is context. You can always re-listen to the recording or ask someone afterwards if a specific quote matters. The written record exists to save people from that level of detail, not to reproduce it.
Within a few hours of the meeting, do two small things:
Stale meeting notes are worse than no notes, because they look authoritative. Keep them current or retire them.
Skip the attendees line (it is always the same two people). Add a "Topics" section at the top for what each person wants to cover. Keep Decisions and Actions tight — the rest can be personal shorthand.
A standup does not usually need a decision section. A simple "What I did / What I'm doing / Blockers" bullet per person is enough. Keep the whole thing under 300 words.
Add a "Open questions" section before Notes. These are points deferred for follow-up research. Without a section of their own, they get lost in the general notes.
Add a "Commitments made to us" and "Commitments made by us" split in the Actions section. This helps keep negotiation states clear later on.
Give each meeting its own note on a dedicated "Meetings" tab. Use colour to mark follow-ups: for example, pink for open items that still need closure, green for fully-resolved meetings. You can use the built-in "Meeting Notes" template as a starting layout: it seeds notes for agenda, action items, and general notes, which map cleanly onto the structure above.
For longer-running projects, keep the meeting-note tab separate from the project's main working canvas. That way, decisions accumulate in one place and the working canvas stays about the work itself.
At the end of every meeting, ask: could someone who missed this meeting read the notes in under two minutes and know what was decided, what they need to do, and when? If the answer is no, the notes need another pass before they go out.