1-on-1 meeting notes: should the manager or the employee write them?

Best practice is for the employee to own the 1-on-1 agenda and notes, which signals the meeting exists for their benefit. The manager can add comments or corrections before the doc is finalised.

15 Best Meeting Notes Templates for 2026 (Free & Copyable)

TL;DR: This page gives you the 15 best meeting notes templates for 2026, ready to copy and paste — covering standups, 1-on-1s, client calls, retrospectives, board meetings, and more. Each template is a plain-text block you can drop straight into Notion, Google Docs, Confluence, or anywhere else.

Well-structured meeting notes are the difference between productive meetings that drive action and wasteful discussions that leave everyone confused. Research shows that teams with standardised meeting documentation see 35% higher action-item completion rates and spend 60% less time clarifying "what was decided."

This guide collects the best meeting notes templates for 2026 in one place. Every template below is self-contained and copy-pasteable — no sign-up, no paywall. Scroll to the type of meeting you need, copy the block, and paste it straight into your tool of choice.

Why the Best Meeting Notes Templates Save Hours Each Week

According to Atlassian's research on meeting effectiveness, standardised templates ensure you never miss critical information:

Consistency across teams: Everyone documents meetings the same way, so notes are instantly scannable by anyone.
Faster note-taking: A pre-defined structure eliminates the "what should I write?" hesitation.
Better follow-through: Action items with owners and due dates are far more likely to get done.
Institutional memory: A searchable archive of every decision prevents repeated debates.
Less meeting fatigue: When people trust that notes will capture the key points, they stop anxiously scribbling and actually engage.

2026 trend: High-performing teams now use AI meeting assistants to handle transcription and first-draft notes automatically. Scroll to the Automation & AI section below to see how — or keep reading for the templates first.

Template 1: Standard Team Meeting Notes

Use for: Weekly team syncs, project updates, general status meetings. This is the free meeting notes template most teams reach for first — it covers every base without being bureaucratic.

MEETING NOTES — [Team / Project Name]
Date:        [YYYY-MM-DD]
Time:        [HH:MM – HH:MM] [Timezone]
Location:    [Zoom / Google Meet / Room name]
Facilitator: [Name]
Note-taker:  [Name]
Attendees:   [Name], [Name], [Name]
Absent:      [Name]

AGENDA & DISCUSSION
──────────────────
1. [Topic]
   Discussion: [Key points raised]
   Decision:   [What was agreed]
   Owner:      [Who is responsible]

2. [Topic]
   Discussion: [Key points raised]
   Decision:   [What was agreed]
   Owner:      [Who is responsible]

ACTION ITEMS
────────────
[ ] [Name] — [Action] — Due: [Date]
[ ] [Name] — [Action] — Due: [Date]

OPEN QUESTIONS / PARKING LOT
─────────────────────────────
- [Unresolved item — follow up by [Date]]

NEXT MEETING
────────────
Date: [Date]  |  Time: [HH:MM]  |  Agenda preview: [Topics]

Template 2: Agile Daily Standup Notes

Use for: Daily scrum, kanban standups, or any quick team sync (15 minutes or less). A standup notes template should be fast to fill in — this one adds just enough structure to catch blockers without creating overhead.

STANDUP NOTES — [Team Name]
Date: [YYYY-MM-DD]
Duration: [X] min

[Name]
  Yesterday: [What was completed]
  Today:     [What is planned]
  Blockers:  [Any impediments — or "None"]

[Name]
  Yesterday: [What was completed]
  Today:     [What is planned]
  Blockers:  [Any impediments — or "None"]

[Name]
  Yesterday: [What was completed]
  Today:     [What is planned]
  Blockers:  [Any impediments — or "None"]

PARKING LOT (discuss after standup)
────────────────────────────────────
- [Topic] — involving [Names]

Template 3: Sprint Planning Meeting Notes

Use for: Agile sprint kickoffs, iteration planning, PI planning. Capture goals, backlog commitments, and capacity in one place.

SPRINT PLANNING — Sprint [#]
Date:      [YYYY-MM-DD]
Team:      [Team name]
Duration:  [X] weeks  |  Start: [Date]  |  End: [Date]

SPRINT GOAL
───────────
[One sentence describing the primary objective]

SPRINT BACKLOG
──────────────
Story ID | Description                    | Assignee | Points | Notes
---------|-------------------------------|----------|--------|------
[ID]     | [Feature / task description]  | [Name]   | [#]    | [—]
[ID]     | [Feature / task description]  | [Name]   | [#]    | [—]

CAPACITY
────────
Total story points committed: [#]
Team capacity (person-days):  [#]
Buffer / margin:               [#]%

DEPENDENCIES & RISKS
─────────────────────
- [External dependency or risk — mitigation: [plan]]

DEFINITION OF DONE
───────────────────
- [ ] Code reviewed and merged
- [ ] Tests passing (unit + integration)
- [ ] Deployed to staging
- [ ] Product owner accepted

Template 4: 1-on-1 Meeting Notes Template

Use for: Manager / direct-report check-ins, skip-level conversations, mentoring sessions. A good 1-on-1 meeting notes template puts the employee's voice first and ensures development conversations don't get lost.

1-ON-1 MEETING NOTES
Date:      [YYYY-MM-DD]
Manager:   [Name]
Employee:  [Name]
Cadence:   [Weekly / Bi-weekly / Monthly]

EMPLOYEE AGENDA ITEMS
──────────────────────
- [Topic the employee wants to discuss]
- [Topic the employee wants to discuss]

UPDATES FROM EMPLOYEE
──────────────────────
Wins / accomplishments:
  - [Achievement since last 1-on-1]
  - [Achievement]

Current challenges / blockers:
  - [Challenge — what support is needed?]

Priorities for next period:
  - [Top 1-3 priorities]

DEVELOPMENT & GROWTH
─────────────────────
Skills to develop:    [What the employee wants to learn]
Career direction:     [Longer-term aspirations]
Support needed:       [How manager can help]
Learning resources:   [Courses, books, stretch projects]

MANAGER FEEDBACK
─────────────────
[Specific, actionable feedback on recent work]

ACTION ITEMS
────────────
[ ] [Manager] — [Action] — Due: [Date]
[ ] [Employee] — [Action] — Due: [Date]

CARRY-FORWARD TOPICS
─────────────────────
- [Item to revisit next time]

Template 5: Client Meeting Notes

Use for: External client calls, discovery sessions, sales meetings, consulting check-ins. Client notes need to be professional enough to share externally if required.

CLIENT MEETING NOTES
Client:      [Company name]
Date:        [YYYY-MM-DD]
Time:        [HH:MM – HH:MM] [Timezone]
Internal attendees: [Name (Role)], [Name (Role)]
Client attendees:   [Name (Title)], [Name (Title)]
Meeting type: [Kickoff / Status update / Issue resolution / Discovery]

MEETING PURPOSE
───────────────
[Brief statement of why you met]

CLIENT NEEDS & REQUIREMENTS
─────────────────────────────
- [Pain point or goal the client expressed]
- [Requirement or constraint mentioned]
- [Timeline or budget expectation]

PROPOSED SOLUTION / OUR RESPONSE
──────────────────────────────────
[Our recommendations, deliverables, or proposed approach]

CLIENT FEEDBACK
───────────────
Positives:  [What they approved or liked]
Concerns:   [Questions or objections raised]
Decision:   [Approved / Pending / Rejected — details]

RISKS & DEPENDENCIES
─────────────────────
- [Any open risk or dependency that could affect delivery]

NEXT STEPS
──────────
[ ] [Internal owner] — [Action] — Due: [Date]
[ ] [Client contact] — [Action] — Due: [Date]

FOLLOW-UP MEETING
─────────────────
Date: [Date]  |  Time: [HH:MM]  |  Agenda: [Preview]

Templates 6–15: Full Copy-Paste Blocks for Every Scenario

The templates below are fully expanded so you can copy and adapt them without needing to fill in structural questions — just replace the bracketed placeholders.

Template 6: Brainstorming Session

BRAINSTORMING SESSION NOTES
Date:        [YYYY-MM-DD]
Facilitator: [Name]
Topic:       [Problem statement]

PROBLEM STATEMENT
─────────────────
[Clear articulation of what we are trying to solve or decide]

IDEAS GENERATED (no filtering during session)
─────────────────────────────────────────────
- [Idea — contributor: Name]
- [Idea — contributor: Name]
- [Idea — contributor: Name]
- [Add as many as needed]

DOT VOTING RESULTS
───────────────────
1. [Idea] — [# votes]
2. [Idea] — [# votes]
3. [Idea] — [# votes]

TOP IDEAS TO PURSUE
────────────────────
- [Selected idea 1] — rationale: [Why chosen]
- [Selected idea 2] — rationale: [Why chosen]

ACTION ITEMS
────────────
[ ] [Name] — research / prototype [idea] — Due: [Date]

Template 7: Decision-Making Meeting

DECISION-MAKING MEETING NOTES
Date:      [YYYY-MM-DD]
Decision:  [Clear yes/no or A/B/C question]
Decider:   [Name — who has final authority]

OPTIONS CONSIDERED
───────────────────
Option A: [Name]
  Pros: [+]
  Cons: [−]
  Estimated cost / effort: [—]

Option B: [Name]
  Pros: [+]
  Cons: [−]
  Estimated cost / effort: [—]

DECISION
────────
Chosen option: [A / B / C]
Rationale:     [Why this option was selected]
Trade-offs accepted: [What we are giving up]
Reversible?    [Yes / No — if no, explain]

IMPLEMENTATION
──────────────
[ ] [Owner] — [First step] — Due: [Date]
[ ] [Owner] — [Next step]  — Due: [Date]

ESCALATION PATH
───────────────
If implementation hits a blocker, escalate to: [Name] by [Date]

Template 8: Sprint Retrospective

RETROSPECTIVE NOTES — Sprint [#]
Date:  [YYYY-MM-DD]
Team:  [Team name]
Facilitator: [Name]

WHAT WENT WELL
───────────────
- [Success] — suggested by: [Name]
- [Success]

WHAT DIDN'T GO WELL
────────────────────
- [Problem] — impact: [Why it mattered]
- [Problem]

ROOT CAUSES
───────────
- [Problem] → root cause: [Why it happened]

ACTION ITEMS (process improvements)
─────────────────────────────────────
[ ] [Owner] — [Improvement] — Due: [Date / Next sprint]

SHOUT-OUTS
──────────
- [Person]: [What they did that deserves recognition]

TEAM HEALTH (1–5)
──────────────────
Collaboration: [#]  |  Quality: [#]  |  Pace: [#]  |  Fun: [#]

Template 9: Board Meeting Minutes

BOARD MEETING MINUTES — [Company Name]
Date:      [YYYY-MM-DD]
Location:  [Address / Virtual link]
Chair:     [Name]
Secretary: [Name]

ATTENDANCE
──────────
Present (quorum): [Name (Role)], [Name (Role)]
Absent with notice: [Name]
Guests: [Name (Organisation)]

CALL TO ORDER
─────────────
Meeting called to order at [HH:MM] by [Chair name].
Quorum confirmed: [Yes / No — [#] of [#] members present].

APPROVAL OF PREVIOUS MINUTES
──────────────────────────────
Minutes of [previous date] meeting reviewed.
Motion to approve: [Name]  |  Seconded: [Name]  |  Vote: [Passed / Failed]

REPORTS
───────
CEO Report:   [Key highlights]
CFO Report:   [Financial summary — revenue, burn, runway]
Committee updates: [Name] committee: [Summary]

RESOLUTIONS
───────────
Resolution [#]: [Text of resolution]
  Motion: [Name]  |  Seconded: [Name]
  Vote: For [#]  |  Against [#]  |  Abstain [#]  |  Result: [Passed / Failed]

EXECUTIVE SESSION
─────────────────
[Entered at HH:MM — exited at HH:MM — summary of matters discussed]

NEXT MEETING
────────────
Date: [Date]  |  Location: [—]

Meeting adjourned at [HH:MM].

Template 10: Product Roadmap Review

PRODUCT ROADMAP REVIEW
Date:     [YYYY-MM-DD]
Quarter:  [Q# YYYY]
PM Lead:  [Name]
Attendees: [Name], [Name]

FEATURES SHIPPED THIS PERIOD
──────────────────────────────
- [Feature] — impact: [Metric or user feedback]
- [Feature]

IN PROGRESS
───────────
- [Feature] — status: [% done / on track / at risk] — ETA: [Date]

UPCOMING (next quarter)
───────────────────────
Priority | Feature           | Target date | Owner
---------|-------------------|-------------|------
High     | [Feature]         | [Date]      | [Name]
Medium   | [Feature]         | [Date]      | [Name]

STAKEHOLDER FEEDBACK
─────────────────────
- [Feedback from whom] — implications: [What we will / won't change]

ROADMAP CHANGES
───────────────
Added:   [Feature — reason]
Removed: [Feature — reason]
Deferred: [Feature — new target: Date]

Template 11: Incident Post-Mortem

INCIDENT POST-MORTEM
Incident ID:  [INC-####]
Date of incident: [YYYY-MM-DD]
Post-mortem date: [YYYY-MM-DD]
Severity:     [P1 / P2 / P3]
Facilitator:  [Name]

SUMMARY
───────
[2–3 sentences describing what happened and the user impact]

TIMELINE (all times in [Timezone])
───────────────────────────────────
[HH:MM] — [Event: alert fired / engineer paged / etc.]
[HH:MM] — [Event]
[HH:MM] — Incident resolved

IMPACT
──────
Users affected:    [#] or [%]
Duration:          [# hours # minutes]
Revenue / SLA hit: [—]

ROOT CAUSE
──────────
[Technical or process explanation of why this happened]

CONTRIBUTING FACTORS
─────────────────────
- [Factor 1]
- [Factor 2]

WHAT WENT WELL
───────────────
- [Response step that worked]

ACTION ITEMS (prevention)
──────────────────────────
[ ] [Owner] — [Fix / process change] — Due: [Date] — Priority: [High/Med/Low]

Template 12: Training Session Notes

TRAINING SESSION NOTES
Topic:       [Subject]
Date:        [YYYY-MM-DD]
Trainer:     [Name / Vendor]
Attendees:   [Names]
Duration:    [# hours]

AGENDA COVERED
───────────────
1. [Module / topic]
2. [Module / topic]
3. [Module / topic]

KEY TAKEAWAYS
─────────────
- [Main learning point]
- [Main learning point]
- [Main learning point]

RESOURCES
─────────
- [Link to slides / recording / documentation]
- [Recommended reading]

Q&A LOG
───────
Q: [Question asked] — A: [Answer given]
Q: [Question asked] — A: [Answer given]

FOLLOW-UP ACTIONS
─────────────────
[ ] [Name] — complete [practice exercise / certification] — Due: [Date]

Template 13: Interview Debrief

INTERVIEW DEBRIEF
Candidate:  [Name]
Role:       [Job title]
Interview date: [YYYY-MM-DD]
Debrief date:   [YYYY-MM-DD]
Interviewers: [Name (Panel)], [Name (Technical)]

SCORECARDS (1–5, 5 = exceptional)
───────────────────────────────────
Interviewer | Criterion            | Score | Notes
------------|----------------------|-------|------
[Name]      | Problem solving      | [#]   | [—]
[Name]      | Communication        | [#]   | [—]
[Name]      | Technical depth      | [#]   | [—]
[Name]      | Culture / values fit | [#]   | [—]

STRENGTHS
─────────
- [Specific strength with example from interview]
- [Strength]

CONCERNS / GAPS
───────────────
- [Concern — is it a blocker?]

RECOMMENDATION
──────────────
[ ] Hire — move to offer  [ ] No hire  [ ] Advance to next round
Decision: [Choice]
Rationale: [Key reasoning]

NEXT STEPS
──────────
[ ] [Recruiter] — [Action] — Due: [Date]

Template 14: Quarterly Business Review (QBR)

QUARTERLY BUSINESS REVIEW (QBR)
Quarter:   [Q# YYYY]
Date:      [YYYY-MM-DD]
Presenter: [Name]
Audience:  [Leadership / Board / Customer]

PERFORMANCE vs. TARGETS
─────────────────────────
Metric          | Target | Actual | Delta | Status
----------------|--------|--------|-------|-------
[KPI name]      | [—]    | [—]    | [±%]  | [On track / At risk / Missed]
[KPI name]      | [—]    | [—]    | [±%]  | [—]

WINS THIS QUARTER
──────────────────
- [Achievement — quantified where possible]
- [Achievement]

CHALLENGES
──────────
- [Challenge — root cause — what we did / are doing]

CUSTOMER HIGHLIGHTS
────────────────────
- [Logo or use case worth highlighting]

GOALS FOR NEXT QUARTER
───────────────────────
Priority | Goal                | Owner  | Metric
---------|---------------------|--------|-------
1        | [Goal]              | [Name] | [KPI]

RESOURCE REQUESTS
─────────────────
- [Budget / headcount / tooling need — justification]

Template 15: Crisis Management Meeting

CRISIS MANAGEMENT MEETING NOTES
Crisis:    [Name / description]
Date:      [YYYY-MM-DD]
Time:      [HH:MM]
Incident Commander: [Name]
Attendees: [Name (Role)], [Name (Role)]

SITUATION STATUS
────────────────
Severity:          [Critical / High / Medium]
Current status:    [Active / Contained / Resolving]
Affected parties:  [Customers / Employees / Public / Regulators]
Estimated impact:  [# users / $value / reputational risk]

IMMEDIATE ACTIONS TAKEN
────────────────────────
[HH:MM] — [Action taken — by whom]
[HH:MM] — [Action taken]

OPEN ACTIONS
────────────
[ ] [Owner] — [Urgent action] — Due: [HH:MM today]
[ ] [Owner] — [Next action]   — Due: [Date]

COMMUNICATION PLAN
───────────────────
Internal:  [Message — channel — by whom — by when]
External:  [Customer / press statement — approved by — ETA]
Regulators: [Required notification — deadline]

NEXT CHECK-IN
─────────────
Time: [HH:MM]  |  Participants: [Names]  |  Decision gate: [What we will decide]

Best Practices for Effective Meeting Notes in 2026

Before the Meeting

Send the template in advance: Let participants know which sections they will need to contribute to.
Assign the note-taker ahead of time: Surprise assignments produce thin notes.
Pre-populate the agenda items: Filling in the topic headings before the meeting starts saves setup time.

During the Meeting

Capture decisions, not discussions: Record what was decided, not every word said.
Use bullet points: Easier to scan than paragraphs when someone missed the meeting.
Name every action item: "Team will follow up" is not an action item — "[Name] will do X by [Date]" is.
Flag open questions inline: Mark unresolved items with a "?" or "OPEN" tag so they are visible in the final doc.
Note timestamps for key moments: Useful when linking to a video recording.

After the Meeting

Share within 2 hours: Memory fades fast and follow-up momentum dies with it.
Use a consistent file naming convention: "YYYY-MM-DD Team Meeting Notes" sorts chronologically in any tool.
Store notes centrally: Notion, Confluence, Google Drive — the tool matters less than the consistency.
Create tasks from action items: Copy them into your project tracker (Asana, Jira, Linear) so they show up in people's work queues.
Link the recording: Attach the Zoom or Meet link so readers can verify context.

How to Take Meeting Notes Automatically with AI (2026)

Manual note-taking forces someone to split attention between participating and typing. In 2026, AI meeting assistants handle the entire documentation layer automatically — generating structured notes that already match the templates above.

How AI Meeting Note-Taking Works

The AI bot joins or receives the recording — it connects to Zoom, Google Meet, Teams, or Webex automatically.
Real-time transcription with speaker labels — every word is captured and attributed to the right person.
AI generates a structured summary — the output maps onto sections like Agenda, Decisions, and Action Items.
Action items are extracted automatically — the AI identifies "who committed to what by when" from natural speech.
Notes are shared within minutes of the meeting ending — no 30-minute post-meeting formatting session.

Time savings: AI documentation reduces note-taking effort by 60–80%, and because you're not splitting attention, the discussion itself is usually sharper. Noteo.ai's free tier covers 300 minutes per month — enough for most teams to eliminate manual notes entirely.

Noteo.ai auto-joins your Zoom, Teams, Google Meet, and Webex calls, transcribes them with 95%+ accuracy, and generates AI summaries structured around your preferred template. It's GDPR-compliant and EU-hosted. If you want to see what automatically generated notes look like in practice, the Zoom transcription guide walks through a real example.

Ready to Stop Taking Manual Meeting Notes?

The templates above cover every meeting type — but even the best free meeting notes template still requires someone to sit there and type. Noteo.ai automates the entire process: join the call, record, transcribe, summarise, and extract action items — all without a dedicated note-taker.

Auto-joins Zoom, Teams, Google Meet, and Webex — no manual recording setup.
95%+ transcription accuracy with speaker identification.
AI-structured summaries matching the sections in the templates above.
Automatic action item extraction — "who will do what by when" pulled straight from the conversation.
Free tier: 300 minutes / month — no credit card required to start.

View pricing and start free — or read how other teams use it in the Zoom transcription guide.

Frequently Asked Questions

What should meeting notes include?

Effective meeting notes should always include: the date, time, and attendees; the agenda items discussed; the key decisions made (with the rationale); action items with a named owner and due date; and any open questions that need follow-up. Optional extras include a link to a recording, vote counts (for formal meetings), and a parking lot for topics deferred to later.

What is the best free meeting notes template?

The best free meeting notes template depends on the meeting type. For general weekly team meetings, Template 1 (Standard Team Meeting Notes) above covers the essentials. For manager check-ins, use Template 4 (1-on-1). For agile teams, Template 2 (Daily Standup) or Template 3 (Sprint Planning) fit best. All 15 templates on this page are free and require no sign-up — copy the plain-text block and paste it into any document tool.

How do I take meeting notes automatically?

AI meeting assistants like Noteo.ai automate the entire process. You invite the bot to your Zoom, Teams, Google Meet, or Webex call (or upload a recording), and the AI transcribes the conversation with speaker labels, then generates a structured summary with decisions and action items. Notes are ready within minutes of the meeting ending. Most tools offer a free tier so you can test the output quality before committing.

How long should meeting notes be?

Meeting notes should be as short as they can be while still capturing every decision and action item. A 30-minute team standup might produce 10 lines of notes; a 2-hour QBR might run to two pages. The test: could someone who missed the meeting read the notes and know exactly what was decided and what they need to do? If yes, the notes are the right length.

Should meeting notes be shared with everyone who was invited, or only attendees?

Share notes with everyone who was invited, including those who could not attend. Absent team members often need to know about decisions that affect them, and sharing broadly prevents the "I didn't know about that" problem. For client meetings, share an edited version externally if the notes contain sensitive internal context.

1-on-1 meeting notes: should the manager or employee write them?

Best practice is for the employee to own the 1-on-1 agenda and notes. This signals that the meeting exists for their benefit, not as a reporting mechanism. The manager can add comments or corrections before the doc is finalised. If your organisation uses an AI meeting assistant, both parties can review the auto-generated transcript rather than relying on one person's interpretation.

Sources & References

Fellow.ai: 5 Professional Meeting Minutes Examples & Templates - Free templates and best practices for meeting documentation
Atlassian: Free Meeting Notes Template - Confluence-based templates and research on meeting effectiveness
Sembly AI: 8 Meeting Minutes Templates & Examples for 2026 - Templates with AI automation tips
Reclaim: 10 Meeting Minutes Templates (Free Docs) - Downloadable Google Docs templates for various meeting types
Harvard Business Review: You're Holding Too Many Meetings - Research on meeting frequency and documentation effectiveness