Decision Log Template: Capture Decisions, Owners and Review Dates

A useful decision log template answers six questions quickly: what was decided, who had authority, why the choice was made, what changes now, when it will be reviewed and what supersedes it. It is not a transcript and it is not a substitute for formal minutes, contracts, approvals or professional advice.

This page focuses on a reusable cross-meeting decision register. That is different from the existing meeting note templates, which structure an individual conversation, and from meeting notes versus minutes, which explains record types. Use this template when people need to find decisions after the original meeting has faded from memory.

Copy this decision log template

Use one row per decision in a spreadsheet, database or project workspace. Add a linked detail page only when the rationale or evidence needs more room.

Decision ID:
Decision date:
Decision statement:
Status: proposed / approved / superseded / withdrawn

Accountable decision owner:
Decision-making body, if applicable:
Recorder:
People consulted:

Context and problem:
Options considered:
Rationale:
Conditions or assumptions:
Dissent or unresolved concern:

Affected projects, customers or policies:
Actions: owner — deliverable — due date
Communication audience and owner:

Review date or trigger:
Evidence to review:
Supersedes / superseded by:
Source meeting or document:
Last verified:

The fields are prompts, not proof that a process is valid. Adapt them to your governing documents, approval rules, confidentiality model and applicable obligations. If a decision has legal, financial, safety, employment or regulatory consequences, have the appropriate qualified person review the process and record.

Decide what belongs in the log

Log a decision when someone will reasonably ask later, “Why did we do this?” Good candidates change product scope, budget, ownership, policy, customer commitments, architecture, risk acceptance or dependencies. Also log a deliberate choice to postpone or reject an option when that choice constrains future work.

Do not flood the register with reversible daily preferences. A developer choosing a local variable name or an organizer selecting a routine meeting time rarely needs a governed entry. The cost of logging should be proportional to the cost of forgetting. A practical threshold is whether reversal would require coordination, approval, customer communication or material rework.

Keep proposals out of the approved view. Mark them as proposed until the authorized owner confirms the choice. A lively discussion is not a decision, and silence is not approval.

Write a decision statement that survives context loss

Write the statement as a complete, testable sentence: “The product team will use option B for the pilot beginning 1 September, limited to the two named regions.” Avoid fragments such as “Option B,” “Proceed,” or “Discussed migration.” A reader should understand the practical change without reopening the transcript.

Include scope and conditions in the statement when they define the decision. Keep rationale separate so the operative choice remains easy to scan. If uncertainty remains, state it. “Approved subject to security review” is different from unconditional approval.

Record alternatives proportionately. You do not need a debate transcript, but naming the serious options prevents the team from reopening already examined paths without new evidence. If the source was a meeting, link the reviewed record rather than copying sensitive conversational detail into a broadly visible log.

Separate the decision owner from the recorder

The decision owner is the person or body with authority and accountability. The recorder maintains the entry. These roles can be held by one person, but they should remain conceptually distinct. A note-taker must not accidentally become the approver because their name is the only one attached to the row.

Use one accountable owner where possible. “Leadership” or “the team” obscures who can confirm, review or supersede the choice. For a board or committee decision, name the body and record the chair, secretary or other role according to its rules. The template does not determine whether that body was properly constituted.

Link resulting work to named action owners. The action-item guide explains how to turn an agreement into an executable task, while who completes the action-item form separates meeting ownership from task ownership.

Capture rationale without manufacturing certainty

Rationale should explain why the selected option fit the information available at the time. List the decisive evidence, constraints and tradeoffs. Preserve material caveats and dissent instead of rewriting a contested choice as unanimous. This makes the log useful for learning rather than merely defensive documentation.

Use neutral language. Replace “the obviously superior vendor” with the criteria that mattered: integration fit, support model, timeline or verified cost. Link dated evidence and identify assumptions that could expire. Do not paste unnecessary personal data, confidential negotiations or privileged advice into a general register.

An AI-generated rationale may sound coherent while combining separate speakers or omitting objections. Treat generated text as a draft. The authorized owner should confirm that it reflects the actual basis for the decision.

Add review dates and event-based triggers

Some decisions should be reviewed on a date; others should reopen when an assumption changes. Use both where appropriate. A date works for a quarterly policy review. An event trigger works for “reassess if pilot error rates exceed the agreed threshold” or “review when the contract expires.”

Define the evidence required at review. Without that field, a review meeting can repeat the original opinions. State who convenes the review and what outcomes are possible: affirm, amend, supersede or withdraw.

Do not set arbitrary review dates merely to fill the template. Permanent or low-risk choices may need only a change trigger. Conversely, do not label a high-impact choice permanent when its evidence, law, market or operating conditions can change.

Connect decisions to actions and communication

A decision is not implemented because it appears in a database. Add the first concrete actions, one owner per action, due dates and a clear completion condition. Put ongoing delivery in the task system and link back to the decision rather than running the whole project from the log.

Identify who must be told and who owns that communication. Different audiences may need different detail: implementers need conditions and dates; customers may need an approved external message; executives may need the risk and resource effect. Apply least-privilege access to sensitive context.

For the communication sequence, use the existing meeting follow-up guide. It complements this page by covering the message after a meeting; it does not replace the long-lived decision register.

Maintain status and preserve history

Use a small controlled status set: proposed, approved, superseded and withdrawn. “Complete” usually belongs to an action, not a decision. A decision can remain approved after implementation finishes.

When the choice changes, create a new entry, mark the old one superseded and link both directions. Do not overwrite the old statement until it appears that the new policy was always in force. Correct spelling or factual metadata transparently and keep an edit history where the platform supports it.

Assign a custodian to check for missing owners, broken source links, overdue reviews and duplicate entries. The custodian improves record quality but cannot retroactively grant authority or consent.

Need a reviewable source for an explicitly agreed in-person decision meeting? Kuno supports visible, consented conversation capture and can help produce a draft for human review. It does not decide, approve or replace your governance process. Explore Kuno

Use the log before, during and after a meeting

Before the meeting, create a proposed entry with the decision question, owner, deadline, options and evidence. During the discussion, show the proposed wording, distinguish conditions from actions and read the final statement back. Afterward, the owner confirms the entry and the recorder links tasks and distributes the approved summary.

If recording is proposed, explain purpose, access, retention and alternatives before capture. Obtain the form of agreement appropriate to the context and jurisdiction, and provide a meaningful manual-notes route. Never treat attendance as automatic recording consent.

The log should then become the index people search first. The source meeting record supports it; the task tracker executes it; neither should silently replace it.

Avoid common decision-log failures

• Logging discussion instead of the decision: use one operative sentence.
• Naming no authority: identify the accountable person or decision-making body.
• Confusing actions with decisions: connect them, but track their statuses separately.
• Erasing changed choices: supersede and link instead of rewriting history.
• Capturing excessive sensitive detail: record only what serves the defined purpose.
• Adding review dates with no owner: name who initiates the review.
• Trusting an AI draft without checking it: verify speakers, conditions, numbers and dissent.

A short complete entry is more useful than a polished essay. If users routinely leave fields blank, reduce the template or clarify the threshold instead of adding mandatory bureaucracy.

Review the register as a system

Once a month or quarter, sample entries for clear statements, valid owners, linked evidence, open actions and due reviews. Look for decisions that live only in chat, duplicate choices across teams and old entries that no longer match practice. Fix routing and ownership, not just wording.

Measure usefulness through retrieval and follow-through: can a new team member find the current decision, and can an owner tell what happens next? Do not score employees by raw decision counts or treat documentation volume as performance.

See Kuno for consent-first in-person source capture when a reviewed recording would support the register. Keep the final decision statement, authority check and publication under human control.