How to write meeting minutes (template + examples)

Good meeting minutes aren't a transcript - they're the short, useful record of what was decided and who's doing what next. Here's exactly what to include, a template you can copy, and a faster way to never miss a decision again.

What meeting minutes should (and shouldn't) contain

Minutes are a decision-and-action record, not a word-for-word log. Skip the small talk. Capture the things someone would need to know if they missed the meeting:

• Basics: date, attendees, and the purpose of the meeting.
• Key points: the main topics discussed, in order.
• Decisions: what was actually agreed (this is the part people forget).
• Action items: each task, its owner, and a due date.
• Follow-ups: anything deferred to next time.

A meeting minutes template you can copy

Tips for minutes people actually read

• Write decisions as decisions. "We decided to ship the mobile redesign first" beats "we discussed the redesign."
• Always name an owner. An action item without a name is a wish, not a task.
• Send them same-day. Minutes are most useful while the meeting is fresh - a quick recap email closes the loop.
• Keep it short. If it's longer than the meeting felt, no one will read it.

The faster way: let it write itself

Taking minutes by hand means you're typing instead of listening. A real-time meeting co-pilot removes the trade-off: it keeps a live transcript, then produces the minutes for you when the call ends - TL;DR, key points, decisions, action items with owners, and a ready-to-send follow-up email. No bot joins the call, and you stay present the whole time.

That's exactly what Wazomind's meeting minutes do - see how the live co-pilot works, or read why no bot joins your meeting.