Decision tracking and decision history
Decision tracking records what was decided, when, by whom, why, and what later changed. A useful decision history preserves the original context and links superseding decisions instead of overwriting them, allowing teams to distinguish a current decision from a proposal, rejected option, or obsolete direction.
What should a meeting decision record contain?
A decision record should contain a concise decision statement, status, decision date, decision-maker or accountable group, relevant conditions, source context, and links to affected work. It should also distinguish the selected option from proposals and capture later corrections or superseding decisions without erasing the original record.
Role frameworks such as Atlassian's DACI model can clarify who drives, approves, contributes, and is informed. The chosen model should match the organisation's decision rights.
How should changed decisions be recorded?
Create a new current decision and link it to the superseded record. Preserve both statements, evidence, dates, responsible actors, and the reason for change. Mark the earlier decision as superseded rather than deleted so later reviewers can reconstruct what guidance applied at each point in time.
What is contradiction review?
Contradiction review compares a candidate decision with relevant earlier records to identify statements that may no longer agree. It is a prompt for human review, not proof of conflict: scope, timing, conditions, terminology, or changed circumstances may explain why two statements appear inconsistent.
An August review approves a September release. A later risk review recommends October. A reviewer links both records, confirms the newer direction, and marks the September decision as superseded.
Decision history checklist
- Use one clear decision statement per record.
- Record conditions and effective dates.
- Identify the decision authority.
- Attach direct source context.
- Link affected actions, risks, and documents.
- Preserve correction and supersession history.
Limits and authorship
A complete history does not prove that a decision was lawful, informed, or successful. Decision rights, retention duties, and approval requirements depend on organisational and legal context.
Written by Ragu Mantatikar, Founder of Groundnote. Groundnote is an interested vendor. Published and reviewed 4 September 2026.