Meeting Notes Template
A copy-paste format for the discussion, decisions and action items that need to survive the meeting. Start with the blank template, then use the filled example to check your notes.
The meeting notes template
Use one document per meeting. Fill in the agenda before you start, capture the outcome of each topic during the discussion, and confirm owners before people leave. Leave a field marked TBD if it has not been agreed; an empty field should not look like a commitment.
Blank meeting notes
# Meeting Notes - [Meeting title] Date: Time / time zone: Location / call link: Facilitator: Note taker: ## Attendees - Name / role: - Absent / needs an update: ## Agenda 1. 2. 3. ## Key discussion points - Topic: ... | Summary: ... | Supporting document: ## Decisions made - Decision: ... | Confirmed by: ... | Effective date: - Still a proposal (not agreed): ## Action items | # | Action | Owner | Due date | Status | |---|--------|-------|----------|--------| | 1 | | | | Open | | 2 | | | | Open | ## Risks and blockers - Risk: ... | Impact: ... | Mitigation / owner: ## Open questions - Question: ... | Who will answer: ... | Needed by: ## Next meeting Date / time: Carried over: Notes reviewed by:
Illustrative example: a weekly product sync
This fictional example shows the level of detail to aim for. Names, dates and decisions are invented, not a customer session or a CoHear-generated result.
Filled meeting notes example
# Meeting Notes - Help center launch sync Date: 2026-10-23 Time / time zone: 10:00-10:25 UTC Facilitator: Priya Note taker: Sam Attendees: Priya (product), Sam (support), Lee (engineering) ## Agenda 1. Review launch blockers 2. Agree on the first release scope ## Key discussion points - Support needs a password-reset article before launch. - Search filters are not ready; the team discussed a later release. ## Decisions made - Launch with the five reviewed articles, without search filters. - Confirmed by: Priya, Sam and Lee | Effective date: 2026-10-26 - Still a proposal: add a video walkthrough. No owner or date agreed. ## Action items | # | Action | Owner | Due date | Status | |---|--------|-------|----------|--------| | 1 | Draft password-reset article | Sam | 2026-10-24 | Open | | 2 | Verify article links in staging | Lee | 2026-10-25 | Open | | 3 | Approve launch checklist | Priya | 2026-10-26 | Open | ## Risks and blockers - If staging links fail, Lee will flag the blocker before approval. ## Open questions - Who will maintain the articles? | Priya to confirm by 2026-10-26 ## Next meeting Date / time: 2026-10-26, 10:00 UTC Carried over: article maintenance owner Notes reviewed by: Priya, Sam and Lee
How to adapt the format
- Weekly team sync: carry forward unfinished actions and update their status instead of recreating them without context.
- Client meeting: add approval requirements and separate client commitments from internal follow-up work.
- One-to-one: use a restricted document for sensitive discussion, with a short shared list of agreed next steps.
- Project review: expand risks and blockers with dependencies, impact and an escalation owner.
Review before sharing
- Check that each decision was actually agreed. Keep suggestions and unresolved alternatives separate.
- Read back every action: a specific deliverable, one accountable owner and an agreed due date or an explicit TBD.
- Ask attendees to correct missing context, names and dates. If you used an authorized recording, check uncertain passages against it.
- Share the notes with the intended recipients, check access permissions and carry open items into the next agenda.
