Most meeting notes are useless. They're either a wall of text nobody reads or a sparse list of bullet points that don't capture what was actually decided. Either way, people leave the meeting, forget what was agreed, and do different things.
Good meeting notes do one job: make it impossible to forget or dispute what was decided and who's responsible. Here's the template and framework to write notes that actually get read.
The Universal Meeting Notes Template
Copy this template. Use it for every meeting. Modify the sections based on meeting type, but the structure stays the same.
Copy-Paste Template
The 5-Part Framework
Each section of the template serves a specific purpose. Here's why each matters and how to write it well.
1Metadata (1 line)
Date, attendees, and purpose. One line each, maximum. The purpose line is the most important — it anchors the notes to a specific goal. If you can't articulate the meeting's purpose in one sentence, the meeting probably shouldn't have happened.
Pre-fill the metadata before the meeting starts. Copy the attendee list from the calendar invite. Write the purpose from the agenda. You'll save 2 minutes of note-taking time and start with structure instead of a blank page.
2Decisions Made
This is the most valuable section. Every meeting should produce at least one decision. Write it as a clear statement of what was agreed — not the discussion that led there.
Bad: "We discussed the new pricing and there were different opinions about whether to go with tiered pricing or flat rate."
Good: "Decision: We will launch with 3-tier pricing (Basic $29, Pro $79, Enterprise $199). Flat-rate option shelved for now."
3Action Items
Every action item has three components: who, what, and when. If any of these are missing, the action item is useless.
Bad: "Follow up on the design." (Who? What specifically? By when?)
Good: "Sarah will send the updated homepage mockup to the client for review by Friday March 28."
Read action items aloud at the end of the meeting before anyone hangs up. This catches misunderstandings immediately and creates verbal commitment. People who hear themselves assigned a task are more likely to complete it.
4Key Discussion Points
Not a transcript. Not every comment. Just the 2–4 most important topics discussed, summarized in 2–3 sentences each. Focus on context that someone reading the notes next month would need to understand the decisions.
Use ToolKit.dev's Word Counter to keep discussion summaries under 50 words each. If it takes more words, you're including too much detail.
5Parking Lot
Topics that came up but weren't resolved. This section is underrated — it acknowledges ideas without letting them derail the meeting, and it ensures they don't get lost. Review the parking lot at the start of the next meeting.
Templates by Meeting Type
Client Kickoff Call
Focus on: project scope confirmation, timeline review, communication preferences, access/credentials needed, immediate next steps. Send notes within 1 hour — this sets the professional tone for the entire engagement. For freelancers, this is also your scope documentation — if the client doesn't correct something in the notes, they've implicitly agreed to it.
Weekly Team Standup
Focus on: what was completed, what's blocked, what's planned for the week. Skip discussion summaries — standups are about status, not debate. Keep notes to half a page. Use a running document so everyone can see the arc of progress over weeks.
Strategy / Brainstorm Session
Focus on: ideas generated (all of them, even rejected ones), decisions on which to pursue, and assigned owners for each initiative. For brainstorms, it's acceptable to capture more raw content — but still organize it into themes rather than a chronological transcript.
Client Feedback Review
Focus on: specific changes requested (numbered list), what was approved, what needs further discussion, and which revision round this represents. This is scope creep defense — documenting each feedback round creates a clear record of revision counts per your contract.
The Freelancer Business Kit
Meeting note templates, client communication scripts, project management frameworks, and more — everything to run your freelance business professionally.
Get the Kit — $196 Meeting Notes Mistakes
Writing a transcript instead of a summary
Nobody will read 3 pages of meeting notes. Capture decisions and actions, not every word spoken. If you need a transcript, record the meeting and use AI transcription.
Sending notes the next day
Notes lose value exponentially with time. Send within 30 minutes of the meeting ending. If they're not worth sending quickly, they're not worth writing at all.
Action items without owners or deadlines
"We should look into this" is not an action item. "[Person] will [action] by [date]" is an action item. If nobody is assigned, it won't happen.
Burying decisions in paragraphs
Decisions should be the first section after metadata — bold, bulleted, impossible to miss. Don't make people hunt for what was agreed.
Not sharing notes with all attendees
Notes that live in your personal notebook don't align the team. Share immediately with everyone who attended and anyone affected by the decisions.
Using notes to rehash debates
Notes document outcomes, not arguments. "After extensive discussion about pricing approaches, the team decided..." should be "Decision: 3-tier pricing model." Save the narrative for a blog post.
Best Tools for Meeting Notes
For simplicity: A Google Doc shared with attendees. Pre-fill the template before the meeting. Share the link in the calendar invite so everyone can see notes in real-time.
For teams: Notion. Create a meeting notes database with properties for date, attendees, project, and status. Use the template feature to auto-fill the structure for every new entry.
For client meetings: Take notes in whatever tool you use, then send a clean summary via email. The email becomes the official record. Use ToolKit.dev's Markdown to HTML converter if you write notes in markdown and want to paste formatted notes into email.
For action item tracking: Copy action items from your notes into your project management tool (ClickUp, Trello, Asana) immediately after the meeting. Notes are for documentation; your PM tool is for execution.
Frequently Asked Questions
Five elements: metadata (date, attendees, purpose), decisions made, action items (who/what/when), key discussion summaries (2–3 sentences each), and next steps. Skip everything else.
During, then clean up immediately after. Jot decisions and actions in real time, then spend 5–10 minutes formatting and filling gaps. Send within 30 minutes of the meeting ending.
One page max for 30-minute meetings, half a page for standups, two pages max for 60-minute strategy sessions. If someone can't get the key outcomes in 2 minutes of reading, cut more.
Rotate the role, or assign it to whoever called the meeting. The facilitator should not also be the note-taker. For client meetings, the freelancer should always take and send notes.
Get Every Business Template You Need
Meeting notes are just one template. The Freelancer Business Kit includes the complete system:
- Meeting notes and follow-up templates
- Client communication scripts
- Proposal and contract frameworks
- Project management checklists
- Invoice templates and payment scripts