What goes in a decision log entry
A decision log is a dated list of what you and a client decided, why, who decided and how it was confirmed: for example, “19 Oct: launch moves from 26 Oct to 9 Nov because the team photos are not ready, decided by the clinic director on a call”, followed by a short email that puts the call in writing.
Weeks into a project, the question is rarely “what did we build?”. It is “when did we agree to that, and who said yes?”. A decision log answers it in one place. Pick a preset to see a full log, then replace the entries with your own and print it, copy it or download it as a spreadsheet.
- Decision
- What was settled, written as a statement anyone could check later: “Launch moves to 9 Nov”, not “talked about the launch”. One decision per entry, so each can be replaced on its own if it changes.
- Why
- The reason in one line. Six weeks later, the reason is what stops the same debate from starting again. It also helps a new person on either side understand the project quickly.
- Decided by
- The person whose call it was, by name. On the client side this is usually the approver for that part of the project. A decision with no name next to it is easy to reopen.
- Confirmed by
- Where the decision was made: email, a review link comment, a chat message, a meeting or a call. Meetings and calls leave no record, so the log flags them and writes a short confirming email for you.
- Impact
- Whether the decision changes the plan: scope (what is delivered), timeline (when) or cost (how much). Entries with an impact should point to the change request, quote or new date they belong to.
- Status
- Agreed, to revisit, or replaced by a later decision. Replaced entries stay in the log rather than being deleted, because the history is often the part you need in a dispute.
A decision log from a website build
This is the website preset from the tool above, a made-up clinic project. It shows the usual mix: decisions from a kickoff meeting, a choice made on the review link, an added page that changed the scope, a launch date that moved, and a decision about prices that was later replaced. Every row comes from the same functions the log uses.
| ID | Date | Decision | Decided by | Confirmed by | Impact |
|---|---|---|---|---|---|
| D-01 | 7 Sept 2026 | Five pages at launch: Home, Treatments, Team, Prices, Book | Dr. Tom Adeyemi | Meeting | No change to the plan |
| D-02 | 14 Sept 2026 | Use the clinic’s existing online booking system, embedded on the Book page | Dr. Tom Adeyemi | No change to the plan | |
| D-03 | 28 Sept 2026 | Home page layout B (one large Book button) chosen over A | Dr. Tom Adeyemi | Review link comment | No change to the plan |
| D-04 | 5 Oct 2026 | Show prices for every treatment | Lena Ruiz (practice manager) | Phone or video call | No change to the plan |
| D-05 | 12 Oct 2026 | Add a Team page bio for each physiotherapist | Dr. Tom Adeyemi | Changes scope | |
| D-06 | 19 Oct 2026 | Launch moves from 26 Oct to 9 Nov | Dr. Tom Adeyemi | Phone or video call | Changes timeline |
| D-07 | 21 Oct 2026 | Prices shown as “from” amounts only | Lena Ruiz (practice manager) | Chat message | No change to the plan |
Keeping a decision log that holds up
A decision log only works if you write it on the day
Entries written from memory a week later are vague and easy to argue with. Add the entry straight after the email, call or meeting, while the wording is fresh. It takes a minute.
Confirm spoken decisions in writing
A call or meeting is the most common place for decisions and the worst place for records. Send the confirming email the log writes for you, and note the reply. If the client corrects it, update the entry.
Share the decision log with the client
A private log helps you remember. A shared one prevents arguments, because the client has seen each entry. Send it at milestones, or attach it to the round email when a decision changes the work.
The log records decisions; it does not replace the contract
If a decision changes the price or what is delivered, it still needs a change request or an updated agreement. The log points to that document so you can find it later.
Questions about decision log templates
What is the difference between a decision log and meeting notes?
Meeting notes record everything that was said in one meeting. A decision log records only what was settled, across the whole project, from every channel. It is shorter, easier to search and the thing you open when someone asks “when did we agree to that?”.
How detailed should each decision log entry be?
One line for the decision, one for why, plus the date, who decided and how it was confirmed. If an entry needs a paragraph, it probably holds two decisions; split them so each can change on its own.
Should I log small design decisions in the decision log too?
Log the ones someone might question later: a layout chosen between options, a colour change, a feature moved to later, anything that changes scope, time or cost. Routine fixes from a feedback round belong in the round, not in the log.
What do I do when a client changes a decision that is already in the log?
Add a new entry for the new decision, mark the old one as replaced, and mention the old date in the new entry’s reason. If the change affects scope or cost, link it to a change request.
How do I confirm a decision log entry made on a call?
Pick the entry and use Copy confirming email. It writes a short note with the date, the decision, the reason and a line inviting corrections. Paste it into your email app and send it the same day.
Where should I keep a client project decision log?
Somewhere both sides can find it: attached to the project folder, pasted into the project thread, or as a printed PDF at each milestone. The Download CSV button gives a spreadsheet you can keep adding to.