Certifications PMP CertificationWorld’s top PM cert CSM: Certified ScrumMasterTop agile cert CAPMEntry-level PM cert PRINCE2UK & Europe standard View All Certifications ?
PM Guides Agile GuideComplete breakdown Scrum GuideRoles, ceremonies, artifacts EVM GuideAll formulas explained View All Guides ?
Career & Salary PM Salary 2026By country & level How to Become a PMStep-by-step roadmap 50 Interview QuestionsWith strong answers
PM Software Monday.com ReviewTop pick 2026 ClickUp ReviewBest value Best Free PM ToolsNo trials, truly free View All Software ?
Free Tools & Templates EVM CalculatorFree, no signup Gantt Chart MakerBuild & export free PMP Eligibility Checker30-second result Free PM Templates30 templates in Excel, Word and PDF
Get the Free PMP Guide ?
Free Template · Excel · Updated March 2026

Free Decision Log Template
Excel Download

Six months into a project, someone will ask "why did we pick that subcontractor?" or "who agreed to change the design?" A decision log gives you the answer. You record each important decision, who made it, what else was considered and why, one row at a time.

✓Excel (.xlsx)
✓Free: no signup
✓Updated March 2026
✓Category drop-down validation
✦
40 pre-numbered rows
DEC-001 through DEC-040, zebra-striped, frozen header, no gridlines: ready to share immediately.
✦
Category drop-down
Technical, Commercial, Scope, Schedule, Resource, Risk and Other: validated drop-down keeps the register filterable.
✦
Rationale + alternatives
Dedicated columns for alternatives considered and the rationale, the two fields most logs omit but most need.
✦
Decision Log Template
Free Excel template: instant download
Format Excel (.xlsx)
Rows 40 pre-numbered entries
Columns 9 fields per decision
Validation Category drop-down
Compatible Excel, Google Sheets, LibreOffice
Price Free: no signup needed
↓ Download Free Template

No email required. Instant Excel download.

Quick answer

A decision log is a running record of the significant decisions made on a project: what was decided, why, by whom and when. This free Excel template has 9 columns and a 7-category drop-down, so months later you can still answer questions like why a vendor was chosen.

This page is for recording choices once they are made. If you need to track problems that are happening now and still need a fix, use my issue log template. When an issue is settled by a decision, log the decision here and note the issue ID.

Decision Log template preview: 9 columns per decision, 7 decision categories, Who decided, when and why, Drop-down validation
What is inside the free decision log template.
01 · What's Included

What's in the decision log template?

The template is a single Excel sheet with a project details row and 40 numbered decision rows. Each row holds the full story of a decision: what was decided, who decided, what else was on the table and what changes because of it.

✦
From my experience: On my projects in the UAE, decisions made in a site meeting were often questioned months later by a new consultant engineer or a new client representative. A simple log of who decided what, when and why settled more of those arguments than any set of meeting minutes did.
ColumnFieldWhat to Enter
IDDecision NumberPre-filled DEC-001 to DEC-040. Add more by copying the last row downward.
DateDecision DateThe date the decision was formally made, not the date it was first discussed.
Decision MadeThe DecisionState the decision in one clear sentence starting with an active verb: "Selected AWS as cloud platform" not "AWS".
CategoryDrop-downTechnical / Commercial / Scope / Schedule / Resource / Risk / Other. Validated drop-down: keeps the log filterable by type.
Alternatives ConsideredOther OptionsList the realistic alternatives that were genuinely evaluated before this decision was made. "Azure, GCP" not just "other providers".
RationaleWhy This ChoiceThe specific reason this option was chosen over the alternatives. Should reference criteria: cost, risk, capability, timeline, existing relationships.
ImpactWhat ChangesWhat changes in the project as a result of this decision: scope, plan, resource, documentation that needs updating.
Decision ByOwnerThe person who made or formally authorised the decision. One named individual, not "the team" or "stakeholders".
Review DateOptional ReviewIf the decision may need revisiting (e.g. vendor shortlist before final award), set a review date. Leave blank for permanent decisions.
✦
The two columns that matter most: Alternatives Considered and Rationale. Most logs leave them out or fill them in vaguely. But when someone challenges a decision months later, they never argue about what was decided. They argue about why. These two columns are your answer.
02 · Decision Categories

Which decision categories should you use?

The Category drop-down has seven options. Using them consistently lets you filter the log, for example to pull all commercial decisions for a contract review.

✦
Technical
Architecture, technology stack, tools, build vs buy, coding standards
✦
Commercial
Vendor selection, contract terms, pricing model, procurement approach
✦
Scope
What's in and out, feature prioritisation, requirements interpretation
✦
Schedule
Milestone dates, phasing, sequencing, dependency resolution
✦
Resource
Team structure, role assignments, outsourcing, training decisions
✦
Risk
Risk response strategies, accepted risks, escalation thresholds
✦
Other
Governance, reporting, communication, anything that doesn't fit above
✦
Drop-down
All 7 are validated in-cell: no free text needed
03 · What to Log

What goes in a decision log?

People either log everything, so the log becomes too big to use, or log too little, so it is useless. Use one simple test: would forgetting why we made this decision cause problems later? If yes, log it.

Always Log These

Any decision that is difficult or costly to reverse. Any decision that affects more than one team member or work stream. Any decision that changes a project baseline or assumption. Any decision involving vendor selection, technology choice or architecture. Any decision where two or more stakeholders had competing preferences.

Don't Bother Logging These

Day-to-day operational choices with no lasting project impact. Decisions already documented in other formal project documents (e.g. an approved change request already records the decision and rationale). Routine administrative decisions like meeting scheduling or document naming conventions.

Writing a Decision Entry That Holds Up

✗ Weak entry
"Decided to use PostgreSQL. Agreed with team. Good for project."
No alternatives listed. No rationale. "Good for project" is not a reason. Useless in 6 months when someone asks why not MySQL.
✓ Strong entry
"Selected PostgreSQL as the primary database. Alternatives: MySQL, MongoDB. Rationale: existing team expertise in PostgreSQL, superior support for complex joins required by reporting module, open-source licence reduces cost vs Oracle. Decision by: Lead Architect (J. Ahmed), 14 March."
Specific decision, named alternatives, concrete rationale tied to project requirements, single named owner with date. Holds up to challenge.
✦
Update the log on the day, not at the end. Logs written at project close are always incomplete. Nobody remembers the reasons, the alternatives get mixed up and the dates are guesses. Add the entry within 24 hours, ideally right after the meeting where the decision was made.

How to fill it in: a construction example

This is an example only, written the way I would log decisions on a building project in the UAE. Notice that every row names the alternatives and one person who decided.

ID / CategoryDecision and decided byAlternatives consideredRationale
DEC-001 / CommercialAward the MEP package to Subcontractor B. Decided by: Project DirectorSubcontractor A (lowest price), Subcontractor CB could meet the chiller delivery date and already had shop drawings approved by the same consultant on a similar job. A had no capacity until later.
DEC-002 / ScheduleMove roof slab pours to night shifts in summer. Decided by: Construction ManagerDay pours with retarder, delay the roof slabAvoids the midday work break and heat risk to concrete quality. Consultant agreed and the night work permit was in place.
DEC-003 / ScopeUse the consultant-approved alternative floor tile. Decided by: Client RepresentativeWait for the specified tile, use a different supplierThe specified tile was a long-lead item. The alternative was approved through a material submittal at no extra cost. Linked to CR-007.

Mistakes I see with decision logs

  • Writing the entry days later from memory. Log it the same day, straight after the meeting.
  • Putting "the team" or "management" as the decision owner. Name one person.
  • Leaving the alternatives blank. That is the first thing people ask about when a decision is challenged.
  • Mixing open problems into the log. Problems belong in the issue log until someone decides how to fix them.
  • Overwriting a decision when it changes. Add a new row and refer to the old ID, so the history stays.
04 · Related Registers

Decision Log vs Action Log vs Issue Log

People often mix these three registers into one sheet. Keep them separate. Each one records a different thing, and each is easier to use on its own.

✦
Decision Log
Records: Choices Made
Past-tense. What was decided, by whom, why and what alternatives were rejected. Permanent record: entries are never deleted.
✦
Records: Tasks to Do
Future-tense. What needs to be done, by whom and by when. Entries close when the task is complete and verified.
✦
Records: Problems
Present-tense problems that have occurred and need resolution. May require escalation, a change request or a formal decision, which then gets logged in the decision log.

A simple workflow: an issue is raised in the issue log. The PM, or the change control board, decides how to resolve it. That decision goes in the decision log. Any tasks that follow go in the action item tracker. You use all three at the same time during execution.

05 · FAQ

Decision Log: 4 Common Questions

A decision log (or decision register) records the important decisions on a project: the date, who decided, the alternatives, the reason and the expected impact. It gives you an audit trail that settles disputes, helps new team members catch up and helps future projects. Many PMOs treat it as a standard project document that you keep updating through execution.
Each entry needs: a decision ID, the date, the decision in one clear sentence, the category, the alternatives you really considered, the reason you chose this option, the impact, one named decision owner, and a review date if it may need a second look. Alternatives and rationale matter most. Without them, the log tells you what but not why.
A decision log records choices already made, with the reason and impact. An action item tracker records tasks still to do, with owners and due dates. A decision often creates actions. For example, choosing a new supplier creates actions to update the procurement schedule and issue a purchase order. Keep them in separate registers so each stays clean.
Log any decision that would be hard or costly to reverse, affects more than one person, changes a baseline or assumption, or would be hard to explain later. That usually means supplier and technology choices, design choices, scope in or out, team structure, budget choices and risk responses. Skip day-to-day choices with no lasting impact, such as booking a meeting room.