A decision log keeps the reason behind each choice where you will find it again, so you can see what you decided, why, and what it touched.
Three months into a project, someone asks why you picked the second vendor, or why the launch moved to spring. You remember a meeting, a chat thread, maybe a note. You do not remember the reasoning. In a 2019 McKinsey survey, 61 percent of respondents said most of the time they spend on decisions is used ineffectively. A decision log is a small habit that stops you from paying for the same decision twice.
What Is a Decision Log?
It is a running record of the choices that shape a project: what you decided, when, who decided, which options you considered, and why you picked this one. Each entry is short. The value comes from keeping all of them in one findable place instead of scattering them across meetings, inboxes, and chat history.
Microsoft’s engineering team describes its decision log as a document used to track key decisions during a project so you can later understand why they were made and by whom. Its template has columns for the decision, the date, alternatives considered, the reasoning, a link to a detailed document, who made it, and the work required.
You do not need a team or a software project to keep one. A freelancer choosing a pricing model, a founder dropping a feature, and a designer settling on a client’s direction all make decisions worth recording.
Why Keep a Decision Log
Decisions get made in the middle of other work. Microsoft’s 2025 Work Trend Index found that employees are interrupted every two minutes during core work hours, 275 times a day, by meetings, emails, or chats. Under that pace, the reasoning behind a choice rarely survives the afternoon it was made.
Software architect Michael Nygard put the problem plainly in a 2011 post on documenting architecture decisions: one of the hardest things to track during the life of a project is the motivation behind certain decisions. A newcomer, or you six months later, has two choices. Blindly accept the decision, which is risky if the context has changed. Or blindly change it, which may damage something you did not know the decision protected.
Memory also edits the record. Psychologists Neal Roese and Kathleen Vohs describe hindsight bias as the feeling that you “knew it all along,” and one of its three forms is memory distortion: misremembering your earlier judgment as “I said it would happen.” Researchers measure that by comparing what someone recalls with what they recorded earlier. A log gives you that earlier record, written before the outcome was known.
A log also saves time when the question comes back. Instead of reopening a closed debate, you read the entry, check whether the reasons still hold, and either move on or revisit it on purpose.

What to Put in Each Entry
Keep entries small enough that you will actually write them. Seven fields cover most situations:
- The decision, in one plain sentence.
- The date it was made.
- Who made it, and who was consulted.
- The options you considered, including the one you rejected first.
- The reasoning, in two or three sentences.
- What the decision affects: files, tasks, people, or other decisions.
- A date to review it, if the decision depends on something that could change.
A short example, written for a made-up client project: “Decision: Deliver the brand guide as a shared web page instead of a PDF. Date: March 4. Made by: me, after a call with the client. Options: PDF, shared page, slide deck. Why: the client updates colors often and a page stays current without resending files. Affects: the logo files, the proposal, and the final invoice note. Review: after the first revision round.”
That entry takes about a minute to write. Six months later it saves an argument.
How to Start a Decision Log
You can begin today with a single page. The system matters less than whether you will open it when a decision lands.
Pick One Place
Choose one home for the log, and put it where you already work. A spreadsheet, a document, or a note on your workspace all work. A log you have to go hunting for will not get used. If you also keep a weekly review, add a check of the log to it so entries do not wait a month to be written.
Write the Entry When the Decision Lands
Log the decision at the end of the call or the moment you choose, not at the end of the week. Memory fades quickly, and the “why” is the first part to go. If the entry feels too heavy, write only the decision, the date, and one sentence of reasoning, and fill in the rest later.
Link the Evidence
A decision usually rests on something: a quote, a screenshot, a meeting note, a spec. Point the entry to it. The Microsoft template has a column for a link to a detailed document for this reason. When you keep your project notes and source material close to the log, you can follow a choice back to what you knew at the time.
Review the Log on a Schedule
Decisions age. A vendor changes its pricing, a constraint disappears, a client changes direction. Pick a review date for the decisions that depend on conditions, and check them when it arrives. This is where a log earns its keep: you can see which choices still stand.

Which Decisions Deserve an Entry
Not every choice needs a record. Logging what you ate for lunch will bury the entries that matter. A few filters help:
- Choices that are costly or slow to reverse, such as a vendor, a tool, a price, or a contract term.
- Choices other people will ask about later, such as why a deadline moved or a feature was cut.
- Choices that depend on a condition that might change, such as a budget or a client’s plan.
- Choices where you rejected a reasonable option and want to remember why.
If you are unsure, write a one-line entry. It is cheaper to log a small decision than to reconstruct a large one.
A Decision Log on a Visual Desk
A log fails when it sits far from the work it describes. You write an entry, the files live somewhere else, and the link breaks the moment someone moves a folder. A digital desk puts the log and the material beside each other.
In Opal, your workspace is a large grid, like a desk. A decision can be a note in the same fence as the project it belongs to, sitting next to the PDF quote, the screenshot, and the meeting notes that explain it. Fences group a project’s items by area, and you can open several items side by side, so reading an entry and its evidence takes one glance instead of three searches. Google Docs and Sheets can sit on the desk too, which suits teams that already keep a decision table in a sheet.
Spatial memory does some of the finding for you. People tend to recall where something lived on a desk more easily than what they named it, so “the decisions note at the top of the client fence” is easier to reach than a filename. Opal’s interactive notes use a full block editor, so an entry can start as three lines and grow into a longer page with linked tasks when a decision needs follow-up work. A binder can hold the log for finished projects so the active desk stays clear while the history stays nearby.

If you work with others, you can share a fence with them on the Studio or Workshop plans, and the person who receives it gets the notes and files in it. Opal is not a project management suite, an approvals workflow, or an audit system, and it does not record who edited what the way a compliance tool would. If you need formal sign-off trails, use a tool built for that. If you need a clear, findable record of the reasons beside the work, a visual desk fits.
Day Desk on Opal is $9 per seat per month, or $7 per month when billed yearly. Studio and Workshop are listed on the visual desk pricing page. All plans are paid, and prices are as shown on that page today.
Other Formats That Work
A spreadsheet is the most common home for this kind of record, and it is a good one when your decisions are short and tabular and your team already lives in sheets. Filters, sorting, and a shared link are hard to beat for that. A plain document works when entries run longer. Engineering teams often keep architecture decision records as short text files in the project repository, a format Nygard describes as small, modular documents that stay easier to update than large specifications.
The common thread is that the record is short, dated, and easy to find. Pick the format you will actually open. If you want a place for decisions to live beside notes, files, and tasks, research notes and project material can sit in the same view.
Key Takeaways
- A log records what you decided, when, who decided, the options considered, and why.
- Fast, interrupted work erases reasoning, and memory tends to rewrite earlier judgments.
- Seven short fields cover most entries, and a one-minute entry beats a perfect one never written.
- Write the entry when the decision lands, link its evidence, and set a review date for decisions that depend on conditions.
- Log costly, hard-to-reverse, and often-questioned choices, not every small one.
- A visual desk helps when you want the log beside the files and notes that explain it.
FAQ
What is a decision log?
It is a running record of key choices on a project: what was decided, when, by whom, which options were considered, and why. It lets you and others understand the reasoning later without relying on memory.
How do you write a decision log?
Pick one place to keep it, then add a short entry whenever a meaningful decision lands. Each entry holds the decision, the date, who made it, the alternatives, the reasoning, what it affects, and a review date if conditions could change. Link to the evidence behind the choice.
Can you give an example of a decision log entry?
Here is a made-up one: “Decision: send the brand guide as a shared web page, not a PDF. Date: March 4. Made by: me, after a call with the client. Options: PDF, shared page, slide deck. Why: the client changes colors often and a page stays current. Review: after the first revision round.”
What is the best decision-making tool?
A log records decisions rather than making them for you. For choosing between options, a simple list of criteria or a pros and cons table works for most small decisions. Use the log afterward to keep the result and the reasoning.
Does Opal have a free plan for keeping a decision log?
No. Opal’s plans are paid, and Day Desk starts at $9 per seat per month ($7 per month billed yearly). Current details are on the pricing page.
Can I use Opal on my phone?
Opal runs in the browser today. You can open it in a phone browser, but the desk is built for a larger screen where you can see your fences and items side by side. Native apps are on the roadmap and are not available yet.
Can I move my existing decision log into Opal?
You can copy and paste entries from a spreadsheet or document into notes on your desk. There is no one-click importer for decision log files today.
When is Opal not the right fit?
If you need approval workflows, a formal audit trail, or a tool your whole company already uses for governance, a dedicated system fits better. Opal fits when you want decisions kept beside the notes, files, and tasks that explain them.
What Opal Is For
- A spatial desk where notes, files, and tasks stay in view together
- Fences and binders that keep active projects and finished ones sorted without hiding either
- Items you can open side by side, so a decision sits next to its evidence
- Opal gives your notes a desk
Guide: Why productivity apps keep failing you
Get the blueprint by email — same one from the lead magnet page. No spam.
