Prompt Notebook

Decision log · Team habits · Templates

Decision log template: what to record, with an example

Last updated By T. Krause

A decision log is one list of every decision a team has made, with the date, the owner, the status and the reason. Here are the fields to use, a format you can copy, four filled-in entries for an example team and the habits that keep the log current.

A decision log is a single list of the decisions your team has made. Each entry has the decision in one line, the date, the person who owns it, its status and the reason it was made. When someone asks "why do we do it this way?" six months later, you search the log instead of asking around.

You can copy the format below into a spreadsheet or a doc today. Further down there are four filled-in entries for an invented team, so you can see what a good entry looks like before you write your own.

What a decision log is for

Most teams make decisions in meetings, in chat threads and in one-to-one calls. The decision itself is usually clear at the time. The reason fades within weeks, and so does the memory of who made the call. A new person joins, sees a rule that looks odd and either follows it without knowing why or quietly changes it.

The log fixes that by keeping every decision in one place, in the same shape, whatever channel it came from.

You need one when any of these is true:

  • Decisions happen in more than one place, so nobody can say where to look for them.
  • People join a project halfway through and need to catch up.
  • The same question keeps coming back in meetings because nobody remembers it was settled.
  • You expect someone to question a decision later, such as a new manager or a client.

A team of two that sits together and decides everything in one weekly call can probably get by on its meeting notes. Once there are more people, more channels or a longer project, the log starts paying for itself.

Decision log, meeting minutes and ADRs

These three overlap, and teams often use all of them.

Meeting minutes record one meeting: who came, what was discussed, what was decided and who does what next. A decision made in a meeting appears in the minutes for that date, mixed in with everything else. To find it later you have to remember which meeting it was. Our guide on how to write meeting minutes covers that record. The decision log pulls the decisions out of the minutes, and out of chats and calls, into one list.

Architecture decision records (ADRs) come from software teams. Michael Nygard described them in his 2011 post "Documenting Architecture Decisions". Each decision gets its own short document with five sections: title, context, decision, status and consequences. He suggested numbering the records in order without reusing numbers, keeping them in the project's code repository, and keeping a reversed decision in place but marked as superseded. His reason was that someone who doesn't know why a decision was made has two bad choices, to accept it blindly or to change it blindly.

A decision log covers the same ground for the whole team, in a lighter form. It is one list rather than a folder of documents, and it holds hiring, budget and marketing decisions as well as technical ones. Engineering teams that already write ADRs can add a row to the log for each one and link to the full record.

What goes into each entry

Keep the fields few enough that writing an entry takes two minutes. If it takes longer, people stop doing it.

  • Decision. One line, written as the outcome. "Free UK delivery on orders over £40", not "Delivery pricing discussion".
  • Date. The day the decision was made, or the day it was proposed if it is still open.
  • Status. Proposed, Decided or Reversed. Proposed means someone has put the decision forward and the owner hasn't made the call yet.
  • Area. The part of the work it belongs to, such as finance, hiring or marketing. This lets people filter the log to their own area.
  • Owner. The one person who made the decision or will make it. A team or "everyone" is not an owner.
  • Why. The reason in a sentence or two. This is the field people will read most, so write it for someone who wasn't there.

Two more things belong with each decision but don't fit in a single line, so put them inside the entry, in a notes field or on a linked page.

  • Options considered. What else you looked at and why it lost. Without this, someone will propose the rejected option again next year.
  • Context and source. A link to the meeting minutes, design doc or chat thread where the decision was made. When a decision changes the scope of a feature, also update that feature's PRD, as how to write a PRD explains.

Some teams add a review date for decisions that are meant to be temporary or that depend on something that might change. If your decisions often come with "let's see how it goes", add one.

A decision log format to copy

This works as the column headings of a spreadsheet or as a table in a doc.

Decision | Date | Status | Area | Owner | Why

Inside each entry:
Options we considered
- [option], [why it lost]
- [option] (chosen)
Source: [link to minutes, doc or thread]
Review by: [date, if the decision is temporary]

Put the newest entries at the top. People open the log to see what changed recently far more often than to read the history from the start.

A filled-in example

The team, the shop and the people below are invented. Larkfield Tea is an online tea shop run by three people: Maya Brennan, the founder, Leo Hart, who does marketing, and Ravi Shah, who runs orders and the accounts. They meet every Monday morning and decide most things there, and some things in the team chat.

DecisionDateStatusAreaOwnerWhy
Free UK delivery on orders over £4012 Oct 2026ProposedFinanceRavi ShahDelivery cost is the reason customers give most often when they reply to abandoned-basket emails
Hire a part-time packer for November and December2 Sep 2026DecidedHiringMaya BrennanLast December, with the three of us packing, Christmas orders shipped up to four days late
Take product photos ourselves instead of booking a photographer20 Jul 2026DecidedMarketingLeo HartNew teas arrive every month and the photographer needs three weeks' notice
Stop putting a free sample in every order6 Jul 2026ReversedFinanceMaya BrennanSamples cost about £1.10 per order. Reversed on 14 Sep 2026 after customers kept asking where they had gone. Samples now go only in orders over £25

Here is what sits inside two of those entries.

Inside "Hire a part-time packer for November and December"

Options we considered:

  • Pack in the evenings ourselves, as last year. Lost because orders still shipped late.
  • Use a fulfilment company. Lost because it needs a three-month contract and we'd have to move our stock to their warehouse.
  • A part-time packer for two months (chosen).

Source: team chat, Wednesday 2 September 2026.

Review by: 15 January 2027. Maya decides then whether the role continues past Christmas.

Inside "Free UK delivery on orders over £40"

Options we're considering:

  • Free delivery over £40.
  • Free delivery over £30, with prices on the 100 g tins going up by 50p.
  • No change.

Source: Monday meeting, 12 October 2026. Ravi decides at the Monday meeting on 26 October 2026, after checking what the threshold would have cost on September's orders.

A few things to notice. Every entry has one owner, even when the whole team discussed it. The packer decision was made in a chat thread on a Wednesday, outside the weekly meeting, and it is logged the same way as the others. The reversed sample decision stays in the log with its status changed and a note on why. Deleting it would leave a gap, and someone would suggest dropping samples again within a year.

How to keep the log alive

A decision log fails the same way a team wiki does: people stop adding to it and then stop trusting it. These habits keep it going.

Keep it in one place everyone can find. Link it from your team's home page or wiki. If you keep a wiki, how to build a team wiki people actually use explains how to link each rule on a wiki page to the decision behind it.

Make one person responsible for the log. That person doesn't write every entry. They make sure entries get written, and they nudge whoever owns a decision that came out of a meeting. In many teams it is the person who takes the minutes.

Log the decision the same day. At the end of a meeting, read the decisions back and add each one before people leave. For chat decisions, the owner adds the entry and posts the link in the thread.

Review it on a schedule. Once a month, spend ten minutes on the log. Check entries still marked Proposed and ask their owners for a decision or a date. Look for review dates that have passed. Mark decisions that have quietly stopped applying as Reversed, with a note.

Link to it when the question comes up. When someone asks why something works the way it does, answer with a link to the entry. People start checking the log first once they've been sent there a few times.

If a decision follows an incident, the review that leads to it belongs in a postmortem, and the decision itself goes in the log. How to write a postmortem covers the first part.

Hiring works the same way. Each interviewer's scores and evidence stay on their interview scorecard, and the log gets the decision and the reason. How to create an interview scorecard covers the scorecards and the debrief.

Keeping a decision log in Prompt Notebook

Prompt Notebook is ours, so weigh this section with that in mind. The decision log template opens as a database with the columns Decision, Date, Status, Area, Owner and Why. Status has the options Proposed, Decided and Reversed. Area comes with Product, Engineering, Hiring, Finance and Marketing, and you can rename those to fit your team.

There are three views. Latest first is a table sorted by date, By status is a board grouped by status, so you can see what is still Proposed, and List is a simpler list by date. The template ships with five sample decisions from an invented software company, and one of them shows options considered and what would change the team's mind written inside the entry.

The template has no review date column. If you want one, add a date property called Review by. To link the source, type @ inside the entry and pick the meeting notes or design doc, and the decision then shows on that page under Linked from. Once the log has some history, Ask your workspace can answer a question like "why did we stop sending free samples?" with numbered links to the entries the answer came from.

Frequently asked questions

What should a decision log include?

At least the decision in one line, the date, the status, the owner and the reason. An area or category helps once the log grows. Inside each entry, add the options you considered and a link to where the decision was made.

Which decisions are worth logging?

Log any decision someone might question later or that changes how the team works. Pricing, hiring, choice of tools, process changes and anything a client agreed to all qualify. Day-to-day choices that are easy to undo, such as the order of tasks this week, don't need an entry.

What is the difference between a decision log and an ADR?

An architecture decision record is a separate document for each technical decision, with sections for context, decision, status and consequences, usually stored next to the code. A decision log is one list of decisions from every area of the team, with a short reason for each. Teams that write ADRs often keep a log row for each one that links to the full record.

Who should keep the decision log?

Each decision's owner writes its entry. One person looks after the log as a whole, chasing missing entries and running the monthly review. That is often whoever takes the meeting minutes.

Should you delete a decision that was reversed?

No. Change its status to Reversed and add a note with the date and the reason. The reversal is useful history, and it stops someone from proposing the same idea again without knowing it was tried.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice