A decision log is a simple table where you record each important project decision: what was decided, why, who decided, which alternatives you rejected, and what happens next. The template below fits in a spreadsheet, a doc or a project tool. It takes about two minutes per entry. It will save you from the "wait, why did we do it this way?" conversation that eats hours in the middle of a project.
This guide gives you the columns to copy, a filled-in example, the rules for keeping the log honest, and the point at which a one-line entry needs a longer page behind it.
TL;DR
- A decision log records the decision, the date, the decision-maker and the reasoning. Everything else is optional.
- Keep the log to a few columns and link out to fuller documents, so you never write the same thing twice.
- Never overwrite a changed decision. Add a new entry, link it to the old one and mark the old one as superseded.
- Capture decisions in the meeting or right after it, and review the log on a regular schedule.
- Use a longer, ADR-style page only for technically complex or high-impact decisions.
Table of Contents
- What a decision log is, and what it is not
- The decision log template
- A filled-in decision log example
- Choosing a decision log format
- How to create and maintain the log, step by step
- Using the log to protect scope
- Our perspective
- Get the rest of the toolkit
- Common mistakes to avoid
- FAQ
- Sources
What a decision log is, and what it is not
A project decision log, sometimes called a decision register, is a structured record of the decisions that shape a project. Public-sector project offices describe it in plain terms: the log answers what the decision was, when it was made, why, and who made it. The Connecticut Department of Social Services Enterprise PMO names the project team, sponsor, business owner, steering committee and key stakeholders as its readers.
It is not meeting minutes. Minutes tell the story of a conversation in order. A decision log keeps only the outcome and the reasoning, so someone can find it in ten seconds six months later.
It is also not a risk log. A RAID log tracks risks, assumptions, issues and dependencies, and decisions are one of the things that can come out of it. If you already keep one, our RAID log examples for freelance PMs show how the two sit side by side.
Why bother? Three reasons come up on every engagement:
- Decisions get re-opened. A written record of the options, rationale and approval reduces confusion and stops settled questions from coming back. That is the argument the Connecticut project office makes for its log.
- People leave or join. Engineering teams treat the log as institutional memory. Microsoft's engineering playbook says later teams need the alternatives, the reasoning, the author and the follow-up work, not only the choice.
- Clients forget. If you work independently, the log is your evidence of what the client approved and when. That matters most when scope and budget start to drift.
The decision log template
Here is a template you can paste into a spreadsheet. Each row is one decision.
| ID | Date | Decision | Context | Alternatives considered | Rationale | Decision-maker | Contributors | Impact | Status | Follow-up action and owner | Link |
|---|---|---|---|---|---|---|---|---|---|---|---|
| D-001 | One sentence, in the past tense | The problem, constraints, assumptions | Options you rejected | Why this one won | One named person | Who was consulted | Time, cost, resources, customer | Proposed / Decided / In effect / Superseded | Next step, owner, due date | Proposal, ticket, email or risk entry |
That is twelve columns, which is the upper limit. If that feels heavy, the minimum version is four columns: decision, date, decision-maker and rationale. One practitioner guide calls these the irreducible core, because the rationale lets a future reader judge whether the decision still holds. Add columns only when you will actually fill them in.
What each column is for
ID. A running number such as D-001 lets you refer to a decision in an email, a status report or another log. The Connecticut template uses an ID for the same reason.
Date. The day the decision was made, not the day you wrote it down. The two often differ, and the difference matters when someone asks what you knew at the time.
Decision. Write one sentence a stranger could understand. Microsoft's template asks for a one-sentence summary, and it is a good discipline: if you cannot say it in a sentence, the decision is not finished.
Context. Record the problem being solved, plus any constraints and assumptions. A common decision-record template keeps Issue, Assumptions and Constraints as separate items. You do not need three columns, but the three questions are worth answering. The goal is that a future reader does not have to reconstruct the original discussion.
Alternatives considered. Name the options you rejected, in a few words each. This column stops the same idea from being proposed again every quarter.
Rationale. The "because" sentence. Cost, risk, deadline, client preference, technical fit. Be concrete.
Decision-maker and contributors. One accountable person, plus the people who advised. The Connecticut log separates contributors from the approver, which is a clean way to show who had a voice and who had the final say.
Impact. How the decision changes timelines, resource allocation or customer outcomes. ProjectManager's template suggests summarizing exactly those three areas, and a single line is enough.
Status. A short list works best. Proposed, Decided, In effect and Superseded cover most projects. Add Archived at closure if you want it.
Follow-up action and owner. A decision that nobody acts on is only an opinion. Typical follow-ups are communicating the change, updating documents, assigning new responsibilities or scheduling a review checkpoint.
Link. Point to the business case, proposal, ticket, risk assessment or meeting record. This is what keeps the log short.
A filled-in decision log example
The entries below are illustrative, written for a small freelance engagement: a PM running a website relaunch for a boutique retailer.
| ID | Date | Decision | Alternatives considered | Rationale | Decision-maker | Impact | Status |
|---|---|---|---|---|---|---|---|
| D-001 | Mar 3 | Hire Agency A for the build | Agency B; build in-house | Quote is lower and the team is in the client's time zone; in-house has no capacity before launch | Client owner | Adds $0 to internal headcount; build starts Mar 17 | In effect |
| D-002 | Mar 12 | Launch the new store in a soft-launch phase for existing customers first | Single public launch | Lets us fix checkout bugs before peak traffic | Client owner, advised by PM | Public launch moves two weeks later | In effect |
| D-003 | Apr 2 | Drop the loyalty-points feature from phase one | Keep it and extend the schedule | Feature needs a payments integration the client has not budgeted | Client owner | Saves about three weeks; feature moves to phase two | In effect |
| D-004 | Apr 20 | Reverse D-002: go straight to public launch | Keep the soft launch | Marketing campaign is booked and cannot move | Client owner | Soft-launch testing replaced by extra QA week | Decided |
D-002 then gets its status changed to Superseded, with a note "replaced by D-004". Nobody deletes the original. Six months from now, when someone asks why there was no soft launch, the log answers in one glance: the campaign could not move, and the client owner approved it on a known date.
The pattern in the example is worth copying. Each rationale names a real constraint such as money, time or capacity. Each impact is something you could verify later. Each decision has one owner.
Choosing a decision log format
The right format is the one your team will open without being asked. There are three common options.
A spreadsheet. This is the default for most project work and matches the public-sector template: a flat table with project name and manager, ID, area, decision, rationale, expected impact, contributors, approver and date. It is easy to filter, easy to share and needs no tooling.
A page or database in your project tool. Good when the team already works there and wants to link decisions to tasks. The risk is that the log gets buried among other pages, so pin it where people look every week.
A short detail page per decision, linked from the table. Use this for technical or high-stakes choices. Microsoft's format includes Decision, Date, Alternatives Considered, Reasoning, a Detailed Document, Made By and Work Required. The UK Government Digital Service summarizes its architecture decision records as Title, Context, Decision and Consequences. Four headings, a few paragraphs, one page.
The table stays the index and the detail pages hold the long story. That split follows advice from a PMI article on project logs: keep a log to a few key fields and link to fuller forms or records. Duplicating long detail in both places only creates admin work.

When a one-line entry is enough
Most decisions need one row. Write a detail page when any of these is true:
- The decision is expensive or hard to reverse.
- Several stakeholders disagreed and the reasoning is likely to be challenged.
- The decision sets a technical or process standard other work will follow.
- A regulator, auditor or contract might ask about it later.
How to create and maintain the log, step by step
- Decide what counts as a decision. Not every choice belongs. Log the ones that change scope, budget, schedule, quality, vendors, architecture, or who is responsible for what. Choosing a meeting time does not make the cut.
- Pick one home for the log. One file or one page, with one link that everyone has. If you work with a client, agree on the location in your kickoff. Our 60-minute kickoff agenda has a natural slot for it.
- Set the columns. Start with the core four and add only what the project needs.
- Assign who captures. Usually that is the PM. Make it explicit, or everybody will assume somebody else did it.
- Capture at the moment of decision. Record the summary, owner and follow-up during the meeting or immediately after, while the context is fresh. A workflow guide suggests finishing the entry before the meeting ends, and PMI advises prompt updates and at least weekly maintenance.
- Link the evidence. Attach the proposal, risk assessment, ticket or email thread.
- Review regularly. The University of Waterloo's project office says its RAID log should be reviewed regularly with the project team and governance and updated with new information. A ten-minute pass in your weekly status meeting is enough: any decision still unresolved, any follow-up overdue, any entry that needs a new status.
- Close it out. At project closure, the same Waterloo guidance recommends reviewing the decision information, communicating outstanding implications during transition to operations and feeding outcomes into lessons learned. For freelancers, this is the log's second life: it feeds your handover pack and your retrospective.
What to do when a decision changes
Do not edit history. Add a new entry, link it to the one it replaces and change the old entry's status to Superseded. The UK Government Digital Service says a superseded record must be clearly marked, and the original reasoning stays visible. This is also what makes the log useful in a client dispute: you can show the sequence, not just the current state.
Using the log to protect scope
For an independent PM, the decision log does a second job: it is a quiet form of scope control. When a client asks for a change, you log it as a decision with its impact on time and cost, and the client approves it by name. Requests stop feeling like casual favors and start looking like trade-offs. If this is a recurring pain point, pair the log with our five-step scope creep process.
The same habit helps with a new client. When you start a role, the previous PM's decision log tells you what was settled and why, which saves you from re-opening questions the client considers closed.
Our perspective
We see the same pattern across freelance and consulting engagements: the PMs who look most reliable are rarely the ones with the fanciest tools. They are the ones who can say, in one sentence, what was decided, when, by whom and why.
That is why we treat a decision log as a core client-facing habit, not paperwork. It is the cheapest way to show a client that you run a controlled project, and it is the first thing that pays off when you transition from a corporate job into independent work, where nobody else keeps your institutional memory for you.
Our approach at The Freelance PM Club is a structured pathway: practical templates, a community of other independent project managers who share how they actually run engagements, and coaching for the moments when a project gets political. We would rather you adopt a four-column log that you use every week than a twelve-column one you abandon by week three.
Ashanti
Get the rest of the toolkit
A decision log works best next to a few other documents: a kickoff agenda, a RAID log, a handover checklist. The Freelance PM Club brings these together with expert-led courses, a PM-specific community and career coaching for independent project managers and consultants. Membership starts with Job Board Access at $5 per month, with Freelancer Pro at $10 per month and Freelancer Elite at $20 per month. You can compare the tiers on our membership plans page.

If you are weighing a move from corporate to freelance work and want a second opinion on how to run your first engagements, our coaching is a good place to start the conversation.
Common mistakes to avoid
- Logging everything. A log with 300 trivial rows hides the six decisions that matter. Set a threshold and keep to it.
- Recording the decision without the reason. A row that says "Use vendor X" with an empty rationale is a reminder of nothing.
- No named owner. "The team decided" means nobody is accountable. Write one name.
- Writing it up weeks later. Memory edits the story. Capture it in the meeting.
- Copying long documents into the log. Link instead.
- Building a template nobody uses. Consistency beats sophistication. A searchable, regularly reviewed log is worth more than an elaborate one that sits untouched.
FAQ
What should be in a decision log?
At minimum: the decision, the date, the decision-maker and the rationale. Most teams add an ID, the alternatives considered, the expected impact, contributors, a status and a follow-up action with an owner. Link to supporting documents rather than pasting them in.
What is the difference between a decision log and a decision register?
In practice, nothing. Both names describe a structured record of project decisions with their reasoning, owners and dates. Use whichever term your client or organization already uses, so the document is easy to find and refer to.
How often should I update a decision log?
Capture each decision during or right after the meeting where it is made, and review the whole log on a regular schedule, such as weekly in your status meeting. Waterloo's project office recommends regular review with the team and governance, and PMI advises at least weekly maintenance.
What do I do when a decision is reversed?
Leave the original entry in place and mark it Superseded. Then add a new entry that explains the change and links back to the first one. This keeps an honest trail of what was decided at each point and why it changed.
When do I need a longer decision record instead of a row?
Write a short detail page when the decision is costly, hard to undo, contested or sets a standard for later work. Keep the log as the index, with title, context, decision and consequences on the linked page.
Sources
- Connecticut Department of Social Services Enterprise PMO, decision log
- Microsoft Engineering Fundamentals Playbook, decision log
- UK Government Digital Service, architecture decisions
- PMI, Risks, issues, and changes: help, I'm drowning in logs
- University of Waterloo PMO, RAID log
- ProjectManager, decision log template
- ITManagement101, decision log template
- Joel Parker Henderson, decision record
- Workhint, decision log workflow
