Free decision log template

A decision log that comes back for the outcome.

Most decision logs preserve what the team chose and stop there. This one also keeps what you expected, the date reality should answer, what actually happened, and the lesson the next decision needs.

Download CSVDownload Markdown

The blank record

Nine fields before the result. Three after.

The first half protects the reasoning from hindsight. The second half turns the record into evidence instead of an archive nobody reopens.

When the call is made

Fill these while the reasoning is still live and the outcome is still unknown.

Decision ID
A stable reference such as D-014.
Decision
One sentence stating the call that was made.
Owner
The person accountable for the next step.
Date decided
When the choice became the team’s working direction.
Why this option
The constraint or evidence that made this option win.
Options not chosen
The real alternatives, with the reason each lost.
Expected outcome
A result specific enough to check later.
Confidence
A probability or plain-language confidence recorded before the result.
Review date
The date when the outcome should be knowable.

When reality answers

Add these without changing the original frame above.

Actual outcome
What happened, written without repairing the original prediction.
Lesson
One sentence worth carrying into the next similar call.
Superseded by
The later decision that replaced this one, if there is one.

If a field will not change a future action, remove it. A short log that gets updated beats a complete one that lasts for three weeks.

Worked decision log example

One record, before and after the result.

The example is illustrative. Its job is to show how the wording changes when a log records an expectation instead of merely recording that a choice happened.

D-014Decided 4 MarchReview 30 June

Move customer data from the US to the EU before the renewal.

Owner: Priya R. · Confidence: 80%

What we knew then

Why this option
The Helsinki renewal required EU data residency by 30 June. Moving now kept the account viable without accepting another two-year exception.
Option not chosen
Keep the US region and seek an exception — rejected because the customer had already made residency a renewal condition.
Expected outcome
Complete the migration before renewal with no more than a two-hour maintenance window.

What happened later

Actual outcome
The migration completed before renewal and the customer signed. The maintenance window ran four hours instead of two.
Lesson
Dry-run the export before committing to the maintenance window.
Result
Successful outcome; timing estimate missed.

How to use the template

Keep the ritual smaller than the decision.

The template works in a spreadsheet, a wiki, or a repository. The habit matters more than the container.

  1. 1

    Write the call, not the meeting

    Record the choice in one sentence. Link to the discussion if it matters, but do not turn the log into minutes.

  2. 2

    Preserve what you expected

    Write the expected outcome and confidence before reality can edit the story. Pick a date when the result can be checked.

  3. 3

    Return once

    On the review date, record the outcome and one reusable lesson. If the decision changed, point to the replacement instead of rewriting history.

By the Decize product teamPublished 16 September 2026

When the spreadsheet stops working

Let the decision arrive from the work itself.

Forward the email your team already sent. Decize drafts the record, follows the owner and review date, and brings the lesson back when a similar call appears.

Create your workspaceSee a decision end to end