---
title: "Meeting Minutes Template: The Structure That Survives Real Use"
description: "Six copy-paste meeting minutes templates, decisions-first, from the team whose AI writes minutes daily. Plus when the formal format is required."
canonical: "https://hirekai.ai/blog/meeting-minutes-template"
date_published: "2026-07-07"
last_updated: "2026-07-07"
article_type: "guide"
author: "lambert"
---
# Meeting Minutes Template: The Structure That Survives Real Use

### Key takeaways

- Most meeting minutes templates are compliance documents in disguise: attendance and ceremony first, decisions buried at the bottom. People fill them for a week, then stop.
- The structure that survives is decisions-first: what was decided (exact wording), who owns what by when, what stayed open. Even Robert's Rules agrees the record is "what was done, not what was said."
- Grab the template that matches your meeting: default, client call, one-on-one, standup, decision meeting, or the formal board variant for when the ceremony is legally required.
- A template fixes the structure, not the labor. Someone still has to fill it after every call, which is exactly the part worth automating.

I work on Kai, an AI executive assistant that turns live meetings into minutes, so I spend an unusual amount of time reading the minutes of other people's meetings. Here is the pattern that took me too long to see: the meeting minutes templates that rank on Google are not designed to be read. They are designed to look official. Attendance first, approval of the previous minutes, reports, old business, new business, and somewhere near the bottom, the only things anyone will ever come back for: what was decided, who owns what, and by when.

That ordering is why templates get abandoned. You fill in the ceremony for a week, nobody reads it ([the author of Zapier's own template roundup describes exactly this fate](https://zapier.com/blog/meeting-minutes-template/)), and the document quietly dies. The structure that survives contact with real meetings is the inverse: decisions at the top, owners and deadlines attached, ceremony demoted to a footer. We did not arrive there by intuition. The summary format behind Kai converged on that shape after processing real calls every day, and, more surprisingly, the formal rulebooks have said it all along.

This guide gives you that structure as six copy-paste templates, one per meeting type. It also covers the one case where the formal, compliance-heavy format genuinely is required, because that case exists and most template roundups pretend it does not.

## The template, first

You came here for a template, so here is the default before any theory. It works for most recurring work meetings: project syncs, team meetings, working sessions.

### The default, action-first

```markdown
# Meeting minutes template: [meeting name]

## Decisions made
- [Decision, in the exact wording the group agreed to]
- [Decision]

## Action items
- [ ] [Verb-first action] · Owner: [name] · Due: [date]
- [ ] [Verb-first action] · Owner: [name] · Due: [date]

## Open questions
- [Anything discussed but NOT decided. Do not dress it up as a decision.]

## Topics, one line each
- [Topic]: [one-line gist]

---
Meeting: [date, time] · Attendees: [names] · Next meeting: [date]
```

Three rules make this template work, and they are the three rules the abandoned templates break:

1. **Decisions carry their exact wording.** "We discussed the launch" is not a record. "Launch moves to March 3, Sara owns the announcement" is. If you cannot write the sentence, the group did not actually decide, and the item belongs under open questions.
2. **No action item without an owner and a date.** An unowned action item is a wish. Write it verb-first ("Send the revised proposal", not "Proposal follow-up") so it can move straight into a task list.
3. **Ceremony is a footer.** Date, attendees, next meeting: 30 seconds at the bottom. Not the opening act.

If you want this filled in for you from a transcript, our free [meeting minutes generator](/tools/meeting-minutes-generator) produces this exact structure in the browser. And if the meeting does not exist yet, start one step earlier with the [meeting agenda generator](/tools/meeting-agenda-generator): an agenda with owners makes the minutes half-written before the call starts.

## Why most meeting minutes templates die after a week

Open the top results for this keyword and count where "decisions" appears in each template. In the galleries of Word and Canva templates, and in most of the listicle roundups, the order runs: meeting title, date, location, attendees, absentees, agenda, discussion notes, and then decisions and action items at the bottom. The document is structured like a court transcript, not like a tool.

The templates are copying a format that was never meant for everyday work meetings. Formal minutes come from parliamentary procedure and corporate law, and here is the irony: even the strictest rulebook does not ask for the narrative bloat. Robert's Rules of Order, the standard for formal meetings, is blunt about it: ["The minutes should contain mainly a record of what was done at the meeting, not what was said by the members"](https://www.jimslaughter.com/minutes) (RONR, 12th edition, 48:2). The companion guide goes further, noting that [secretaries "make unneeded work for themselves by putting far more into the minutes than is required or appropriate"](https://acadgov.msu.edu/about/commentsfromthefloor/minutescontent).

So the attendance-and-narrative format is not even compliance. It is ceremony that got mistaken for rigor, and it produces documents nobody reads. The writer of Zapier's own template roundup admits as much about her student-government days: ["members never read them and usually forgot what they'd discussed in their meetings the next day... minutes were kept in a scattered Word Doc and could put a civics professor to sleep"](https://zapier.com/blog/meeting-minutes-template/).

The cost of the dead document is not abstract. In [iBabs' 2024 State of Meeting Management survey](https://www.ibabs.com/en/tools-templates/) of over 2,000 respondents, fewer than half felt that action points from meetings were adequately followed up on, and only 65% confirmed minutes are taken and distributed at all. [Atlassian's 2024 State of Teams report](https://www.atlassian.com/blog/workplace-woes-meetings), surveying 5,000 knowledge workers, found meetings ineffective at their basic jobs 72% of the time. A template whose structure hides the decisions is part of that machinery.

There is a real person on the receiving end of the bad format. In a thread on r/ExecutiveAssistants that ranks on page one for this exact keyword, an EA assigned to take weekly minutes describes the template she was handed, in March 2025: ["The template I was originally given was just TITLE, 1.1.1, LEAD BY. Nothing for discussion, or tasks etc."](https://www.reddit.com/r/ExecutiveAssistants/comments/1jo538p/meeting_minutes_templates/) Numbering and formality, no place for what was decided or who does what. Her execs "just like to ramble on with very little format." That is the gap between templates that look official and templates that help.

## The anatomy of minutes that survive

Here is the same meeting recorded two ways.

![The same meeting in two templates: the compliance-first version opens with call to order, attendance, approval of previous minutes, reports and old business, with decisions buried at the bottom without owner or date, and gets abandoned after a week; the action-first version opens with decisions made in exact wording, action items with owner and deadline, then open questions, one-line topics, and a 30-second footer for date and attendees](/blog/images/meeting-minutes-template/minutes-anatomy-schema.webp)

The surviving structure has four load-bearing parts, in this order:

**Decisions made, in exact wording.** The whole point of minutes is that six months later, nobody re-litigates. That only works if the decision is written as the sentence the group agreed to, not as a topic label. This is also where most drafts cheat: "reconsider dropping the feature" is not a decision, it is a question wearing a decision's clothes. We caught exactly that phrase in one of our own AI-drafted recaps, which is why the review pass exists.

**Action items with owner and date.** One user review of board software on Capterra names the failure this section prevents: ["Actions no longer get lost in the minutes because we all have full visibility on the list of open action items"](https://www.capterra.com/p/180383/iBabs/reviews/). Actions get lost in prose. A checklist with names does not scan away.

**Open questions.** The most underrated section. Without it, unresolved threads either disappear or get promoted into fake decisions. With it, the next meeting's agenda writes itself.

**Topics, one line each.** Context for the person who was not there, compressed. If someone needs the full story, that is what the transcript or recording is for, not the minutes.

I learned the value of the open-questions section the slow way, from years of writing minutes by hand before working on Kai. The recurring failure in project-scoping meetings was never the big items: it was the small tasks mentioned in passing that made it into nobody's list, and the brainstorm ideas that evaporated because they were neither decisions nor actions, so the template had no shelf for them. Open questions is that shelf.

## Templates by meeting type

One structure does not fit every meeting, a complaint real users make about one-size template kits. The five variants below keep the decisions-first skeleton and adapt the sections to what each meeting type actually produces.

### Client or investor one-on-one

The highest-stakes minutes most of us write, and the variant I use most: when I talk to potential clients, the recap is what keeps both sides honest about what was agreed.

### Client or investor 1:1

```markdown
# Call notes: [name, company] · [date]

## What we agreed
- [Commitment, in plain words both sides would sign]

## What you'll get from us
- [ ] [Deliverable] · by [date]

## What we're waiting on
- [ ] [Their input, decision, or intro]

## Next step
- [The one concrete next step and its date]
```

Two deliberate omissions. There is no "discussion summary" section: a client-facing recap that narrates the whole conversation reads like surveillance, not service. And nothing goes in that you would not want quoted back. Send it within 24 hours, in the body of the email, not as an attachment.

> A lesson from my own client calls: a recap that is too complete can spook the other side. I once caught myself retyping a recap by hand to remove detail, because a complete machine-perfect note would have told an older, AI-wary client that everything he said had been captured. Curate what you send. The full record is for you; the recap is for the relationship.

### Internal one-on-one

A running document, not a fresh file per meeting. Keep one per person, newest entry on top, so commitments carry over instead of resetting.

### Internal 1:1 (running doc)

```markdown
# 1:1 · [name] · [date]

## Decisions
- [Anything we settled]

## Commitments
- [ ] Mine: [action] · by [date]
- [ ] Theirs: [action] · by [date]

## Carried from last time
- [ ] [Still-open commitment, with its original date]

## Parking lot
- [Topics for next time]
```

The "carried from last time" section is the whole value. A one-on-one where commitments silently expire teaches both people that the meeting is theater.

### Standup or project status

Blockers and changes only. If the standup minutes take longer to write than the standup took to hold, the template is wrong.

### Standup or project status

```markdown
# Standup · [team] · [date]

## Blockers
- [Blocker] · unblocking owner: [name]

## Changed since yesterday
- [Only what changed. No status recitals.]

## Decisions
- [Rare in standups. When one happens, it goes here.]
```

### Decision meeting or steering

The one variant where recording the "why" matters as much as the "what", because these decisions get challenged later.

### Decision meeting or steering

```markdown
# Decision record: [topic] · [date]

## The decision
[Exact wording. One sentence if possible.]

## Options considered
- [Option A] · rejected because [reason]
- [Option B] · chosen because [reason]

## Dissent
- [Who disagreed and why. Recording it is what makes the decision stick.]

## Action items
- [ ] [Action] · Owner: [name] · Due: [date]

## Revisit when
[The condition that would reopen this decision]
```

The dissent section looks confrontational and does the opposite: a recorded objection is an objection that does not need relitigating in the hallway.

### Board or formal meeting (the compliance variant)

Sometimes the ceremony is the law. Corporate boards, nonprofits, public bodies, and HOAs have real requirements: Delaware corporate law assigns an officer the [duty to record the proceedings of board meetings](https://www.acc.com/resource-library/quickcounsel-minutes), the IRS asks nonprofits on [Form 990 whether board minutes are documented contemporaneously](https://minnesotanonprofits.org/resources-tools/topics/finance-legal/meeting-documentation-on-the-form-990), and state open-meeting laws prescribe minimum contents down to [how each member voted](https://www.openrecords.pa.gov/SunshineAct.cfm). For those bodies, use this:

### Board or formal meeting

```markdown
# Minutes · [body name], [regular/special] meeting

Kind of meeting: [regular / special] · Date, time, place: [...]
Present: [chair, secretary or substitutes; members present; quorum: yes/no]
Previous minutes: [approved / approved as corrected]

## Motions
1. Motion: "[exact wording as stated]"
   Moved by: [name] · Disposition: [adopted / rejected / postponed]
   Vote: [counted result if a count was ordered; roll call only if taken]

## Reports
- [Report name, presenter. One line. Attach the report; do not summarize it.]

## Announcements / notices of motion
- [...]

Adjourned: [time] · Next meeting: [date]
Submitted by: [secretary name]
```

Notice what is still missing, on purpose: discussion summaries and who-said-what. We did not invent that omission: [Robert's Rules itself instructs it](https://www.jimslaughter.com/minutes). Even the compliance format is decisions-first once you strip the cargo cult. The exact statutory fields vary by state and body type, so check your own statute or bylaws before adopting this as-is.

## Meeting minutes vs meeting notes: pick the right tool

The two terms get used interchangeably and they are different documents. A quick test: who is the reader?

| | Meeting notes | Meeting minutes |
|---|---|---|
| Reader | You | The group, including absentees |
| Register | Informal, personal shorthand | Shared record, sometimes official |
| Content | Whatever helps you act | Decisions, actions, votes |
| Lifespan | Until the follow-up is done | Archived, sometimes legally retained |
| Approval | Never | Formal bodies approve them next meeting |

If you are capturing for yourself, you want a notes workflow, not a minutes template, and we wrote a separate guide on [how to take meeting notes](/blog/how-to-take-meeting-notes) for exactly that. If you produce the record the group relies on, minutes, and this page's templates apply. The confusion is old enough that "meeting notes template" and "meeting minutes template" have become near-synonyms in search, but the reader test never fails: notes serve the writer, minutes serve the room.

For the full writing process around the artifact, from listening to distribution, see [how to write meeting minutes](/blog/how-to-write-meeting-minutes). For running the meeting so there is something decision-shaped to record in the first place, start with [how to run a meeting](/blog/how-to-run-a-meeting) and [AI meeting prep](/blog/ai-meeting-prep).

## A template fixes the structure, not the labor

Here is the part the template pages do not say out loud: the blank template is the easy 10%. The other 90% is a person, usually the most junior one in the room, reconstructing the meeting from memory afterward, retyping action items into a task tool, and chasing the recap email. The EA in that Reddit thread was not missing a document format. She was assigned a labor problem shaped like a formatting problem.

![Who fills the template: the relay path where the call ends, you fill the template from memory at roughly 45 minutes per meeting, then retype every action item into your task app and the recap goes out three days late or never, versus the captured path where the structure is already drafted when the call ends, you review and correct it in 10 to 15 minutes, action items land as tasks with owner and due date, and the recap is sent minutes after the call](/blog/images/meeting-minutes-template/minutes-relay-schema.webp)

I lived on the left side of that diagram. With 8 to 10 meetings a week, a proper recap used to cost me a solid 45 minutes each: reconstruct, structure, retype the actions, write the email. The structure was never the hard part. Holding the whole meeting in your head at 6pm was.

This is where the 2026 answer diverges from the 2019 answer. The 2019 answer was "discipline": fill the template live, or right after. The 2026 answer is that AI note-takers, [Granola](/blog/granola-review), [Otter, Fathom](/blog/fathom-vs-otter), and [the rest of the field](/blog/otter-ai-alternatives), already produce a decisions-and-actions draft from the transcript. Interestingly, their default output converged on the same decisions-first shape this article argues for; the AI era quietly standardized the surviving structure while the template galleries stayed frozen in the compliance era. If your calls happen where recording is appropriate (check the [consent rules](/blog/ai-meetings-consent) first), the draft is free. Your job compresses to review: correct what the machine hedged on, add what only a participant knows, send.

## How we automated our own minutes with Kai

Since we build [Kai's meeting capture](/meetings), our own minutes run through it, so here is the honest version of what that looks like on a real meeting, including the part where I still have to do work.

Kai captures the call from my own device on Zoom, Google Meet, Teams, Webex, and Slack Huddles, with no bot joining the room. When the meeting ends, the summary is already structured the way this article recommends, because that structure is enforced in the product: Topics Discussed, Decisions Made, Next Steps, with action items extracted separately, each with an assignee, a due date, and a priority, split into "assigned to you" and "assigned to others." The extraction rules are strict on purpose: action items are written verb-first, and if the AI cannot confidently tell who owns one, it leaves the owner empty rather than guessing a name.

Then I hand the meeting to "Email participants" and Kai proposes the recap email itself: pre-addressed to everyone who was on the call, drafted in my tone because it checks how I have written to these people before. The draft is a starting point you steer in chat, in plain language. You can adapt it to the audience (a client gets a tighter, curated version than the internal team), or keep the base structure and rework the content around it: for one investor call I added "let him know I'll be in Zurich next week if he wants to meet in person," and the line went in before sending.

The structure itself is teachable too. Tell Kai in the chat that you want your recaps in a specific template, the same way you would brief a human assistant, and it saves that preference to Kai memories, the editable knowledge it keeps about how you communicate. The next meeting's draft comes out already in your format instead of the default one.

![Kai right after a meeting: the Summary and Tasks view lists the extracted action items with owners and due dates, and in the chat a draft email titled Meeting Minutes is ready to send to the participants, updated with a personal line the author asked Kai to add](/blog/images/meeting-minutes-template/kai-minutes-draft-email.webp)

What the other side receives is a normal email in my tone, structured like the default template above: topics, decisions, action items with owners and priorities.

![The recap email as participants receive it in Gmail: Topics Discussed with one short block per topic, Decisions Made as a short list, and Action Items with owner and priority, ending with a personal line about meeting in Zurich](/blog/images/meeting-minutes-template/minutes-recap-email-received.webp)

My 45 minutes per meeting became 10 to 15: around five to read and correct the draft, five for a human check of the recap, five more if something needs adjusting. The review pass is not optional politeness, it catches real things. In the recap above, the draft had listed a scheduled sync both as a decision and as an action item, and phrased one open question ("reconsider dropping the feature") as if it were settled. Two minutes to fix, but only a participant would have noticed.

The honest limitation: Kai's minutes leave the product by clipboard, email, or a public share link, and that is it. There is no PDF or Word export. For the everyday meetings that make up my week, that covers everything. But a board secretary who must file a signed document has to paste Kai's output into the formal template above; Kai drafts the record, it does not produce the filing. Related: on the web app Kai captures your microphone only, so for full both-sides capture you want the desktop app.

That draft-not-filing distinction is also where governance lawyers have landed on AI minutes generally, which the FAQ below gets into.

## FAQ

## Frequently asked questions

### What is the standard format for meeting minutes?

For formal bodies, the standard is Robert's Rules: kind of meeting, date and place, attendance, approval of previous minutes, then each motion with its exact wording, mover, and disposition, and counted votes when ordered. For everyday work meetings there is no legal standard, which is why we recommend the action-first format: decisions with exact wording, action items with owner and date, open questions, then one line per topic, with logistics as a footer.

### Is an AI-generated summary a valid official meeting minute?

Treat it as a draft, not the record. Governance counsel converges on this: [automatic transcripts must still be edited into proper minutes](https://www.wagenmakerlaw.com/blog/always-listening-ai-automatic-note-takers-and-related-risks), and boards are advised to [treat AI outputs as drafts requiring verification](https://www.directorsandboards.com/board-issues/ai/ai-board-minutes-and-confidentiality/) before anything becomes official. Verbatim AI records also carry discovery and privilege risks that curated minutes avoid, and recording itself requires consent in [all-party-consent states](/blog/ai-meetings-consent). A human approves the record; the AI writes the draft.

### What should meeting minutes NOT include?

What was said, as opposed to what was done. Robert's Rules is explicit that debate summaries and members' remarks stay out, and for guest speakers "no effort should be made to summarize" their remarks. Practically: no discussion narratives, no opinions, no who-said-what, nothing you would not want read back in a dispute. Decisions, actions, votes, open questions. That is the record.

### How soon after a meeting should minutes be sent?

Within 24 hours for working meetings, and for client calls the same day if you can. The IRS's contemporaneous-documentation standard for nonprofit boards allows until the next meeting or 60 days, but that is a floor for compliance, not a target for usefulness. A recap that arrives three days late arrives after memories have already diverged. There is also an upper speed limit nobody mentions: with AI drafting, my recap is ready ten minutes after the call, and I learned that a long, perfectly structured email landing that fast unsettles an AI-wary client. How does he remember everything? So I schedule those sends for about two hours after the meeting. Fast enough to be useful, slow enough to feel human.

### Do I need a different template for every meeting type?

You need one skeleton and a few variants, not a 28-template library. Decisions, actions with owners, open questions: that core does not change. What changes by meeting type is which extra section earns its place: dissent and rationale for decision meetings, carried-over commitments for one-on-ones, motions and votes for boards. The six templates above cover the types most people actually run; if your meeting is not one of them, start from the default and delete what stays empty. Meetings are also expensive enough to deserve the check: our [meeting cost calculator](/tools/meeting-cost-calculator) puts a number on the room before you even open the template.

### How do I get minutes out of a meeting I couldn't attend?

Ask for the decisions and action items, not "the notes." If the meeting was captured, a tool like our free [meeting transcription tool](/tools/meeting-transcription) plus the [minutes generator](/tools/meeting-minutes-generator) turns the recording into the structured record; the skill of extracting a usable record from a call is the same one [good executive assistants](/blog/executive-assistant-skills) have always had, the tooling just moved.

## Sitemap

See the full [sitemap](https://hirekai.ai/sitemap.md) for all pages.