Meeting Notes Template: 7 Formats You Can Copy

The default template

If you only adopt one, use this. It works for most internal meetings.

# 2026-07-31 · Acme kickoff
**Attendees:** …  
**Purpose:** one line, written before the meeting

## Decisions  
- Decided: …  
  - Why: …  
  - Owner: …

## Action items  
- [ ] Owner — task — due date

## Open questions  
- … (who needs to resolve it, by when)

## Notes  
Raw discussion. Written during. Not cleaned up.

The ordering is the whole point. Decisions and action items sit above the notes because those are what people return for. Most templates put discussion first and outcomes last, which is backwards for every read after the first one.

Purpose is written before the meeting starts. It takes fifteen seconds and it is the field that makes the note comprehensible later, when nobody remembers why the meeting was on the calendar.

Four rules that decide whether a template works

Format matters less than these.

One owner per action item. An item assigned to two people is assigned to nobody. If two people genuinely need to act, that is two items. This is the single most common failure in meeting notes, and no template fixes it for you.

Decisions are separate from discussion. A summary preserves what was said. It does not reliably preserve what the group committed to, or which alternatives were rejected and why. Keeping decisions in their own block — with the reasoning attached — is what makes notes useful in a disagreement six weeks out. If your team makes enough consequential calls, promote them out of the notes entirely into a meeting decision log.

Write outcomes within ten minutes of the call. Everything else can wait. Ten minutes after, you still remember what the vague "we should probably look at that" actually referred to. The next morning you do not.

Raw notes stay raw. Do not clean up during the meeting. Cleaning while listening costs you the thing you are there for. Capture messily, structure after.

Template 1: One-on-one

The point of a 1:1 template is continuity. Most 1:1s fail because they restart from zero every time.

# 1:1 — [Name] — 2026-07-31

## Since last time  
- Carried over: …          ← pulled from last 1:1's open items  
- Landed: …

## Their agenda  
- …

## My agenda  
- …

## Feedback  
- Gave: …  
- Received: …

## Action items  
- [ ] Owner — task — due date

## Next time  
- …

Since last time and Next time are what turn a series of disconnected chats into a thread. If you use nothing else here, use those two fields.

Keep Their agenda above yours. It is a small ordering choice that changes who sets the direction of the conversation. More on the mechanics in how to have productive one-on-one meetings.

Template 2: Standup

Standup notes should take under a minute to write. If your template takes longer, people stop.

# Standup — 2026-07-31

| Person | Yesterday | Today | Blocked on |
| --- | --- | --- | --- |
| … | … | … | … |

## Blockers needing someone outside this room  
- [ ] Owner — blocker — who can unblock

The second section is the only part that matters after the meeting ends. A blocker that stays inside the standup notes is a blocker nobody acted on.

Template 3: Customer or discovery call

Structured for recall across many calls, not for a single conversation.

# [Company] — discovery — 2026-07-31
**Attendees:** … (roles matter more than names)  
**Stage:** …

## Their situation  
- Current process: …  
- Tools in use: …

## Problems, in their words  
- "…"  
- "…"

## Requirements  
- Must have: …  
- Nice to have: …

## Objections and concerns  
- …

## Next step  
- [ ] Owner — what — by when

Problems, in their words should hold actual quotes. Paraphrased customer pain converges on generic language within two calls, and then every account sounds the same in your notes. Verbatim phrasing is also what you reuse in positioning later.

Next step is a single committed action with a date, not a list of possibilities. A discovery call without one did not close.

Template 4: Project kickoff

Kickoffs generate the most durable notes of any meeting type, because everything downstream refers back to them.

# [Project] kickoff — 2026-07-31

## Problem we are solving  
One paragraph. If this is hard to write, the project is not ready.

## Success criteria  
- …  ← measurable, not "improve X"

## Explicitly out of scope  
- …

## Owners  
| Area | Owner | Backup |
| --- | --- | --- |

## Key dates  
| Milestone | Date | Depends on |
| --- | --- | --- |

## Risks  
| Risk | Likelihood | Mitigation | Owner |
| --- | --- | --- | --- |

## Open questions  
- [ ] Question — who resolves — by when

Explicitly out of scope prevents more rework than any other field on this page. Scope creep is rarely a decision; it is usually an assumption that was never written down and contradicted.

Template 5: Retrospective

# Retro — [Sprint/Period] — 2026-07-31

## What worked  
- …

## What did not  
- …

## What we are changing  
- [ ] Owner — change — review on [date]

## Carried over from last retro  
- … ← did the change actually happen?

The last section is what separates a retro that improves things from a recurring venting session. If a change from the previous retro never happened, that is the most useful data point in the room.

Keep What we are changing short. Three changes get done. Twelve do not.

Template 6: Formal minutes

For board meetings, committees, HOAs, nonprofits, and anywhere the record may be reviewed externally. This is a different document from working notes — it records the proceeding, not the discussion.

# [Organization] — [Body] — Minutes
**Date:** 2026-07-31   **Time:** 14:00–15:30   **Location:** …
**Present:** …
**Absent:** …
**Quorum:** Yes / No
**Chair:** …   **Recorder:** …

## 1. Call to order  
Called to order at 14:00 by [name].

## 2. Approval of previous minutes  
Minutes of [date] approved / approved as amended.
- Moved: [name]  Seconded: [name]  Result: Carried / Failed

## 3. [Agenda item]  
Discussion: brief, neutral summary.  
**Motion:** [exact wording]  
- Moved: [name]  Seconded: [name]  
- Vote: For __ / Against __ / Abstain __  
- Result: Carried / Failed

## 4. Action items  
| # | Action | Owner | Due |
| --- | --- | --- | --- |

## 5. Adjournment  
Adjourned at 15:30. Next meeting: [date].

Two things differ from working notes. Motions are recorded in their exact wording, because paraphrase changes meaning. And discussion summaries stay neutral — minutes record that a matter was debated, not who argued badly.

Template 7: Interview

# [Candidate] — [Role] — [Round] — 2026-07-31
**Interviewer:** …   **Focus area:** …

## Questions and responses  
**Q:** …  
**A:** … (what they said, not your read of it)

## Signals  
- Evidence for: …  
- Evidence against: …

## Recommendation  
Strong hire / Hire / No hire / Strong no hire  
**Rationale:** …

Keep observation separate from judgment. Mixing them is how interview notes turn into a record of an impression formed in the first four minutes. Write what the candidate said, then decide.

Interview notes are also the clearest case for keeping recordings and transcripts off third-party servers — they contain personal data about someone who did not choose your vendor.