Board AI Risk Intelligence | 3 November 2026 | Approval Is Not Evidence
Issue 04 · Board AI Risk IntelligenceThe Decision Layer™ · Executive Edition

Approval Is Not Evidence.

A signed approval proves that somebody said yes. It does not prove what they knew, which assumptions mattered, what challenge occurred, or why the decision was reasonable at the time.
Published3 November 2026
Read time15 minutes
Use forThe next 30 days
DI focusEvidence
01 · Executive summary

Three evidence decisions need attention before assurance becomes archaeology.

Governance often preserves the approval and loses the decision. That distinction matters most when an outcome is challenged months later and the organisation has to explain not only who signed, but why signing was reasonable.

Decision 01

Define minimum decision evidence.

Specify what must exist before a consequential AI-enabled decision is accepted: material facts, assumptions, alternatives, challenge, authority and rationale.

Decision 02

Separate approval from rationale.

A workflow timestamp is evidence of approval. It is not evidence of judgement. Preserve the reasoning that made the approval defensible.

Decision 03

Decide what must survive.

Evidence scattered across email, model logs, meeting notes and vendor portals is evidence in theory. In practice, it is archaeology.

A defensible decision is not one with perfect information. It is one whose evidence, assumptions and reasoning can still be understood after the room has emptied.
02 · The evidence problem

Most organisations preserve activity better than judgement.

AI systems generate more data than most governance teams could ever read. That can create a false sense of evidential abundance. Logs multiply. Dashboards thicken. Approvals acquire timestamps. Yet the material context of the decision can remain surprisingly fragile.

Decision Evidence is narrower and more demanding. It asks what a reasonable outsider would need in order to understand why the decision made sense given what was known at the time.

What often survivesWhat often disappears
Approval timestampWhy the approver believed the evidence was sufficient
Model outputWhich assumptions and thresholds shaped reliance on it
Meeting invitationWhat challenge materially changed the discussion
Final recommendationWhich alternatives were rejected and why
System logWhat the human understood, questioned or accepted
03 · Five evidence failure patterns
01

The approval survives. The rationale does not.

The organisation can prove that the decision passed governance, but not why the evidence was judged sufficient.

02

The output survives. The context does not.

The recommendation remains available after the model version, prompt, policy threshold or source data have changed.

03

The vendor owns the evidence.

Critical reasoning depends on logs or documentation that sit outside the organisation and may not be retained on the same timetable.

04

The challenge happened, but left no trace.

A strong question changes the decision. Minutes record the outcome, not the objection that improved it.

05

The evidence is everywhere.

Nothing is missing individually. The problem is that reconstruction requires six systems, three inboxes and somebody who still remembers the meeting.

04 · The minimum evidence test

Before accepting a consequential decision, ask whether six things would survive it.

Evidence elementWhat should be recoverable later
Material factsThe information actually available when the decision was made
AssumptionsThe conditions believed to be true, including uncertainty
AlternativesMaterial options considered and why they were not selected
ChallengeThe objections, tests or contrary views that mattered
AuthorityWho had the right to decide, approve, stop or override
ReasoningWhy the final decision was reasonable in its original context
Board implication

The question is not whether every decision needs a dossier. It is whether the evidence requirement scales with consequence. A low-impact workflow may need a compact receipt. A material decision may need a reconstructable decision trail.

05 · Board questions
  1. For our most consequential AI-enabled decisions, what evidence must exist before approval?
  2. Can we distinguish evidence of approval from evidence supporting the decision?
  3. Which parts of the decision trail depend on a supplier retaining records for us?
  4. Could we explain why a decision was reasonable if the outcome was poor?
  5. What evidence is deliberately not retained, and why?
  6. Who decides when the evidence base has changed enough to reopen the decision?
06 · Actions for the next 30 days
ActionTest of completionOwner
Define a minimum evidence standardMaterial AI-enabled decisions have a documented evidence requirement proportionate to consequenceCRO / AI Governance
Test one past decisionA reasonable outsider can reconstruct the evidence and reasoning without relying on memoryCAE / Assurance
Review supplier evidence dependencyContracts and retention arrangements support the organisation's reconstruction needsCIO / Procurement
Create reopening triggersMaterial changes in model, data, policy, supplier or operating context force reconsiderationExecutive owner
Decision Infrastructure View
Component affected
EVIDENCE
Governing question
What makes this decision defensible?
Decision affected
Whether a consequential AI-enabled decision has enough surviving context to justify reliance and later scrutiny.
Accountable owner
The executive who owns the decision, supported by risk, legal, technology and assurance as appropriate.
Evidence needed
Material facts, assumptions, alternatives, challenge, authority and reasoning linked to the decision.
Reopening trigger
A material change in model, data, supplier, policy, operating condition, risk exposure or underlying assumption.
Executive decision required
What is the minimum evidence we require before accepting this class of decision?
Approval is not evidence.

An approval tells us somebody said yes. Decision Evidence tells us why yes was reasonable at that moment.

Decision Infrastructure · Authority · Evidence · Boundaries · Traceability · Challenge · Reopening

Next: Decision Signals, 10 November. The Audit Trail Is Not the Decision Trail.