Good meeting minutes answer one question: what changed in the world because we met? Decisions, owners, and dates go at the top. Discussion goes at the bottom or nowhere. Most AI templates invert this order and produce neat documents nobody opens. The template below is the one we ship in relly, tuned over hundreds of real meetings.
Why most AI meeting minutes templates fail
Most templates fail because they copy a format that was built for a different job. Paper minutes from boardrooms in the 1980s had to record who was present, who voted, and what motion passed, because they served as a legal record. That format trickled into Word templates, then into AI prompts, and now into half the meeting tools on the market.
The job of modern team minutes is different. No one is going to subpoena a Tuesday standup. The job is to make the meeting reusable: a teammate who missed the call can read for one minute and know what they need to do. Anything that gets in the way of that single read is dead weight.
When you ask a generic AI to "summarize this meeting," it gives you a five-paragraph essay because that's what its training data calls a summary. That essay is not minutes. It's an artifact that costs the next reader two minutes of scrolling and ends with three questions in their head.
The template, in one block
Here is the structure. Steal it. Paste it into your tool of choice. Or use a voice AI that fills it for you.
Title: [meeting name], [date]
One-line outcome: what changed because of this meeting
Decisions
- [Decision]. Owner: [name]. By: [date].
Open questions
- [Question]. Owner: [name]. By: [date].
Blockers
- [Blocker]. Owner: [name]. Needs: [what unblocks it].
Context (optional, 3 sentences max)
Why we met, what was on the table, what we agreed wasn't in scope.
That's the whole thing. Five fields, ranked by what a future reader needs first. No attendance roster. No verbatim quotes. No "Discussion" section that turns into a wall of text.
Why this order works
Decisions go first because they're the only thing that matters in a week
If you opened a doc from a meeting six weeks ago, you wouldn't read the discussion. You'd scan for what was decided. The template puts decisions at line one because that's where your eyes land.
Each decision is a single sentence. If it takes a paragraph to describe, it isn't a decision yet. Send it back to the team.
Open questions go second because they're the next meeting's agenda
Open questions are decisions you didn't make, with the same shape: question, owner, due date. Treating them this way means they stop disappearing. The owner knows it's their job to either answer it or escalate. The due date keeps it from drifting forever.
Blockers go third because they need help, not just tracking
A blocker is different from an open question because someone outside the meeting can probably solve it. Listing blockers explicitly, with the "needs" field, is the cheapest way to get cross-team help without scheduling a separate call.
Context goes last and almost never gets read
Three sentences, max. Why we met, what was on the table, what we explicitly said wasn't in scope. The "not in scope" line is the most useful part because it stops the same conversation from restarting next week.
What we leave out (and why)
Templates are defined as much by what they omit as by what they include. A few things we deliberately drop:
- Attendance lists. Calendar already knows who was invited. If attendance is legally required, your tool should auto-attach it as metadata, not paste it at the top of the doc.
- Verbatim transcripts. Useful for audit, useless for re-reading. Link to the recording instead. The minutes are the index, not the full text.
- Discussion sections. A summary of what was said is not a summary of what was decided. The discussion is what got us to the decisions; once we have those, the discussion is exhaust.
- Sentiment notes. "The team felt strongly that..." adds drama, not direction. If a feeling matters, it becomes a decision or an open question.
- Long agendas. The agenda lives in the calendar invite. Repeating it in the minutes is a tell that the team didn't actually finish the agenda.
Each of these existed in old paper minutes for a reason. None of those reasons apply when AI can produce a transcript on demand and the meeting is already on Zoom.
How to make AI fill it well
If you're using a generic chatbot, paste the template above as the system prompt and add: "Use only what was said in this meeting. Mark anything you can't fill with TBD and flag it for the owner. Keep total length under 400 words." That alone fixes most of the common failures.
The harder problem is that generic AI can't always tell a decision from a strong opinion. "I think we should ship Friday" is not a decision. "Let's ship Friday, Sara owns the launch" is. The template is also a forcing function for the meeting itself: if the AI can't fill the decisions field, the meeting didn't decide anything, and the team should know that.
We built relly so the meeting AI doesn't just fill the template after the call. It nudges in real time: when an hour is almost up and the decisions field is empty, the AI surfaces the gap so the team can close it before they leave the room. The template stops being a post-meeting artifact and becomes a live scoreboard.
Where the template lands
Minutes that sit in a tool no one opens are the same as no minutes. Three rules for placement:
- Wherever the team already works. If decisions live in Notion, push there. If owners check Linear every morning, the action items go to Linear. The minutes doc is the canonical source, but each section also fans out to where the work happens.
- One link, not five attachments. The link to the minutes goes in the same channel as the meeting invite. Past versions are searchable in one place.
- Tagged with the team and the topic, not the date. "May 8 standup" is useless in November. "Pricing decision, growth team" is searchable forever.
One worked example
Real shape, anonymized. A 45-minute pricing meeting:
Pricing review, May 8
Outcome: moved to two tiers, locked the launch price for early access.
Decisions
- Two tiers at launch: Team and Business. Owner: Sara. By: May 14.
- Early access price stays at 50% off for the first 12 months. Owner: Sara. By: May 9 (locked).
- Annual billing only at launch, monthly added in Q3. Owner: Mike. By: May 14.
Open questions
- Do we cap seats on Team? Owner: Sara. By: May 12.
- What's the upgrade path mid-contract? Owner: Mike. By: May 14.
Blockers
- Stripe metered billing config. Owner: Mike. Needs: finance review of the new SKUs.
Context
We met to lock pricing before the launch announcement. Three-tier model was on the table; we ruled it out as too complex for a beta cohort. Per-seat caps and discounts beyond 50% were declared out of scope.
Word count: 165. Total reading time: about 40 seconds. A teammate who missed the call now knows the new pricing structure, who owns what, and what's still unsettled.
Where relly fits
relly ships this template by default. It joins your meeting, listens, and fills the fields live. When the call ends, the doc is already in Notion, the action items are already in Linear, and the recap drops into the right Slack channel. (See how relly compares to other meeting AI tools for the full picture.)
If you're tired of meetings that end without a decision and notes that no one re-reads, early access is open through May 18, 2026, with 50% off for the first 12 months. No card needed until launch.
Common questions
What should an AI meeting minutes template include?
An AI meeting minutes template should include decisions, owners, and due dates at the top, followed by open questions, blockers, and a short context paragraph. Skip attendance lists, verbatim quotes, and section headings the team never reads. The order matters because the first thing on the page is the only thing most people scan.
Why are most AI meeting minutes templates wrong?
Most templates copy the format of paper minutes from the 1980s: attendees, agenda, discussion, action items, signed by chair. That format optimized for legal record-keeping, not team execution. AI can produce that block in three seconds, but no one reads it, so the meeting still relies on memory.
How long should AI meeting minutes be?
Aim for under 200 words for a 30-minute meeting and under 400 words for a 60-minute meeting. Anything longer is a transcript, not minutes. The job of minutes is to be re-readable in under a minute by someone who missed the call.
Can AI generate meeting minutes accurately?
Modern voice AI can identify decisions, owners, and dates with high accuracy when the meeting is structured. Accuracy drops when the meeting itself is vague, so the template doubles as a forcing function: if the AI can't fill the decision field, the team didn't decide anything.
Want minutes that fill themselves?
relly drops decisions, owners, and dates into your team's tools while the meeting is still running. Early access is open through May 18, 2026, with 50% off for your first year.
Claim early access →