Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

All tools › Decision log

Saved in this browser only

The tool · project delivery

Decision log

Project
Kept by
1

The log

newest on top
IDDateDecision, and the why in one lineDecided byAlternatives consideredStatus

Why keep one

The rationale is the payload. Everyone remembers what was decided; nobody remembers why, and the why is what stops the re-litigating.

Record the rejected options. "We considered X and chose Y because Z" ends the "did anyone think of X" meeting before it starts.

Decisions have IDs like risks do. D-007 in a status report is checkable; "as discussed" is not.

Superseded, never deleted. A reversed decision stays visible with its replacement linked; that trail is the project’s memory.

Log it the day it happens. A decision log reconstructed at closure is fiction with dates.

Pairs with the RAID log, which tracks the moving parts; this one tracks the calls you made. Everything saves in this browser only.

Prefer paper? Download the blank sheet as a PDF. The thinking behind it, and the nine tools it works with, is in The Project.

General guidance from practice, not legal, HR, or financial advice. Everything you type stays in this browser and is never sent to a server.