Meeting minutes are the written record of what was said, decided, and assigned in a meeting. Most teams skip them or write a wall of text that nobody reads afterward. Both habits cost time later, because the same questions come back the next week and the room has to re-decide what it already settled. A plain minutes template fixes this: it tells the note-taker exactly what to capture, and it tells readers exactly where to look. Below is a template you can copy today, a filled-in example, and the mistakes that make minutes useless.
The point of minutes is not to transcript the meeting. Nobody reads a transcript. The point is to record decisions and owners so the work that follows has a paper trail. When a task slips, good minutes answer "who said they would do this and by when" in ten seconds. That is the only test that matters.
If your team also runs one-on-one meetings, keep the same discipline with a one-on-one meeting agenda so individual commitments get written down too, not just group ones. And if you report progress upward, fold the decisions from minutes into a weekly report so leadership sees what changed.
What Goes in Meeting Minutes
Minutes are short by design. They answer five questions, and nothing else:
- Who was there. Names of attendees and who ran the meeting. Note absences only if the missing person owned an open item.
- What was decided. Every conclusion the group reached, written as a fact, not a discussion. "Approved the Q3 budget" not "talked about budget."
- What was assigned. Each task with a name and a date. A decision without an owner is a wish.
- What was deferred. Topics pushed to a later date, with the reason. This stops them from being forgotten and re-litigated.
- When you meet again. The next date, or a note that none was set.
Keep the writing flat. Past tense for decisions, present tense for open items. No adjectives about how the meeting "felt." The reader needs facts they can act on, not a mood report. Aim for one to two pages. If your minutes run longer, you are summarizing the talk instead of recording the output.
Template
MEETING MINUTES
Date: [YYYY-MM-DD]
Attendees: [Name, Name, Name]
Facilitator: [Name]
1. DECISIONS
- [Decision] — agreed by [attendees], no objection from [name]
- [Decision] — tabled pending [input needed]
2. ACTION ITEMS
- [Task] — Owner: [Name] — Due: [YYYY-MM-DD]
- [Task] — Owner: [Name] — Due: [YYYY-MM-DD]
3. DEFERRED
- [Topic] — moved to [date], reason: [why]
4. NEXT MEETING
- [Date] or "no follow-up scheduled"
Notes: [one line on the meeting's main outcome]
Real Example
MEETING MINUTES
Date: 2026-04-08
Attendees: Priya, Tom, Lena, Sam
Facilitator: Priya
1. DECISIONS
- Launched the new onboarding flow on May 1, agreed by all, no objection
- Dropped the SMS reminder feature for Q2 to free up two engineers
2. ACTION ITEMS
- Write the launch announcement — Owner: Tom — Due: 2026-04-15
- Migrate user data to the new schema — Owner: Lena — Due: 2026-04-22
- Brief support team on the change — Owner: Sam — Due: 2026-04-25
3. DEFERRED
- Pricing page redesign — moved to June, reason: waiting on finance sign-off
4. NEXT MEETING
- 2026-04-29
Notes: Team aligned on scope; the main risk is the data migration timeline.
Priya's minutes work because every line names an owner and a date. The deferred item has a reason, so it will not sneak back into next week as if it were new. The "Notes" line gives a reader who skipped the rest the one thing to watch.
Common Mistakes
- Writing a transcript. Capturing who said what and how they said it buries the decisions. Record outcomes, not the conversation.
- Leaving action items without owners. "The team will follow up" means nobody will. A task needs one name or it dies.
- Using future tense for decisions. "We will launch on May 1" reads as a plan. Once agreed, write "Launched May 1." The tense tells the reader it is settled.
- Forgetting deferred items. Topics that got pushed with no record come back as new debates, and the group re-fights old ground.
- Sending minutes late. Minutes sent three days after the meeting arrive after people have already acted on memory. Send them the same day while details are fresh.
- Keeping them in a chat thread. A wall of chat messages is not searchable minutes. Put them in one document everyone can find, or the trail disappears when someone leaves.
Take the Next Step
Copy the template above into your notes app and run your next meeting through it. After the call, spend five minutes filling in decisions and owners before you do anything else — the details are sharpest right then. If your meetings produce notes you want to turn into a standing record, pair this with how to write meeting notes for the lighter format used in working sessions. For the wider habit of keeping leadership informed, a weekly report picks up where minutes leave off.
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →