Decision Log Template
The columns to keep, a filled-in example, and how to run the log so the next person can see what was decided, why, and what happened next.
A decision log is a running list of the significant decisions a team, project or company makes. Each entry records what was decided, the options on the table, the reasoning, who owned and approved it, and what happened afterwards.
Most organizations keep the outcome of a decision somewhere: in an email, a contract, a changed setting. What they lose is the reasoning. When the people who made the call move on, the next team cannot tell whether a choice was deliberate, what was tried before, or what would justify changing it. A decision log keeps that reasoning in one place that outlasts any one person.
The template below works in a spreadsheet, a wiki page or a shared document. Download the CSV to open it in Excel, Google Sheets or Numbers, or copy the Markdown version into Confluence, Notion or any wiki that accepts tables.
The template: 14 columns
Each row is one decision. Keep the columns in this order so the log reads left to right: what was decided, why, who owned it, and what happened.
| Column | What to write | Example |
|---|---|---|
| ID | A short, permanent reference so other documents can point to the decision. | DEC-014 |
| Date decided | The day the decision was made, not the day it was written down. | 2026-03-12 |
| Decision | One sentence a newcomer would understand without context. | Raise the invoice auto-approval limit for contracted suppliers from $5,000 to $10,000. |
| Context | The problem, and why it had to be decided now. | Approvers were clearing a large queue of small invoices by hand, and month-end close was slipping. |
| Options considered | Every option that was seriously on the table, including doing nothing. | Keep $5,000; raise to $10,000; raise to $25,000; remove the limit for top suppliers. |
| Reasoning | Why this option won, and why the others lost. | $10,000 covers most of the queue while keeping larger invoices under review. |
| Evidence and assumptions | What the team knew, where it came from, and what it assumed but could not check. | Queue export from the AP system. Assumes contracted prices are loaded correctly. |
| Owner | The one person accountable for the decision and its follow-up. | AP manager |
| Approved by / consulted | Who signed off, and who gave input. Names or roles, as your policy allows. | Approved: Controller. Consulted: Procurement, Internal audit. |
| Status | Proposed, Decided, Deferred, Reversed or Superseded. | Decided |
| Expected result and measure | What should happen if the decision is right, and how you will check. | Fewer invoices waiting for manual approval at month end; no rise in overpayments found in audit. |
| Review date or reopen condition | When to look again, or what would make the question worth reopening. | Review after two month-end closes, or sooner if an overpayment is found. |
| Actual result | What happened, filled in at review. Write it down even when the answer is unclear. | Queue down; one pricing error caught by audit. Kept, with a monthly price check added. |
| Links | Where the evidence, approvals and related decisions live. | AP queue report; approval email; DEC-009 |
Short on time? Start with six: ID, decision, reasoning, owner, status and review date. Add the rest once the habit sticks.
Copy the template
Download the template (CSV) to open it in Excel, Google Sheets or Numbers. It has the column headers and one example row to delete. For a wiki page in Confluence, Notion or similar, paste this Markdown table header:
| ID | Date decided | Decision | Context | Options considered | Reasoning | Evidence and assumptions | Owner | Approved by / consulted | Status | Expected result and measure | Review date or reopen condition | Actual result | Links |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |Decision log examples
Three sample entries, made up to show the format: one decision made, one deferred, one reversed. Only the columns that matter most for each are shown.
Sample · A decision that was made
- ID
- DEC-014
- Decision
- Raise the invoice auto-approval limit for contracted suppliers from $5,000 to $10,000.
- Options considered
- Keep $5,000; raise to $10,000; raise to $25,000; remove the limit for top suppliers.
- Reasoning
- $10,000 clears most of the manual queue while keeping larger invoices under review. $25,000 and no limit were rejected as too much exposure if contracted prices were wrong.
- Owner
- AP manager
- Status
- Decided
- Review date or reopen condition
- Review after two month-end closes, or sooner if an overpayment is found.
Sample · A decision that was deferred
- ID
- DEC-021
- Decision
- Do not move support and field service onto one ticketing system this year.
- Options considered
- Migrate now; migrate at the support contract renewal; keep both systems.
- Reasoning
- The cost of breaking the current support contract early could not be confirmed, and nobody owned the migration.
- Evidence and assumptions
- Ticket volumes from both systems. Early-exit terms not yet confirmed with the vendor.
- Status
- Deferred
- Review date or reopen condition
- Reopen 90 days before the support contract renews, or if duplicate tickets keep reaching customers.
Sample · A decision that was reversed
- ID
- DEC-009
- Decision
- Reverse DEC-003: return quarterly pricing reviews to the regional teams.
- Context
- Central reviews (DEC-003) were meant to make discounts consistent, but they slowed quotes in two regions.
- Actual result
- DEC-003 made discounts more consistent but quotes slower. Kept the central discount bands and handed reviews back to regions.
- Status
- Decided (supersedes DEC-003)
- Links
- DEC-003; pricing review notes
How to run a decision log
- Decide what counts as a decision worth logging. Agree a simple test up front, such as: it commits money or people beyond a set amount, it is hard to undo, it changes a policy or a customer-facing rule, or someone is likely to ask why later. Write the test at the top of the log so everyone applies the same one.
- Give the log one owner and one home. One person keeps the log tidy and chases missing entries. It lives in one place everyone involved can read, linked from the project or team page, not in a personal drive.
- Write the entry when the decision is made. Fill in the entry in the meeting or the same day, while the options and reasoning are fresh. An entry written weeks later records what people remember, which is rarely what they knew at the time.
- Record deferred and undecided questions too. When the team stops short of a decision, log it with the status Deferred, what was unknown, and the condition for reopening it. These are the entries that save the most rework, because the same question tends to come back.
- Never delete or overwrite an entry. If a decision changes, add a new entry that supersedes the old one and update the old entry's status. The history of what changed, and why, is the point of the log.
- Review it on a schedule. At each review date, fill in the actual result and decide whether to keep, change or reverse the decision. A short monthly or quarterly pass through open review dates is usually enough.
What to log, and what to leave out
Log:
- Choices that commit budget, headcount or a contract
- Changes to policies, approval limits or customer-facing rules
- Trade-offs between teams, where one team gives something up
- Decisions to wait, not act, or stop a piece of work
- Exceptions to a standing rule, and why they were granted
Leave out:
- Routine work that follows an existing rule
- Tasks and action items (keep those in your task tracker)
- Discussion that did not lead to a decision or a deliberate deferral
- Personal or confidential details your policies keep elsewhere: link to them instead
Common mistakes
Logging the outcome but not the reasoning. "Chose supplier B" tells a successor nothing. The options, the reasons and the assumptions are what make the entry useful a year later.
Leaving out the options that lost. Without them, the next team proposes the same rejected option and has to rediscover why it was rejected.
Only logging decisions that worked. Reversed, failed and inconclusive decisions are where most of the learning is. Keep them in the log with an honest actual result.
No review date. A decision with no review date is never checked. Set a date or a clear reopen condition on every entry.
Too many columns for the team to keep up. If the log goes stale, cut it back. ID, decision, reasoning, owner, status and review date are the minimum worth keeping.
How it differs from similar records
Decision log vs. meeting minutes
Minutes record what was said in one meeting. A decision log records only the decisions, across every meeting and channel, in one place you can search.
Decision log vs. RAID log
A RAID log tracks a project's risks, assumptions, issues and dependencies (some teams read the D as decisions instead). Where it doesn't cover decisions, keep a decision log next to it and link the two when a decision answers a risk or issue.
Decision log vs. architecture decision records
Architecture decision records (ADRs) are a format software teams use for technical decisions, usually one short file per decision kept with the code. A decision log covers business decisions in one shared list. The two can point to each other.
Decision log vs. a decision register
The terms are often used for the same thing. Some organizations use "register" for a formal, governance-level list, such as decisions taken by a board or steering committee.
When a spreadsheet stops being enough
A spreadsheet works while a team writes its own entries. It gets harder when decisions are spread across finance, procurement, HR and support systems, when the evidence lives in those systems rather than in the log, or when software agents start acting on decisions and every action needs a record of who approved it.
At that point some companies move to software that keeps the record as the work happens. Nodes, which commissions this publication, is one example: it records a Decision Trace for each decision, with the evidence, reasoning, approval, action and result, including ones that failed. Whatever you use, the test is the same as for the template above: can someone who was not in the room see what was decided, why, who approved it and what happened?
Frequently asked questions
What is a decision log?
A running record of significant decisions: what was decided, when, by whom, the options considered, the reasoning, and the result. It lets anyone check later why something is the way it is.
What should a decision log include?
At minimum: an ID, the date, the decision in one sentence, the reasoning, the owner, the status and a review date. The full template adds context, options considered, evidence and assumptions, approvers, the expected and actual result, and links.
Who should own the decision log?
One named person, usually the project manager, chief of staff or team lead. They keep it tidy and chase missing entries. Each decision still has its own owner, recorded in the entry.
Should I use Excel, Google Sheets or a wiki?
Use whatever your team already opens every day. A spreadsheet is easiest to filter and sort; a wiki page is easier to link from project pages. The CSV above opens in Excel, Google Sheets and Numbers, and the Markdown version pastes into most wikis. Check your own tool's template gallery too: many wikis and project tools offer a decision page or log template you can adapt to these columns.
How is a decision log different from an action log?
An action log tracks tasks: who will do what, by when. A decision log records choices and the reasoning behind them. One decision often creates several actions; link them rather than mixing the two lists.
Should deferred or undecided questions go in the log?
Yes. Log them with the status Deferred, what was unknown, and the condition for reopening. Questions that come back are where an undocumented team loses the most time.
The Institutional Edge is commissioned by Nodes and produced with AI assistance. This template is free to copy and adapt.





