Meeting notes template that captures decisions
A free meeting notes template built around decisions and action items, with a filled-in example and how to write and send notes people actually use.
Six weeks after a planning meeting, someone asks why the team chose to delay the mobile release. The notes exist. They're four pages of who said what, and the decision is a half-sentence in paragraph eleven, with no reason and no owner.
Notes are written once and searched many times. This template is built for the search: decisions and actions first, discussion last. Atlassian's meeting notes template uses the same three jobs, agenda, notes, and action items, checked on 16 November 2026.
The template
# [Meeting name]: [Date]
Purpose: [The question this meeting answers, in one line]
Attendees: [Names] Absent but affected: [Names]
Notes by: [Name]
## Decisions
| Decision | Owner | Why |
|---|---|---|
| [What was decided] | [Who decided] | [The reason, one line] |
## Action items
| Action | Owner | Due |
|---|---|---|
| [Specific next step] | [One name] | [Date] |
## Open questions
| Question | Owner | By |
|---|---|---|
| [Not decided yet] | [Who will get the answer] | [Date] |
## Discussion (optional)
- [Key points or options considered, briefly]
Why this order
- Decisions first. It's what people search for later, and what's most often missing.
- One owner per action. "The team" doesn't do things.
- Open questions separate from decisions. Otherwise a maybe gets read as a yes.
- Discussion last and short. The reasoning that matters goes in the decision's "Why."
- "Absent but affected." The people most likely to be surprised by a decision weren't in the room.
A filled-in example
# Mobile release planning: 14 Nov
Purpose: Decide whether the mobile release ships on 1 Dec
Attendees: Priya, Arjun, Mei, Sam Absent but affected: Support lead
Notes by: Mei
## Decisions
| Decision | Owner | Why |
|---|---|---|
| Release moves to 15 Dec | Priya | Offline sync fails on 3% of test devices |
| Ship without dark mode | Priya | Not ready; not a launch blocker |
## Action items
| Action | Owner | Due |
|---|---|---|
| Fix sync conflict on Android 13 | Arjun | 22 Nov |
| Update release notes and support macros | Mei | 1 Dec |
| Tell the two pilot customers about the date | Sam | 15 Nov |
## Open questions
| Question | Owner | By |
|---|---|---|
| Do we need a beta for the pilot customers? | Priya | 18 Nov |
How to take them
- Fill the template live. Write decisions and actions as they happen, not a transcript.
- Name the decision out loud. "So we're moving to the 15th, Priya's call?" makes the decision explicit.
- Read back at the end. Two minutes on decisions and actions catches misunderstandings.
- Send within the hour, to attendees and to anyone affected.
- Post where the work happens: the project channel or page, not only email.
Notes vs minutes
Minutes are a more formal record, often required for boards and committees, sometimes with motions and votes. For most product and engineering meetings, notes focused on decisions and actions are enough.
Where meeting decisions go to die
A decision written in meeting notes is findable only by someone who knows which meeting to look in. A month later, nobody does. The fix is to copy each decision into a running decision log with its owner, date, and reason, linked back to the notes.
Where Lockstep fits
Lockstep does that copying. It captures decisions from documents, Slack, and pull requests, routes each to its owner for approval, and keeps them in one place, with a new decision superseding the old. Engineers and Claude Code sessions are briefed on the ones that apply to their work, so "ship without dark mode" reaches the people building the release.
See Lockstep for product teams.
Sources checked 16 November 2026
Related reading
For deciding who decides, see RACI vs DACI. For turning decisions into a log, see the Notion decision log template. For who owns each task, see the RACI chart template.
Frequently asked questions
- What should meeting notes include?
- The meeting's purpose, who attended, the decisions made with their owner and reason, action items with an owner and a due date, and open questions. A short summary of discussion is optional; the decisions and actions are what people come back for.
- How do I write meeting notes quickly?
- Use the template live, filling in decisions and actions as they happen rather than transcribing. At the end of the meeting, read the decisions and actions aloud for confirmation, then send the notes within the hour.
- What is the difference between meeting notes and meeting minutes?
- Minutes are a more formal record, often required for boards and committees, sometimes with motions and votes. Meeting notes are informal and practical. For most product and engineering teams, notes focused on decisions and actions are enough.
- How should I send meeting notes after a meeting?
- Send them within an hour to attendees and anyone affected by the decisions, with the decisions and action items at the top. Post them where the team works, such as the project channel or the project page, not only in email.
- How do I keep decisions from getting lost in meeting notes?
- Copy each decision into a running decision log with its owner, date, and reason, and link back to the notes. Meeting notes get buried; a log is where people look later.
Keep reading