How to Write Meeting Minutes That Actually Get Things Done (Free Template)
Minutes nobody reads and tasks nobody does? From real meetings, here's what minutes should capture, how to separate decisions from action items, whether to write verbatim, and a free template you can drop in.
I used to hate taking minutes — it felt like busywork. Until I got burned a few times: a meeting that went great, with clear conclusions, and a week later everyone had a different memory of "what we decided," and nothing got done. That's when it clicked: the real value of minutes isn't recording the discussion — it's making sure the work actually happens afterwards.
Here's how to write minutes where the meeting leads to action.
What problem do minutes solve?
Be clear on the goal and you'll know what to record. Good minutes answer three questions:
- What did we decide? (decisions)
- Who does what, by when? (action items)
- When's next, and what do we follow up?
If your minutes answer those three clearly, they pass. Record every word but miss the conclusions and action items, and however long they are, they're useless.
What minutes should contain
| Block | Content | Why |
|---|---|---|
| Basics | Title, time, location/link, chair, note-taker | Easy to find and file |
| Attendees | Present, apologies | Who was part of decisions |
| Follow-up | Status of last meeting's actions | Nothing falls through |
| Discussion | Key points per topic | Record "why we decided" |
| Decisions | Conclusions reached | On the record, no re-litigating |
| Action items | Who, what, by when | The key to things happening |
| Next meeting | Time, location, follow-ups | Continuity |
Don't rebuild this each time — drop in the ToolKing meeting minutes template, paste it into Word or Google Docs, and fill in the blanks.
The key move: separate decisions from action items
If you remember one thing: put "decisions" and "action items" in two separate sections.
- Decisions record the result: "Confirmed option A for the July campaign, budget cap $15k."
- Action items record the action: "Sam to get a venue quote for option A by 6/25"; "May to deliver a first draft of the copy by 6/28."
I've seen far too many minutes that say "decided on option A" — and then nothing. Because no one knew who moves next or by when. Break out action items, each with an owner and a due date, and the work gets chased.
A simple table works:
Action item Owner Due
Venue quote (option A) Sam 6/25
First draft of copy May 6/28
Habits that make minutes useful
1. Read them aloud before everyone leaves. Two minutes at the end: read the decisions and action items, confirm on the spot. Saves the "I thought you were doing that" later.
2. Don't write verbatim — capture points and conclusions. A transcript wastes time and goes unread.
3. Send the same day. Minutes lose value fast; send (or post to a shared doc) while it's fresh, and let people flag errors.
4. Make action items actionable. Not "look into marketing" but "May to propose three marketing angles by 6/30" — an owner, an output, a date.
Three steps to usable minutes
- Before the meeting, download the meeting minutes template and fill in title, time and attendees.
- During the meeting, capture key points, put conclusions in "Decisions" and tasks in "Action items" with owner and due date.
- Before everyone leaves, read decisions and action items aloud to confirm, then send to all attendees that day.
The bottom line
Minutes aren't busywork to file — they're how the work after a meeting actually gets done. Fill in the basics, capture key discussion points, separate decisions from action items (with owners and dates), confirm before leaving, and send the same day. Start from a template, and after a few meetings you'll find "we talked and forgot" is finally over.
FAQ
How detailed should minutes be? Do I write everything verbatim?
No verbatim. A transcript takes ages and no one reads it; the point is to record the conclusions and 'who does what by when.' For discussion, just capture the key points (why a decision was made). A useful test: three months later, someone reading these minutes needs to know what was decided and who's responsible — not every sentence spoken.
What's the difference between decisions and action items?
Separate them — it's the most important part. A decision is the conclusion reached in the meeting (e.g. 'we'll go with option A'); an action item is who does what by when after the meeting (e.g. 'Sam to get a quote for option A by 6/20'). Many meetings fizzle because only decisions were recorded, not owners and deadlines. Put action items in their own section with an owner and due date for each.
Who should write the minutes?
Usually the organiser or a designated note-taker, agreed before the meeting rather than grabbed at the end. The note-taker doesn't have to be the most junior person — they need to understand the content and catch conclusions. A good practice: take notes live, then before everyone leaves, read the decisions and action items aloud to confirm, and send straight after.
How do I take minutes efficiently for online meetings?
Type into a shared doc (Google Docs, Notion) as the meeting runs, so everyone sees and can add. You can record or use auto-transcription as a backup, but don't paste a raw transcript as the minutes — someone still needs to distil decisions and action items. The essentials are unchanged: confirm conclusions before leaving, spell out who does what, and share the link with all attendees.