# How to Write Meeting Minutes That Actually Get Used

URL: https://aginsi.com/journal/how-to-write-meeting-minutes
Type: blog
Locale: en
Published: 2026-09-24
Updated: 2026-09-24

---

> Meeting minutes serve one purpose: making sure the work discussed actually happens. Here is how to write them so they do.

The question of how to write meeting minutes rarely gets asked until something goes wrong. Three years ago, a client sent me the record from a strategy session she had attended. The document ran to 14 pages -- a near-verbatim transcript of a two-hour conversation, complete with digressions and two paragraphs on catering. The decisions were not highlighted. Nobody had followed up on any of them two weeks later.

That document was not meeting minutes. It was a transcript. The distinction matters more than most organisations acknowledge.

## Meeting minutes exist to record decisions, not conversations

The purpose of meeting minutes is narrow: confirm what was decided, identify who is responsible for each next step, and set a deadline. Anything beyond that is optional context, added only when a reader will genuinely need it to act. A 30-minute team check-in does not need four pages of prose. It needs a list of three decisions and five action items.

This sounds obvious until you sit down to write them. The instinct under time pressure is to take the notes you captured during the meeting, paste them into a document, and send the result. The output is a long, poorly structured file that nobody will read more than once. Useful minutes are concise by design, not by accident. The person writing them has to make choices about what stays and what gets cut.

A useful benchmark: if your minutes for a 60-minute meeting exceed two pages of plain text, something has been included that did not need to be. Either the context is too detailed, the discussion was transcribed rather than summarised, or the structure is absent and the content repeats itself.

## The four fields every set of minutes needs

A minimal template covers four things: meeting metadata, agenda items, decisions, and action items. That structure is sufficient for most working meetings, from weekly team check-ins to quarterly board sessions.

**Meeting metadata** includes date, time, location or platform, attendees with their roles if the group is large, and who chaired the session. This takes three lines and serves as the reference anchor when someone retrieves the document six months later.

**Agenda items** give the minutes their skeleton. Each item becomes a heading under which you record what was discussed in one or two sentences, what was decided, and what follows. If an agenda item produced no decision and no action, that observation still belongs in the record: deferred to the next meeting, further information needed, no consensus reached. Silence on a topic creates ambiguity later.

**Decisions** deserve their own formatting. A decision is not the same as a discussion point. Use a consistent visual marker -- bold text, a dedicated column in a table, or a symbol -- so a reader scanning the document can locate every decision in under 30 seconds. That 30-second test is a practical quality check: run it on your draft before sending.

**Action items** are the most important section, and the one most often done poorly. Each item names the responsible person, states what they are expected to deliver, and sets a specific date. "Leon will investigate pricing options" is not an action item. "Leon will compare three vendor quotes and share them with the group by October 3rd" is one.

![Structured meeting notes template showing decisions and action items columns](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/aginsi/2026-09/1a3924-img-inline1.webp)

## Formal and informal minutes: the difference matters

Not all minutes are equal in standing. Informal minutes, which cover most internal team meetings, are working documents: they exist to coordinate effort and can be corrected without ceremony. Formal minutes, used by boards, general assemblies, and committees with legal or regulatory obligations, carry a different weight.

Formal minutes must be approved at the following meeting, signed by the chair, and sometimes filed with a regulatory body. They use precise language around motions, seconders, and votes. They record abstentions and dissenting votes. A director who votes against a resolution will want that dissent in the record. These requirements are procedural, not stylistic -- getting them wrong has consequences.

For most of the meetings people attend at work, informal minutes are appropriate. The structure is the same; the formality is lower. Knowing which type you are writing shapes how much care you put into phrasing and how long you retain the document.

## Preparing before the meeting makes everything easier

The worst time to design your minutes template is while the meeting is already running. A pre-built structure -- even a simple table with the four sections above -- takes five minutes to prepare and saves fifteen once you are in the room.

Get the agenda in advance when one exists. Map your template fields to the agenda items. This means you arrive knowing roughly how many decision or discussion sections to expect, and you can label them before anyone speaks. When an agenda item produces no decision, you notice the gap and can prompt for clarity before the meeting closes.

Assign the note-taking role explicitly before the session starts. When everyone assumes someone else is capturing the minutes, quality drops in a predictable way: the notes are incomplete, the decisions are ambiguous, and the follow-up suffers. One person types live into the template during the meeting, then spends 15 to 20 minutes cleaning up immediately afterward. That post-meeting window is when context is sharpest.

## What a good note-taker captures during the meeting

The working rule is to capture outcomes, not process. If the group spends 20 minutes debating two options before choosing one, the minutes record the choice and the rationale in two sentences, not the debate itself. Readers who were not in the room need to understand the decision; they do not need to re-live the deliberation.

Verbatim quotes belong in two cases: when the phrasing of a decision matters for later interpretation -- legal or contractual language, for example -- or when someone made a commitment that could be disputed. In both cases, note the speaker's name and mark the quotation clearly.

Numbers anchor minutes to reality. "The team agreed on a Q4 target" is less useful than "The team set a Q4 target of 2,400 units, subject to confirmation from the operations side by October 10th." The second version is harder to misremember and harder to reinterpret after the fact.

When something is left unresolved, write that down explicitly. "No decision reached on the agency contract; deferred to the October 14th meeting pending revised proposal from the supplier" is more useful than a blank. Unresolved items have a way of disappearing from the record unless someone actively logs them.

## How to write up and circulate the minutes

The interval between the meeting ending and the minutes going out is where most of the value is lost. Minutes sent three days later are working from degraded memory and have already missed the window where they could redirect action. Same day, within the hour if the meeting is short, is the target.

Write up from your live notes, not from memory. Clean the language, remove the digressions, add any missing deadlines you can confirm from the agenda or a quick message to the relevant person. The draft should take 15 to 30 minutes for a standard 60-minute meeting. If it is taking longer, you are writing too much.

Format for scanning, not for reading. Use the section headings you prepared beforehand, bold the decisions and the action item owners, and place the action item table in a prominent position -- either at the top as a summary, or at the end as a clean reference. A participant who opens the document two hours later and needs to know what they are on the hook for should find their name and task within 60 seconds.

The subject line of the email or the document title matters more than it seems: "Minutes: Product Review Meeting 2026-09-24" is retrievable in six months. "Quick follow-up from today" is not.

![Small team in a conference room, one person taking notes on a laptop during discussion](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/aginsi/2026-09/8c1b9b-img-inline2.webp)

## When AI tools take over the transcription layer

For meetings conducted over video platforms, a category of tools now handles recording and initial transcription automatically. Choosing among them depends on what you actually need: a raw transcript, a structured summary, or an integration with the project management or CRM system where your follow-up lives.

Otter.ai produces a live collaborative transcript and assigns turns to speakers. It works well when you need the full record alongside a summary -- useful for long client meetings or sessions where accuracy of attribution matters. The free tier covers 300 minutes per month, which is enough for light or occasional use.

Granola runs as a local application, capturing microphone and system audio without joining the meeting as a visible participant. Its approach combines a brief human note during the meeting with AI expansion afterward, which preserves the writer's editorial judgment on what counted. Less intrusive for external calls.

Fireflies.ai joins as a bot, supports over 60 languages, and connects directly with CRM platforms. For teams whose follow-up process lives in HubSpot or Salesforce, the integration pushes action items directly into the right place without a manual transfer step.

tl;dv generates short video clips tied to specific moments in the transcript. When you need to share the exact context of a decision with someone who was not present, a 30-second clip anchored to the timestamp answers the question more precisely than a summary paragraph.

None of these tools replace the judgment call about significance. They produce transcripts and draft summaries; they do not decide what constitutes a decision, who carries responsibility, or what deadline is realistic. That step still belongs to a person, and it is the step that determines whether the minutes are useful.

## The mistakes that make minutes useless

Long minutes with no structure are the first failure mode. A document written as prose narration of a meeting forces every reader to reconstruct which parts are decisions and which are background. Most will stop reading before they find the action items.

Passive phrasing is the second. "It was agreed that the timeline would be reconsidered" tells you nothing about who agreed and leaves ownership ambiguous. "Elena will circulate a revised timeline by Friday" is actionable. The grammatical switch from passive to active is not a stylistic preference; it is what makes follow-up possible.

Sending minutes without a review mechanism is the third. Some organisations ask one other attendee to confirm accuracy before distribution; others open each meeting with a standing item to approve the previous session's minutes. Either method catches the misattributions and gaps that are inevitable in live note-taking.

Four days is too long. If the minutes arrive at the end of the week for a Monday meeting, the attendees have already moved on and the document is already behind the flow of events. The value of minutes is highest in the first few hours, when people are still holding the context of the conversation and can act immediately on what they read.

The minutes that get used are short, specific, and arrive fast. That is not a style preference. It is the functional definition of the document.

## FAQ

### How long should meeting minutes be?

For a standard 60-minute working meeting, two pages of plain text is a reasonable upper limit. Minutes for shorter check-ins can often be a single page. Length is determined by the number of decisions and action items, not by the duration of the meeting. If your minutes exceed two pages consistently, you are likely including discussion rather than decisions.

### Who should write meeting minutes?

One designated person should own this role for each meeting. Rotating the responsibility across attendees is common, but the role must be explicitly assigned before the session starts. Shared or unassigned responsibility reliably produces incomplete or inaccurate minutes. For recurring meetings, some teams assign a permanent secretary or note-taker.

### How quickly should meeting minutes be sent out?

Same day, ideally within one to two hours of the meeting ending. The further you get from the session, the more context degrades and the more the minutes become a reconstruction rather than a record. Minutes sent after 24 hours have already missed most of the window where they can redirect action.

### What is the difference between meeting minutes and meeting notes?

Meeting notes are informal records taken for personal use -- a capture of what was said and what you observed. Meeting minutes are the official shared record of the meeting, covering decisions and action items for all participants. Notes are a tool; minutes are a document with a formal distribution function.

### Do meeting minutes need to be approved?

For formal meetings -- board meetings, general assemblies, committee sessions -- yes. Approval typically happens at the start of the following meeting, and the minutes are signed by the chair. For informal working meetings, approval is optional and not standard practice. A confirmation reply from one other attendee is often sufficient for an informal quality check.

### Can AI tools write meeting minutes automatically?

AI meeting tools can produce transcripts and draft summaries automatically, but they do not yet replace the human judgment required to identify which items are decisions, who carries each responsibility, and what deadline is realistic. The most effective approach uses AI for transcription and a person for the editorial pass that turns a transcript into usable minutes.

### What should be included in meeting minutes?

The minimum is four fields: meeting metadata (date, time, attendees), agenda items covered, decisions made for each item, and action items with a named owner and a specific deadline. Additional context -- background discussion, supporting data, follow-up resources -- is included only when a reader will need it to act on the minutes.