Skip to content
Meetings BriefStart live transcription →Transcribe

Decision Log Template: Record What Your Team Decided

A decision log keeps every agreed decision in one place, with who decided, why and what changed later. Copy the template and the rules.

Published By KCF LLC
On this page

A decision log is a single list of the decisions your team has agreed, with the date, who made each decision, the reason and its current status. It answers the question every team eventually asks: "When did we decide that, and why?" Copy the template below, add confirmed decisions with their evidence, and preserve a link to any later replacement. Apply the access and retention rules required for the material.

Why keep a decision log

Meeting notes record decisions, but they scatter them across dozens of documents and emails. A few weeks later:

  • people disagree about what was agreed;
  • someone reopens a settled question because they missed the meeting;
  • a new team member can't see why things are done the way they are;
  • nobody knows whether an old decision still applies.

A maintained log gives the team a single place to check the current decision and its history.

Copy this decision log template

Use a shared spreadsheet or table with these columns:

ID / dateDecision and conditionsReasonDecided byStatusSource
D-001 / [date][one decision, with any condition][main reason][authorised person or group]Agreed[record link]

For a complex decision, add a linked note with options considered, evidence, expected consequences and the date to review it. This keeps the working list readable without discarding the rationale.

What each field is for:

  • ID: a short number, so people can refer to "D-014" in conversations and other documents.
  • Decision: one plain sentence a newcomer could understand. "Move the launch to March" rather than "Go with option B".
  • Why: the main reason, in a line or two. This is the field people most often skip and later most often need.
  • Decided by: the person or group with authority to decide. Not everyone who was in the room.
  • Options considered: the alternatives, so nobody spends a meeting rediscovering them.
  • Conditions: anything the decision depends on, such as "subject to budget approval".
  • Status: Proposed, Agreed, Superseded by D-0xx, or Reversed.
  • Source: a link to the meeting notes, minutes or document where it was decided.

What counts as a decision

Log a decision when the people with authority have agreed a course of action. Don't log:

  • Proposals that are still being discussed. Mark them as Proposed if you want to track them, but keep them clearly separate.
  • Preferences ("I'd lean towards March").
  • Topics where no agreement was reached. "We discussed pricing" is not a decision. Note it as an open question in the meeting record instead.
  • Routine tasks. "Arjun will send the slides" is an action item. Keep it on your action list.

A decision not to do something is a decision. "No paid advertising for the pilot" belongs in the log.

Rules that keep the log useful

  1. Log decisions within a day, while people remember the reason.
  2. Read decisions back at the end of the meeting so the people present can correct the wording before it's logged.
  3. Keep a traceable revision history. When a decision changes, add a replacement entry and link the old one to it. Restrict or remove personal data when the applicable retention policy requires it.
  4. Keep each entry to one decision. Split compound decisions so each can be superseded on its own.
  5. Give one person responsibility for keeping the log up to date.
  6. Put the link everywhere. Pin it in your team channel and link to it from meeting agendas.

Worked example

This example is fictional.

IDDateDecisionWhyDecided byConditionsStatus
D-0123 NovHold the reading pilot on Saturdays, 10–11amFamilies said weekday evenings are hardSteering groupLibrary confirms the roomSuperseded by D-015
D-0133 NovNo paid advertising for the pilotSmall first session; word of mouth is enoughSteering groupNoneAgreed
D-0143 NovLimit the first session to twenty peopleRoom capacity and volunteer numbersSteering groupNoneAgreed
D-01510 NovMove the pilot to Sundays, 2–3pmLibrary room unavailable on SaturdaysSteering groupNoneAgreed

D-012 stays in the log, so anyone can see the original plan and why it changed.

A condition is not a completed task

In the fictional example, D-012 depends on the library confirming the room. Keep it as conditional until that evidence exists. If the venue refuses, record the new decision and link it to the earlier plan. Do not silently edit the original to suggest the team always chose Sunday.

Keep execution separate. “No paid advertising” is a decision. “Arjun will draft the invitation by Thursday” is an action. “Do we have enough chairs?” is an open question unless an authorised decision or assignment was actually made. Link related records rather than turning every discussion point into a commitment.

A lightweight review can be part of the next meeting. Ask whether an agreed decision is still current, whether its conditions were satisfied, and whether anyone needs access to the supporting record. Reopen a decision when new evidence matters, and record what changed.

Filling the log from meetings

The quickest source is the decisions section of your meeting record. Before copying a decision into the log, check that it was actually agreed and not just discussed, and that you have the reason.

If you use Meetings Brief live notes, the brief collects the meeting's decisions separately from action items and open questions, and it distinguishes an agreed decision not to do something from a topic where nobody reached a decision. Use that draft as an extraction aid for the log. The brief is AI-written from your transcript, so check each decision against what was said before logging it. Writing a brief sends the transcript text to an online AI service, and daily limits apply.

For the meeting before the decision, the meeting preparation guide has a one-page decision brief that sets out the options and recommendation. The decision log records the outcome.

Frequently asked questions

What's the difference between a decision log and meeting minutes?

Minutes record one meeting. A decision log collects decisions across all meetings and documents in one list, and tracks whether each still applies.

Should a decision log include action items?

No. Keep actions on your task list or board. Link to the decision from the action if it helps.

Who should be able to edit the decision log?

Usually one or two people, so entries stay consistent. Give read access to the people who need the decisions, with tighter access for confidential entries or evidence.

What tool should I use?

Whatever your team already opens every day: a shared spreadsheet, a page in your wiki or a table in your project tool. The habit matters more than the tool.

Is this the same as an architecture decision record?

It's the same idea. Software teams often write one short document per technical decision. A decision log is a simpler, single-list version that works for any team.

Sources and scope

Product workflow checked against the Meetings Brief source on 11 November 2026. The template and reading-pilot example are original working aids, with fictional people and decisions.

Michael Nygard’s architecture-decision-record proposal describes retaining context, status and consequences and linking superseded decisions to their replacements. The compact log above adapts that principle for everyday team decisions. Documenting architecture decisions.