At a glance: 4-part structure for any meeting. Templates for 1:1s, team standups, sales calls, project meetings. Best AI tools: Granola ($14/mo, local Mac), Otter ($16.99/mo, 300 free min/mo), Fireflies ($10/mo, 50+ integrations), Fathom (free Zoom). Hybrid workflow, manual capture + AI transcription, beats either alone. Standard fields: date, attendees, agenda, decisions, action items (Owner, Action, Deadline), follow-ups. 24-hour cleanup window for action items.
Meeting notes are usually bad. They're too long, full of who-said-what, and missing the only things that matter, decisions and action items. Most professionals spend more time in meetings than on focused work, so getting meeting notes right is genuinely high-use.
This guide covers the 4-part system that works for almost any meeting, templates for the most common meeting types, and the apps that automate the parts you shouldn't be doing manually.
Meeting-notes methods compared
| Method | Capture speed | Structure | Best for | Output |
|---|---|---|---|---|
| DAR (Decisions / Actions / Risks) | Fast | Fixed buckets | Status meetings | Scannable summary |
| Q-notes | Medium | Question + answer | Interviews, 1:1s | Linkable answers |
| [Cornell | Slow | Notes / cues / summary | Long-form discussions | Review-ready](https://ctl.stanford.edu/students/cornell-method-taking-notes) |
| Verbatim + highlights | Fastest with AI | Transcript + tags | Legal, customer calls | Searchable archive |
| Sketch-notes | Variable | Visual map | Workshops, brainstorms | Memorable artifact |
The 4-Part Meeting Note Structure
Almost every meeting note needs four sections.
Attendees and date. Who was there, when. Usually auto-filled by your calendar tool.
Agenda or topics. What you covered, in the order you covered it. Don't recap; just list.
Decisions. What was decided. Use clear, unambiguous language. "Team will use Postgres" is good. "Discussed databases" is useless.
Action items. Owner, Action, Deadline. This is the most important section. If a meeting produces no action items, it probably shouldn't have happened.
Add a 5th section, follow-ups, for open questions or items to revisit next meeting.
For research-focused meetings, add a 6th section: summary, 2-3 sentences capturing the high-level outcome. Useful when you'll reference the meeting weeks or months later.
Templates by Meeting Type
1:1 Meeting
Date: [YYYY-MM-DD]
Attendees: [Manager], [Report]
Topics:
- Career goals
- Current projects
- Blockers
Decisions:
- Will start mentoring junior engineer
Action items:
- [Manager]: Connect Sarah to junior eng team, by Friday
- [Report]: Complete Q3 OKR draft, by next 1:1
Team Standup
Date: [YYYY-MM-DD]
Attendees: [Team]
Updates:
- [Person 1]: Yesterday X. Today Y. Blocker: Z.
- [Person 2]: Yesterday A. Today B. No blockers.
Decisions:
- Pause work on feature C until next sprint
Action items:
- [Person 3]: Unblock Z by EOD
Sales / Client Meeting
Date: [YYYY-MM-DD]
Company: [Client Name]
Attendees: [Names + roles]
Topics covered:
- Discovery questions
- Demo highlights
- Pricing discussion
Pain points raised:
- Current tool doesn't integrate with X
Decisions:
- Next call scheduled for [date]
- Will share pricing PDF + case study
Action items:
- [Sales]: Send pricing PDF, today
- [Sales]: Schedule technical demo, by Friday
- [Client]: Share existing workflow doc, by next call
Project Meeting
Date: [YYYY-MM-DD]
Project: [Name]
Attendees: [Names]
Status:
- Milestone 1 complete
- Milestone 2 in progress, on track
Decisions:
- Move milestone 3 deadline to [date]
- Add [requirement] to scope
Action items:
- [Owner 1]: Update project plan, by Wed
- [Owner 2]: Review new requirement with stakeholder, by Thu
Follow-ups for next meeting:
- Review Q4 budget impact
- Demo of milestone 2 progress
Capture During or Clean Up After?
The strongest workflow is hybrid.
During the meeting. Capture rough notes, keywords, decisions, action items. Don't try to write full sentences.
Within 24 hours. Clean up the notes. Expand keywords into clear sentences. Format action items consistently. Send to attendees.
The biggest mistake is trying to write polished notes during the meeting. You'll either miss content or stop participating in the conversation. Rough during, polished after.
AI Tools for Meeting Notes
AI meeting notes tools handle transcription, summaries, and action item extraction automatically. The 2026 leaders:
- Granola ($14/month), best for individual professionals on Mac. Local-first.
- Otter ($16.99/month, 300 free min/mo), multi-platform.
- Fireflies ($10/month), best for CRM and integrations.
- Fathom (free for Zoom), strongest free Zoom option.
- Notion AI Meeting Notes ($10/month), best for Notion users.
- Tactiq ($12/month, 10 free meetings/mo), Google Meet specialist.
For the full comparison, see best meeting notes app; for the prompt-and-review workflow, see how to use AI to take meeting notes; and for Microsoft Teams specifically, how to take meeting notes in Teams. When you want a structured starting point by meeting type, our meeting-notes templates cover standups, 1:1s, decisions, retros, and more.
Common Meeting Note Mistakes
Recording everything verbatim. Word-for-word notes are useless to read later. Capture decisions and action items, not statements.
No clear owner on action items. "We should do X" with no owner means nobody does X. Always assign.
No deadline on action items. Same problem, without a deadline, it's a wish, not a task.
Notes that nobody reads. If meeting notes never get re-read, you're writing for an audience of zero. Either share them with attendees, file them where you'll review later, or stop writing them.
Different formats every meeting. Pick a template and reuse it. Consistency makes meeting notes searchable across time.
Where Meeting Notes Should Live
The single biggest workflow improvement is picking one place where all meeting notes go.
Options. Notion (most teams), Obsidian (power users), Apple Notes (Apple-only quick capture), OneNote (Microsoft 365 teams).
Anti-pattern. Different meeting tools dropping notes in different places, Otter in one folder, manual notes in Notion, Slack threads from standups. Pick one destination and route everything there.
For research-heavy meetings where notes need to connect to documents and other notes, Atlas builds a mind map across meeting notes, documents, and ideas, useful when meetings are part of a larger thinking process.
Atlas is privacy-first and AI-native, designed so research, briefs, and meeting notes accumulate compounding context across projects rather than dissolving into one-off chats. Every response is a cited answer back to the underlying document, with mind maps from multiple sources available when you need a structural view. $20/mo Pro. Get started.
Action-Item Follow-Through Rates
Action items are the highest-value output of a meeting and the most frequently lost. Across a year of standup and project meetings tracked by several engineering teams, the realistic completion rate for action items by capture style:
| Capture Style | 1-Week Completion | 4-Week Completion |
|---|---|---|
| Verbal only, no written record | ~25% | ~10% |
| Notes with action items, no owner assigned | ~40% | ~20% |
| Notes with owner assigned, no deadline | ~60% | ~35% |
| Owner + deadline + shared with team | ~80% | ~65% |
| Owner + deadline + tracker integration (Linear, Jira) | ~90% | ~80% |
Two patterns stand out. The owner-plus-deadline pair drives most of the lift; either alone is roughly half as effective as both together. Routing action items into a dedicated tracker (Linear, Asana, Jira, GitHub Issues) closes the loop better than leaving them in meeting notes; the meeting notes app rewards re-reading, not status updates.
For teams that take meeting notes in Notion or Obsidian and want action items tracked, the strongest pattern is a Notion database (or Obsidian Dataview query) that aggregates action items across all meetings into a single view, scoped by owner. The week-over-week stale-action-item count becomes a visible health metric.
Notes That Compound Across Meetings
The single biggest difference between meeting notes that pay off and those that don't: do they reference each other?
The compounding pattern. A 1:1 with the same person for 6 months should reference prior 1:1s ("we agreed in March that X; status now is Y"). A weekly project standup should reference the prior week's standup ("blocker from last week resolved Tuesday"). A quarterly review should pull from all 12 weekly standups, not start from scratch.
Tools that make this easy: Obsidian (wikilinks between meeting notes); Notion (database relations between meeting pages); Atlas (AI Q&A across all meeting notes from a project, with citations back to the source meeting).
The compounding becomes visible at roughly 25-50 meetings tracked. Below that, each meeting note is isolated; above it, the cross-references make pattern-finding trivial. Quarterly reviews stop being a re-discovery exercise and start being a confirmation of patterns the notes already surfaced.
Real-World Meeting Type Adaptations
The 4-part structure (attendees, topics, decisions, action items) is the universal scaffold. Different meeting types reward different emphasis.
Standups (15 minutes daily). Skip topics; capture only blockers and action items. Most teams over-document standups, which trains the team to tune them out. A standup note should be readable in 30 seconds. Fits in Notion, Slack, or Linear; Obsidian and OneNote are overkill for the cadence.
1:1s (30-60 minutes weekly). Heavy on personal context, light on decisions. The action items are usually for the manager (unblock a thing, share an article, intro to a contact); the value compounds across months. Run 1:1 notes in a single rolling document per person, not a new file each week, so prior context is one scroll away.
Sales discovery calls (30-60 minutes). Heavy on questions asked and pain points raised, lighter on decisions. The next-step is often the only meaningful action item. Standardize the question template across calls so reps can compare prospects later.
Project reviews (60-90 minutes weekly or biweekly). Heavy on status updates and decisions, light on raw discussion. Capture the decision and one-line rationale; skip the deliberation. The decision log becomes the project's institutional memory once people rotate off.
All-hands (60 minutes monthly or quarterly). Heavy on announcements and Q&A, light on action items (most are the leadership team's). Capture the announcements verbatim because slack threads about them will reference them; capture the Q&A as paraphrased one-liners.
Customer feedback calls (30-45 minutes). Heavy on quotes (verbatim where possible), light on internal interpretation. The customer's exact words drive product decisions; your summary loses signal. Tag each note with feature areas so PM can pull patterns later.
The pattern: under-document low-stakes recurring meetings (standups, 1:1s) and over-document high-stakes one-time meetings (customer calls, project decisions). The temptation is the inverse, which is why most teams have hundreds of dead standup notes and missing notes from the meeting that decided the company's roadmap.
Final Take
Good meeting notes follow a 4-part structure: attendees, topics, decisions, action items. AI tools handle transcription so you can focus on the conversation. Hybrid, rough manual capture plus AI transcript, is strongest. Pick one template, one app, and one destination. The compounding starts when meeting notes from six months ago are still findable and useful.
