Governance
Decision Log Template
Six weeks later, nobody remembers why you chose Option B — or that you decided at all. A decision log fixes that. Use this free template to record decisions and their rationale — or let Planquora capture them automatically as your project runs.
What it is
A decision log is a running record of significant decisions: what was decided, the context and options, who made the call, and when. It's the project's memory.
Its real value shows up later — when someone questions a direction, revisits a settled trade-off, or a new team member asks "why is it built this way?" The log answers without a meeting.
When to use it
- Whenever a decision has lasting consequences or was contested.
- After steering meetings, design reviews, or change boards.
- Any time you pick between real options and want the rationale on record.
The template
ID D-01, D-02… | Decision What was decided, in one sentence | Date When it was made | Context / rationale Why — the problem and reasoning | Options considered What else was on the table | Decided by The accountable decision-maker | Status Active / Superseded / Revisit on <date> |
|---|---|---|---|---|---|---|
| D-01 | Adopt PostgreSQL over MySQL for the platform | 2026-07-15 | Need JSON support + strong tooling; team familiarity | MySQL, MongoDB | Tech lead + PM | Active |
| D-02 | Launch to a single region first, expand later | 2026-07-20 | Reduce scope risk; validate before scaling | Multi-region at launch | Sponsor | Active |
| D-03 | Defer SSO to phase 2 | 2026-07-22 | Not required by launch customers; frees two weeks | Build SSO now | Sponsor + PM | Revisit on 2026-10-01 |
Tips
- Capture the rationale, not just the decision. The 'why' is what stops re-litigation.
- Log the options you rejected. Knowing what was considered is as useful as the choice.
- Name a decider. Decisions without an owner tend to unravel.
- Mark decisions as superseded rather than deleting them — the trail matters.
Browse all free templates or read the Help Center.