How to Write Meeting Minutes in 2026 (Template, Rules, and What AI Can Actually Do)

Meeting minutes need to capture exactly four things: what was decided, what happens next (the action items, each with an owner and a deadline), who was present, and the date and time the meeting took place. That's the core of it. Everything else — a summary of the discussion, an agenda reference, a note on what was tabled for later — is useful context, but those four elements are what make minutes actually function as a record rather than a diary entry. If you write nothing else down, write those.

The rest of this guide works through the questions that come right after that one: what exactly to include, how formal your minutes need to be, a template you can copy, whether they're legally required, how minutes differ from notes and transcripts, the mistakes that make minutes useless six months later, and whether it's actually fine to let AI write them now.

What should meeting minutes include?

A complete set of minutes, for almost any kind of meeting, covers the following ground. Not every meeting needs every item — a weekly team sync doesn't need a quorum count — but this is the full checklist to draw from:

• Meeting metadata — organization or team name, date, start and end time, location or call link.
• Attendees and absentees — who was present, who was invited but absent, and (for formal meetings) who chaired and who took the minutes.
• Approval of prior minutes — for recurring or governance meetings, a note that the previous meeting's minutes were reviewed and approved, with any corrections.
• Decisions made — the actual outcome of each discussion item, stated as a fact ("the team approved the Q3 budget") not a debate transcript.
• Action items — each one with a named owner and a due date. An action item with no owner is not an action item, it's a wish.
• Votes, where applicable — the motion, who moved and seconded it (in formal settings), and the result.
• Next meeting — date, if already set, or who's responsible for scheduling it.

Notice what's missing: a play-by-play of who argued for what. Minutes record outcomes, not debate. That distinction is the single biggest thing people get wrong, and it's worth its own section below.

Formal vs. informal meeting minutes

How formal your minutes need to be depends entirely on what the meeting is for, not on how important it feels in the room.

Formal minutes apply to governance bodies: boards of directors, nonprofit boards, HOAs, committees operating under bylaws, and any meeting where a documented decision has legal or fiduciary weight. These typically follow Robert's Rules of Order or a similar parliamentary procedure, and the minutes reflect that structure precisely: motions are recorded verbatim ("Jane Doe moved to approve the 2027 budget as presented"), the name of who seconded the motion, and the vote count or consensus result. Formal minutes are written in a neutral, almost legal register — they record what happened, not how anyone felt about it, and they're typically approved as an agenda item at the start of the next meeting before being filed as the official record.

Informal minutes cover everything else: team meetings, project syncs, client calls, one-on-ones. There's no parliamentary structure to follow, no motions, usually no vote. What survives from the formal model is the underlying discipline — decisions, owners, dates — just delivered in plain, readable prose instead of procedural language. If you've ever gotten a meeting follow-up email with a clean "here's what we decided, here's who's doing what" structure, that's informal minutes doing their job well.

A simple meeting minutes template

This structure works for the vast majority of business meetings, formal or not, and it maps cleanly onto Robert's Rules if you need to dress it up further:

1. Header: meeting name, date, time, location/link, attendees, absentees.
2. Approval of previous minutes (recurring meetings only): approved as written / approved with corrections.
3. Agenda item 1: one-line summary of the topic, the decision reached, and any action items with owner + due date.
4. Agenda item 2, 3, ...: repeat the same pattern for each topic discussed.
5. Open items / parking lot: anything raised but not resolved, so it doesn't quietly disappear.
6. Next steps: full list of action items pulled together in one place, plus the next meeting date.

Meeting minutes vs. notes vs. transcript: what's the difference?

These three get used interchangeably in casual conversation, but they're genuinely different artifacts, built for different purposes and different audiences.

In practice, the three build on each other: a transcript is the raw material, notes are what one person pulls from it while it's happening, and minutes are the polished, agreed-upon summary that becomes the official record. The mistake is treating any one of them as a substitute for the others — a full transcript isn't minutes (nobody wants to read forty pages to find the one decision that mattered), and quick personal notes aren't a reliable record (they reflect what one person noticed, not what the group agreed to). For meetings that don't need an official record at all, plain notes are often enough — see our guide on taking notes in one-on-ones for that lighter-weight case.

Are meeting minutes legally required?

Sometimes, yes — and it depends heavily on the type of meeting, not just the fact that people met.

• Corporate boards: in most jurisdictions, corporate law requires companies to keep minutes of board of directors' meetings and shareholder meetings as part of the corporate record. They don't need to be filed with a government agency in most cases, but they need to exist, be retained, and be produced if the company is ever audited, sued, or sold.
• Nonprofits: nonprofit boards generally carry the same requirement — minutes documenting board decisions are standard practice for maintaining nonprofit status and satisfying grantors, auditors, and the IRS in the US (or equivalent regulators elsewhere).
• HOAs, condo associations, and public bodies: many are legally required to keep and, in some cases, publish minutes, since these bodies operate under statutes that treat their decisions as matters of public or member record.
• Regular team and work meetings: no. There's no legal requirement to take minutes of a weekly standup, a project check-in, or a client call. Any documentation there is a business choice, not a compliance one — useful for accountability, not mandated by law.

The line, roughly, is fiduciary responsibility: if a group of people is making decisions on behalf of an organization with legal obligations to its shareholders, members, or the public, minutes are part of how that responsibility gets documented and defended later. If a group of people is just doing their jobs, minutes are a courtesy to future-you, not a legal obligation.

Common mistakes people make writing minutes

• Recording opinions instead of decisions. "Sarah felt strongly that we should delay launch" is not a decision. "The team agreed to delay launch to March 3rd" is. Minutes exist to capture what was resolved, not who said what.
• Action items with no owner. An action item that just says "follow up on vendor contract" with nobody attached to it will not get done, and nobody will feel responsible when it doesn't.
• No due dates. An owner without a deadline just means the task moves to next week's meeting, indefinitely.
• Writing minutes days later, from memory. Details compress and specifics blur fast — this is well documented in memory research and it's exactly why people forget meetings almost as soon as they end. Minutes written the same day are dramatically more accurate than minutes written from a foggy recollection on Friday.
• Skipping the recap send. Minutes that live in a drafts folder or a private doc nobody's notified about might as well not exist. The whole point is that people who need the record can find it.
• Confusing minutes with a transcript. Nobody needs, or will read, a full verbatim record of a one-hour discussion. If everything is highlighted, nothing is.

The part nobody tells you: writing minutes while running the meeting

Here's the honest problem with almost every meeting-minutes guide, including the template above: it assumes someone can simultaneously participate in a discussion and produce an accurate, well-structured record of it in real time. In practice, that's the hardest part of the whole job. The person taking minutes either has to disengage from the actual conversation to write, or engage fully and reconstruct the minutes afterward from a half-remembered outline — and reconstruction is where decisions get fuzzy, action items get dropped, and "I think we agreed to..." creeps into what's supposed to be a factual record.

The fix isn't a better template. It's separating the two jobs — capturing what was said, and writing the minutes — so a person only has to do the second one. Meetly records and transcribes meetings directly on your iPhone, with no bot joining the call and nothing uploaded to a cloud. You get a full, accurate transcript to work from afterward, which turns writing minutes from a memory exercise into an editing exercise: you're pulling decisions and action items out of a record that's already complete, instead of trying to remember what was said while you were also busy participating.

Should AI write your meeting minutes now?

AI is genuinely good at one part of this and genuinely bad at another, and it's worth being precise about which is which. AI summarization tools are strong at compressing a transcript into a readable overview and pulling out candidate action items — that's pattern extraction from text, and it's the kind of task large language models handle well. What they're not reliably good at is judgment: knowing that "we should probably look into this eventually" wasn't actually a decision, or that the offhand comment from the VP outweighs the longer debate that preceded it, or that a legally sensitive board resolution needs to be worded with precision rather than paraphrased for readability.

The practical answer is a hybrid: let AI turn the raw transcript into a first-pass draft — decisions, action items, owners, all pre-populated — and have a human review and correct it before it becomes the official record, especially for anything formal. That's a meaningfully different workflow from either extreme (fully manual minute-taking, or trusting an AI notetaker output unread), and it's also the one that actually holds up when someone questions a decision six months later. For governance and board minutes specifically, keep a human in the loop on the final wording — the legal weight those documents carry is exactly the case where "AI got 95% of it right" isn't good enough.

For everything else — team meetings, project syncs, client calls — a good AI-assisted draft, lightly reviewed before it's sent, is not just acceptable, it's now the more accurate option in most cases, simply because it isn't relying on anyone's memory of a conversation that happened an hour ago.

Meeting minutes: frequently asked questions