Meeting Notes Template
Why most meeting notes fail (and what a template fixes)
Most meeting notes fail in the same way: they record everything that was said and nothing that was decided. A week later, nobody can tell who agreed to do what, which questions were left open, or whether that "quick sync" actually settled anything.
A good meeting notes template fixes this by separating the record into six buckets — context, discussion, decisions, action items, risks, and open questions — so the outcome of the meeting is visible at a glance, not buried in paragraphs. The template below is the one format that covers almost every recurring meeting. Copy it, paste it into your notes app or doc tool, and fill it in live or right after the meeting ends.
The meeting notes template (copy and paste)
Blank template
Meeting Notes — [Meeting title]
Date:
Time:
Location / call link:
Facilitator:
Note taker:
Attendees
Agenda
Key discussion points
Decisions made
- Decision: … | Decided by: … | Date effective: …
Action items
| # | Action | Owner | Due date | Status |
|---|---|---|---|---|
| 1 | Open | |||
| 2 | Open |
Risks & blockers
- Risk: … | Impact if it happens: … | Mitigation / owner: …
Open questions
- Question: … | Who will answer: … | Needed by: …
Next meeting
Date / time:
Carried over:
Example: the template filled in for a product sync
Here is the same template completed for a realistic weekly product sync, so you can see the level of detail each section needs — and, just as important, what to leave out.
Filled example
Meeting Notes — Q4 Launch Sync
Date: Tuesday, Oct 14
Time: 10:00–10:45
Location / call link: Meet — Launch room
Facilitator: Priya (PM)
Note taker: Sam
Attendees
- Priya — Product Manager
- Sam — Engineering Lead
- Elena — Design
- Marcus — Support Lead
Agenda
- Launch date confirmation
- Pricing page readiness
- Support staffing for launch week
Key discussion points
- Beta feedback: onboarding drop-off is concentrated at the import step; 4 of 9 beta teams mentioned it unprompted.
- Pricing page copy is final; the comparison table still uses old plan names.
- Support expects 2–3x normal ticket volume in launch week based on the last release.
Decisions made
- Decision: Launch moves from Nov 5 to Nov 12 | Decided by: Priya, agreed by all | Date effective: immediately
- Decision: Pricing page ships with v2, not v1.1 | Decided by: Priya
Action items
| # | Action | Owner | Due date | Status |
|---|---|---|---|---|
| 1 | Ship API migration to staging | Sam | Fri Oct 17 | Open |
| 2 | Update comparison table with new plan names | Elena | Wed Oct 15 | Open |
| 3 | Draft launch-week support rota | Marcus | Mon Oct 20 | Open |
| 4 | Send updated launch date to beta teams | Priya | Thu Oct 16 | Open |
Risks & blockers
- Risk: Design review for the new pricing page is still open | Impact: pricing page cannot ship with v2 | Mitigation / owner: Elena to book review by Oct 15
- Risk: Vendor contract unsigned | Impact: blocks the integration announcement | Mitigation / owner: Priya escalating to legal this week
Open questions
- Question: Do we announce the date change publicly or only to beta teams? | Who will answer: Priya | Needed by: Oct 16
- Question: Is the legacy import path supported after v2? | Who will answer: Sam | Needed by: next sync
Next meeting
Date / time: Tuesday, Oct 21, 10:00
Carried over: Public announcement decision; legacy import support
Notice what the example does not contain: a transcript of the debate about the launch date. The discussion points capture the evidence (beta feedback, ticket volume), the decisions capture the outcome, and everything else is compressed into actions, risks, and questions. That compression is the whole point of the format.
Which sections to use for which meeting
Not every meeting needs all six sections. Use this guide to keep the template fast instead of bureaucratic:
- Weekly team sync / standup: Attendees, discussion points, decisions, action items. Add Risks & blockers whenever anything is stuck — in a standup, that section is often the only one that matters.
- Planning or kickoff meeting: Use everything. Decisions and risks carry the most weight here, because the meeting exists to surface them early.
- 1-on-1: Keep it light — discussion points, action items, open questions. Skip the agenda formality, but never skip owners and dates on actions.
- Client or stakeholder meeting: Decisions, action items, and open questions are essential, because the notes become the shared record both sides refer back to. Note who decided what — "decided by" matters when memories differ later.
- Brainstorm or ideation session: Discussion points become the main section (capture ideas raw, judge later). Decisions may shrink to a shortlist; action items are usually just "prototype X" or "research Y."
Two rules apply to every meeting type:
- Every action item gets an owner and a date. An action without both is a wish. If nobody volunteers, the facilitator assigns it before the meeting ends.
- Decisions and discussion are different sections. Mixing them is how "we talked about moving the launch" gets remembered as "we decided to move the launch."
If writing notes in this format still takes too long, the usual fix is to write less in the discussion section — evidence and outcomes, not narration.
How to turn a meeting recording into action items
To turn a meeting recording into action items, identify what each person actually committed to deliver, record the confirmed owner and deadline, and retain a quote or timestamp for review. Keep suggestions and unresolved assignments separate. Missing information is a question to resolve, not a field for AI to guess.
Separate commitments, suggestions, and decisions
Consider this example conversation:
Alex: “I’ll send the revised proposal on Thursday.” Jordan: “We should ask Finance about the payment terms.” Alex: “Let’s confirm who will do that. We have agreed to keep the current launch date.”
Record the outcomes separately:
- Confirmed action: Send the revised proposal. Owner: Alex. Deadline: Thursday; confirm the calendar date. Evidence: Alex’s commitment.
- Open follow-up: Ask Finance about payment terms. Owner: unconfirmed. Deadline: not stated. Evidence: Jordan’s suggestion and Alex’s request to resolve ownership.
- Decision: Keep the current launch date. Do not add a delivery task unless the discussion also establishes one.
Add a source field to the action list
Use these fields for each candidate action: task, owner, due date, source quote or timestamp, and confirmation status. “Speaker 2” is a transcript label, not proof of a person’s identity. Check the voice before attaching a name, and listen for later revisions before treating the first deadline as final.
Keep unresolved items visible under Open questions. If someone accepts ownership later, update the item with that confirmation. A useful template should distinguish an incomplete assignment from an accepted action.
Use AI for the first draft, then confirm the handoff
CoHear supports phone recording and audio imports on iPhone and Android, then organizes conversations into transcripts, summaries, and action items. Use the generated notes to prepare a first draft, check important names, commitments, and dates against the recording, and ask the team to resolve missing assignments before sharing a final action list.
For the capture and analysis workflow, see how CoHear works. Use the meeting notes template above to keep confirmed actions, decisions, and open questions in separate sections.
How an AI note taker fills this template for you
The structure above is exactly what AI note-taking apps are good at producing, because the template is mostly sorting: who said what, what was decided, who owns the next step. With CoHear, you record the meeting on your iPhone — no bot joins the call, and it works the same in a conference room as on a video call — and the recording is turned into a transcript and an organized summary in about 65 seconds for a one-hour meeting. Sessions can run 4+ hours, so a full planning day fits in one recording.
The honest division of labor: the AI fills the template's first draft — discussion points, candidate decisions, action items with owners — and you spend two minutes checking the decisions and dates before sharing. That review step matters, because a wrong owner or a misheard date in an auto-filled template is worse than a blank one. Treat the AI output as a fast first pass, not the final record.
If you record most of your meetings in person or on the move, see how CoHear works. For the template itself in other situations, we also have a lecture notes template for classes and an interview notes template for research and journalism.
FAQ
What if a meeting action item has no owner or due date?
Mark the missing field as unconfirmed or not stated, and keep the item as an unresolved follow-up until someone accepts the assignment. Do not assign it to the person who suggested it unless the conversation establishes that agreement.
What should a meeting notes template include?
At minimum: the meeting title, date, and attendees; the agenda; key discussion points; a decisions section; action items with an owner and a due date each; risks or blockers; and open questions with someone responsible for answering them. If a template is missing decisions or owners, it will produce notes that nobody can act on.
What is the difference between meeting notes and meeting minutes?
Minutes are a formal record, often required for board or governance meetings, written in a prescribed format and approved at the next meeting. Notes are a working document for the team: less formal, focused on decisions and actions. This template is for notes; if your meeting legally requires minutes, keep the same sections but record motions and votes explicitly.
How do I make sure action items actually get done?
Three things: one owner per item (never a team), a specific due date (never "soon"), and a review of last meeting's items at the start of the next meeting. The template's Carried over field under "Next meeting" exists for exactly that review — anything still open moves forward visibly instead of disappearing.
Can AI fill in a meeting notes template automatically?
Yes — that's the standard workflow of AI note-taking apps. The app records and transcribes the meeting, then sorts the content into summaries, decisions, and action items that map onto the sections above. You should still review decisions, owners, and dates before the notes are shared, since those are the fields where an error costs the most.
All note-taking templates
- Lecture notes template for students
- Interview notes template for research and journalism
- One-on-one meeting notes template
- Standup meeting notes template
- Weekly team meeting notes template
- Sales call notes template
- Client meeting notes template
- Project kickoff meeting notes template
- Retrospective meeting notes template
- Board meeting minutes template
- Seminar and study group notes template
- Training session notes template
- Conference notes template
- Interview scorecard template
- All note-taking templates
