PCS CHG 001 Programme Change and Transition Control Procedure_v1.0

Document Control

Document identification

• Document code: PCS-CHG-001

• Title: Programme Change and Transition Control Procedure

• Scope: How PCS initiates, reviews, approves, publishes, and transitions changes to controlled documents, methodologies, tools, templates, registry rules, labels, and claims requirements

• Crediting outcome: Not applicable (governance procedure)

Version history and change log

Table DC-1. Revision history

Version	Date	Status	Summary of changes	Prepared by	Approved by
v1.0	TBD	Draft	Initial release for public consultation	PCS Secretariat	TBD

Superseded versions

No superseded versions for v1.0.

Governance note on versioning and archiving

Only the latest approved version of this Procedure shall be used. Superseded versions shall be archived and retained for traceability and audit purposes. Printed or downloaded copies are uncontrolled; stakeholders must refer to the PCS-published version as the authoritative current version.

Chapter 1 - Community summary

1.1 What this Procedure is

This Procedure explains how PCS changes its rules and documents (standards, methodologies, tools, templates, registry rules, labels and claims). It defines how changes are proposed, assessed, approved, published, and how projects transition from old to new requirements.

1.2 Why this matters

If programme rules change without clear transition rules, projects and buyers face uncertainty and inconsistent treatment. This Procedure makes updates predictable and auditable, while allowing PCS to act quickly when integrity risks are identified.

1.3 Who this applies to

Actor	What they do in this procedure
PCS Secretariat / Standards Secretariat	Maintains the change register, classifies changes, manages consultations, and publishes change notices.
Technical panels / reviewers	Provide technical impact reviews for major or urgent integrity changes.
Governance / approval authority	Approves major changes and emergency integrity changes under defined authority rules.
Project proponents and VVBs	Apply transition rules and update documentation when required.

1.4 Change types at a glance

Change type	What it means
Minor change	Clarification, correction, or editorial improvement that does not materially affect eligibility, crediting outcomes, or stakeholder rights/obligations.
Major change	Could materially affect eligibility, quantification outcomes, credit volumes, integrity risk, labels/claims, or stakeholder rights/obligations.
Emergency integrity change	Time-critical major change required to address a demonstrated integrity risk (for example systemic over-crediting risk, fraud vector, or legal/regulatory requirement).

1.5 Common scenarios

• Scenario 1: A methodology is updated to close a gaming loophole. Outcome: The change is classified, consulted (unless emergency), approved, and published with clear transition rules stating which projects are affected and by when.

• Scenario 2: PCS discovers a systemic over-crediting risk. Outcome: PCS may implement an emergency integrity change immediately, publish the rationale, and consult retrospectively where appropriate.

• Scenario 3: A minor editorial correction is needed. Outcome: A minor change is approved by the document owner with compliance review and published in the change log.

Chapter 2 - Purpose

This Procedure defines how changes to the PCS programme (including standards, methodologies, procedures, tools, templates, registry rules, and labels/claims requirements) are proposed, assessed, approved, implemented, and communicated, including transition arrangements for projects and issued credits.

Chapter 3 - Scope

This Procedure applies to all PCS programme rules and controlled documents. It does not govern project-specific post-registration changes, which are handled under the project-cycle processes.

Chapter 4 - Definitions

Term	Definition (PCS)
Major change	A change that could materially affect eligibility, quantification outcomes, credit volumes, integrity risk, labels/claims, or stakeholder rights/obligations.
Minor change	A change that does not materially affect outcomes (for example clarifications, editorial corrections, non-substantive improvements).
Emergency integrity change	A time-critical major change required to address a demonstrated integrity risk.
Transition period	A defined period during which existing projects may comply with prior requirements, subject to conditions.

Chapter 5 - Change initiation and logging

All proposed changes shall be recorded in the Programme Change Register maintained by the PCS Secretariat.

Minimum content of a change request	Requirement
Description and rationale	What is changing and why.
Impacted documents/clauses	Specific documents and clauses affected.
Proposed effective date	Date the change becomes active.
Transition proposal	Which projects/credits are affected and transition duration.
Integrity risk assessment	How the change affects integrity and gaming risk.
Stakeholder impact assessment	Who is impacted and likely costs/benefits.

Chapter 6 - Classification and impact assessment

The PCS Secretariat shall classify each change as Minor, Major, or Emergency integrity change and shall obtain technical and integrity reviews proportionate to the change.

Chapter 7 - Consultation requirements

Change category	Minimum consultation approach
Major methodology changes	Public consultation unless emergency integrity change.
Major non-methodology changes (registry rules, labelling rules)	Stakeholder consultation proportionate to impact, normally not less than 15 calendar days.
Emergency integrity changes	May be implemented without prior consultation, with rationale published and retrospective consultation where appropriate (normally within 60 days).

Chapter 8 - Approval authority

Change category	Approval rule
Minor change	Approved by the document owner with compliance review.
Major change	Approved by PCS governance following required reviews and consultations.
Emergency integrity change	Approved by delegated authority for urgent action with notification and subsequent ratification.

Chapter 9 - Transition rules and grandfathering

PCS shall define transition arrangements for each Major change, including which project stages are affected, required updates, end dates for prior requirements, and integrity conditions for grandfathering.

Grandfathering shall not be used to permit continued application of a requirement where PCS has identified a demonstrated integrity failure that materially increases over-crediting risk or double counting risk.

Chapter 10 - Communication and publication

PCS shall publish change notices that include a summary of the change, documents impacted, effective date, transition rules, and links to consultation materials where applicable. PCS shall maintain a public change log for active programme rules and methodologies.

Chapter 11 - Implementation and verification of effectiveness

Document owners shall update controlled documents, record approvals, and withdraw obsolete versions from use. PCS shall review the effectiveness of Major changes within six months of the effective date, including any unintended consequences or gaming vectors.

Chapter 12 - Records retention

PCS shall retain change requests, review reports, consultation materials, approvals, and implementation evidence for at least seven years from the effective date of the change.