METHODS / DECISIONS AND OWNERSHIP / DECISION LOG
PRACTICE
Decision Log
A decision log is the shared record of material decisions for a team, project, or leadership group. It records what was decided, who had authority, why the choice was made, what it affects, and whether a later decision replaced it.
Leadership choices that cross functions. Budget, vendor, policy, launch, and scope decisions that may be questioned later. Policy exceptions that change how future cases should be handled. Anything a board follow-up depends on.
The log needs a clear materiality rule. Record the decisions people may need to execute, explain, review, or revisit, while leaving routine choices out.
WHAT IT IS
How a decision log preserves history.
A decision log captures the decisions people may need to understand, execute, review, or revisit later. Meeting notes may supply the source material, and a task tracker may carry the resulting work, but the log remains the place for the confirmed decision and its reasoning.
When a decision changes, keep the earlier entry and mark it as superseded. Create a new entry for the current decision and explain what changed. This preserves the history without treating a reasonable revision as a mistake.
FIT
When a decision log is useful.
Reach for it when
- A leadership decision affects several functions.
- The hiring sequence or organization design changes.
- A budget, vendor, policy, launch, or scope choice may be questioned later.
- A board or investor follow-up depends on a confirmed decision.
- A policy exception changes how future cases should be handled.
- Ownership may change before the consequences are fully known.
Use a different record when
- The choice is a routine preference or a small task.
- The idea has not become a decision yet.
- The matter is a sensitive employee or legal issue and the record would be broadly accessible.
- It is an emergency where writing first would delay action. Act, then record the decision afterward.
THE RECORD
What each entry should capture.
Include enough context for someone outside the original discussion to understand the current decision and act on it.
- Decision title and ID
- Date and current status
- Decision owner or final authority
- The final decision
- The question or context
- Rationale and evidence used
- Options considered
- Consequences and affected work
- Follow-up owner and date
- Review or reopen trigger
- Supersedes or superseded by
- Access level
HOW TO SET IT UP
Create one reliable decision record.
EXAMPLE
A launch-date decision.
Decision: move the enterprise launch from October 1 to October 15. Owner: the CEO. Reason: two required security controls remain incomplete, and leadership considers the exception risk greater than the cost of a two-week delay. Alternatives considered: launch to all customers, limit the first release to pilot customers, or delay. Consequences: Sales updates the forecast, Product changes customer communications, and the board receives a schedule note. Review trigger: reconfirm on September 29 if the security work remains incomplete.
This fictional entry gives future readers the decision, authority, reasoning, alternatives, consequences, and condition for review.
KEEP IT USEFUL
Common implementation and access considerations.
Common implementation issues
- Logging so many small choices that the record becomes unusable.
- Recording the answer without the reasoning.
- Reconstructing the reasoning months later.
- Maintaining several competing logs.
- Editing an old entry until the original decision disappears.
- Leaving the active decision unclear.
- Recording a decision without connecting it to action.
People and access considerations
- A written record can expose disagreement, reversals, and unclear authority. Use neutral language.
- Restrict sensitive entries rather than watering the whole log down.
- Allow a concise record of material dissent.
- The decision owner should confirm the final entry before it becomes the official record.
AI AND JUDGMENT
Use AI to prepare the record. The decision owner confirms what became official.
AI can help
- Draft a proposed entry from approved meeting notes or a transcript.
- Extract the proposed decision, rationale, options, actions, and review conditions.
- Find related entries and flag a possible conflict or superseded decision.
- Draft links between the confirmed decision and affected projects or actions.
People remain responsible for
- Confirming that a decision was actually made.
- Verifying the decision, authority, scope, rationale, and effective date.
- Setting the access level for sensitive entries.
- Approving the official entry and any later supersession.
A convincing summary does not prove that a decision occurred. Off-record context, disagreement, or unclear authority may be missing from the source material.
SOURCES
What the guidance agrees on.
Documented professional practice
Decision logs are established practice in government, project, and technical work. The sources below consistently emphasize timely capture, clear ownership, rationale, and preserving the record when a decision changes.
View sources (4)OpenClose
WHERE IT FITS