Free tool
Decision Log Template — Free Generator
Free decision log template: record each decision with its date, owner, context, and the alternatives you rejected, then export as Markdown or CSV. Nothing is sent to a server.
Decision log template
From adding a row to downloading the finished log — four steps.
- Add a decision rowClick "Add decision" and fill in the date, a one-sentence statement of the decision, and the owner who made the call.
- Record context and rejected alternativesAdd a short note on why the decision was made, and list the alternatives that were considered and rejected — this is the field that saves a decision log from being reopened later.
- Set the statusMark each row as proposed, decided, or revisited. A revisited decision keeps its original row so the history is not lost when circumstances change.
- Export as Markdown or CSVCopy the log to your clipboard, download it as a Markdown file for a wiki or README, or download it as CSV to keep in a spreadsheet alongside other project tracking.
Why "rejected alternatives" is the most important field in a decision log
A decision log that only records the outcome tells you what was picked, not why the other options were ruled out. Six months later, when a new team member or a changed constraint brings up an option that already looks obvious again, there is no record of whether it was already considered. Without the alternatives field, that decision gets reopened and re-debated from scratch, even though the team already spent time settling it once.
Writing down even a single sentence per rejected alternative — "MongoDB, no native multi-document transactions at our write volume" — is usually enough. It does not need to be a full write-up. The goal is to leave a trail that answers "did we already think about this" without anyone having to remember the meeting where it came up. Pair the decision log with a meeting notes template during the discussion itself, and pull the decisions worth tracking long-term into this log afterward.
Decision log example
A filled decision log for a checkout redesign project, including one decision that was later revisited when circumstances changed.
Decision Log — Checkout Redesign Project
| Date | Decision | Owner | Context | Rejected Alternatives | Status |
|---|---|---|---|---|---|
| 2026-06-02 | Use Postgres instead of MongoDB for the order service | Diego Alvarez | Order data is relational and needs multi-row transactions for refunds and partial cancellations | MongoDB — no native multi-document transactions across shards at our write volume; DynamoDB — would need a second query engine for reporting | decided |
| 2026-06-15 | Ship the new checkout to 10% of mobile traffic first, not a full rollout | Priya Nair | Apple Pay integration timeline was still unconfirmed with the payments vendor | Full rollout on launch day — too risky if Apple Pay breaks for a subset of users; delay launch until Apple Pay is confirmed — blocks unrelated improvements already tested | decided |
| 2026-06-20 | Keep the legacy checkout as a fallback route instead of deleting it immediately | Tom Wallace | Support needed a way to route affected users back if the new flow had a payment bug in week one | Delete legacy checkout at launch — removes the fallback support needs; feature-flag per user instead of a fallback route — adds more state to track for a one-week window | proposed |
| 2026-07-10 | Reopen the Postgres decision for the refunds table specifically | Diego Alvarez | Refund volume grew 3x after a promo and the shared order table now has lock contention during nightly reporting jobs | Sharding the existing table — more operational complexity than splitting refunds out; switching the whole service to DynamoDB — would repeat the original transaction problem for orders | revisited |
Need the fuller record of what was discussed, not just the decisions? Use the meeting minutes template for the whole meeting, or the meeting action items tracker when a decision produces more follow-up tasks than fit in one row.
Why use a free decision log template?
- Free decision log template — no account, no login, no watermarks
- Dedicated field for rejected alternatives — the part most decision logs skip
- Status field tracks proposed, decided, and revisited decisions separately
- Export as Markdown for a wiki page or README, or CSV for a spreadsheet
- Copy to clipboard in one click for pasting into Notion, Confluence, or Slack
- Entirely client-side — your decisions never leave your browser
- Works for engineering, product, and any team that needs to remember why it chose one option over another
Frequently Asked Questions
A decision log should include the date, a one-sentence statement of the decision, who made it, the context or reason behind it, the alternatives that were considered and rejected, and a status such as proposed, decided, or revisited. The rejected alternatives field is what separates a useful decision log from a plain changelog — it captures why the other options were not chosen, not just what was picked.
Without recording what was rejected and why, a decision log only shows the outcome, not the reasoning. Six months later, when circumstances change and someone asks "why didn't we just use X", there is no record of whether X was already considered and ruled out or never came up at all. Teams end up re-debating decisions that were already settled, because the reasoning behind them was never written down. Listing the alternatives, even briefly, prevents that.
Meeting minutes record everything discussed in a specific meeting, in chronological order. A decision log records only the decisions themselves, across any number of meetings, indexed by decision rather than by date of meeting. A team might use the meeting minutes template for the full record of a meeting and a decision log to pull out just the decisions worth tracking long-term.
Mark the original row as revisited and add a new row for the updated decision when the situation that justified the original choice has changed — new information, new constraints, or a new alternative that was not available before. Keeping both rows preserves the history: what was decided, why it changed, and what replaced it.
Yes, completely free. Add as many decision rows as you need and export as Markdown or CSV — no account, no sign-up, and no usage limits. Everything runs in your browser.
Yes. Download the CSV export and open it directly in Google Sheets, Excel, or Numbers — each decision row becomes a spreadsheet row with its own columns for date, decision, owner, context, rejected alternatives, and status.
More Meeting Templates
MeetWave records your Zoom, Teams, and Google Meet calls without a bot — then generates AI summaries, decisions, and action items automatically. No bot joins your calls: the Chrome extension records web calls on macOS, Windows, Linux and ChromeOS, and the Windows desktop app also captures system audio from any app.
