# Decision log

> A dated record of decisions, their owners, reasoning, alternatives and conditions that could cause a review.

## What it means

What to record for each decision (date, decision, who decided, options considered, why, what would make you revisit it), decision log vs minutes vs a RAID log, and when it pays off (handovers, async teams, client work).

## A practical example

“Use option B” becomes useful history when it also records the date, owner, rejected option, reason and review trigger.

## Put it into practice

- Name the concrete situation before applying the label. Decision log is useful only when it changes a choice, boundary or next action.
- Make the state visible: write the owner, time, source or stopping condition down instead of relying on memory.
- Review what happened. Keep the part that reduced ambiguity and change the part that added ceremony without helping the work.

## How it relates to Plexii

the Project Hub starter puts a Decisions log note on a new desk (/help/desk-templates); Resume notes list Key decisions (/help/desk-resume); the Brain area includes Decisions (/help/plexii-areas).