01
Question
State the claim to be examined.
Decision pointIs the question precise enough to examine, and is it relevant to the decision?
HOW AN EXAMINATION WORKS
An examination connects a defined claim to the records available, verifies their basis against defined criteria and states what the record supports—or leaves unresolved.
The procedure applies the evidence chain. It does not imply that every system property has been examined.
Explore the eight steps →PROCEDURE
The procedure organises the work. It is distinct from the seven-element conceptual chain: Requirement → Control → Evidence → Provenance → Verification → Finding → Bounded Assurance.
01
State the claim to be examined.
Decision pointIs the question precise enough to examine, and is it relevant to the decision?
02
Identify the system, version, period, environment and exclusions.
Decision pointAre the boundary, authority and permitted use clear?
03
Identify the applicable requirements and examination criteria.
Decision pointWhat would count as support, contradiction or insufficient evidence?
04
Identify the records actually available.
Decision pointDo the records relate to the defined question and scope?
05
Establish origin, collection context, system state and time.
Decision pointCan the record be traced, and where does that traceability stop?
06
Verify basis, integrity and relevance against defined criteria.
Decision pointWhich checks were performed, with what results and unresolved limits?
07
State what the examined record supports, contradicts or leaves unresolved.
Decision pointDoes the conclusion follow from the record rather than assumptions?
08
Preserve the conditions constraining the conclusion.
Decision pointWhich gaps, exclusions or changes limit reliance on the finding?
The record may need to return to an earlier step when a scope, source or verification problem emerges. Completion of a sequence is not evidence that the requested conclusion is supported.
STOP RULE
A missing source, broken chain of custody, contradictory record or unsupported inference may prevent the requested conclusion. Record the boundary and its implications; do not supply a substitute claim.
OUTPUT
The examination record identifies the question, evidence base, verification performed, finding and material limitations. The agreed deliverable and permitted reliance are defined in the engagement scope.
A change in the system or evidence may require revisiting the finding. It does not extend automatically to a new release, configuration or operating period.
Explore the assurance model →ILLUSTRATIVE SYNTHETIC RECORD
This is a synthetic illustration of record structure, not client work or an examination performed by ODA3 Institute.
R-001 · INITIAL RECORD · T₀
Scope: A single action in a specified test environment and build.
Basis: A test protocol and synthetic log linked to the build and time.
Result: The observed attempt was blocked in those conditions.
Limit: No observation of production or other versions.
R-001.1 · SUBSEQUENT REVIEW · T₁
Trigger: A version change after the initial evidence cutoff.
Link: Reference R-001 while preserving that original record.
Status: The changed build remains unexamined.
Notably Absent: A basis for transferring the earlier conclusion to this build.
A subsequent review creates a dated, linked record. It does not silently alter the conclusion warranted by the earlier evidence.
APPLY THE METHOD
Evidence Readiness Assessment is one route when the suitability of existing records is unclear. It is not a prerequisite for every research, standards or assessment engagement.
Start with a non-confidential description of the decision, system and available record types. Technical examination begins under an agreed paid scope, with independence, authority and data-handling arrangements established.