Never walk into a meeting empty-handed again.
Fill in who's coming, what you're deciding, and how long each topic gets. We'll turn it into a clean, printable agenda built to keep the conversation on track.
Free template · no signup · no email required
Meeting minutes template builder
Fill in what you know ahead of time. Leave the discussion notes and action items blank — those are meant to be written in live, not guessed at the night before.
Starting from scratch? Pick one of the free meeting agenda templates and it'll open here already filled in.
Set the scene
The basics your attendees need before they even open the invite.
Comma-separated names. We'll leave a spot on the template for each one to check in.
One or two lines, so nobody's guessing why they're here.
What does "done" look like?
List the outcomes you need before anyone's allowed to leave the room.
Time-box the agenda
Give every topic a name and a number of minutes, and the rest fills itself in.
Runs 6:45 PM – 7:00 PM (15 min)
worked example
What completed meeting minutes look like
The same weekly team meeting as the agenda template, written up after it happened.
Weekly Team Meeting
This week · 9:00–9:30 AM · Minutes by Dana Whitfield
- Present
- Dana Whitfield, Marcus Bell, Priya Raman, Tom Okafor
- Apologies
- Elena Sokolov
Discussion
- 1
Wins and metrics
Activation up 4 points week over week. Support backlog cleared Thursday.
- 2
Open action items from last week
Two closed. The pricing-page copy review slipped and moves to this week.
- 3
Priorities for this week
Onboarding email sequence, then the Q3 roadmap draft. Everything else waits.
- 4
Blockers and decisions needed
Design review is the bottleneck on onboarding. Needs a standing slot.
Decisions
- Design review gets a recurring Wednesday slot instead of being requested ad hoc.
- Q3 roadmap draft goes out for comment before it goes to the board, not after.
Action items
| Item | Owner | Due |
|---|---|---|
| Book the recurring design review | Marcus Bell | Tomorrow |
| Draft the onboarding email sequence | Priya Raman | Thursday |
| Pricing-page copy review (carried over) | Tom Okafor | Friday |
Next meeting: same time next week. The carried-over item stays on the agenda until it's closed.
-
One line per topic
Every discussion note records where the conversation landed, so nobody has to reconstruct the argument to find the answer.
-
Decisions pulled out separately
Buried in a paragraph, a decision gets remembered three different ways. On its own line it can only be read one way.
-
Every action item has a name on it
An owner and a date, captured while the room could still hear it. Anything assigned to the team is assigned to nobody.
-
The carried-over item is visible
Last week's unfinished item appears again rather than quietly dropping off, which is how most commitments die.
the seven parts
What to include in meeting minutes
Minutes fail in one of two ways: too thin to be a record, or too long to be read. These are the parts that earn their space.
Meeting name, date and time
Plus the location or the video link. Minutes get read months later, out of context, by someone who wasn't there.
Who was there, and who wasn't
A present list and an apologies list. This is the line people go back to when a decision gets questioned.
The agenda topics, as headings
Reuse the agenda's structure so the minutes have the same shape as the meeting. It also stops you writing chronologically.
Discussion notes, kept short
Record where the conversation landed. A line or two per topic is usually enough, and a transcript is worse than a summary nobody has to skim.
Decisions, stated once
Write each one so somebody who missed the meeting can't read it two ways. Vague decisions get re-litigated at the next occurrence.
Action items with an owner and a date
One line each: what, who, by when. This is the part that decides whether the meeting changed anything.
When you're meeting next
The date, and anything carried forward to it. An open item with no next occurrence attached is an item nobody will chase.
how to take them
Taking minutes without missing anything
Most of the work happens before the meeting starts. If you're writing from a blank page while trying to follow the discussion, something gets lost.
-
Before: build the page
Start from the agenda so you're filling in a structure rather than inventing one live. Put the attendee list in before anyone arrives, and mark apologies as they come through.
-
During: capture commitments as they're made
Write the owner and the date at the moment someone agrees to something, while the rest of the room can still correct it. Reconstructing that afterwards is guesswork.
-
After: send within the day
Close with a line inviting corrections. It costs nothing and it surfaces the misunderstanding now rather than at the next occurrence.
Meeting Minutes FAQ
Writing the Minutes
What should be included in meeting minutes?
How detailed should meeting minutes be?
Who takes the minutes?
How soon should minutes be sent out?
Formats and Formalities
What's the difference between meeting minutes and an agenda?
Can I download the template as a PDF or Word doc?
Do meeting minutes have to be formally approved?
Does anything join the call to record it?
A template gets you organized once. Less Meeting keeps you that way.
Timed agendas that carry forward, action items that don't die in a doc, and meeting notes your whole team edits together in real time — so you're not rebuilding this from scratch every week.