Keep the decision and the evidence together
A decision log records what was decided, who had authority to decide it and the evidence available at that time. Preserve rejected options and define a reason to revisit the decision. Track subsequent actions separately so that completing a task does not rewrite the original rationale.
Use one record per decision. A meeting note can contain several decisions, open questions and actions; linking to the note alone can leave readers unsure which statement was authorised.
Copy this decision record
| Field | Fill in |
|---|---|
| ID, date and status | Proposed, decided, superseded or withdrawn |
| Question | The choice that needs an authorised answer |
| Options | Alternatives considered, including retaining the current approach |
| Evidence and limits | Sources inspected and what they do not establish |
| Decision and rationale | Selected option, reason and any conditions |
| Authority | Person or body authorised to decide |
| Actions | Owner and completion evidence for each follow-up |
| Revisit trigger | New evidence, changed condition or a stated review date |
| History | Prior decision reference and reason for any replacement |
Synthetic example: incomplete handoff data
A delivery team expects twelve months of history but has evidence of only eleven. The example does not establish whether the missing month exists elsewhere or whether the customer would accept a smaller scope.
| Option | Evidence needed | Decision state |
|---|---|---|
| Obtain the missing month | Source owner confirms availability and permitted access | Open check |
| Proceed with eleven months | Appropriate scope authority accepts the limitation | Proposed alternative |
| Delay the affected analysis | Decision owner assesses dependency and consequence | Proposed alternative |
The team records a decision to ask the source owner for the missing month by an agreed date. That is a decision about the next check. It is not approval to reduce the delivery scope. If scope later changes, create a linked decision with its own authority and rationale.
Review without erasing history
When new evidence arrives, compare it with the recorded assumptions. If it changes the chosen option, mark the earlier decision superseded and link the replacement. Retain the old evidence reference so someone can understand why the earlier choice was made.
Avoid confidence percentages unless the team has a defined way to produce and interpret them. A clear statement such as “availability has not been checked with the source owner” is more useful than an unexplained score.
Use the sales handoff example to identify commitments that need decisions. The log then preserves the authorised response. It does not establish that the eventual outcome was caused by that decision; outcomes need their own evidence.
Which decision is authorised, and what would justify revisiting it?
Preserve the decision, rejected options, authority and conditions for a later review.
Your starting question: Which decision is authorised, and what would justify revisiting it?
Start by checking
- Identify the decision rather than only an action.
- Record options and evidence limitations.
- Link any replacement to the prior decision.
Evidence to gather
- Decision record and source references.
- Authority and changed conditions.
Not established yet
- The decision caused a later outcome.
- A next-check decision authorises a scope change.
