01 / DEFINE
Set the boundary.
Identify the system, period, claim, criteria and exclusions before examination.
EVIDENCE READINESS ASSESSMENT · PAID, AGREED SCOPE
Start with one defined system, one bounded question and the records available. Examine whether that evidence is traceable and suitable for the decision—and where further work is needed.
Evidence readiness is one assessment route. It is not a prerequisite for every ODA3 Institute service.
Discuss an evidence-readiness assessment →Security, AI governance, risk and leadership teams with an identified system, question, authorised access and a funded examination need.
THE EXAMINATION QUESTION
Define the claim, scope and control context, then examine the records that actually exist. A question may remain unresolved when evidence is unavailable, stale, contradictory or outside scope.
HOW IT WORKS
Define the question and its scope, identify the control context, then follow the evidence through provenance and verification to a finding with explicit limitations.
01 / DEFINE
Identify the system, period, claim, criteria and exclusions before examination.
02 / EXAMINE
Examine source, provenance, operating state and suitability against defined criteria.
03 / RECORD
Document readiness, missing or conflicting evidence and the work needed for a stronger conclusion.
Requirement → Control → Evidence → Provenance → Verification → Finding → Bounded Assurance
The wider assurance chain provides context. This engagement examines evidence readiness; it does not automatically deliver assurance over the system.
THE BOUNDED ASSESSMENT
The final scope is agreed in writing before records are examined. This describes responsibilities and outputs, not a promise of a particular finding.
01 / YOU BRING
Name the system and version, operating environment, relevant period and claim to be examined. Identify the records you know exist and your authority to make them available. Send no credentials or sensitive evidence with the first enquiry.
02 / WE DEFINE
ODA3 Institute documents the question, applicable criteria, permitted inputs, exclusions, evidence use and review terms. Responsibilities, fees and handling arrangements are agreed before technical work begins.
03 / WE EXAMINE
We examine source, provenance, integrity, relevance and conflicts against defined criteria. Missing, stale or contradictory evidence remains visible; it is not replaced by assumption.
04 / YOU RECEIVE
The Evidence Readiness Report records what the examined evidence supports, partly supports or leaves as a gap or unknown, where those outcomes are defined by the agreed method. It states limitations and what further evidence could change the answer.
Outside this assessment: certification, a general safety or compliance claim, and conclusions about unexamined systems, versions, environments or periods.
| Scope element | What we agree |
|---|---|
| Subject | System, version, configuration, environment and accountable owner. |
| Question | Claim, control or decision to be examined; applicable criteria. |
| Evidence | Available records, permissions, provenance, exclusions and observation period. |
| Delivery | Named responsibilities, duration, client effort, fees, report recipients and permitted reliance. |
One Evidence Readiness Report describing scope, records considered, their traceability and suitability for the question, gaps, limitations and recommended next steps.
The report informs your next decision. Any further examination or remediation support requires a separately agreed scope; there is no obligation to continue.
If the assessment identifies fragmented records or missing traceability, evidence reconstruction may be an appropriate next step under a separately agreed paid scope. It is not an automatic follow-on engagement.
Explore Evidence Reconstruction →No certificate, general maturity score, legal compliance determination or assurance over unexamined controls. No assertion that a system is safe or compliant. Results do not extend to unexamined versions, periods or environments; missing evidence is not resolved by assumption.
START WITH A QUESTION
A short written note can establish whether this assessment is an appropriate route. Identify the system and claim, operating context, known record types and any immediate constraint.
Describe available evidence at this stage. Exchange of sensitive records follows agreed permissions and secure handling arrangements.
INITIAL SCOPING NOTE
For system [name/version], in [environment/period], what do the available records establish about [specific behaviour or control]?
Illustrative wording only. Do not send credentials, confidential files or personal datasets with the initial enquiry.
Discuss the assessment scope →Fees, duration and client effort are quoted after commercial qualification. They depend on scope, access and the condition of the records.
The proposal identifies responsibility and the competence needed. Relevant conflicts are screened before acceptance; unmanageable conflicts exclude the work.
No confidential records or credentials should accompany an initial enquiry. Evidence exchange follows agreed permissions and secure handling arrangements.
A useful first note identifies the system, the question, the types of records available and your authority to commission the work. Describe the evidence initially; do not attach confidential records.