Decision Reconstruction Risk

Decision Reconstruction Risk (DRR) is present when the reasoning behind a decision lived in the decision-maker's knowledge, in a conversation, or in context that was obvious at the time, rather than on the page. The decision may have been sound. The record still cannot demonstrate why it was reached. When that record is later examined, in litigation, audit, investigation, or a public-records request, by someone who was not there, it cannot answer the only question that matters under scrutiny: how was this conclusion reached?

DRR is not "bad documentation"

Decision quality and record defensibility are different properties. A decision can be excellent and its record can still carry high Decision Reconstruction Risk, because the basis was never committed to the page. A weaker decision can be fully reconstructable, because every step was anchored. DRR does not measure whether a decision was right. It measures whether an independent reviewer could rebuild the reasoning from the record alone. That is what determines whether an organization can defend the decision later.

Why AI accelerates DRR

Context is perishable, so DRR has always existed. What is new is that AI-assisted drafting produces records that are fluent, confident, and professionally worded at scale, and fluency is not evidence. The old warning signs of a weak record, prose that read as rushed or vague, are exactly what a language model smooths away. The result is a record that looks more finished while being less reconstructable. AI raises the volume and the polish of records without guaranteeing that the basis for the conclusion is present. DRR now spreads while wearing the appearance of its opposite.

How to recognize it

A record carries Decision Reconstruction Risk when one or more of the following is true:

• The basis for a conclusion is asserted but not identifiable in the record.
• The chronology cannot be rebuilt from the record's own dates.
• The path from evidence to conclusion (its Decision-Process Traceability) is not visible on the page.
• Evaluative characterizations appear without a documented anchor.
• The record depends on its author remaining available to explain it.

Related terms

Managing it

Naming a problem is how a discipline begins to manage it, as "technical debt" and "alert fatigue" did in their fields. Decision Reconstruction Risk is diagnosable before a record is finalized, and it can be detected, reduced, and designed out of a workflow. The Justification Review Standard (JRS) is a record-level review method built for exactly that: a five-condition check applied before a record becomes permanent. The tool matters less than the recognition. The first step is to treat "the record did not hold up" not as bad luck or bad writing, but as a specific, nameable condition with specific causes.