Exposure Readout
The first paid verification step.
Independent board-level verification of whether operational road exposure can be evidenced as stable, or whether the organisation is relying on assumed control. One question, fixed scope, existing evidence, board-ready artefact in five to seven working days.
The QuestionCan operational road exposure be evidenced as stable, or is the organisation relying on assumed control?
ORRE does not design, implement, rewrite, certify, or advise on operational controls. The Readout verifies the evidence position and identifies the next governance decision. It establishes whether that evidence position can support a claim of system stability before a regulator, court, insurer, or inquiry asks for it.
Four Entry Streams
Where the verification question sits most sharply.
The Readout can be applied at four entry points. Instrument, duration, and output format are identical across all four.
IBoard File Verification Review
Tests whether the board-level record can evidence operational road exposure as stable, or whether it shows activity, incidents, assurance, and assumed control. Reviews existing board-level material only: risk committee papers, executive safety reports, critical control assurance reports, risk register extracts, incident and near-miss summaries, contractor governance reporting, assurance schedules, internal audit summaries, and board-reported regulator correspondence.
ORRE is not auditing the file. ORRE is verifying whether the file would withstand a regulator, court, insurer, or inquiry asking for evidence of system stability.
Board-altitude entry point. Can be authorised without admitting operational weakness. Output: the Board File Evidence Position.
IIContractor Interface Readout
Tests whether the exposure created at a single contractor interface can be evidenced as controlled, or whether control is assumed across the handover between organisations.
IIICorridor Readout
Tests whether the exposure across a single road corridor can be evidenced as stable under current operational load.
IVSite Readout
Tests whether the operational road exposure at a single site can be evidenced as stable, or whether the operating system has diverged from the documented system.
Scope and Method
What the Readout requires, and what it does not.
DurationFive to seven working days
ScopeOne board file, one contractor interface, one corridor, or one site
Data basisExisting documents and data only
Operational disruptionNone
Site shutdownNone
Workforce interviewsNone, unless separately scoped
Four Outcomes
Every Readout concludes with one of four findings.
IEvidenced stable
The evidence position can support a claim of system stability within the defined scope.
IILimited verification gap
The evidence position is largely sound but contains a defined gap requiring targeted action.
IIIMaterial verification gap
The evidence position cannot currently support a claim of system stability. Full OREX Diagnostic is the recommended next step.
IVInsufficient evidence to determine stability
The available evidence does not allow the verification question to be settled either way within the defined scope.
Finding IntegrityA finding that no material gap is evidenced within scope is a successful Readout outcome. The value of the Readout is the defensibility of the evidence position, not progression to a further engagement.
