meeting minutes

How to take meeting minutes automatically — and keep them minutes, not a transcript

By Jack Jay · 7 November 2026 · 3 min read

Here's the thing most people get wrong about meeting minutes: they aren't a record of the conversation. Michigan State University's guide to writing minutes, which follows Robert's Rules of Order, puts it in one line: "Minutes should contain mainly a record of what was done at the meeting, not what was said by the members."

That's good news if you want them taken automatically. A machine that writes down every word gives you a transcript, and a transcript is the raw material, not the minutes. The job is to pull out what was done.

What goes in the minutes

For a formal body, like a board, a council or a committee, the usual list from MSU's guide is:

  • The date, start time and place, and who presided
  • Approval of the agenda and of the previous minutes
  • Every main motion and what happened to it, including the vote
  • Who made each motion
  • The time the meeting ended

The City of Madison's guide for its committees adds attendance, so a quorum can be shown, and warns: "Under no circumstances should you attempt to be a stenographer." (City of Madison)

For an ordinary team meeting, the same idea gets lighter: who was there, what was decided, who is doing what next, and what is still open.

A template

[Meeting name], [date], [start time] to [end time] Present: [names] Chair: [name] Minutes: [name]

Decisions

  1. [What was decided, in one sentence.] Proposed by [name]. [Agreed / vote result.]

Action items

  • [Name]: [verb + what] by [date]

Open questions (carried to the next meeting)

  • [The question], raised by [name]

Next meeting: [date]

How automatic minutes go wrong

AI can draft this from a recording in seconds. It also tends to fail in three predictable ways, and each one matters more in minutes than anywhere else, because minutes become the official memory.

1. The wrong name on a decision. Most tools transcribe one mixed recording of the whole room and then guess who was speaking. When the guess is wrong, the minutes say someone proposed something they never proposed. More on why this happens in why AI notes put the wrong name on what was said.

2. A discussion written up as a decision. "We talked about moving the launch" quietly becomes "the team decided to move the launch." If you can't point to the moment someone agreed, it's an open question, not a decision. A decision log helps keep the line clear.

3. Details that were never said. Summaries fill gaps with plausible dates, numbers and owners. Before minutes go out, every decision and action item should trace back to words someone actually spoke. Here's how to check an AI meeting summary quickly.

Doing it in Meetful

Meetful was built so the draft can't take those shortcuts:

  • Each person's microphone is transcribed on its own. The name on a line is the microphone it came from, not a guess about a voice.
  • Every line of the draft carries its evidence. After the call, open the meeting and go to Make. Decision log lists only what was actually decided or agreed, with who agreed it. One-page brief gives context, decisions, open questions and next steps for someone who wasn't there. Each line about the meeting comes with the exact words it was built on, checked against the transcript, and a line whose words can't be found is dropped.
  • Action items have owners. They're pulled out with the person who took them on.

Copy the result into your minutes template, or download it as a Markdown file. It's free on every plan, and calls have no time limit.

For a formal body, the AI draft is still a draft. The secretary checks it, and the body approves the minutes at its next meeting, as it always has. What changes is that the secretary starts from the decisions instead of from a blank page.

Start a meeting and try it on your next one.

Sources

Read next

← All posts