TL;DR: How to take meeting notes template that drive action, not archive. Six templates for six meeting types: standup (3 bullets), 1:1 (rolling doc), decision (DACI), customer call (JTBD), retro (4 quadrants), sprint planning (goal + scope + risks). Match structure to job, generic templates underperform. Apps: Notion (200+ templates, $10/mo), Loop (free with M365), OneNote (free), Atlas (free tier, $20/mo for cited Q&A across meetings). Share within 24h: late-circulated notes lose follow-through as context fades.
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. Free tier covers solo use; Pro is $20/mo. Get started.
At a glance: Six meeting types = six templates. Standup: yesterday/today/blockers. 1:1: rolling doc. Decision: DACI (Driver, Approver, Contributor, Informed). Customer call: JTBD (Job To Be Done). Retro: start/stop/continue/action. Sprint planning: goal/scope/capacity/risks. Notion: 200+ built-in templates. Microsoft Loop: native to Teams. Atlas ($20/mo): cited cross-meeting Q&A. 24-hour share rule: circulate before context fades. Word count bands: standup 30-50w, 1:1 200-400w, customer call 300-600w.
Generic meeting-notes templates fail because meetings are not generic. A standup, a 1:1, and a decision meeting need entirely different structures. Mueller and Oppenheimer 2014 research found longhand structured note-taking outperformed verbatim transcription on conceptual recall, the practical implication: pick a template that forces synthesis, not stenography. This guide gives you the six templates that cover ~90% of business meetings, plus the apps that ship them ready-to-use, and pairs with our broader piece on how to take meeting notes for the underlying frame.
Meeting-notes templates compared
| Template | Sections | Best meeting type | Length |
|---|---|---|---|
| Standup | Yesterday / Today / Blockers | Daily team standup | < 1 page |
| Decision log | Context / Options / Decision / Owner | Steering, architecture review | 1 page |
| Discovery interview | Goals / Workflow / Pain / Quotes | Customer / user research | 2-3 pages |
| Project kickoff | Scope / Stakeholders / Risks / Milestones / Next | Project initiation | 2-3 pages |
| Weekly 1:1 | Wins / Blocks / Asks / Career | Manager-direct one-on-one | 1 page |
Template 1: Standup (Daily/Weekly)
Date: [YYYY-MM-DD]
Attendees: [names]
[Person 1]
- Yesterday: [done]
- Today: [will do]
- Blockers: [if any]
[Person 2]
...
Action items
- [ ] [Action], [owner], [date]
Read in 2 minutes. Action items at the bottom force translation from blocker to assignment. Karpicke and Roediger 2008 retrieval-practice research (80% vs 36% one-week recall) supports the pattern, naming and dating an action triggers the kind of recall that survives a week.
Template 2: 1:1 (Manager + Report)
A rolling document, not per-meeting notes. Top of doc has long-running items; each meeting appends a date-stamped section.
[Direct Report] + [Manager] 1:1
Started: [YYYY-MM-DD]
## Open items (rolling)
- Career goals: [...]
- Current projects: [...]
- Active blockers: [...]
## [YYYY-MM-DD] meeting
What's working
- [...]
What's not
- [...]
Decisions made
- [...]
Action items
- [ ] [Action], [owner], [date]
Rolling beats per-meeting because 1:1s are continuous: you reference last week's blockers; you track career goals across months. Pennebaker 1997 research on expressive writing showed cumulative reflective notes drove emotional and cognitive integration that one-off entries did not.
Template 3: Decision Meeting (DACI)
DACI = Driver, Approver, Contributor, Informed. Atlassian's adapted RACI for software teams. The pattern echoes Cornell Notes (formalized in 1962 by Pauk in How to Study in College), a fixed structure that pays off precisely because it removes per-page decisions.
Decision: [statement of the decision]
Driver: [name, owns the decision process]
Approver: [name, final say]
Contributors: [names, input, not vote]
Informed: [names, notified after]
Context
- [why this decision is needed]
Options considered
1. [Option A], pros/cons
2. [Option B], pros/cons
3. [Option C], pros/cons
Decision: [chosen option, by whom, on date]
Action items
- [ ] [Action], [owner], [date]
The DACI matrix prevents the classic dysfunction where everyone thinks they're the approver.
Template 4: Customer Call (JTBD)
Job To Be Done framework. Best for product discovery, customer success, sales discovery.
Customer: [company + role]
Date: [YYYY-MM-DD]
Recording: [link]
Job to be done
- [the outcome the customer is trying to achieve]
Current solution
- [what they use today + why it falls short]
Pain points
- [specific pains, with quotes]
Success criteria
- [what would "solved" look like]
Quotes (memorable phrasings)
- "..."
Action items
- [ ] [Action], [owner], [date]
The JTBD structure forces problem-first framing instead of feature-request collection.
Template 5: Retro (Start/Stop/Continue + Action)
Sprint/Project: [name]
Date: [YYYY-MM-DD]
Attendees: [names]
Start
- [behaviors to start]
Stop
- [behaviors to stop]
Continue
- [behaviors to continue]
Action
- [ ] [concrete change], [owner], [date]
The fourth quadrant (Action) is what separates retros that change behavior from retros that vent.
Template 6: Sprint Planning
Sprint #[N]: [YYYY-MM-DD] to [YYYY-MM-DD]
Goal: [single sentence]
Scope
- [user story / ticket], [estimate]
- [user story / ticket], [estimate]
- ...
Capacity: [team-days available]
Total estimate: [team-days]
Risks
- [risk + mitigation]
Commitments
- [team commits to: Goal] by [end date]
Goal-first framing keeps the team aligned when scope tradeoffs come up mid-sprint.
Apps That Ship These Templates
Notion ($10/month Plus, free for students per Notion pricing page, May 2026). 200+ built-in templates plus 20,000+ community templates. Best template marketplace.
Microsoft Loop (free with M365 per Microsoft Teams documentation, May 2026). Native to Teams; standup and decision templates ship in-product. For the Teams-specific stack see how to take meeting notes in Teams.
OneNote (free). Notebook templates for project archives. Less polished than Notion but free.
Atlas (free tier, $20/month Pro). Doesn't bundle templates but excels at cross-meeting Q&A: "what action items haven't been closed across our last 6 standups?" with cited transcript passages. The Ahrefs 600K-page AI-content study (2024) reported 86.5% of top-ranked pages now use AI assistance, the cross-meeting use case is where AI grounded in your own notes pays back.
The 24-Hour Share Rule
Notes not circulated within 24 hours lose follow-through as context fades for attendees, and items are less likely to be picked up. The Ebbinghaus forgetting curve (1885) explains the mechanism, recall halves within 24-48 hours without retrieval cues. Set a calendar reminder. The format for the share email or chat:
- 2-3 sentence summary at top
- Decisions made
- Action items with owners and dates
- Open questions
- Link to full notes / transcript / recording
Common Mistakes
Generic template for all meeting types. Match structure to job. Six templates beat one generic, the Microsoft Work Trend Index 2024 survey reported teams with structured templates spent 11 minutes/day less reconciling notes than ad-hoc teams.
Action items without owners or dates. Observations, not commitments. Always assign. For the qualitative side of writing useful notes, see how to take good meeting notes.
Notes longer than the meeting. Compress. A 30-minute meeting does not need 1500 words. Mueller and Oppenheimer 2014 research suggests verbatim transcription hurts recall versus selective synthesis.
Late share. 24-hour rule. Past 48 hours, the meeting may as well not have happened.
When AI Helps Most
The strongest fit for AI is cross-meeting synthesis: closing the loop on action items spanning multiple meetings. Atlas earns its keep here, ask "what's still open from the last 4 customer calls?" with cited transcript passages. For the prompt patterns and tool stack, see our guide on how to use AI to take meeting notes.
Atlas free tier covers individual use; Pro at $20/month adds higher AI usage limits.
Final Take
One template doesn't fit all meetings. Six templates cover ~90% of business meetings: standup, 1:1 (rolling), decision (DACI), customer call (JTBD), retro, sprint planning. Use Notion or Loop for the templates themselves; add Atlas for cross-meeting Q&A with citations. Share within 24 hours. The template is the structure; the action items are the point.
