Search for "meeting minutes template" and you'll find forms with fields for attendees, apologies, approval of previous minutes, and a signature line. These templates descend from board-meeting bureaucracy, and they optimize for one thing: proving the meeting happened. Nobody reads them afterwards, which is fine, because they weren't written to be read.
Working meetings need the opposite: a document whose only job is to make the next week go differently. That document is short, has a rigid skeleton, and is mostly a list of names next to verbs. Here's the template — and how to stop filling it in by hand.
Key takeaways
- Minutes die when they mirror the conversation (chronological, exhaustive) instead of the outcome (decisions, owners, deadlines).
- Four sections cover everything a working meeting produces: decisions · action items · risks and blockers · open questions.
- Every action item needs an owner and a date at the moment of writing — "someone should" is how commitments evaporate.
- The template is also exactly what AI summarization produces from a recording, which is why this document is the most automatable artifact in your workflow (product fact below).
Why most minutes are dead on arrival
The natural way to take notes is chronological: write down what was said, in order. The result reads like a diluted transcript — accurate, complete, and useless, because the reader's question is never "what was said third?" It's "what do I need to do?"
The second killer is the missing owner. Notes full of passive constructions — "the deadline will be moved", "the design should be reviewed" — record intentions without attaching them to anyone. Two weeks later, everyone remembers agreeing; nobody remembers volunteering.
The four-section template
Everything a working meeting produces fits in four blocks:
MEETING: <topic> — <date> — <participants>
DECISIONS
- <what was decided, in one sentence each>
ACTION ITEMS
- <verb + what> — @owner — by <date>
RISKS / BLOCKERS
- <what could derail the plan, who flagged it>
OPEN QUESTIONS
- <what was raised but not resolved — becomes agenda for next time>
That's the whole document. Attendees and duration are metadata, not content. The chronology lives in the recording or transcript if anyone ever needs the exact wording — the minutes link to it, they don't reproduce it.
Two rules keep the template honest. First: if a discussion produced no decision, action, risk, or question, it doesn't appear — minutes are a filter, not a mirror. Second: an action item without an owner and a date goes into "open questions" instead, because that's what it actually is.
Filling it automatically
The reason this structure matters beyond tidiness: it's machine-producible. The template above is essentially the output format of AI meeting analysis, which means the discipline nobody sustains by hand can be sustained by a pipeline.
Process a recording through MeetResult and the summary comes back already structured: what was discussed, decisions and risks extracted as key items, and next steps as action items with suggested owners and deadlines pulled from what was actually said (product facts). Summaries also adapt to the meeting type — a sales call gets accents on objections and next steps, a one-on-one on goals and blockers, a stand-up on done/planned/stuck (product fact: type is auto-detected and can be set manually).
The action items don't stop at being a list: you confirm the real ones and they move into your tracker with owners attached — the workflow covered end-to-end in how to turn a meeting recording into tasks. The transcript stays attached as the source of truth, searchable when someone asks for the exact wording.
The habit that remains manual
One thing no pipeline does for you: the last two minutes of the meeting. Read the action items out loud before everyone leaves — "so: Anna, quote by Thursday; Mark, staging access today." It takes ninety seconds, surfaces the "wait, that's not what I meant" objections while everyone is still in the room, and turns the minutes from a report about the meeting into a contract made at it. The automation handles the writing; the reading is yours.
Sources and method
Product facts (structured summary with decisions/risks as key items, next steps with suggested owners and deadlines, meeting-type-aware summary accents with auto-detection, task confirmation and tracker push, searchable transcript) describe MeetResult as documented in the product catalog at the time of writing. The template itself is editorial methodology, not a product requirement — it works on paper too. No market statistics are cited or invented.
Related: How to turn a meeting recording into tasks · Turn voice messages into structured tasks · Meeting bots vs. uploading recordings · Weekly stand-up → tasks (use case)
Skip the form-filling entirely: record your next meeting, drop the file into @meetresultbot, and get minutes in this exact structure — decisions, owners, deadlines — in minutes. New accounts include a welcome pack of free processing minutes.