📝 Template · Updated October 2026

Meeting Notes Templates: Seven Formats, Written for Future You

Notes fail when they record what was said rather than what was decided. These seven formats lead with decisions, owners and dates, and they are short enough that people read them the following week.

Disclosure: We may earn a commission when you purchase through links. See our affiliate disclosure.
🧪 General Assistant

Claude

$20
per month · Pro

Strongest at holding a long brief steady across a full draft, and at flagging the parts you left unspecified.

Try it →
💰 Low Cost

Rytr

$7.50
per month · Unlimited

The cheapest way to turn a finished brief into twenty drafts before you decide which shape is worth writing properly.

Try it →

The test for good meeting notes is whether someone who missed the meeting can act on them. A chronological transcript fails that test — it records the discussion but not the outcome, so the reader has to reconstruct the decision from the argument. That is work, so they ask someone instead, which is how the same meeting gets held twice.

Every format below leads with decisions and actions. Discussion goes last, or is omitted.

The three sections that make notes usable

  1. Decisions — what was settled, with the date. Written as statements, not as summaries of discussion.
  2. Actions — one line each: what, owner, due date. No action without both a name and a date.
  3. Open items — what was raised and deliberately not settled, with who is taking it forward.

If your notes have none of the three, the meeting produced nothing you can record, and it is worth asking whether it needed to happen.

Seven formats

1. Decision log

Use when: the meeting exists to settle something.

Date: [date] · Present: [names]

Decisions
1. [Decision] — basis: [the reason or evidence] — effective: [date]
2. [Decision] — basis: [reason] — effective: [date]

Not decided
· [Item] — carried forward by [name], revisit [date]

2. Action table

Use when: the meeting is mostly coordination.

ActionOwnerDueStatus
[What, with a verb][Name][Date]Open
[What][Name][Date]Open

Send this within a few hours, while people still remember agreeing to it.

3. Daily standup

Use when: short daily sync. Keep it to three lines per person.

[Name] · [date]
Done: [what moved]
Next: [what is in progress]
Blocked: [what is stopping it, and who can unblock]

4. One-on-one

Use when: recurring manager conversation. Track commitments across weeks.

[Name] · [date]
Raised this time: [topics]
Still open from last time: [items carried over]
Agreed: [commitments, with dates] — mine / theirs

5. Client call record

Use when: anything a client may later refer back to.

[Client] · [date] · [attendees]
Context: [why the call happened]
What the client asked for: [in their words]
What we said: [commitments made on the call]
Next: [what happens, by when, who sends it]

6. Retrospective

Use when: reviewing a completed piece of work.

Period: [dates]
Worked: [what, and why]
Did not work: [what, and the contributing cause]
Change for next time: [one specific thing, with an owner]

7. Board or leadership summary

Use when: reporting upward. One page.

Period: [dates]
Position: [two or three sentences on current state]
Against plan: [what is ahead, what is behind, with numbers]
Decisions needed: [what you need from this group, by when]

Where AI helps

Strong for: compressing a long transcript into decision-plus-action form; grouping scattered comments under themes; turning rough bullets into the three sections above; rewriting for brevity.

Weak for: knowing which decision was actually final; assigning owners it was not told about; judging whether an action item is realistic. It will also produce confident summaries of discussion that never resolved — always mark open items yourself.

What we measured over 30 days

Converting a 45-minute call transcript into decision-plus-action notes took about 6 minutes with the tools, against roughly 25 minutes manually. The drafts were reliable on structure and unreliable on ownership — roughly one in four action items had an owner that was inferred rather than stated, so every line needed checking against the recording.

Compress, then verify

Let the tool do the compression. Check owners and dates yourself — those are the parts it guesses at.

Try Rytr →

Frequently Asked Questions

Should I record the meeting and transcribe it?

With consent, yes — a transcript makes the note-writing step far more reliable than memory. Tell attendees before recording.

How soon should notes go out?

Within a few hours if there are actions with dates. After 24 hours the commitments start to feel negotiable.

What if an action item has no owner?

It is not an action item. Either assign one in the meeting or move it to open items.

Can AI attend the meeting for me?

It can summarise afterwards, but it cannot tell you what mattered. Read the decisions before forwarding.

How detailed should notes be?

Detailed enough that an absent person can act. Usually decisions, actions, open items — discussion only where context will be needed later.

Should I share raw transcripts?

Generally no. A transcript is a record for you; a summary is the artefact for everyone else.