Meeting Notes Template: Decisions, Owners & Follow-Ups

A useful meeting notes template does more than capture a conversation. It makes decisions explicit, gives every action one owner, preserves unresolved questions, and creates a reliable starting point for follow-up. The template below is designed for recurring team meetings, project reviews, customer calls, and AI-assisted workflows.

An operational template combines a readable meeting page with typed controls for decisions, actions, permissions, evidence, and follow-up.

Copy this meeting notes template

# [Meeting name] — [YYYY-MM-DD]

**Meeting type:** [Weekly sync / decision review / project review / 1:1 / customer call]
**Facilitator:** [Name]
**Note owner:** [Name]
**Participants:** [Names]
**Linked project or account:** [Link]
**Access class:** [Internal / Confidential / Restricted]
**Recording consent:** [Not recorded / Obtained — text / Obtained — spoken]
**Meeting objective:** [The outcome this meeting must produce]

## Agenda

1. [Topic and expected outcome]
2. [Topic and expected outcome]
3. [Topic and expected outcome]

## Context and pre-reads

- [Document, dashboard, ticket, or prior decision]
- [Constraint, deadline, or known risk]

## Discussion notes

### [Topic 1]

- Evidence:
- Options considered:
- Concerns:
- Open questions:

## Decisions

### D-[ID] — [Decision statement]

- **Status:** Proposed / Accepted / Superseded / Reversed
- **Decision owner or approver:**
- **Rationale:**
- **Effective date:**
- **Affected systems or teams:**
- **Evidence:** [Transcript timestamp or note]
- **Review date:**

## Action items

| ID | Action | Owner | Due date | Status | Acceptance criteria | Source decision | Destination |
| --- | --- | --- | --- | --- | --- | --- | --- |
| A-[ID] | [Verb-first task] | [One person] | [Date] | Proposed | [Proof of done] | D-[ID] | [Task link] |

## Risks and dependencies

| Risk or dependency | Owner | Impact | Mitigation | Review date |
| --- | --- | --- | --- | --- |
| [What may block progress] | [Name] | [Impact] | [Next step] | [Date] |

## Open questions

| Question | Owner | Needed by | Resolution |
| --- | --- | --- | --- |
| [Unresolved question] | [Name] | [Date] | [Answer or link] |

## Follow-up

- **Next review date:**
- **Outstanding actions from the previous meeting:**
- **Completed work and evidence:**
- **Changes to prior decisions:**
- **What must be on the next agenda:**

Use this as the page body. Then add typed database properties so meetings, decisions, and actions can be filtered, assigned, automated, and reviewed.

The short answer

A high-value meeting notes template needs six layers:

1. identity and governance;

2. objective and agenda;

3. structured discussion notes;

4. explicit decision records;

5. accountable action records;

6. a follow-up section that checks prior work.

The most important design choice is to keep decisions and actions separate. “We discussed launching next week” is not a decision. “Launch the beta to twelve design partners on July 28” can be a decision. “Mina will draft the partner invitation by July 24” is an action.

Database properties to add

Use a meeting database when the template will recur. The page holds the narrative; properties make the record queryable.

Avoid a single “Owner” property for the whole meeting if action items can have different owners. The meeting owner maintains the record; each action has its own accountable owner.

The four objects inside the template

1. The meeting record

The meeting record answers: what was this event, who was involved, what policy applied, and what outcome was expected?

Required fields:

• Meeting ID

• title

• date

• type

• facilitator

• note owner

• objective

• access class

• consent state

2. The discussion record

Discussion notes capture evidence, alternatives, objections, and unresolved questions. They are not a chronological transcript unless that is genuinely useful.

Organize discussion by topic. For each topic, ask:

• What evidence was presented?

• What options were considered?

• What changed?

• What remains uncertain?

• Is a decision required?

3. The decision record

A decision should be a clear statement with authority and evidence.

Minimum fields:

• Decision ID

• decision statement

• status

• approver or decision owner

• rationale

• effective date

• source meeting

• evidence

• review date

Use lifecycle states. Accepted decisions can later be superseded or reversed; do not simply edit history until the old choice disappears.

4. The action record

An action is work, not a bullet.

Minimum fields:

• Action ID

• verb-first task

• one owner

• due date or review date

• status

• acceptance criteria

• source meeting

• source decision

• destination task ID

If the team uses a task manager, create the action there after approval and store the destination link in the meeting record.

Why the owner, date, and evidence fields are mandatory

“Follow up with the customer” is easy to write and hard to execute. It does not say who is responsible, when the work is expected, what outcome counts as done, or why it exists.

A stronger action is:

Send the revised design-partner terms to Acme’s legal contact by July 24 and link the acknowledged email. Owner: Mina. Source: D-071-02.

The sentence is longer, but the ambiguity cost is lower.

Use these validation rules:

• exactly one accountable owner;

• an explicit due date or review date;

• a verb-first task;

• acceptance criteria that can be observed;

• a link to the meeting;

• a link to the decision when applicable;

• no sensitive content copied into a broader destination without review.

Five template variants

Keep one canonical meetings database, then create variants for recurring meeting types.

1. Weekly team sync

Use when the goal is coordination and blockers.

Sections:

• changes since last week;

• metrics or signals;

• blockers and dependencies;

• decisions needed;

• action items;

• next-week priorities.

Avoid turning the meeting into a status-reading session. Ask participants to update routine status asynchronously and reserve live time for exceptions and decisions.

2. Decision review

Use when a group must choose among options.

Sections:

• decision to make;

• decision owner;

• deadline;

• options;

• evaluation criteria;

• evidence;

• risks;

• objections;

• final decision;

• review or reversal trigger.

A decision review should end with either an accepted decision or an explicit reason the decision remains open.

3. Project review

Use when the goal is to verify progress against a plan.

Sections:

• target outcome;

• milestone state;

• evidence of completed work;

• variance from plan;

• risks and dependencies;

• change requests;

• decisions;

• next actions.

Do not rely on color-only status. Require a short explanation and a link to evidence.

4. Customer meeting

Use when the record must separate customer facts, requests, commitments, and internal interpretation.

Sections:

• customer objective;

• participants and roles;

• current environment;

• stated pain;

• evidence and quotes;

• objections;

• customer commitments;

• company commitments;

• follow-up communication;

• sensitive-information check.

Never present a generated summary as a customer-approved statement without review.

5. One-to-one meeting

Use when the content is personal and access must be restricted.

Sections:

• wins;

• current priorities;

• support needed;

• feedback;

• growth topics;

• manager commitments;

• employee commitments;

• follow-up.

Keep access private to the intended participants. Do not reuse a broadly shared team-meeting template without revisiting permissions.

Keep one governed meeting schema and vary only the sections required for weekly syncs, decision reviews, project reviews, customer meetings, and one-to-ones.

How to build it in Notion

Notion database templates can prefill page content and property defaults. According to Notion’s documentation, templates are specific to the database where they are created, and repeating templates can generate new copies daily, weekly, monthly, or yearly.

A practical setup:

1. create a Meetings database;

2. add the properties above;

3. choose New template from the database’s New menu;

4. paste the canonical page body;

5. create variants for weekly sync, decision review, project review, customer call, and one-to-one;

6. prefill only safe defaults such as meeting type or status;

7. leave project relations empty unless every copy should relate to the same record;

8. add a linked view of open action items filtered to the current meeting or project;

9. set a repeat schedule only for genuinely recurring events;

10. assign a template owner and review date.

Do not prefill sample decisions, action owners, or stale dates. Example content that survives duplication can become false operational data.

Using Notion AI Meeting Notes with the template

As of July 21, 2026, Notion AI Meeting Notes can transcribe meetings, generate summaries and action items, use custom summary instructions, and consider both transcript and manual notes. Notion describes the feature as beta for Business and Enterprise plans, with eligible mobile availability.

Create custom summary instructions that match the template:

Produce four sections: Decisions, Action candidates, Risks and dependencies, and Open questions.

For each decision:
- preserve the exact decision statement;
- name the approver only when explicit;
- cite transcript evidence;
- mark ambiguous choices as proposed.

For each action candidate:
- use a verb-first task;
- include owner and due date only when explicit;
- never invent missing values;
- link the source decision when one exists;
- return an ambiguity reason and confidence.

Do not create downstream tasks. Return a reviewer packet.

This helps the AI produce structured candidates. A person should still validate consequential records before they are synced to another system.

Consent, permissions, and retention

Recording and transcription require an explicit policy.

Notion says users should disclose AI Meeting Notes and obtain consent from all participants before proceeding. It offers text, spoken, and automatic audio consent mechanisms, and workspace owners can enforce automatic consent messaging.

Notion also says meeting notes are private to the creator by default and inherit the permissions of their page. Depending on settings, notes created from calendar entry points can be auto-shared with internal workspace participants.

Add these fields or checks:

• consent status and method;

• recorder;

• access class;

• external-participant flag;

• transcript retention date;

• deletion-request owner;

• redaction status;

• destination permission check.

A template is not a legal policy. Use counsel and company policy to define what can be recorded, how consent must be obtained, and how long evidence is retained.

The follow-up view

A meeting template becomes operational when it starts the next meeting with unfinished work.

Create a linked actions view filtered to:

• source meeting is the previous occurrence, or project matches the current meeting;

• status is not Done or Cancelled;

• due date is before or within the next review window.

Show:

• action;

• owner;

• due date;

• status;

• blocker;

• source decision;

• destination task;

• completion evidence.

Create a linked decisions view showing accepted decisions that have a review date or were superseded. This prevents teams from making the same decision repeatedly without knowing why.

Template quality checklist

Structure

• The objective is visible near the top.

• Agenda topics state an expected outcome.

• Decisions and actions have separate sections.

• Open questions do not disappear into prose.

• Prior follow-up appears before new discussion.

Fields

• Meeting ID is stable.

• Every action has one owner.

• Every action has a due or review date.

• Decision status uses controlled values.

• Evidence links back to the meeting.

• Destination task IDs are stored after sync.

Governance

• Consent state is explicit.

• Access class is explicit.

• Sensitive variants use restricted permissions.

• Transcript retention is defined.

• External sharing requires review.

• Template ownership is assigned.

Automation

• AI returns proposed records, not silent writes.

• Missing values remain unresolved.

• Schema validation runs before sync.

• Task creation is idempotent.

• Destination state is read back.

• Exceptions have an owner and SLA.

Maintenance

• The template has a version or last-reviewed date.

• Recurring defaults are still correct.

• Example data is removed.

• Relations do not point every copy to the same record by accident.

• Changes are tested on a duplicate before rollout.

Common meeting-notes template mistakes

One giant notes field

A single narrative page is readable but hard to query. Keep the page, then create typed records for decisions and actions.

A checkbox without ownership

A checked or unchecked bullet does not say who is accountable. Use a Person field and require exactly one owner.

Action items without acceptance criteria

“Investigate pricing” has no finish line. Define the artifact, decision, or evidence that completes the task.

Prefilled relations

Notion warns that a relation filled in on a database template will point every created page to the same existing record. Leave dynamic relations empty unless the shared target is intentional.

Repeating stale context

A weekly template can create pages automatically, but copied dates, sample decisions, and old participants may become misleading. Use safe defaults only.

Recording without a consent state

A capture block is not a consent process. Put consent near the top and make it part of the start checklist.

Treating AI output as approved truth

AI can extract and summarize. It can also misattribute a speaker, infer a deadline, or convert a suggestion into a commitment. Review the records that will change downstream state.

No template owner

Templates drift. Assign an owner who reviews fields, variants, permissions, and automation behavior.

When to add an agent

A template is enough when people can reliably fill it and follow up manually.

Add an agent when the workflow needs to:

• extract decisions and action candidates;

• compare actions with existing tasks;

• resolve names against an identity directory;

• propose links to projects or accounts;

• prepare a compact reviewer packet;

• sync approved records to scoped tools;

• monitor missing owners or overdue actions;

• draft the next agenda from unresolved work.

Keep deterministic controls around identity, dates, permissions, schema, idempotency, and audit logs.

Upgrade to an agent only after the template is stable: let AI propose records, require human review for consequence, and use deterministic controls for writes and read-back.

Example: a completed decision review

Meeting: Beta launch review

Objective: Decide the first launch audience and assign the remaining launch work.

Decision D-071-01

Launch to twelve design partners before general availability.

• Status: Accepted

• Decision owner: Product lead

• Rationale: Limit support load while validating onboarding

• Evidence: 00:32:10–00:32:41

• Review date: August 11

Action A-071-03

Draft the design-partner invitation.

• Owner: Mina

• Due date: July 24

• Acceptance criteria: reviewed email draft linked

• Source decision: D-071-01

• Destination: Campaign task TSK-4821

• Status: In progress

Open question Q-071-02

Has legal approved the revised terms?

• Owner: Legal liaison

• Needed by: July 25

• Resolution: Unresolved; blocks launch

This is more useful than a perfect paragraph because the team can filter, assign, sync, and review each object.

Frequently asked questions

What should a meeting notes template include?

At minimum: meeting identity, objective, agenda, discussion notes, decisions, action items, risks, open questions, and follow-up. Add consent and access fields when recording or sensitive content is involved.

What is the best format for action items?

Use a table or database with task, owner, due date, status, acceptance criteria, source meeting, source decision, and destination link.

Should meeting notes include a full transcript?

Usually no. Keep the transcript as evidence and use the notes as the operating summary. Link to bounded transcript evidence for consequential decisions.

Can Notion create recurring meeting notes?

Yes. Notion’s repeating database templates can create new copies daily, weekly, monthly, or yearly. Test defaults and relations before enabling recurrence.

Can AI fill out the template?

AI can extract proposed decisions, actions, risks, and questions from a transcript and notes. Require review before creating tasks or broadly sharing sensitive output.

How soon should meeting notes be reviewed?

Review immediately after the meeting while context is fresh. For automated workflows, set an SLA for approving or rejecting action candidates.

What makes a meeting notes template AI-ready?

Typed fields, controlled states, stable IDs, evidence links, explicit permissions, a review gate, and clear boundaries between AI interpretation and deterministic execution.

Last verified: July 21, 2026.

Use the reusable template

Open the structured working table below, duplicate it into your operating workspace, and replace the sample rows with a real meeting before adding automation.

Sources

• Notion: AI Meeting Notes (beta)

• Notion: Database templates

• Notion: Using database templates for teams

• Notion: Using linked databases

Product capabilities and availability were last verified on July 21, 2026.

Where Dokki fits

Recreate the meeting schema as a Dokki table when decisions and follow-ups need durable owners, review state, evidence, and agent assistance. Keep the agenda and narrative notes in a linked document, while the table remains the operational source of truth.

• Meeting notes that become actions: a practical AI workflow

• Notion templates vs agent-native workspaces

• Notion Custom Agents: workflow design and permissions