How to Write Meeting Minutes That People Actually Read

The transcript trap

Most minutes fail for a structural reason, not a writing-quality reason. Whoever's taking notes tries to capture the conversation chronologically — who raised what point, who pushed back, how the discussion evolved — because that's what happened in front of them. The result reads like a court transcript: accurate, exhaustive, and useless to anyone trying to figure out what to do next.

The test is simple. If someone has to read three paragraphs to find out whether a decision was made, the format has already failed. Discussion is the process; minutes are the output. Conflating the two is why most minutes get skimmed once and never opened again.

Three things worth writing down

Everything else in a meeting is disposable once the meeting ends. These three categories are the only things that need to survive it, and they map directly onto the questions someone asks when they open old minutes weeks later.

Decisions record what changed and why, so nobody re-litigates a call that's already been made. Owners record who is accountable for what happens next, so action doesn't quietly evaporate. Open questions record what's still unresolved, so the next meeting starts from where this one left off instead of re-discovering the same gap.

• Decisions — what was decided, in one line, with the reasoning if it isn't obvious
• Owners — who is responsible for the next step, by name, not by team
• Open questions — what's still unresolved, with a target date for resolving it

A format that actually holds up

Write each decision as a single line: what was decided, who decided it, and why — only if the why isn't self-evident from the decision itself. "Ship v2 with rate limiting — approved by Priya — current load is causing timeouts" tells a reader everything they need in under ten seconds. A paragraph describing the debate that led there tells them nothing they'll use.

Owners get named, not departments. "Engineering will follow up" means nobody follows up. "Marcus will send the fallback proposal by Tuesday" means someone can be asked about it on Wednesday. If a decision has no owner, that's worth flagging rather than smoothing over — it usually means the meeting agreed on something without agreeing on who's doing it.

Open questions need the same discipline as decisions: state the question, not the argument around it, and attach a name and a date if either exists. A list of unresolved questions with no owner is just a list of things everyone will forget.

Why this shape is also the searchable shape

The structure that makes minutes readable right after the meeting is the same structure that makes them findable months later. A decision written as "we agreed to delay the launch" is something a search will find; three paragraphs of back-and-forth about launch timing usually aren't, because the actual conclusion is buried in the middle of a sentence nobody would think to search for.

This matters more once a team has fifty meetings' worth of history instead of five. AVAY's AI participant keeps a running record of decisions and open questions as a call happens, and because they're written in that decision-owner-question shape rather than as free-form discussion, a later search across past meetings — "what did we decide about the EU rollout" — actually surfaces the line that answers it instead of a transcript fragment that requires reading in context to interpret.

What to leave out, and one honest caveat

Cut anything that didn't change as a result of the meeting: context that everyone already had, tangents that got resolved without a decision, and commentary on tone or dynamics. If it didn't produce a decision, an owner, or an open question, it doesn't belong in the minutes — it belongs, at most, in a private note to yourself.

One limitation worth naming: tools that transcribe or summarize automatically, including AVAY, are good at capturing what was said but not at judging what actually counts as a decision versus a strong opinion that didn't go anywhere. That judgment call — deciding what's worth recording — still needs a person reviewing the output before it goes out, at least until the team has a shared sense of what "decided" means in practice.

Common questions

How long should meeting minutes be?

Short enough to read in under a minute — most meetings produce two to five decisions and a handful of open questions, which fits on half a page. If minutes regularly run longer than that, the meeting probably needed more structure, not the notes.

Should minutes include who said what?

Only when attribution matters to the decision itself, such as who raised an objection that changed the outcome. Attributing every comment turns minutes back into a transcript, which is the exact failure mode this structure is meant to avoid.

What if nothing was decided in the meeting?

Say so directly — "no decisions made" — rather than writing a summary of the discussion to fill the space. A meeting that produced no decisions and no new open questions probably didn't need to happen, and the minutes should make that visible rather than disguise it.

How soon after the meeting should minutes go out?

Within the hour, while people still remember enough context to catch an error or a missing owner. Minutes sent the next day get skimmed for accuracy at best; minutes sent a week later get skimmed for nothing.

What's the difference between meeting minutes and meeting notes?

Notes are usually a record of the discussion as it happened, kept for the note-taker's own reference. Minutes are a distilled output meant for people who weren't taking notes — which is why they should contain only decisions, owners, and open questions rather than a play-by-play.

The short version

Minutes get read when they record what changed — decisions, owners, open questions — and skipped when they record what was said; the same three-part structure that makes them readable right after the meeting is what makes them findable months later.