An evidence gap is not simply a missing file. It exists whenever a material claim or review requirement does not have enough reliable support.
Common types of evidence gaps
Missing evidence
A required document, confirmation, or source record is absent.
Weak attribution
A document exists, but the system cannot determine who produced it or whether the source is authoritative.
Stale evidence
The material may have been valid earlier but is no longer current enough for the review requirement.
Incomplete coverage
A document supports only part of the claim. For example, an invoice supports value but not proof of shipment.
Contradictory evidence
Multiple records support incompatible versions of the same material fact.
Unconfirmed interpretation
The files exist, but the meaning depends on an assumption that no authorized participant has confirmed.
Why gaps should remain visible
Poor systems turn unknowns into blank fields or silently select a preferred value. A review-ready workspace should preserve the distinction between:
- known and supported;
- claimed but unverified;
- conflicting;
- missing;
- not applicable.
Evidence gap versus risk decision
An evidence gap is an input to review, not an automated decision. Identifying it is review preparation only and does not approve or reject a transaction, funder request, payment, settlement, token movement, or capital execution.
A useful gap record
Each gap should include:
- the affected claim or requirement;
- why current evidence is insufficient;
- the source already checked;
- the participant expected to respond;
- the next review-only action;
- whether the gap blocks handoff readiness.
Making gaps explicit is one of the fastest ways to reduce repeated review work.