Meeting Notes Template: A Format That Works for Every Meeting Type

Most meeting notes templates that show up on the internet do not get used. They get bookmarked, copied into a Notion page once, and abandoned by week three. The template was not the problem. The structure inside the template, and the discipline around what gets written down, were.

This guide covers the meeting notes template that actually holds up across the meeting types most teams run: standups, one-on-ones, client meetings, project kickoffs, board meetings, and retrospectives. The core template is short and copy-paste ready. The variations cover the cases where the core needs to flex. The last section covers where the notes should land once they are written, because notes that get written and never read might as well not have been written at all.

The five elements every meeting notes template needs

Every meeting type uses some version of the same five elements. Skipping any of them produces notes that fall short in predictable ways.

Header. Date, meeting type, and attendees. The header is what makes the note findable two months from now. A note titled "Sync" with no header is a note nobody will ever read again.

Agenda or topics. What the meeting was meant to cover. Even informal meetings benefit from an agenda written at the top of the doc, because it scopes what the note is going to capture.

Discussion log. The substantive conversation. This is where most templates over-engineer and most note-takers under-deliver. The right move is brief bullet points focused on the why behind each decision, not a transcript. If you need the transcript, an AI notetaker has it.

Decisions. The explicit, separately-flagged section for "what was decided." Most meeting notes bury the decisions inside the discussion log. The decisions section pulls them out so anyone scanning the note a week later can see what happened in 30 seconds.

Next steps. Action items in the format Owner-Verb-Object-Date. Not "follow up on pricing," but "Sarah to send revised pricing to Acme by Thursday." The format is what makes action items actionable.

Five elements. The discussion log can run long when the meeting was substantive. Everything else should be tight.

The general-purpose template

The copy-paste version. Drop this into Notion, Google Docs, or a markdown editor and start filling.

# [Meeting Type] - [Date]

**Attendees**: [Names]
**Meeting type**: [Standup / 1-on-1 / Discovery / Kickoff / Retro / Other]
**Duration**: [Planned vs actual]

## Agenda
- [Topic 1]
- [Topic 2]
- [Topic 3]

## Discussion
### [Topic 1]
- [Brief bullet on what was discussed]
- [Why it matters]

### [Topic 2]
- [Brief bullet on what was discussed]

## Decisions
- [Explicit decision 1]
- [Explicit decision 2]

## Next Steps
- [ ] [Owner] to [verb] [object] by [date]
- [ ] [Owner] to [verb] [object] by [date]
- [ ] [Owner] to [verb] [object] by [date]

## Open Questions
- [Anything unresolved that needs a follow-up meeting]

That is the entire template. Eight sections, all optional except the header, decisions, and next steps. The discussion log gets as detailed as the meeting warranted and no more.

Variations by meeting type

The core stays. The agenda and discussion sections flex.

One-on-one

The agenda becomes a recurring three-section structure that holds up across weeks.

## Agenda
- Progress since last 1-on-1
- Blockers and asks
- Career and growth
- Manager's items

The discussion log captures what was actually said in each. The decisions section is rarely used in a healthy one-on-one. The next steps section captures what either party committed to before the next meeting.

For one-on-ones specifically, keep the running doc as a single page with all weeks stacked, not a new page per week. The continuity is the point.

Team standup

The agenda is implicit (yesterday, today, blockers). The discussion log compresses to a per-person bullet block.

## Standup
### [Person 1]
- Yesterday: [what shipped]
- Today: [what's planned]
- Blockers: [if any]

### [Person 2]
...

## Blockers raised
- [Anything that needs follow-up after standup]

## Next Steps
- [ ] [Owner to handle each blocker]

The right move for standups is usually to skip the long doc and let the team's tasks tool hold the work. The standup note exists primarily to capture the cross-cutting blockers.

Client meeting or discovery call

The most important variation, because the notes need to survive the handoff between sales, account management, and delivery.

## Client meeting - [Client Name] - [Date]

**Attendees** (client side): [Names, roles]
**Attendees** (internal): [Names]
**Meeting type**: [Discovery / Status / Kickoff / Renewal / Other]

## Client context
- [Goals stated by the client]
- [Constraints mentioned]
- [Pain points referenced]

## Discussion
- [Substantive conversation, organized by topic]

## Decisions
- [Anything formally agreed]

## Next Steps
- [ ] [Owner] to [verb] [object] by [date]

## Internal notes
- [Political dynamics, stakeholder map, things to remember]
- [These do not get shared with the client]

The internal notes section is the one most client meeting templates skip. It is where the qualitative context that makes the relationship work lives. Without it, the account manager picking up the engagement six months later misses the dynamics that shaped every previous decision.

For sales teams running client meetings in Notion, the discovery call notes structure covers the variation in more depth.

Project kickoff

The kickoff note becomes the source of truth for the project's first quarter.

## Project Kickoff - [Project Name]

**Date**: [Date]
**Attendees**: [Names, roles]

## Goals
- [Specific outcome 1]
- [Specific outcome 2]

## Scope
- [In scope]
- [Out of scope]
- [Explicitly deferred]

## Stakeholders
- [Decision maker]
- [Day-to-day contact]
- [Influencers]

## Timeline
- [Phase 1: dates]
- [Phase 2: dates]

## Risks
- [Risk 1: how we mitigate]
- [Risk 2: how we mitigate]

## Decisions
- [Anything decided in the kickoff]

## Next Steps
- [ ] [Owner] to [verb] [object] by [date]

The kickoff note gets opened more often than any other meeting note for the next 90 days. Treat it accordingly.

Board meeting

The board meeting note has a regulatory cousin (board minutes) that has its own legal format. The internal note for the team is different.

## Board Meeting - [Date]

**Attendees**: [Names]
**Quorum**: [Yes/No]

## Agenda
- CEO update
- Financials
- Product update
- Specific decisions on the docket

## Discussion summary
- [High-level recap, not transcript]

## Decisions
- [Formal resolutions, captured separately for the minutes]

## Action items for the team
- [ ] [Owner] to [verb] [object] by [date]

Keep the board-facing minutes separate. The internal action items doc is what the team actually works from.

Retrospective

The retro template is the simplest.

## Retro - [Project / Sprint / Quarter]

**Date**: [Date]
**Participants**: [Names]

## What went well
- [Bullet]

## What did not go well
- [Bullet]

## What we will change
- [Bullet]

## Action items
- [ ] [Owner] to [verb] [object] by [date]

The discipline that separates a useful retro from a ritualistic one is whether the action items actually get assigned and tracked. A retro with "we should improve X" but no owner is a retro that produces no change.

Where to store meeting notes

The template is half of the value. Where the notes land is the other half.

Internal meetings (standups, one-on-ones, team retros) belong in the team's workspace tool. For most teams that is Notion. The Notion sales workspace setup guide covers the database structure for a meetings database that holds all of these in one queryable place.

Client meetings need to land in two places: the team's workspace tool (for the internal notes and ongoing context) and the CRM record (for the deal timeline and shared context with the rest of the company). Storing client notes only in Notion means the AE running the renewal a year later has no idea what was discussed. Storing them only in the CRM means the team that needs the qualitative thinking cannot get to it.

The bridge between Notion and the CRM is where most teams underinvest. Reps write detailed client meeting notes in Notion (because Notion is a better writing environment than any CRM), the CRM shows nothing, and the rest of the team flies blind. The cleanest fix for the Notion-to-HubSpot case specifically is NoteLinker: a Sync to HubSpot checkbox on any Notion row pushes the formatted note onto the matching HubSpot contact or deal timeline.

The discipline that makes the template stick

A template only works if the team uses it consistently. Three habits separate the teams whose notes get used from the teams whose notes get filed and forgotten.

Write as the meeting happens. Notes written after the meeting from memory miss the specific language used, miss decisions that felt obvious in the moment, and miss action items that nobody wrote down. The note-taker should be writing in real time, even if the writing is rough.

Capture decisions in the language used. A decision recorded as "we will move forward with the bigger plan" is useless six months later when nobody remembers what the bigger plan was. A decision recorded as "we will ship the redesign in Q3 with the analytics integration deferred to Q4" is unambiguous.

Assign action items with owner, verb, object, and date. Items without all four parts do not get done. Items with all four parts mostly do.

The pattern across all three is that the discipline matters more than the format. A team that writes terrible notes consistently into a generic template ends up with more usable notes than a team that writes occasional perfect notes into a beautiful template and then stops.

Common mistakes

Four patterns that consistently make meeting notes worse than no notes.

Burying the decisions in the discussion log. If the decision section is empty and the discussion log has a paragraph that ends with "so we agreed to do X," the note is going to fail. Pull the decisions out.

Skipping the next steps. A meeting that produced no action items did not produce a meeting note. It produced a memo. That is fine for status meetings but wrong for almost everything else.

Writing for the meeting, not for the future reader. The audience for a meeting note is the person reading it three months from now, not the person who was in the room. Write accordingly.

Storing the notes nowhere useful. A note that lives in a Slack DM from the note-taker to the manager is a note that does not exist. The note needs to live in a tool where the people who need to find it later actually look.

The best meeting notes template is the one your team uses every time. The one above will hold up across most meeting types. The variations cover the cases where the core needs to flex. The discipline is what makes either of them produce notes that get used a week, a month, and a year later.