Meeting summary vs decision log: what should your team keep?

A meeting summary and a decision log solve different problems. A summary helps someone understand what happened in a meeting. A decision log helps the team find a specific choice later, understand why it was made and connect it to the work that followed.

If your team only needs a quick recap, a summary may be enough. If decisions need to survive beyond the meeting, they should be recorded separately from the narrative summary.

The difference is structure, not just detail

A meeting summary usually follows the shape of the conversation. It compresses discussion into a shorter narrative or a set of bullets. That is useful when someone missed the meeting or wants a quick reminder.

A decision log treats each important decision as its own record.

The formats can complement each other. The problem starts when a summary is expected to act as the team's long-term decision memory.

Why meeting summaries become hard to use later

Imagine a product team discusses onboarding in five weekly meetings. Each meeting produces a clear AI summary. Two months later, someone asks: "Why did we keep the existing onboarding flow for the beta?"

The answer may exist somewhere in those summaries, but finding it requires knowing which meeting contained the discussion and reading enough surrounding text to reconstruct the conclusion.

The information was captured, but it was not organized for retrieval as a decision.

This distinction matters more as the number of meetings grows. Summaries are documents. Decisions are individual pieces of organizational memory that may need to be searched, compared, revisited or superseded.

What belongs in a decision log

A useful decision record starts with a clear statement of what the team actually decided. Depending on what was established in the meeting, it can also preserve:

• the rationale behind the choice;
• the meeting where the decision was made;
• relevant source evidence from the transcript;
• people involved in the decision;
• related actions or unresolved questions;
• lifecycle information when a later decision replaces or changes it.

Do not add details simply because they would make the record look complete. If the meeting did not establish a reason, owner or deadline, the record should not invent one.

For a practical process, see how to track meeting decisions.

A summary can hide the boundary between discussion and decision

Meetings contain proposals, objections, questions, tentative agreements and final choices. A concise summary can flatten those stages into a few polished bullets.

For example:

The team discussed delaying the beta because of onboarding issues and agreed to keep the current launch date while preparing a fallback flow.

That sentence is a useful summary. For follow-up, however, the team may need separate records:

Decision: Keep the current beta launch date.

Action: Prepare a fallback onboarding flow.

Open question: What performance threshold would trigger the fallback?

Separating these outcomes makes each one easier to act on and retrieve. The same principle applies when you turn a meeting transcript into action items: not every important sentence is the same kind of outcome.

When a meeting summary is enough

A decision log is not necessary for every conversation. A summary may be sufficient for informational meetings, routine updates or discussions that produce no durable choices.

A separate decision record becomes more useful when a choice:

• changes a product, project or process;
• creates work for other people;
• is likely to be questioned later;
• depends on trade-offs that will matter in the future;
• affects work across multiple meetings;
• may later be replaced by another decision.

The test is simple: if someone asks about this choice in three months, would finding the meeting summary be enough, or would they need to know exactly what was decided and why?

AI meeting assistants make capture easier, not automatically durable

Transcription and summarization reduce the effort required to capture a meeting. They do not, by themselves, determine which statements should become trusted organizational records.

That requires separating outcomes and reviewing them against the source. A proposed decision extracted by AI should still be checked before the team relies on it, particularly when the discussion was ambiguous or changed direction during the meeting.

WhyBecause is designed around this distinction. It turns transcripts into structured candidates such as decisions, actions and unresolved topics, then lets the team review the extracted information before it becomes shared meeting memory. The meeting decision tracker shows how decisions can remain connected to rationale and source evidence instead of disappearing inside a recap.

Use both formats for the jobs they do well

You do not have to choose between summaries and decision logs for every meeting.

Keep the summary when people need the story of the conversation. Keep a decision record when the choice itself needs to remain findable, explainable and connected to future work.

A good meeting system makes that separation explicit. The transcript is the source, the summary is the recap, and the decision log is the durable record of choices that matter.

Frequently asked questions

Is a meeting summary the same as a decision log?

No. A meeting summary condenses the conversation, while a decision log records specific decisions in a structured form that can be found and reviewed later.

What should a meeting decision log contain?

A useful decision record identifies what was decided and keeps relevant context such as rationale, source meeting, supporting evidence and related follow-up when those details are available.

Do teams still need meeting summaries if they keep decision logs?

Often, yes. Summaries are useful for catching up on the discussion, while decision logs serve a different purpose: preserving important choices as durable records.