Blog

Meeting minutes vs decision records: what your team actually needs

MG

Michael Green

Founder, Withose · 26 June 2026 · 5 min read

TL;DR

  • Minutes are a chronological account of a meeting. A decision record is the durable outcome: the question, the decision, who stood where, and why.
  • Minutes go stale in days and are rarely read again. Decision records get consulted months later, precisely when the context is gone.
  • Most teams need fewer minutes and more decision records, and the two should not live in the same document.

What is the difference between minutes and decision records?

Meeting minutes are a chronological account of a meeting: who attended, what was discussed, in what order, and what actions were assigned. A decision recordis the durable outcome of a decision, wherever it happened: the question, the decision, who stood where, and the reasoning. Minutes answer “what happened in that meeting?”. A decision record answers “what did we decide about X, and why?”.

The two get conflated because meetings are where many decisions become official, so the minutes seem like the natural home for them. But the documents have opposite lifecycles. Minutes are read within a day or two, mostly by people checking their action items, then never again. Decision records are barely read at first, because everyone present already knows the outcome, and become valuable months later, precisely when memories have diverged and half the audience was not in the room.

Why minutes fail as decision memory

Burying decisions inside minutes breaks in four predictable ways:

  • Findability.The rationale for the pricing change lives in “Leadership sync, March 14”, findable only by someone who remembers the date. Decisions need to be indexed by question, not by meeting.
  • Chronology hides conclusions.Minutes faithfully record the debate's wandering path. The actual ruling is one sentence in paragraph nine, phrased as “it was agreed that”, with the reasoning scattered above it.
  • Positions go unrecorded.“Discussion followed” is minute-speak for the most important information in the room: who supported, who opposed, and why. Six months later, that is what everyone wants to know, and it was never written down. Silence in the meeting reads as agreement in the minutes, which is how teams end up relitigating settled questions.
  • Not every decision has a meeting. An increasing share of decisions conclude in Slack or Teams threads with no meeting at all, so a minutes-based memory has a growing blind spot.

What to keep, what to change

Keep minutes for what they are good at: attendance, action items, and a legal or governance trail where one is required. Boards need minutes. Most working meetings need something much shorter: actions, and decisions extracted out of the prose into a decision record that lives in its own findable home.

The practical rule: the moment a meeting settles something, the decision gets its own record with five fields (question, decision, date, people and their positions, reasoning) in the team's decision log or tool, and the minutes just link to it. Our free decision log template covers the manual version; if your decisions mostly conclude in chat rather than meetings, documenting decisions in Slack covers that path, including where Withose (our product) fits and where a plain convention is enough.

One test tells you whether your current system works: pick a significant decision from two quarters ago and try to answer, in under a minute, what was decided, who disagreed, and why the losing option lost. If the answer lives in minutes, you will feel the problem immediately.

See it work before you sign up for anything.

The playground runs the whole flow on sample data: capture, stakeholder positions, AI synthesis, and a finalized record. No account needed.

Every new workspace starts with a free 7-day Team trial. No card required.