Analysis & Strategy
Decision Log
MyPMP
QMS Template
| # | Decision | Made by | Date | Rationale |
|---|---|---|---|---|
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Decision Log for $1/mo, or get everything with membership ($9/mo or $99/yr).
π§ Analysis & Strategy
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Decision Log template
A Decision Log is a running record of the significant decisions made across a project, capturing what was decided, who decided it, and the reasoning behind it. It creates an auditable trail that prevents teams from relitigating settled questions and clarifies accountability when circumstances or personnel change. Without one, the rationale behind key choices tends to evaporate the moment the meeting ends.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Decision Log
- βΈWhen a steering committee or sponsor approves a scope, budget, or vendor choice that shapes downstream work
- βΈDuring Agile ceremonies or governance boards where architectural or trade-off decisions need to be traceable
- βΈWhen onboarding new stakeholders who need context on why earlier paths were chosen or rejected
- βΈIn audits, stage gates, or post-project reviews where you must demonstrate due diligence
What a good Decision Log includes
- βDecision ID and date, so entries can be referenced unambiguously
- βA clear statement of the decision and the question or issue it resolves
- βDecision owner and any approvers or bodies consulted
- βRationale and the options considered, including why alternatives were rejected
- βStatus (proposed, approved, superseded) and any linked risks, assumptions, or actions
- βImpact or affected areas, such as scope, cost, schedule, or specific deliverables
What's inside this template
The interactive form above gives you:
A table of #, Decision, Made by, Date, RationaleNotes
Tips & common mistakes
- π‘Log the decision when it is made, not weeks later β reconstructed rationale is rarely accurate
- π‘Record rejected options and their reasons; this is what stops the same debate resurfacing
- π‘Mark superseded decisions rather than deleting them, so the history of a reversal stays visible
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
How is a Decision Log different from a RAID log?οΌ
A RAID log tracks risks, assumptions, issues, and dependencies as ongoing conditions, whereas a Decision Log records the concrete choices made to address them. Many teams cross-reference the two so each decision links back to the risk or issue that prompted it.
Who is responsible for maintaining the Decision Log?οΌ
The project manager or PMO typically owns the log, but the decision owner supplies the rationale and approval details. Keeping it centrally accessible ensures stakeholders can update and consult it without version conflicts.
What makes a decision worth logging?οΌ
Log any decision that affects scope, budget, schedule, quality, or direction, or that would be costly to reverse or hard to explain later. Routine operational choices with no lasting impact usually don't warrant an entry.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membershipRelated free apps
More Analysis & Strategy templates