5 Notion Meeting Note Templates by Scene (Copy & Paste) + AI Auto-Fill Guide

Notion meeting notes templateNotion 1on1 templateNotion AI Meeting Notesmeeting notes automationNotion meeting database
5 Notion Meeting Note Templates by Scene (Copy & Paste) + AI Auto-Fill Guide

Are you still rebuilding the meeting note format from scratch every time — once for 1-on-1s, again for team standups, again for sales calls?

The more disciplined you are about keeping meeting notes in Notion, the more your templates drift. The 1-on-1 page has tidy headings. The sales note is just a stream of bullets. Only the kickoff is unusually long. Six months later you can't even search through them.

This article gives you five copy-and-paste Notion meeting note templates — one for each scene — plus the database property design that holds them together, plus a realistic path to AI auto-fill for people who can't use Notion AI Meeting Notes. It's especially for those of you who heard "just use Notion AI" from a coworker and then bounced off the Business plan requirement.

Why Notion Meeting Templates Should Be Scene-Specific

Let's start with why a single one-size-fits-all template breaks down.

One template can't cover every scene cleanly

A 1-on-1 and a customer sales meeting need completely different properties and a completely different body weight.

  • 1-on-1: Two-person conversation. You need "follow-up from last time," "what's been hard," and "career talk" — not a generic agenda
  • Sales call: "Customer name," "deal status," "decision process," "key stakeholders" matter most. The body is mostly "their concerns" and "what we send next"
  • Standup: Needs "agenda tag" and "note taker." Decisions and ToDos are the point
  • Kickoff: Written once, but needs structured "success criteria," "milestones," "risks"
  • Retrospective: Fixed Keep / Problem / Try frame

In other words, jamming everything into one universal template gives you one that's "a little short" for every scene.

But one database is enough — switch by template button

This is the single most important idea in this article. Keep one meeting notes database, and create five template buttons inside it.

That way you get all three of the following at once:

  • Search stays clean because everything is in one DB
  • Type tags (1-on-1, standup, sales call, etc.) let you filter into per-scene views
  • Creating a new page is one click to pick the right template

The "meeting notes templates" you find on Notion's public marketplace almost never split into multiple databases either.

5 Copy-and-Paste Notion Meeting Templates

Here's the main payload. Paste each code block below into a new page of your meeting notes DB. Notion parses Markdown, so ## and - become headings and bullets automatically.

① 1-on-1 Template (Manager × Direct Report)

For weekly or biweekly 1-on-1s. This reflects the 60% direct report / 40% manager split widely recommended by Lattice and Asana, so the report writes first. The ideal flow: the direct report fills in their section 24 hours before the meeting, the manager adds notes before the call.
## 1. From the Direct Report (fill in 24h before)
### This Week's Focus / Priorities
-

### Where I'm Stuck / Where I Need Help
-

### Topics I Want to Discuss
-

### Questions for My Manager
-

## 2. Follow-up from Last Time
- Previous action item:
  - Status: ✅ Done / 🟡 In progress / 🔴 Not started
-

## 3. Two-Way Feedback
### Direct Report → Manager
- Recent support that helped:
- Support I'd like more of:

### Manager → Direct Report
- Observation (specific fact):
- Impact (what it led to):
- Suggestion (what to try next):

## 4. Career & Growth (deep-dive monthly or quarterly)
- Progress on this quarter's goals:
- Skill I want to learn / type of work I want to try:
- Mid- to long-term career direction:

## 5. Next Actions
- [ ] (Owner: Direct report / Due: / Check-in: next 1-on-1)
- [ ] (Owner: Manager / Due: / Check-in: next 1-on-1)
Recommended properties: Date / Counterpart (People) / Status (Draft / Confirmed) / Follow-up needed (Checkbox) / Quarterly career discussion (Checkbox)

② Team Standup Template (Weekly)

This applies the classic standup pattern (Yesterday / Today / Blockers) to a weekly cadence, while explicitly separating status updates from discussion. Mixing the two is what makes weekly meetings drag, so split them. Setting a timebox at the top keeps things tight.
## Meeting Info
- ⏱️ Timebox: 5 min status / 20 min discussion / 5 min action review

## Status Updates (≤2 min per person)
### Member A
- ✅ Done last week:
- 📅 Doing this week:
- 🚧 Blockers / Need help with:

### Member B
- ✅ Done last week:
- 📅 Doing this week:
- 🚧 Blockers / Need help with:

## Discussion Points (prioritized)
1. **Topic 1**:
   - Summary:
   - **Decision**:
   - If undecided, reason for parking:

2. **Topic 2**:
   - ...

## ToDos (action items raised in this meeting)
- [ ] (Owner: / Due: / Where to confirm: next standup)
- [ ] (Owner: / Due: / Where to confirm: Slack #channel)

## Carried Over to Next Week
-
Recommended properties: Date / Attendees (People) / Agenda tags (Multi-select) / Note taker (Person) / Timebox held (Checkbox)

③ Sales / Customer Meeting Template (MEDDIC)

This template bakes the MEDDIC qualification framework — used heavily in B2B SaaS sales — directly into your meeting notes. The six axes (Metrics / Economic Buyer / Decision Criteria / Decision Process / Identify Pain / Champion) get filled in incrementally across multiple calls, and forecast accuracy and close rates rise once you have the discipline.
## Customer Info
- **Account name / department**:
- **Their attendees**:
- **Our attendees**:
- **Deal stage**: First call / Proposal / Closing

## Identify Pain
- Surfaced pain points:
  - e.g., 20 hours/month spent on monthly reporting / X deals lost per month
- Latent pain points (visible but not articulated by them):
- Past attempts and why they didn't work:
  - What tools/processes they tried, and why it didn't stick

## Metrics
- Cost / time the customer loses today on this problem:
  - e.g., $X/month in labor / X opportunities lost per month
- Expected outcome (numerical) if solved:
- Estimated ROI of our product:
  - e.g., $X implementation cost vs. $X/month savings → payback in X months

## Economic Buyer
- Name / title:
- Direct access? Yes / No (if no, who connects?)
- Their area of focus:
  - e.g., cost reduction vs. revenue growth

## Decision Criteria
- Must-have requirements:
- Evaluation axes (features / price / implementation effort / support):
  - Top 3 by priority:
- Competitors being compared:

## Decision Process
- Approval steps:
  - e.g., Rep → manager approval → director sign-off → legal review → contract
- Estimated timeline:
- Anticipated blockers (legal / security / budget):

## Champion
- Name / title:
- Why they're championing us:
  - e.g., tied to their personal KPI / prior experience with a similar tool
- Internal-selling assets to hand them:
  - e.g., ROI sheet / case study / pre-filled security questionnaire

## Customer Feedback / Concerns
- Positive reactions:
- Concerns / objections:
- Items they took back to consider:

## Next Actions
### On our side
- [ ] (Owner: / Due: / Purpose: )

### On their side
- [ ] (Ask: / Due: / Reminder set: )
Recommended properties: Account name (Relation: Accounts DB) / Deal status (Select: First call / Proposal / Closing / Won / Lost) / Attendees / Next action due date (Date) / Forecast confidence (Select: A/B/C)
💡 For something simpler, drop down to BANT (Budget / Authority / Need / Timeline). MEDDIC is enterprise-grade, BANT is better for SMB deals — pick to match the deal size.

④ Project Kickoff Template (Project Charter + RACI)

You only write this once per project, but you'll keep coming back to it. This is a Project Charter structure with RACI, Definition of Done, and a Communication Plan added — enough rigor that "what did we agree at kickoff?" is fully answered months later.
## Project Overview
- **Project name**:
- **Project owner**:
- **Sponsor / requester**:
- **Kickoff date**:
- **Target end date**:

## Business Context & Purpose
- Why now:
- Problem being solved:
- Expected business impact:

## Scope
### In Scope
-

### Out of Scope (separate project or won't do)
-

## Success Criteria (KPIs)
- Primary KPI:
- Secondary KPI:
- Measurement timing:

## Definition of Done
- [ ]
- [ ]
- [ ]

## RACI Matrix
| Task / Area | R (Responsible) | A (Accountable) | C (Consulted) | I (Informed) |
|-------------|-----------------|-----------------|---------------|--------------|
| Design      |                 |                 |               |              |
| Development |                 |                 |               |              |
| QA / Testing|                 |                 |               |              |
| Release     |                 |                 |               |              |

## Milestones
- [ ] (Date: / Owner: / Deliverable: )
- [ ] (Date: / Owner: / Deliverable: )

## Assumptions & Constraints
### Assumptions (if these break, replan)
-

### Constraints (immovable limits)
-

## Risks & Mitigations
| Risk | Probability | Impact | Mitigation | Owner |
|------|-------------|--------|------------|-------|
|      |             |        |            |       |

## Communication Plan
- Standing meetings: cadence / attendees / format
- Status updates: channel / frequency / owner
- Escalation path:

## Budget & Resources (optional)
- Total budget:
- Breakdown (labor / external / tools):
- Resource allocation (FTE equivalent):

## Stakeholders
| Name | Role | Area of Interest | Contact Frequency |
|------|------|------------------|-------------------|
|      |      |                  |                   |

## Approval / Sign-Off
| Role | Name | Date | Status |
|------|------|------|--------|
| Project Sponsor |  |  | Pending / Approved |
| Product Owner |  |  | Pending / Approved |
| Engineering Lead |  |  | Pending / Approved |

## Post-Kickoff Next Actions
- [ ] (Owner: / Due: )
💡 Notion's own Project Charter guide treats this as a living document — updated at each major milestone, not a static kickoff artifact. Set a reminder to revisit it at the end of each major phase.
Recommended properties: Project name (Relation: Projects DB) / Owner (Person) / Stakeholders / Date / Project status (Select: Planning / In progress / Done / Frozen)

⑤ Retrospective Template

The frame you use changes the insights you get. Pick one of three depending on the team's situation.

FrameWhen it fits
KPT (Keep / Problem / Try)Default. Pick this when in doubt. Easy to run with a team new to retros
4Ls (Liked / Learned / Lacked / Longed for)When you want to surface learning. End-of-project retros
Start / Stop / ContinueWhen you want behavior change. Good for stuck teams

KPT Template (default)

## Period Covered
-

## Keep (what we want to keep doing)
-

## Problem (what's not working)
-

## Try (what we'll do next)
- [ ] (Owner: / Due: / How we'll measure: )
- [ ] (Owner: / Due: / How we'll measure: )

## Next Retro Date
-

4Ls Template (learning-focused)

## Period Covered
-

## Liked (what we enjoyed)
-

## Learned (insights and discoveries)
-

## Lacked (what was missing)
-

## Longed for (what we wish we had)
-

## Next Actions
- [ ] (Owner: / Due: )

Start / Stop / Continue Template (behavior-change-focused)

## Period Covered
-

## Start (begin doing)
-

## Stop (stop doing)
-

## Continue (keep doing)
-

## Next Actions
- [ ] (Owner: / Due: )
Recommended properties: Period (Date Range) / Attendees (People) / Framework used (Select: KPT / 4Ls / Start-Stop-Continue)
💡 Always assign owner + due date for every Try / Start item: The single biggest reason retros become theater is leaving action items as "the team should…" One person, one item, with a deadline tied to the next retro.

Notion Meeting DB Property Design (Shared Across Scenes)

To make the five templates above work as one system, the underlying database needs a small, sharp set of properties.

The Five Properties You Actually Need

PropertyTypePurpose
TitleTitleUse "YYYY-MM-DD — ◯◯ standup" style naming
DateDateRequired for sorting and calendar views
TypeSelect1-on-1 / Standup / Sales / Kickoff / Retro
AttendeesPeopleSearchability
StatusSelectDraft / Confirmed

Add any more and you start dreading filling them in. Start here, and add more only when you hit a real need.

Useful Extensions

  • Relations: Linking to a Projects DB or Accounts DB lets you filter "all notes for this customer"
  • Rollups: Surface "number of open action items" right on the note to prevent forgotten follow-ups

Setting Up Template Buttons

Inside the meeting notes DB, click the ▼ next to "+ New" and select "New template." Register all five templates here so you can pick one with a single click.

You can also set default property values per template, so picking the 1-on-1 template automatically sets Type to "1-on-1" — which keeps per-scene views clean later.

AI Auto-Fill, Realistically — Who Can Use Notion AI Meeting Notes and Who Can't

Filling templates by hand is still tedious. Here's where automation comes in.

Notion AI Meeting Notes — Exact Specs (2026)

Released in May 2025, Notion AI Meeting Notes records meeting audio, transcribes it automatically, and extracts a summary plus action items. Per Notion's official help center, the specs are:

  • Business Plan or higher required (effectively unavailable on Plus and Free)
  • macOS 13+ / Latest Windows
  • Desktop app v4.7.0+ recommended
  • Desktop captures both system audio and microphone; the browser version only captures the microphone
  • 10 hours per user per day; speaker labeling is English-only
  • Minimum 1 minute (~300 characters) of audio required
Notion AI Meeting Notes interface
Notion official site

So if you have a Business contract, a current Mac/Win setup, and your meetings are in English, you get a near-ideal experience. If you're on individual Plus or Free, or your meetings are mostly non-English, the bar is real.

The Alternative Route if You're Not on Business

The practical alternative is a three-step chain:

  1. Record meeting audio on your Mac (both system audio and microphone)
  2. Run it through AI for transcription and summarization
  3. Drop it into your Notion meeting template

The nice properties of this chain are:

  • No bot has to join the meeting (no awkwardness in customer calls)
  • Notion can stay on Free or Plus
  • Works the same for Zoom, Google Meet, and Microsoft Teams

Qureco: One App for Record → AI Notes → Notion

Trying to glue together three separate apps usually breaks down at the integration step. Qureco is a Mac app that runs the whole chain in one place.
Qureco interface
Qureco official site
  • No virtual audio setup required to capture system audio on Mac (no BlackHole and friends)
  • AI generates the meeting notes automatically, with customizable template output (you can tune it to match the five scene templates above)
  • One-click Notion integration to push the result straight into your meeting notes DB

The Free tier covers recording with no time limit and no watermark, so you can start by just capturing audio cleanly. AI notes and Notion integration are on the Pro plan ($9/month, first month free, no credit card required).

Pro plan free for 3 months

Join the Beta Waitlist

Early adopters get 3 months of Pro plan for free

By signing up, you agree to our Privacy Policy

Operational Tips — Make the Pile Actually Useful

A template alone gives you a folder that fills up but doesn't pay you back. Three tips to actually get value from the pile.

Use Status to Separate "Draft" and "Confirmed"

Right after a meeting it's a rough note — mark it Draft. Once you clean it up, mark it Confirmed. Search precision jumps. You can also build a Draft-only view to surface notes you haven't tidied yet.

Use the Type Tag to Build Per-Scene Views

Filter by Type to get "my 1-on-1s for the last six months" or "all sales meetings with one customer." This is a huge win at performance reviews and customer QBRs.

Split Next Actions Into a Separate DB

Inline - [ ] lists in the note are convenient in the moment but invisible across notes. Keep a separate Tasks DB and link to it from each meeting note — now your whole ToDo pile is searchable.

Summary

The shape of Notion meeting notes that doesn't drift:

  • One DB, five template buttons — that's the design that survives
  • The five templates (1-on-1, standup, sales, kickoff, retro) are in the code blocks above — paste them directly
  • AI auto-fill has two real paths: Notion AI Meeting Notes (requires Business) or Mac recording → AI notes → Notion (Qureco or similar makes it one app)
  • Don't forget the "after you've piled them up" layer: Status, Type tag, and a separate Tasks DB

Start by pasting the templates and using them in Monday's 1-on-1. When manual filling starts to hurt, move the recording-based automation in.

Qureco

Qureco Screen Recorder

Powerful screen recording app for Mac

Record meetings, let AI handle the notes, just read what arrives in Notion.Join the beta waitlist and get Pro plan free for 3 months.

No Setup RequiredNo WatermarkAI Meeting NotesNotion Integration
Pro plan free for 3 months

Join the Beta Waitlist

Early adopters get 3 months of Pro plan for free

By signing up, you agree to our Privacy Policy

About the Author

Shunsuke Inoue

Shunsuke Inoue

CEO, Qurio Inc.

Founder of Qurio, an AI consulting company. Majored in AI at Sophia University and founded the AI research circle "SOMA." As CEO of JPMT Inc., developed "MinPro" (1,300+ users) and business analysis SaaS "Optpath." Established Qurio Inc. in October 2025, focusing on AI and data development consulting. Speaker at the 30th Nikkei Forum "Future of Asia." Committed to promoting technological advancement and creating new value through AI.