Flagship service
Know what was approved. Know what changed. Know whether you can still rely on it.
The service
An approval is rarely unconditional. It depends on evidence, assumptions, suppliers, controls, architecture, operating conditions, risks, people, data and other dependencies.
Those conditions can change while the organisation continues behaving as though the original decision still stands.
CEREARK establishes the approval basis, identifies the material conditions and dependencies, compares them with current operating reality, and determines where change has affected the strength of the original decision.
Two routes
Both routes produce a usable dependency set. They carry different evidential strength and effort, which we state explicitly.
Evidenced route
We establish the dependency set from the recorded decision: its evidence, assumptions, conditions, owners, controls and material dependencies.
Reconstructed route
We reconstruct the dependency set from operating reality and available evidence. We do not imply that an adequate original record existed.
What we establish
What leadership receives
Where it applies
A system now uses a different model, dataset or decision role from the one assessed.
Approval depended on controls or mitigations that were later weakened or normalised.
Data location, service architecture, subcontracting or operating assumptions changed.
Temporary acceptance conditions quietly became permanent operating dependencies.
Begin with the decision
We can determine whether Approval Integrity is the right focused intervention.
