ICEQC-GOV-006 — Version, Revision and Transition Rules cover

Official ICEQC controlled document

ICEQC-GOV-006 — Version, Revision and Transition Rules

Sets the rules for editions, amendments, corrections, supersession and transition periods.

Issued byInternational Council for Education Quality Certification

Document
ICEQC-GOV-006:2026
Version
2026
Language
EN
Document text
View document
ICEQC-GOV-006 — Version, Revision and Transition Rules
ICEQC-GOV-006 — Version, Revision and Transition Rules cover

Controlled document record

Document
ICEQC-GOV-006:2026
Edition
2026
Version
2026
Status
Published
Authoritative language
EN
1

Scope

#
1.1

This document governs the lifecycle of every published ICEQC controlled document and the effect of an edition, amendment, correction, interpretation, supersession, withdrawal and transition notice.

1.2

It establishes the public rules by which a reader can determine which text applied to a certification object at a stated time and prevents a published obligation from being changed without traceable authority.

2

Immutable publication

#
2.1

A published edition is an immutable record.

2.2

Its authoritative content, document number, edition identifier, language status, publication date, content hash and approval record shall not be overwritten or silently replaced.

2.3

A normative change shall be issued through a new edition or a controlled amendment.

2.4

A correction may repair an error only within the limits stated in this document.

2.5

Archived representations shall remain retrievable or otherwise verifiable after a later publication takes effect.

3

Edition

#
3.1

An edition is a complete approved state of a controlled document identified by its document number and edition designation.

3.2

A new edition shall be used where changes materially restructure the document, alter several requirements, change scope or certification architecture, consolidate amendments, or make continued citation of the former text unreliable.

3.3

The edition record shall identify the preceding edition, the nature of the change, publication and effective dates, and any transition arrangements.

4

Amendment

#
4.1

An amendment is an approved change to specified provisions of a published edition without republication of the complete edition as a new edition.

4.2

It shall identify every affected clause, the exact added, replaced or deleted text, the reason for change, normative impact, approval authority, publication date, effective date and transition rule.

4.3

An amendment forms part of the cited edition from its effective date and shall be presented with that edition wherever omission could mislead the reader.

5

Correction

#
5.1

A correction repairs a typographical, formatting, numbering, cross-reference, metadata, translation or comparable error that does not change the intended normative effect.

5.2

It shall identify the original and corrected text and the date of correction.

5.3

If a proposed repair could reasonably change who is subject to a provision, what is required, the evidence needed, applicability, a deadline or a conformity outcome, it is not a correction and shall be processed as an amendment or new edition.

6

Interpretation

#
6.1

A published interpretation explains how existing authoritative text is applied to an identified ambiguity.

6.2

It shall cite the provision, state the question, explain the conclusion and identify the approving authority and date.

6.3

An interpretation shall not create a new obligation, exception, evidence threshold or scope condition.

6.4

Where clarification cannot be achieved without changing normative effect, ICEQC shall issue an amendment or new edition rather than rely on interpretation.

7

Classification of change

#
7.1

Each proposed change shall be classified by effect, not by its length or label.

7.2

An editorial change affects presentation without changing normative meaning.

7.3

A limited normative change alters one or more obligations without redesigning the document.

7.4

A major revision changes scope, architecture, central concepts or a substantial body of requirements.

7.5

The public change record shall state the classification and the reasons for it.

7.6

A change shall be treated at the higher level wherever reasonable readers could disagree about whether conformity may be affected.

8

Change transparency and impact

#
8.1

A new edition or normative amendment shall be accompanied by a public change summary sufficient to identify substantive differences and their intended effect.

8.2

Where clause identifiers or requirement locations change, a disposition or correspondence table shall permit traceability from the preceding text.

8.3

The impact statement shall address affected certification scopes, evidence, assessment activity, certificates, translations, digital representations and transition needs.

8.4

The summary is informative and does not replace the authoritative text.

9

Publication date and effective date

#
9.1

The publication date is the date on which an approved document becomes publicly available in controlled form.

9.2

The effective date is the date from which the document may or shall be applied as stated in its transition notice.

9.3

The dates may be the same only where immediate effect is justified and does not unfairly prejudice affected parties.

9.4

Before the effective date, a published document shall be clearly identified as not yet effective and shall not be represented as the sole current certification basis.

10

Transition principles

#
10.1

A transition shall be proportionate to the magnitude, urgency and implementation burden of the change and shall protect the reliability of existing certification.

10.2

The notice shall state the beginning and end of the transition, the editions that may be used, the treatment of applications and current certificates, any required additional verification and the consequence of not completing transition.

10.3

A transition shall not permit the selective combination of provisions from different editions unless a published amendment expressly defines that combination.

11

Default transition periods

#
11.1

An editorial correction may take effect on publication.

11.2

Unless the approved notice states a different justified period, a limited normative amendment shall allow six months and a new edition containing major normative change shall allow twelve months from publication before exclusive application.

11.3

An approved transition may range from immediate effect to twenty-four months where urgency, learner protection, legal change, implementation complexity or continuity of valid certification supports that result.

11.4

Any departure from the default shall be stated with reasons in the public transition notice.

12

Applications and certificates during transition

#
12.1

An application, assessment and certification decision shall identify one applicable edition and its effective amendments.

12.2

A certification decision shall not be based on an undisclosed mixture of editions.

12.3

During an authorized transition, a new application may use an edition permitted by the transition notice; the resulting certificate shall identify that edition and shall not remain valid beyond any applicable transition deadline without the required transition decision.

12.4

A current certificate remains governed by its recorded edition until expiry, transition, reduction, suspension, withdrawal or another outcome expressly stated in the notice.

13

Supersession and withdrawal

#
13.1

A superseded document has been replaced for future use but remains part of the historical record.

13.2

A withdrawn document is no longer available as a basis for new certification from the stated date.

13.3

The public record shall identify the successor, if any, and the effect on existing certification.

13.4

Supersession or withdrawal does not retroactively invalidate a decision that was properly made under the applicable edition, but it does not extend that decision beyond its certificate, transition or surveillance conditions.

14

Systematic review

#
14.1

Each normative governance, certification, core-requirement and scheme document shall be reviewed at least once every five years after publication and earlier where material legal, technical, educational or societal change, repeated interpretation requests, inconsistent conformity outcomes, stakeholder evidence or an identified risk to public trust indicates a need.

14.2

Review shall result in confirmation, amendment, new edition or withdrawal.

14.3

Confirmation preserves the edition and shall be recorded with the review date and responsible authority.

15

Emergency change

#
15.1

ICEQC may authorize an accelerated amendment, correction, suspension of a provision or shortened transition where continued use would create a material risk to learners, legal compliance, validity, security, impartiality or the integrity of certification.

15.2

The public notice shall identify the risk, affected text, temporary or permanent effect, authority, effective date and review date.

15.3

Emergency treatment shall be no broader or longer than necessary and shall not be used to avoid ordinary consultation for reasons of convenience.

16

Archive, authenticity and citation

#
16.1

Every lifecycle action shall preserve the document number, edition, language, status, relevant dates and relationship to earlier and later records.

16.2

The Standards Register shall identify the current text and shall distinguish it from development, superseded and withdrawn texts.

16.3

A content hash or equivalent integrity mechanism shall permit verification of the controlled digital representation.

16.4

A citation remains historically valid only when it identifies the edition and any amendment necessary to reconstruct the text applied.

17

Lifecycle-state model

#
17.1

Every controlled version shall occupy one defined lifecycle state and shall move only through an authorized transition permitted for its document class.

17.2

For lifecycle-state model, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

17.3

States shall distinguish proposal, development, consultation, approval, publication, supersession, withdrawal and archive and shall identify when normative effect begins or ends.

17.4

The lifecycle-state model record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

17.5

A status event affecting current use shall state the applicable date and any overlap with another permitted state.

17.6

Any lifecycle-state model effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

17.7

Technical storage state, visibility or workflow completion shall not substitute for institutional status.

17.8

No action concerning lifecycle-state model shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

18

Project-proposal state

#
18.1

A project proposal records a request to develop, revise or withdraw a document and has no normative, approval or certification effect.

18.2

For project-proposal state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

18.3

The record shall identify the need, intended scope, proposer, related documents and authorization outcome.

18.4

The project-proposal state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

18.5

No transition applies until a competent body authorizes work and later publishes a change.

18.6

Any project-proposal state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

18.7

Public mention of a proposal shall not be presented as a commitment to adopt its wording or timetable.

18.8

No action concerning project-proposal state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

19

Development state

#
19.1

A version in development may be drafted, reviewed and tested but shall be clearly separated from published requirements.

19.2

For development state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

19.3

The record shall identify the exact iteration, responsible body and development purpose.

19.4

The development state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

19.5

Use in a pilot shall preserve the current published basis and shall not create provisional certification under the draft.

19.6

Any development state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

19.7

Distribution shall carry development status and shall not use current-edition links or publication metadata.

19.8

No action concerning development state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

20

Consultation state

#
20.1

A consultation version is a controlled draft released for a defined opportunity for public comment and has no certification effect.

20.2

For consultation state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

20.3

The exact text, hash, opening and closing dates, responsible body and submission route shall be recorded.

20.4

The consultation state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

20.5

A later consultation round shall identify changed text and shall not overwrite the draft on which earlier comments were made.

20.6

Any consultation state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

20.7

Consultation availability shall not cause the draft to replace the current edition in search or citation.

20.8

No action concerning consultation state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

21

Approved-for-publication state

#
21.1

A version approved for publication shall contain the exact content authorized by the final approval authority and shall be protected from substantive alteration.

21.2

For approved-for-publication state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

21.3

The approval record shall identify the content hash, conditions, authority and date while public status remains not yet published.

21.4

The approved-for-publication state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

21.5

Any delayed effective date or coordinated publication dependency shall be identified before release.

21.6

Any approved-for-publication state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

21.7

A material post-approval change shall return to the review and approval proportionate to its effect.

21.8

No action concerning approved-for-publication state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

22

Published state

#
22.1

Publication shall release the approved controlled text and metadata through an authorized public event and shall not silently substitute a different representation.

22.2

For published state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

22.3

The Standards Register shall identify edition, language, status, owner, approval authority, dates, hash and predecessor relationships.

22.4

The published state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

22.5

Publication may begin a preparation period before exclusive application and shall link to the governing transition.

22.6

Any published state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

22.7

A file accessible before the authorized event or mirrored afterward does not independently determine published status.

22.8

No action concerning published state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

23

Effective state

#
23.1

A published provision becomes effective only on the date and under the conditions assigned by its publication and transition record.

23.2

For effective state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

23.3

The record shall distinguish effective from publication, approval and download dates.

23.4

The effective state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

23.5

Where different provisions phase in at different times, each temporal boundary and certificate effect shall be unambiguous.

23.6

Any effective state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

23.7

A revised requirement shall not be applied adversely before effectiveness except through an authorized urgent protective measure.

23.8

No action concerning effective state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

24

Confirmed state

#
24.1

Systematic review may confirm a published edition without altering its content or edition identity where it remains fit for purpose.

24.2

For confirmed state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

24.3

The confirmation record shall identify the review scope, date, evidence, responsible body and next review point.

24.4

The confirmed state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

24.5

Confirmation shall not restart or extend an existing transition unless a separate notice lawfully does so.

24.6

Any confirmed state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

24.7

A silent decision to make no change is not controlled confirmation and shall not reset the review period.

24.8

No action concerning confirmed state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

25

Superseded state

#
25.1

An edition becomes superseded when an identified successor takes over new general use under a published relationship.

25.2

For superseded state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

25.3

The record shall identify the successor, effective date, transition and any continuing limited use.

25.4

The superseded state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

25.5

Existing certification may remain under the older edition only as authorized and shall not continue beyond the stated transition basis.

25.6

Any superseded state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

25.7

Superseded does not mean erased, invalid from inception or available for unrestricted new application.

25.8

No action concerning superseded state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

26

Withdrawn state

#
26.1

Withdrawal ends authorization to use a document or edition for new application from the stated date and shall identify any successor or cessation route.

26.2

For withdrawn state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

26.3

The public record shall state reason, authority, date and effect on pending work, certificates and claims.

26.4

The withdrawn state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

26.5

A transition may permit limited continuing use but shall not display the withdrawn text as current.

26.6

Any withdrawn state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

26.7

Withdrawal shall preserve historical access and shall not reuse the identifier.

26.8

No action concerning withdrawn state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

27

Archived state

#
27.1

Archive preserves a controlled historical record after active lifecycle use and shall retain the status and period that applied.

27.2

For archived state, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

27.3

The archive shall preserve content, metadata, relationships and authenticity sufficient for legal, certification and standards history.

27.4

The archived state record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

27.5

Archive presentation shall direct readers to any current successor and transition information.

27.6

Any archived state effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

27.7

Archiving shall not be used to conceal a current obligation, unresolved complaint or material correction.

27.8

No action concerning archived state shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

28

Authoritative source immutability

#
28.1

The approved normative content of a published edition shall remain immutable at its authoritative source.

28.2

For authoritative source immutability, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

28.3

Any changed content shall receive a correction, amendment, interpretation or new edition record and a new integrity value as appropriate.

28.4

The authoritative source immutability record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

28.5

Consolidated views shall identify incorporated actions and preserve access to the original publication.

28.6

Any authoritative source immutability effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

28.7

Routine website editing, content-management replacement or file regeneration shall not alter the approved text invisibly.

28.8

No action concerning authoritative source immutability shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

29

Equivalent publication representations

#
29.1

HTML, PDF, plain text, structured data and accessible representations may express one approved edition where normative content and identity remain equivalent.

29.2

For equivalent publication representations, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

29.3

The record shall identify representation-specific integrity where needed and the common controlled normative source.

29.4

The equivalent publication representations record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

29.5

A representation correction shall state whether other forms are affected and how readers can obtain accurate text.

29.6

Any equivalent publication representations effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

29.7

Layout differences shall not create or remove obligations, status, exceptions or clause relationships.

29.8

No action concerning equivalent publication representations shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

30

Change-request intake

#
30.1

Any person may propose correction, interpretation, amendment, revision or withdrawal by identifying the document, provision, issue and supporting reason at a level reasonably available to that person.

30.2

For change-request intake, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

30.3

The request shall receive a traceable disposition or be grouped with an equivalent issue without losing material reasoning.

30.4

The change-request intake record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

30.5

Receipt of a request does not suspend the current text unless an authorized protective notice states otherwise.

30.6

Any change-request intake effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

30.7

Commercial status, membership or drafting expertise shall not determine whether a material issue is considered.

30.8

No action concerning change-request intake shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

31

Change triage

#
31.1

A reported issue shall be classified for urgency, normative effect, scope, safety, legal, translation, digital and certification consequences before a change route is selected.

31.2

For change triage, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

31.3

The classification and reasons shall be recorded and reconsidered if later evidence shows greater effect.

31.4

The change triage record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

31.5

A potential conformity change shall receive normative controls pending resolution rather than an editorial shortcut.

31.6

Any change triage effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

31.7

Triage shall not decide the technical solution or prejudge a complainant's separate rights.

31.8

No action concerning change triage shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

32

Editorial change

#
32.1

An editorial change may correct presentation, spelling, punctuation, formatting or metadata only where normative meaning and public effect remain unchanged.

32.2

For editorial change, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

32.3

The record shall identify the error, correction, affected representations and date at a level proportionate to reliance.

32.4

The editorial change record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

32.5

Immediate incorporation may be permitted, but an edition-specific archive shall show the correction relationship.

32.6

Any editorial change effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

32.7

If scope, obligation, exception, evidence, timing or outcome could change, the action is normative.

32.8

No action concerning editorial change shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

33

Limited normative amendment

#
33.1

A limited normative amendment changes one or more identified obligations or effects without requiring complete architectural revision.

33.2

For limited normative amendment, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

33.3

The public record shall present exact old and new text, rationale, impact, approval, dates and comment history appropriate to the change.

33.4

The limited normative amendment record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

33.5

The transition shall address only affected requirements while maintaining coherence of the complete edition.

33.6

Any limited normative amendment effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

33.7

A series of limited amendments shall not be allowed to make the applicable text inaccessible or structurally unreliable.

33.8

No action concerning limited normative amendment shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

34

Major revision

#
34.1

A major revision shall be used where scope, architecture, central concepts, certification model or a substantial body of requirements changes.

34.2

For major revision, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

34.3

The project shall identify the predecessor, principal changes, public consultation, unresolved objections and complete new edition.

34.4

The major revision record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

34.5

The transition shall treat the new edition as a coherent whole and shall prevent selective mixing with the predecessor.

34.6

Any major revision effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

34.7

Calling a major revision an amendment shall not reduce due process or conceal its effect.

34.8

No action concerning major revision shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

35

Scope-changing revision

#
35.1

A change that includes new object classes, activities, users or exclusions shall be treated as normative even where existing requirement wording is unchanged.

35.2

For scope-changing revision, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

35.3

The impact record shall identify newly included and excluded populations and related schemes, modules and claims.

35.4

The scope-changing revision record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

35.5

Transition shall protect persons not previously subject and shall address certificates whose wording would become misleading.

35.6

Any scope-changing revision effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

35.7

Scope shall not be expanded through examples, search metadata, title change or interpretation.

35.8

No action concerning scope-changing revision shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

36

Rationale for change

#
36.1

A normative change shall state the problem, evidence, intended outcome, alternatives and reason the selected response is proportionate.

36.2

For rationale for change, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

36.3

The public rationale shall acknowledge material uncertainty, affected interests and unresolved opposition without overstating consensus.

36.4

The rationale for change record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

36.5

Transition length and urgency shall follow the stated impact and risk.

36.6

Any rationale for change effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

36.7

Rationale shall not replace clear normative text or enforce an intention absent from the approved words.

36.8

No action concerning rationale for change shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

37

Normative impact assessment

#
37.1

Before approval, ICEQC shall identify every provision whose applicability, obligation, permission, prohibition, evidence, timing or conformity outcome changes.

37.2

For normative impact assessment, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

37.3

A public summary and correspondence shall allow affected readers to locate material differences.

37.4

The normative impact assessment record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

37.5

Impact shall include direct and consequential changes across schemes, modules, assessment units and certificates.

37.6

Any normative impact assessment effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

37.7

A change shall be classified at the higher effect where reasonable analysis remains uncertain.

37.8

No action concerning normative impact assessment shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

38

Stakeholder impact

#
38.1

Change assessment shall consider learners, providers, certified clients, applicants, assessors, decision users, regulators and other materially affected interests.

38.2

For stakeholder impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

38.3

The record shall identify burdens, protections, access effects and stakeholder categories requiring consultation or communication.

38.4

The stakeholder impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

38.5

Transition shall provide meaningful preparation without preserving unacceptable risk solely for convenience.

38.6

Any stakeholder impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

38.7

A dominant market participant's implementation preference shall not be treated as the complete stakeholder impact.

38.8

No action concerning stakeholder impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

39

Legal and regulatory impact

#
39.1

A change touching law or regulated matters shall be reviewed for authority, jurisdictional variation and risk of misleading claims.

39.2

For legal and regulatory impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

39.3

The record shall distinguish ICEQC normative effect from external legal change and shall identify authoritative legal sources where relied upon.

39.4

The legal and regulatory impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

39.5

Urgent legal incompatibility may justify shortened transition but shall preserve governance approval and public reasons.

39.6

Any legal and regulatory impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

39.7

ICEQC shall not claim that revision itself grants legal compliance or recognition.

39.8

No action concerning legal and regulatory impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

40

Technical and evidence impact

#
40.1

A change shall be reviewed for effects on technology, interoperability, test methods, evidence availability, sampling, data and consistent binary decisions.

40.2

For technical and evidence impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

40.3

The record shall identify obsolete or newly required methods and any validation or pilot evidence.

40.4

The technical and evidence impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

40.5

Transition shall allow proportionate implementation and verification and shall address legacy systems or versions within scope.

40.6

Any technical and evidence impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

40.7

A preferred tool shall not determine the transition where equivalent evidence can achieve the outcome.

40.8

No action concerning technical and evidence impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

41

Certification impact

#
41.1

Every normative change shall identify whether it affects eligibility, application, assessment, findings, corrective action, technical review, decision, surveillance, recertification, certificate content or public status.

41.2

For certification impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

41.3

The Scheme and transition records shall be updated or expressly confirmed as unaffected.

41.4

The certification impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

41.5

No positive decision shall rely on a hybrid requirement set not authorized by the transition.

41.6

Any certification impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

41.7

Change shall not reopen a final historical decision retroactively absent fraud, error or authority expressly provided by the certification rules.

41.8

No action concerning certification impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

42

Digital and data impact

#
42.1

A lifecycle action shall consider reader data, identifiers, hashes, schemas, interfaces, permanent links, search, downloads and cached public representations.

42.2

For digital and data impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

42.3

The record shall map changed clauses and preserve machine and human equivalence.

42.4

The digital and data impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

42.5

Deployment timing shall follow institutional effectiveness and shall not cause a new rule to appear active early or remain active late.

42.6

Any digital and data impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

42.7

A technical migration shall not be classified as editorial where it changes public meaning or verification.

42.8

No action concerning digital and data impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

43

Language impact

#
43.1

A change shall identify every authoritative, co-authoritative, controlled and informative language version affected.

43.2

For language impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

43.3

Translation status, lag, corrected terminology and precedence shall be public under ICEQC-GOV-007.

43.4

The language impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

43.5

A non-authoritative translation may lag only with visible notice and shall not continue to present obsolete text as complete current content.

43.6

Any language impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

43.7

Translation difficulty shall trigger clarification of the source where it reveals material ambiguity.

43.8

No action concerning language impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

44

Intellectual-property impact

#
44.1

Revision shall consider rights in incorporated sources, contributions, marks, methods, data and translations and shall preserve lawful public access.

44.2

For intellectual-property impact, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

44.3

The record shall identify a material new license, patent or proprietary dependency and the solution adopted.

44.4

The intellectual-property impact record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

44.5

Transition shall address lawful use of old and new content without implying external endorsement.

44.6

Any intellectual-property impact effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

44.7

Rights concerns shall not be hidden by deleting approved text without correction history.

44.8

No action concerning intellectual-property impact shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

45

Change proposal publication

#
45.1

A substantive proposed change shall be published as an exact consultation draft with status, scope, change explanation and comment period.

45.2

For change proposal publication, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

45.3

The record shall identify the source edition and provisions affected and shall preserve the draft after consultation.

45.4

The change proposal publication record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

45.5

Expected effective and transition approaches shall be described sufficiently for informed comment.

45.6

Any change proposal publication effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

45.7

A proposal shall not be presented as certain future law or used for certification before approval.

45.8

No action concerning change proposal publication shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

46

Reconsultation after material change

#
46.1

A post-consultation change introducing a new material obligation, expanded scope, removed protection or different certification model shall receive renewed consultation.

46.2

For reconsultation after material change, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

46.3

The record shall identify changed provisions and why the earlier opportunity was insufficient for the new effect.

46.4

The reconsultation after material change record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

46.5

Reconsultation may be focused but shall include connected consequences needed for coherent comment.

46.6

Any reconsultation after material change effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

46.7

Editorial response to comments need not restart consultation where no new material effect arises.

46.8

No action concerning reconsultation after material change shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

47

Approval of change

#
47.1

A normative change shall complete technical, impartiality, legal and intellectual-property, governing-body and publication-authorization gates proportionate to its class.

47.2

For approval of change, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

47.3

The approval record shall identify exact content, unresolved objections, impact and transition.

47.4

The approval of change record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

47.5

Conditions imposed at approval shall be resolved visibly and shall not authorize later unreviewed technical rewriting.

47.6

Any approval of change effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

47.7

Approval shall not be inferred from elapsed time, silence or publication capability.

47.8

No action concerning approval of change shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

48

Change summary

#
48.1

A new edition or amendment shall provide a public summary of principal substantive changes and their intended effect.

48.2

For change summary, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

48.3

The summary shall distinguish editorial, limited normative and major changes and identify deleted protections or expanded scope.

48.4

The change summary record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

48.5

It shall link to detailed correspondence where many clauses changed and shall remain informative.

48.6

Any change summary effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

48.7

Omission from a summary does not erase a normative change, but a materially misleading summary shall be corrected and reliance assessed.

48.8

No action concerning change summary shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

49

Clause correspondence

#
49.1

Where numbering, structure or requirements change materially, ICEQC shall publish a mapping of predecessor and successor provisions.

49.2

For clause correspondence, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

49.3

Relationships shall identify unchanged, modified, split, merged, relocated, deleted and new content without claiming false equivalence.

49.4

The clause correspondence record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

49.5

Transition and assessment records shall cite the governing edition rather than substitute the mapping for requirements.

49.6

Any clause correspondence effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

49.7

A mapping correction shall preserve prior versions and shall not change normative text.

49.8

No action concerning clause correspondence shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

50

Correction notice

#
50.1

A correction notice shall identify the document, edition, location, erroneous and corrected forms, classification, authority and date.

50.2

For correction notice, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

50.3

The reader shall show whether the correction is incorporated and provide access to original publication history.

50.4

The correction notice record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

50.5

Where reliance could have affected assessment or a deadline, the notice shall state remedial treatment.

50.6

Any correction notice effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

50.7

A correction shall not be used to change intended normative effect.

50.8

No action concerning correction notice shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

51

Interpretation notice

#
51.1

An interpretation notice shall identify the ambiguity, controlling text, conclusion, reasons, authority, date and effect on application.

51.2

For interpretation notice, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

51.3

The notice shall be searchable with the interpreted edition and shall state if later incorporated or withdrawn.

51.4

The interpretation notice record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

51.5

Pending a disputed translation, no adverse finding shall rest solely on non-authoritative wording known to be unreliable.

51.6

Any interpretation notice effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

51.7

Interpretation shall not introduce a new rule under the appearance of continuity.

51.8

No action concerning interpretation notice shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

52

Amendment consolidation

#
52.1

ICEQC may provide a consolidated reading view incorporating effective amendments and corrections into the base edition.

52.2

For amendment consolidation, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

52.3

The view shall list incorporated actions, consolidation date and content integrity and preserve the original and separate change texts.

52.4

The amendment consolidation record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

52.5

Only effective provisions shall appear as current and future changes shall be distinguished.

52.6

Any amendment consolidation effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

52.7

Consolidation shall not create an edition, alter transition or resolve conflict by editorial choice.

52.8

No action concerning amendment consolidation shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

53

Emergency protective change

#
53.1

An emergency change may be authorized where delay creates unacceptable risk to learners, law, evidence integrity, security, impartiality or certification credibility.

53.2

For emergency protective change, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

53.3

The public record shall state risk, necessity, authority, affected text, immediate effect, duration and review.

53.4

The emergency protective change record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

53.5

Transition may be immediate or shortened while providing the safest reasonable implementation route.

53.6

Any emergency protective change effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

53.7

Commercial pressure, launch timing or administrative convenience shall not establish emergency.

53.8

No action concerning emergency protective change shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

54

Transition plan

#
54.1

Every change affecting conformity or certification activity shall have a transition plan approved with or before the effective change.

54.2

For transition plan, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

54.3

The plan shall identify affected documents, scopes, old and new dates, communications, implementation, assessment, decision, certificate, register and failure consequences.

54.4

The transition plan record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

54.5

Its period shall be sufficient for reasonable implementation and reliable assessment having regard to risk.

54.6

Any transition plan effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

54.7

Absence of a plan shall not authorize case-by-case unpublished arrangements.

54.8

No action concerning transition plan shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

55

Default transition period

#
55.1

Unless an approved notice states justified different treatment, an editorial correction may take effect on publication, a limited normative amendment ordinarily allows six months and a major new edition ordinarily allows twelve months before exclusive use.

55.2

For default transition period, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

55.3

The notice shall state reasons for any immediate, shorter, longer or staged period.

55.4

The default transition period record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

55.5

A period up to twenty-four months may be used where complexity and safe continuity require it, while urgent protection may require immediate effect.

55.6

Any default transition period effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

55.7

Defaults shall not override a specific Scheme or legal deadline approved through higher protection.

55.8

No action concerning default transition period shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

56

Transition communication

#
56.1

Affected persons shall receive or have accessible timely information sufficient to identify the change, applicability, actions, evidence, deadlines, certificate effect and assistance routes.

56.2

For transition communication, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

56.3

Public notices and direct communications shall use consistent dates and edition identifiers.

56.4

The transition communication record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

56.5

Acknowledgement may be required where the Scheme makes it material but silence shall not be treated as informed consent to a hidden rule.

56.6

Any transition communication effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

56.7

Language and accessibility arrangements shall be proportionate to the populations affected.

56.8

No action concerning transition communication shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

57

New applications during transition

#
57.1

A new application shall use an edition permitted by the transition notice and shall identify the selected basis before assessment.

57.2

For new applications during transition, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

57.3

Where more than one route is offered, eligibility, last application date and resulting certificate limit shall be clear.

57.4

The new applications during transition record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

57.5

An applicant shall not combine provisions or change route after adverse findings without the authorized treatment.

57.6

Any new applications during transition effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

57.7

A certificate under an older route shall not extend beyond the transition limit without a positive transition decision.

57.8

No action concerning new applications during transition shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

58

Pending applications

#
58.1

The transition plan shall state how applications already accepted, assessed or awaiting decision are treated when a new edition takes effect.

58.2

For pending applications, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

58.3

The record shall identify whether work continues, converts, requires gap assessment or must restart and who bears resulting information and timing consequences under published terms.

58.4

The pending applications record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

58.5

A pending case shall not be moved to a new requirement after assessment merely to secure a preferred outcome.

58.6

Any pending applications effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

58.7

Learner protection or legal necessity may require immediate additional safeguards with reasons and fair notice.

58.8

No action concerning pending applications shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

59

Current certificates

#
59.1

A current certificate remains governed by its recorded edition until expiry, authorized transition decision, reduction, suspension, withdrawal or another published transition event.

59.2

For current certificates, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

59.3

The register and transition notice shall identify the last permitted date and required conformity activity.

59.4

The current certificates record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

59.5

Surveillance may include transition verification as authorized but shall not treat future text as already applicable.

59.6

Any current certificates effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

59.7

Historic validity under an older edition shall not be marketed as current conformity to the successor after the deadline.

59.8

No action concerning current certificates shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

60

Surveillance and recertification

#
60.1

The plan shall coordinate transition with scheduled surveillance and recertification where this can produce reliable verification without weakening deadlines.

60.2

For surveillance and recertification, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

60.3

It shall identify additional or replacement activity, decision authority and effect of incomplete transition.

60.4

The surveillance and recertification record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

60.5

Scheduling convenience shall not allow a material changed requirement to escape assessment throughout the transition.

60.6

Any surveillance and recertification effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

60.7

Duplicate activity shall be avoided where the same evidence reliably serves both purposes and independence is preserved.

60.8

No action concerning surveillance and recertification shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

61

No mixed-edition decision

#
61.1

One certification decision shall identify one coherent requirement edition set and its effective amendments and modules.

61.2

For no mixed-edition decision, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

61.3

The decision record shall distinguish historic evidence from the requirements against which it is evaluated.

61.4

The no mixed-edition decision record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

61.5

A transition may authorize defined combined provisions only by publishing the exact combination and effect.

61.6

Any no mixed-edition decision effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

61.7

Assessor preference, system limitation or applicant choice shall not create an undisclosed hybrid.

61.8

No action concerning no mixed-edition decision shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

62

Translation during transition

#
62.1

Translated versions shall identify whether they incorporate the new edition or amendment and when they may be relied upon.

62.2

For translation during transition, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

62.3

The authoritative source and status shall remain visible where translation lags.

62.4

The translation during transition record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

62.5

Affected language users shall receive a meaningful route to understand changed obligations before exclusive application where practicable.

62.6

Any translation during transition effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

62.7

An obsolete translation shall not be presented under the new edition identifier.

62.8

No action concerning translation during transition shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

63

Claims and marks during transition

#
63.1

Public claims shall identify the edition where omission could imply conformity to a newer requirement not yet assessed.

63.2

For claims and marks during transition, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

63.3

The transition notice shall state when certificates, marks, digital badges and register descriptions must change.

63.4

The claims and marks during transition record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

63.5

Use under an older permitted edition shall not be described as certification to the successor.

63.6

Any claims and marks during transition effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

63.7

After the deadline, stale claims shall be corrected under ICEQC-GOV-009 and applicable certification rules.

63.8

No action concerning claims and marks during transition shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

64

Failure to transition

#
64.1

The transition plan shall state the status consequence where required implementation, assessment or positive transition decision is not completed by the deadline.

64.2

For failure to transition, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

64.3

The outcome may include scope reduction, suspension, expiry, withdrawal or another Scheme-authorized status and shall require competent decision where applicable.

64.4

The failure to transition record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

64.5

A missed deadline shall not be concealed by changing edition metadata on the existing certificate.

64.6

Any failure to transition effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

64.7

Fair notice and appeal rights shall remain while protection and public accuracy are maintained.

64.8

No action concerning failure to transition shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

65

Transition extension

#
65.1

An extension may be granted only under published authority and objective exceptional conditions and shall preserve learner protection and reliable certification.

65.2

For transition extension, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

65.3

The record shall identify scope, reason, new deadline, interim controls and public status.

65.4

The transition extension record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

65.5

Commercial inconvenience, delay in beginning work or desire to retain a favorable old requirement shall not alone justify extension.

65.6

Any transition extension effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

65.7

Comparable cases shall receive comparable treatment and the extension shall not silently amend the general transition.

65.8

No action concerning transition extension shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

66

External dependency transition

#
66.1

Where a change depends on law, external standards, testing capacity, technology or recognized evidence, the plan shall address availability, edition, rights and timing of that dependency.

66.2

For external dependency transition, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

66.3

The public record shall identify a material dependency and any contingency if it is delayed or withdrawn.

66.4

The external dependency transition record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

66.5

ICEQC shall not require impossible implementation or accept unsupported conformity merely because an external source changed unexpectedly.

66.6

Any external dependency transition effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

66.7

A contingency changing normative effect shall receive authorized publication.

66.8

No action concerning external dependency transition shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

67

Systematic review interval

#
67.1

Each normative governance, certification, requirements and scheme document shall be reviewed at least once every five years unless a shorter published interval applies.

67.2

For systematic review interval, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

67.3

The register shall show the last review and next due point and distinguish confirmation from revision.

67.4

The systematic review interval record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

67.5

Review shall consider the continuing suitability of transition defaults and current certified scopes.

67.6

Any systematic review interval effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

67.7

Failure to meet the interval shall be disclosed and remedied and shall not silently confirm the document.

67.8

No action concerning systematic review interval shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

68

Early review triggers

#
68.1

Review shall begin earlier where law, technology, educational evidence, stakeholder harm, repeated ambiguity, inconsistent findings, security, translation or document conflict materially challenges fitness.

68.2

For early review triggers, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

68.3

The record shall identify the trigger and any immediate protection while ordinary review proceeds.

68.4

The early review triggers record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

68.5

A high number of complaints is not required where one credible issue creates serious risk.

68.6

Any early review triggers effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

68.7

Early review shall not prejudge that change is necessary but shall reach a controlled conclusion.

68.8

No action concerning early review triggers shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

69

Review outcome

#
69.1

Systematic review shall result in confirmation, correction, amendment, new edition or withdrawal and shall identify reasons and authority.

69.2

For review outcome, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

69.3

The outcome shall address unresolved issues, evidence, stakeholder input and related documents.

69.4

The review outcome record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

69.5

Any resulting normative effect shall receive appropriate consultation, approval and transition.

69.6

Any review outcome effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

69.7

A review record shall not describe an unapproved draft as the adopted outcome.

69.8

No action concerning review outcome shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

70

Withdrawal without successor

#
70.1

Where no suitable successor exists, withdrawal shall state that the subject is no longer covered and shall prevent current links or claims from implying replacement.

70.2

For withdrawal without successor, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

70.3

The record shall address existing certification, pending applications, archives and external references.

70.4

The withdrawal without successor record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

70.5

A wind-down period may protect orderly cessation but shall not imply continuing scheme availability after its final date.

70.6

Any withdrawal without successor effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

70.7

Historical certificates shall retain their actual period without suggesting current certification.

70.8

No action concerning withdrawal without successor shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

71

Sunset provisions

#
71.1

A temporary provision may include a predetermined expiry or review date and shall state what occurs if no further action is approved.

71.2

For sunset provisions, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

71.3

The register and affected documents shall make the sunset visible and shall not rely on staff memory.

71.4

The sunset provisions record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

71.5

Transition before expiry shall address cases and certificates that would otherwise lack a governing basis.

71.6

Any sunset provisions effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

71.7

Passing the date shall not silently convert temporary text into permanent authority.

71.8

No action concerning sunset provisions shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

72

Status and date correction

#
72.1

An erroneous lifecycle status or date shall be corrected by the competent authority after assessing publication, certification and reliance effects.

72.2

For status and date correction, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

72.3

The correction record shall show old and new values, reason, date and affected representations.

72.4

The status and date correction record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

72.5

Where users reasonably relied on the error, remedial and transition treatment shall be stated.

72.6

Any status and date correction effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

72.7

Correction shall not fabricate an approval, publication or effective event that did not occur.

72.8

No action concerning status and date correction shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.

73

Lifecycle auditability

#
73.1

ICEQC shall be able to reconstruct every material document lifecycle event from proposal through archive using attributable records and stable identifiers.

73.2

For lifecycle auditability, the responsible and approving authorities shall act according to actual normative and public effect rather than the label, file size or urgency preferred by a proposer.

73.3

The public register shall expose the subset necessary to verify current and historical authority.

73.4

The lifecycle auditability record shall preserve the prior state, authority, dates, content identity, rationale and relationship necessary for a reader to reconstruct what applied at a stated time.

73.5

Migration, organizational change or supplier failure shall preserve event sequence and content identity.

73.6

Any lifecycle auditability effect on applicants, certified clients, assessment activity, certificates, translations, claims or external dependencies shall be stated through a proportionate published transition.

73.7

An unexplained gap affecting validity shall be treated as an integrity issue and shall not be filled by undocumented assumption.

73.8

No action concerning lifecycle auditability shall retroactively create a requirement, erase a lawful historical decision or permit an unpublished mixture of editions.