Work template
Meeting Notes Template
Quick answer
A meeting notes template is a reusable outline for capturing who attended, what was discussed, what was decided, and who owns each follow-up task. Use it any time you're in a recurring team sync, a client call, or a one-off planning meeting where decisions and owners need to be traceable afterward. The structure below works for a two-person check-in or a ten-person cross-team review.
The template
Meeting Notes Date: Attendees: Purpose: Agenda - Discussion Points - Decisions Made - Action Items - [ ] Owner: | Task: | Due: Next Meeting
How to use this template
- 1Fill in the date, attendees, and a one-line purpose before the meeting starts, so latecomers can orient themselves quickly.
- 2During the meeting, jot Agenda items in the order they're covered rather than trying to reorganize live.
- 3Capture Discussion Points as short phrases, not full sentences — you only need enough detail to jog your memory later.
- 4Write Decisions Made as complete statements ('We will ship X by Friday'), not open questions, so there's no ambiguity afterward.
- 5For every Action Item, record an explicit owner and due date — an action item with no owner rarely gets done.
- 6Right after the meeting, send or share the notes within the hour while context is still fresh for everyone.
Filled-in example
Meeting Notes Date: March 3, 2026 Attendees: Priya (PM), Daniel (Eng Lead), A.J. (Design) Purpose: Decide launch date for the referral feature Agenda - Review beta feedback - Confirm launch scope - Assign remaining work Discussion Points - Beta users liked the reward amount but were confused by the redemption flow - Daniel flagged that the payout API needs one more week of testing - A.J. proposed simplifying redemption to a single button Decisions Made - We will simplify redemption to one-click before launch - Launch date moves from March 10 to March 17 to allow for payout testing Action Items - [ ] Owner: A.J. | Task: Ship simplified redemption UI | Due: March 12 - [ ] Owner: Daniel | Task: Finish payout API load testing | Due: March 14 - [ ] Owner: Priya | Task: Update stakeholders on new date | Due: March 4 Next Meeting: March 10, status check
Tips and common mistakes
- Don't wait until the meeting ends to write anything down — notes written live are far more accurate than notes reconstructed from memory.
- Avoid recording every sentence spoken; if you're transcribing instead of summarizing, you'll miss the actual decisions.
- Separate 'discussion' from 'decisions' clearly — teams often argue later about what was agreed simply because the two got blended together.
- If a meeting produces zero action items, ask whether it needed to happen at all.