The Record That Stops at Approval
Decision records are built to capture what was decided. They do not necessarily capture what would have to remain true for that decision to still be sound.
Decision records exist primarily to serve retrospective accountability: what was decided, by whom, on what basis, at what time. This is necessary and well established. What is less well established is a forward-facing function: preserving the conditions a decision depended on, so that if those conditions change, the record itself signals that the decision may need to be revisited.
The gap. Many consequential decisions are, explicitly or implicitly, conditional — sound given a set of assumptions about market conditions, partner performance, regulatory posture, or internal capacity. Standard decision records capture the decision and its stated rationale at the moment of approval. They typically do not capture, in any structured or monitored way, which of those underlying conditions would need to change before the decision should be reconsidered. The record is complete as a historical artifact. It is inert as a forward-looking one.
Why this matters. A decision approved on the assumption that a specific condition would hold can continue to be executed, referenced, and relied upon long after that condition has quietly changed, because nothing in the standard decision record structure is designed to notice. The record does not lie — it accurately reflects what was decided and why, at the time. It simply has no mechanism for flagging that the “why” may no longer apply.
What a living record requires. Some organizations have moved toward treating decision records as living documents — mutable artifacts that accumulate dated updates as new information arrives, rather than static files that are closed at the moment of approval. This is a promising direction, but it requires more than mutability; it requires that the record explicitly name, at the point of approval, which underlying conditions the decision depends on, so that later updates have something specific to check against rather than requiring someone to reconstruct the original reasoning from scratch.
Governance consequence. Without this forward-facing structure, an organization can be executing against a decision whose foundational assumptions have silently failed, with no governance mechanism positioned to notice, because the decision record was designed only to answer “what did we decide,” not “is what we decided still valid.”
What this requires in practice. Obraval’s interpretation is that a consequential decision record can serve a forward-looking governance function if it preserves the conditions on which the decision depends and gives the organization some way to recognize when those conditions materially change.
Evidence boundary. The general shift toward mutable, living decision records is documented in emerging organizational and knowledge-management practice. The specific recommendation to structure records around explicit dependency conditions, checked against ongoing reality, is Obraval’s interpretation and synthesis rather than an established industry standard.
The executive question. For any significant standing decision, what would have to change in the world for this decision to no longer be sound — and is anything actually watching for that change?