Protected registryPublic registerIAS v3.4.0

Institutions can see what changed, what it affects and whether an existing acceptance record requires acknowledgement or reassessment.

Version and change control

IAS changelog

Every release records materiality, affected components, migration impact and review requirements. Active institutional outcomes remain bound to the version and evidence set originally reviewed unless the receiving institution expressly accepts a change.

No silent rule changes

Acceptance criteria, protocols and authority rules are versioned and cannot be rewritten retroactively.

Material changes create notices

Active IAS-5 and IAS-6 outcomes receive a protected impact notice when reassessment may be required.

Institution retains control

The receiving institution decides whether to acknowledge, condition, re-review or discontinue reliance.

Controlled release history

Version register

Latest release first.

Reliance continuity

How changes affect accepted reviews

01Scope the change

Identify whether the release changes presentation, workflow, criteria, assurance protocol, authority logic or decision status.

02Assess materiality

Presentation-only changes do not alter active reliance. Material governance changes may require institutional acknowledgement or reassessment.

03Notify affected records

Protected change notices link the new version to each active IAS-5 or IAS-6 outcome potentially affected.

04Record the institution’s response

The outcome remains unchanged, becomes conditional, enters reassessment or is withdrawn only through an authorised institutional record.