Meetings

5 Meeting Note Templates
Copy, adapt, and use

Choose standard minutes, action items, brainstorming, one-on-ones, or a decision log. Capture decisions, owners, dates, and open questions using a template you can copy or download as Markdown.

Start with standard minutes if unsure.Record the date, attendees, topics, rationale, decisions, owners, deadlines, and open questions. Copy any of the five templates below or download its Markdown file.

Updated September 9, 2026. These five editable templates were created for this article. At the end of the meeting, confirm decisions, owners, and due dates with participants.

What is a standard meeting minutes template I can use?

For recurring team or project meetings. Keep context and reasons alongside decisions, and mark unresolved topics clearly. Add fields required by your team’s own record format.

# [Meeting name] — Meeting notes
When: [YYYY-MM-DD / HH:MM–HH:MM / time zone]
Attendees: [Names]
Note-taker: [Name]
Purpose: [What this meeting should decide]
References: [Links]

## Topics and context
- Topic: [Subject]
  - Background / checked facts: [Summary]
  - Remaining question: [Details]

## Decisions
- Decision: [What will happen and within what scope]
  - Rationale: [Reason / important assumption]

## Actions
- [ ] [Specific deliverable] / Owner: [One name] / Due: [YYYY-MM-DD]
  - Completion check: [Destination, link, or acceptance condition]

## Open / deferred
- [Question] / Follow-up owner: [Name] / Check on: [YYYY-MM-DD]

## Next meeting
When / what to review: [Details]
Sharing scope / reviewers: [People or group]
Download Markdown

Template 2: Action items

For brief check-ins centered on next actions. Name the deliverable and completion check instead of leaving a vague task such as “research it.”

# [Meeting name] — Next actions
Date: [YYYY-MM-DD]
Purpose: [One line]

## Agreed
- [Decision and scope]

## Tasks
- [ ] [Deliverable] / Owner: [Name] / Due: [YYYY-MM-DD]
  - Done means: [Verifiable result]
  - Status: [Not started / In progress / Awaiting review / Done]

## Blockers
- [Information or help needed] / Ask: [Name] / Check next: [Date]

## Next review
[YYYY-MM-DD / Tasks to review]
Download Markdown

Template 3: Brainstorming

For generating options and choosing a small test. Separate idea capture from evaluation and selection.

# [Theme] — Brainstorm notes
Date: [YYYY-MM-DD]
Question: [Where do we need more options?]
Constraints: [Budget, time, or requirements]

## Ideas (capture first)
1. [Idea]
2. [Idea]
3. [Idea]

## Group and compare
- Group: [Common theme]
- Criteria: [Impact, effort, or ease of testing]
- Candidate to try: [Idea and reason]

## Small test
- Try: [Experiment or prototype]
- Owner: [Name]
- Review on: [YYYY-MM-DD]
- Look for: [Evidence for the decision]
Download Markdown

Template 4: One-on-one

For conversation topics, support needs, and agreed actions. Confirm what belongs in the shared record rather than treating everything discussed as something to circulate.

# One-on-one — [Name / Name]
When: [YYYY-MM-DD / HH:MM]
Sharing scope: [Who can read this note]

## Topics for today
- [Topic the participant wants to share]

## Since last time
- [Agreed action and current situation]

## Questions and support
- [Challenge]
- [Help requested]

## Agreed today
- [ ] [Action] / Owner: [Name] / Review on: [YYYY-MM-DD]

## Continue next time
- [Topic]
Download Markdown

Template 5: Decision log

For decisions whose rationale you will need later. Record assumptions, alternatives, and review conditions; link to a new entry if the decision changes.

# Decision log — [Topic]
Decided on: [YYYY-MM-DD]
Decision-maker / reviewers: [Names]
Status: [Proposed / Decided / Reconsidering / Superseded]

## Decision
[Chosen option and scope]

## Context and assumptions
[Problem, checked facts, constraints]

## Options considered
- A: [Option, benefit, concern]
- B: [Option, benefit, concern]

## Rationale
[Why this option / What was deferred]

## Risks and responses
- [Risk] → [Response and owner]

## Review conditions
Review on: [YYYY-MM-DD]
Reconsider if: [Changed assumption or result]
References / previous decision: [Links]
Download Markdown

Turn a vague task into a verifiable action

“Review the document” does not say who must do what or how completion will be checked. Mark an unassigned task as unassigned and choose who will confirm its owner and when. This is a fictional example.

Before: Review the document.

After: Alex checks the three pricing items in the proposal and records differences in the shared document by 2026-09-11. Sam reviews those differences to confirm completion.

Use a date instead of only “Friday,” and include a time zone if a specific time matters. Mark an unagreed date as awaiting confirmation instead of guessing it.

From a post-meeting memo to follow-through

  1. Separate decisions from open questions.Do not present an option still under discussion as approved. Add relevant context and rationale while they are fresh.
  2. Confirm owners, due dates, and completion checks.Distinguish accepted tasks from requests awaiting a response.
  3. Store the record where the team can access it.Use the agreed shared document or project location and check access. Sending a note to your own inbox does not complete team sharing or review.
  4. Create needed tasks and review dates.A checkbox in a note or star on an email does not necessarily create a deadline notification. Check the task or calendar tool you use.

A personal post-meeting memo can briefly capture a decision, your next action, and what still needs confirmation. Keep its purpose separate from the team record so private working notes are not circulated accidentally.

Use the templates with the right destination and access

These are plain-text templates you can paste into an existing notes or document app. Markdown-aware apps may render headings and checklists, but the template does not automatically notify owners or create deadlines.

If using Simple Memo, follow recipient verification and sending setup or configure the Obsidian vault and target note, then verify the first result. Use accounts and destinations permitted for the meeting content by your organization.

For one-on-ones or client discussions, decide who should read the record and what should be kept. A personal email address alone does not establish that a destination is suitable for confidential information.

Frequently asked questions

What should meeting notes include?

Record the date, attendees, topics, relevant context and rationale, decisions, owners, due dates, and open questions. Follow any required team format and confirm decisions and owners before the meeting ends.

Can I copy these templates directly?

Yes. Use the Copy template button or select and copy the text. Download Markdown provides a file as well. Edit the fields to fit your meeting after copying.

Are minutes the same as personal notes?

Team minutes document shared decisions and next actions. Personal notes may include working thoughts, so review content and recipients before sharing. Follow your organization’s requirements for record format and review.

What if an owner or due date is not decided?

Mark it as unassigned or awaiting confirmation instead of guessing. Record who will confirm the owner or date and by when so the open item can be tracked.

How do I use a post-meeting memo?

Briefly capture decisions, your next action, and what needs confirmation. Then put the team record in its shared location and create any tasks or deadline notifications in the tool you use. Emailing yourself alone does not complete sharing or notifications.

Related Articles

Keep meeting takeaways at your chosen destination
Capture short text for a configured recipient or note destination and verify the first result.
Download on the App Store

Related Pages

Reference

For agendas, decision rationale, owners, due dates, and shared storage, see Atlassian’s meeting notes guide. The five templates here are original formats; no measured productivity improvement is claimed.