PCS PP 013 Program Processes_v1.0

Document Control

Document identification

• Document code: PCS-PP-013

• Title: Program Processes (Operational Process Manual)

• Scope: Defines the end-to-end PCS operational procedures and decision pathways across the full PCS project lifecycle, including project submission, completeness/eligibility checks, stakeholder consultation, validation, registration, monitoring, verification, issuance, post-registration changes, crediting period renewals, VVB accreditation/oversight, grievances/appeals, methodology governance, and registry/blockchain operations.

• Program outcome: Establishes binding procedural controls and recordkeeping/transparency rules to ensure consistent administration, integrity, and traceability of PCS projects and Planetary Carbon Units.

Version history and change log

Table DC-1. Revision history

Version	Date	Status	Summary of changes	Prepared by	Approved by
v2.0	TBD	Draft	Release for public consultation	PCS	TBD

Superseded versions

v1.0 - superseded upon approval of v2.0.

Governance note on versioning and archiving

Only the latest approved version of this Operational Process Manual shall be used for administering PCS processes. Superseded versions shall be archived and retained for traceability and audit purposes, consistent with PCS governance rules.

Chapter 1 - Introduction

1.1 Purpose of the Manual

1. The PCS Operational Process Manual establishes the operational procedures governing the implementation of the Planetary Carbon Standard (PCS). It defines the processes, decision pathways, and institutional responsibilities that apply throughout the full lifecycle of PCS projects. This manual is intended to ensure consistency, transparency, and integrity in project registration, validation, monitoring, verification, issuance of Planetary Carbon Units (PCUs), and subsequent administrative actions.

2. It serves as a binding reference for Project Developers, Validation and Verification Bodies (VVBs), Host Country Authorities, the PCS Secretariat, and other stakeholders engaged in the governance and operation of PCS.

1.2 Scope and Applicability

1. This manual applies to all activities undertaken within the PCS project cycle, irrespective of project type or technological category. It governs the processes for project submission, assessment, validation, registration, monitoring, verification, issuance, post-registration adjustments, renewal of crediting periods, corrective actions, grievances, appeals, and registry administration.

2. The requirements contained herein shall be applied in conjunction with PCS Framework v2.0, approved PCS methodologies, sector-specific tools, accredited VVB procedures, and all applicable PCS governance instruments. Where discrepancies arise, PCS Framework v2.0 shall prevail.

1.3 Alignment with PCS Framework v2.0

1. PCS Framework v2.0 establishes the principles, governance architecture, and operational foundations for the standard. The present manual operationalizes those principles by providing procedural steps, administrative requirements, recordkeeping rules, and compliance expectations.

2. This manual reflects the provisions of PCS Framework v2.0, including governance structures, methodological rigor, environmental and social safeguards, monitoring and reporting expectations, validation and verification standards, registry operations, and Article 6 alignment. It further ensures that all processes remain consistent with internationally recognized best practices and transparency requirements.

1.4 Roles and Responsibilities

1. The operation of PCS involves several entities with defined mandates and responsibilities.

2. The PCS Regulatory Council functions as the highest oversight body, responsible for approving policies, major governance decisions, methodologies, and escalated appeals. It ensures that PCS remains credible, impartial, and aligned with international requirements.

3. The PCS Secretariat manages the day-to-day administration of PCS. This includes the receipt and assessment of project submissions, performance of completeness checks, assignment of VVBs where applicable, maintenance of registry operations, management of blockchain verification processes, and oversight of public information disclosures. The Secretariat ensures that procedural timelines and transparency requirements are upheld.

4. Validation and Verification Bodies (VVBs) provide independent assurance of project design and performance. Only VVBs accredited or approved under the PCS VVB accreditation procedures may conduct validation and verification activities. Their responsibilities include conducting impartial assessments, reviewing evidence, undertaking site visits where necessary, and issuing professional opinions in accordance with PCS requirements.

5. Project Developers are responsible for preparing and submitting all required project documentation, implementing monitoring plans, maintaining safeguard and SDG compliance, and responding to any requests for corrective actions, clarifications, or additional evidence.

6. Host Country Authorities or Focal Points issue authorizations where applicable, confirm alignment with national climate policies, and interface with PCS on matters relating to Nationally Determined Contributions (NDCs) or Article 6 provisions.

7. Stakeholders, including affected communities and the general public, may engage through public consultation processes or submit grievances under the PCS grievance and appeals mechanism.

1.5 Definitions and Abbreviations

1. Definitions and abbreviations relevant to the operational processes of PCS are provided in Annex C of this manual. These include terminology relating to governance, validation and verification procedures, safeguard assessment, issuance processes, registry operations, and Article 6 associated concepts. The Annex shall be consulted for authoritative definitions.

Chapter 2 - PCS Governance And Institutional Structure

2.1 Overview

1. The Planetary Carbon Standard (PCS) operates through a governance architecture designed to ensure independence, transparency, technical credibility, and operational efficiency. This governance structure defines the institutional roles, mandates, and responsibilities of all entities contributing to the development, assurance, and maintenance of the standard. The components of the governance system operate in a coordinated manner, ensuring that all decisions, assessments, and registry actions are undertaken in accordance with PCS Framework v2.0 and internationally recognized good practices.

2.2 PCS Regulatory Council

1. The PCS Regulatory Council serves as the apex decision-making authority within the PCS governance structure. It is responsible for approving policies, methodologies, major procedural decisions, and the outcomes of escalated appeals. The Council ensures that PCS remains aligned with international integrity frameworks, maintains impartiality, and operates in accordance with environmental and social safeguards.

2. The Council also oversees the performance of the PCS Secretariat, confirms the accreditation status of Validation and Verification Bodies (VVBs), and endorses significant updates to the PCS Framework and associated procedural documents.

2.3 PCS Secretariat

1. The PCS Secretariat is responsible for the administration and daily operation of the Planetary Carbon Standard. Its responsibilities include the receipt and preliminary assessment of project documentation, performance of completeness checks, facilitation of validation and verification assignments, supervision of registry processes, and maintenance of public information systems.

2. The Secretariat serves as the technical and administrative interface between Project Developers, VVBs, Host Country Focal Points, and the general public. It ensures that time-bound procedures, transparency requirements, and recordkeeping obligations are fulfilled. The Secretariat is also responsible for the management of blockchain-based registry processes, issuance activities, project validity tracking, and operational reporting.

2.4 Validation and Verification Bodies

1. Validation and Verification Bodies (VVBs) are independent entities approved or accredited under the PCS VVB Accreditation Procedure. They provide assurance that project designs, monitoring reports, and emission reduction calculations conform to applicable PCS methodologies, tools, and framework requirements.

2. VVBs operate independently of Project Developers and the PCS Secretariat. They are required to demonstrate technical competence, impartiality, adequate internal oversight, and compliance with PCS rules, including all provisions related to reporting, evidence review, site visits, and the issuance of professional validation or verification opinions.

2.5 Host Country Authorities

1. Host Country Authorities, typically designated as Focal Points, are responsible for authorizing or endorsing the participation of PCS projects within their jurisdiction. Their responsibilities include issuing Letters of Authorization where applicable, confirming alignment of projects with national climate strategies or Nationally Determined Contributions (NDCs), and ensuring compliance with national policies, laws, and regulatory frameworks.

2. For activities seeking use toward Article 6 mechanisms or international transfers, Host Country Authorities provide official authorization and implement corresponding adjustment procedures consistent with their national reporting obligations.

2.6 Project Developers

1. Project Developers are responsible for preparing, submitting, and maintaining all project documentation required under the PCS project cycle. Their responsibilities include compliance with applicable methodologies, adherence to safeguard and SDG requirements, implementation of approved monitoring plans, maintenance of credible and traceable data records, and timely response to requests for corrective action or clarification.

2. Developers must maintain engagement with affected stakeholders, ensure compliance with national environmental and social regulations, and uphold all obligations related to transparency and disclosure as defined under PCS Framework v2.0.

2.7 Stakeholders and Affected Parties

1. Stakeholders, including project-affected persons and members of the general public, may participate in the PCS process through public consultations or through the submission of grievances or comments. Their involvement supports transparency and ensures that project impacts are adequately considered during validation and monitoring stages.

2. All relevant stakeholder inputs are recorded, reviewed, and addressed in accordance with the PCS Grievance and Appeals Procedure.

2.8 Interaction Between PCS Institutional Bodies

1. The governance structure of PCS functions through coordinated interaction among the PCS Regulatory Council, the PCS Secretariat, VVBs, Host Country Authorities, and Project Developers. Each entity performs its responsibilities independently but in a sequenced and interdependent manner, ensuring that no single actor has undue influence on the outcome of the project cycle.

2. The Council provides strategic oversight, the Secretariat manages operations, VVBs ensure assurance integrity, Host Country Authorities provide sovereign authorization, and stakeholders contribute to transparency and accountability. This coordinated governance model ensures that PCS maintains its credibility and alignment with international expectations.

Chapter 3 - PCS Project Lifecycle Overview

3.1 General Overview

1. The PCS project lifecycle establishes a standardized sequence of steps through which all mitigation activities must pass in order to achieve registration, verification, issuance of Planetary Carbon Units, and continued compliance throughout subsequent crediting periods. The lifecycle is designed to ensure environmental integrity, methodological consistency, and transparent recordkeeping. All activities undertaken within the PCS system operate through this lifecycle unless otherwise specified in methodology-specific guidance.

2. The lifecycle integrates procedural controls, independent validation and verification, safeguard and sustainable development assessments, and registry-based governance. It is supported by the PCS Secretariat, governed by the PCS Regulatory Council, and subject to oversight by host country authorities where applicable.

3.2 Core Lifecycle Stages

1. The lifecycle consists of several operational stages beginning with project submission and concluding with the issuance of Planetary Carbon Units. Each stage is defined by specific procedural requirements and associated institutional responsibilities.

2. The initial stage involves submission of a project under the PCS Project Submission Form, together with all required documentation including the project description, applied methodology, monitoring plan, safeguard and SDG assessments, and evidence of host-country authorization where necessary. The Secretariat performs a completeness and eligibility assessment before assigning the project for validation.

3. During validation, an accredited Validation and Verification Body conducts an independent assessment of the project design, the applicability of the selected methodology, the baseline and monitoring approaches, safeguard compliance, stakeholder consultation outcomes, and any other requirements outlined in the PCS Framework and methodology. The VVB issues a Validation Report that forms the basis for the Secretariat’s registration decision.

4. Once registered, the project enters the monitoring phase. The Project Developer collects data in accordance with the approved monitoring plan and periodically prepares the PCS Monitoring Report. Safeguard and SDG compliance must be maintained and reported throughout the project’s implementation.

5. The verification stage follows submission of the Monitoring Report. An accredited VVB performs an independent evaluation of the monitored data, the reported emission reductions, the application of the methodology, and the overall integrity of the monitoring procedures. The VVB issues a Verification Report confirming the quantity of verified emission reductions for the period.

6. Following verification, the PCS Secretariat conducts a final assessment and proceeds with the issuance of Planetary Carbon Units. Each PCU is assigned a unique serial number and is recorded permanently in the PCS Registry and on the associated blockchain archive.

7. The lifecycle continues with the possibility of post-registration changes, renewal of crediting periods, and ongoing monitoring and verification cycles for as long as the project remains active under PCS.

3.3 Required Documentation at Each Stage

1. Each stage of the project lifecycle is supported by specific documentation requirements. These include, but are not limited to, the Project Submission Form, Validation Report, Monitoring Report, Verification Report, Post-Registration Change Request, and all safeguard and SDG assessment forms. Project Developers must ensure that all documents are complete, internally consistent, and submitted within the timelines established by the PCS Secretariat.

2. Validation and verification documentation issued by VVBs must comply with PCS templates and procedural rules. Host Country Letters of Authorization, where applicable, must be obtained and maintained by the Project Developer and submitted to the Secretariat for recordkeeping. All final decisions taken by the PCS Secretariat and Regulatory Council are recorded in the PCS Authorization Archive and reflected within the PCS Registry.

3.4 Transparency and Public Disclosure

1. The PCS system maintains a strong commitment to transparency and public accessibility of information. Project documentation that does not contain confidential or commercially sensitive material is made publicly available on the PCS Registry, including the Project Submission Form, Validation and Verification Reports, Monitoring Reports, summaries of safeguard and SDG performance, and issuance records.

2. Public consultation processes are conducted in accordance with the requirements outlined in this manual and the PCS Framework. The Secretariat ensures that stakeholder comments are recorded, published, and considered as part of validation and registration procedures. This transparency supports trust in the standard and promotes accountability across all participating entities.

3.5 Digital Registry and Blockchain Traceability

1. The PCS Registry provides the authoritative record of all project activities, decisions, and issuance events. Each registry entry is supported by an immutable blockchain record that captures verification hashes, timestamps, and serial numbers associated with Planetary Carbon Units. This digital architecture ensures that all transactions are traceable, tamper-resistant, and permanently accessible for audit and reporting purposes.

2. The Registry also facilitates tracking of unit ownership and retirement, provides interfaces for host country corresponding adjustment reporting, and ensures interoperability with national and international carbon market systems as needed.

Chapter 4 - Project Registration Process

4.1 Introduction to the Registration Stage

1. Project registration under the Planetary Carbon Standard represents the formal recognition that a proposed mitigation activity has satisfied all eligibility, methodological, safeguard, and procedural requirements necessary to qualify as a PCS-approved project. Registration confirms that the project is based on a credible design, applies the selected methodology appropriately, meets safeguard and SDG expectations, and incorporates a monitoring plan capable of generating reliable emission reduction data.

2. Registration is not an assurance of future issuance; rather, it establishes the foundational integrity of the project and authorizes the developer to proceed with implementation and monitoring activities under PCS governance.

3. The registration stage consists of five principal phases: submission, completeness assessment, eligibility review, public stakeholder consultation, and validation assignment, followed by a final registration decision. Each phase must comply with the requirements described in this chapter.

4.2 Project Submission Requirements

1. A project may be submitted to PCS once the Project Developer determines that all required documents are complete and consistent. Submission is made through the PCS digital registry interface using the approved PCS Project Submission Form (PSF v2.0).

2. A complete submission typically includes the Project Submission Form, the detailed project description, the applied methodology and all methodological tools, the monitoring plan, environmental and social safeguard assessments, SDG impact assessments, host country authorization (if applicable), evidence of stakeholder consultations, and all supporting technical documents. The Project Developer is responsible for ensuring that all documentation is internally consistent and reflects the latest project design.

3. Upon submission, the PCS Registry assigns a unique PCS Project ID. This identifier is retained throughout the project's lifecycle and is used in all subsequent registry entries, validation activities, verifications, monitoring reports, issuance events, and post-registration changes.

4.3 Completeness Assessment by the PCS Secretariat

1. Once a project is submitted, the PCS Secretariat conducts a formal completeness assessment. This assessment does not evaluate technical validity or accuracy; instead, it ensures that all required documentation is present, readable, and structured according to PCS templates.

2. The Secretariat verifies that the Project Submission Form is filled in fully, that the applied methodology is listed in the PCS methodology library or appropriately submitted for approval, that safeguard and SDG assessments are included, that monitoring plans correspond to the methodology requirements, and that any host country documentation is attached and valid.

3. f documentation is incomplete, the Secretariat notifies the Project Developer with a request for additional information. The project does not advance to eligibility assessment until all missing elements have been provided.

4.4 Eligibility Review

1. Following a positive completeness check, the Secretariat performs an eligibility review to determine whether the project meets the fundamental criteria for participation under PCS. This includes alignment with designated project types, compliance with PCS Framework v2.0, adherence to methodological applicability conditions, and conformity with safeguard requirements at the design stage.

2. The eligibility review also assesses alignment with host country climate strategies and determines whether additional national documentation is required. The Secretariat reviews any conditions or risks that may impede validation and identifies them for consideration during subsequent stages.

3. If the project is deemed ineligible, the Secretariat issues a formal decision stating the reasons for ineligibility. The Project Developer may revise and resubmit the project or file a governance appeal in accordance with Chapter 10.

4.5 Public Stakeholder Consultation

1. PCS requires that project developers conduct a public stakeholder consultation prior to or during validation. This consultation ensures that affected communities and interested stakeholders are informed about the project’s scope, potential impacts, and expected benefits.

2. The Project Developer must publish information about the project in an accessible manner and provide channels for stakeholders to submit comments. Consultation outcomes must be documented and submitted as part of the project design documentation.

3. The PCS Secretariat posts the project summary on the PCS Registry for public comment. The public comment period remains open for the duration specified in PCS Framework v2.0. All comments received must be addressed by the Project Developer and subsequently reviewed during validation.

4. The Secretariat maintains an archive of all stakeholder submissions and responses as part of the project’s public record.

4.6 Assignment of Validation and Verification Body

1. After eligibility confirmation and completion of public consultation requirements, the project is assigned to an accredited Validation and Verification Body (VVB) for validation. Assignment procedures follow the PCS VVB accreditation rules to ensure impartiality and independence.

2. The Secretariat verifies that the selected VVB is accredited for the applicable sectoral scope and methodology, has no conflicts of interest, and possesses the technical expertise required for the project’s complexity. If a conflict is identified, an alternative VVB is appointed.

3. The Project Developer coordinates with the assigned VVB to commence validation activities, which are documented in accordance with PCS Validation Report requirements.

4.7 Validation Outcome and Secretariat Decision

1. Upon completion of validation, the VVB issues a formal Validation Report detailing methodological conformity, safeguard compliance, monitoring plan adequacy, and any corrective actions or clarifications required. The Project Developer must address all outstanding issues raised by the VVB before a positive validation opinion can be issued.

2. The PCS Secretariat reviews the Validation Report, confirms that all procedural requirements have been fulfilled, and makes a registration decision. The decision is recorded in the PCS Authorization Archive and published in the PCS Registry as a public entry.

3. If validation is rejected, the project is not registered. The Project Developer may revise the project or appeal the decision following procedures outlined in Chapter 10.

4.8 Issuance of Registration Certificate

1. For projects receiving a positive registration decision, the PCS Secretariat generates an official PCS Registration Certificate. This certificate includes the PCS Project ID, the approved methodology, the crediting period start date, the applicable track (Regular or NBS), and all relevant authorizations.

2. The certificate is recorded on the PCS Registry, making the registration event permanent, immutable, and publicly traceable. This marks the formal entry of the project into the PCS system and the transition to implementation and monitoring phases.

4.9 Suspension or Withdrawal During Registration

1. The PCS Secretariat may suspend or withdraw a project from the registration process if material discrepancies, falsified information, or unresolved safeguard issues arise. Suspension or withdrawal decisions are documented and published in the PCS Registry. The Project Developer may submit corrective evidence or choose to terminate the submission voluntarily.

4.10 Recordkeeping and Transparency

1. All documents submitted during registration, except those marked as confidential, are published in the PCS Registry to ensure transparency. The Secretariat maintains all records in accordance with PCS document retention policies, ensuring availability for audits, appeals, and Article 6 reporting.

2. The PCS Registry maintains cryptographic hashes of all registration-related documents, ensuring long-term data integrity and compliance with international transparency requirements.

Chapter 5 - Validation Process

5.1 Introduction to Validation

1. Validation represents the independent assessment of a project’s design against the requirements of the Planetary Carbon Standard, the applied methodology, and all relevant policies governing environmental and social safeguards, monitoring, and sustainable development impacts. It is a mandatory step prior to project registration and serves to confirm that the project is capable of achieving measurable, reportable, and verifiable emission reductions or removals.

2. Validation must be conducted by a Validation and Verification Body accredited or formally approved under PCS procedures. The objective of validation is to evaluate the credibility, completeness, and methodological soundness of the proposed activity to ensure that only high-integrity projects progress toward registration.

5.2 Scope of Validation

1. The scope of validation covers all components of project design, including the project description, baseline establishment, additionality demonstration, applicability of the methodology, monitoring plan, safeguard and SDG performance assessments, stakeholder consultation outcomes, and the host country’s authorization where relevant.

2. Validation also assesses the internal consistency of the project documentation. Methodological deviations, omitted data, contradictory descriptions, and insufficient evidence are identified and must be addressed prior to the finalization of the validation opinion. The scope extends to examining any supplemental documentation necessary for clarifying design assumptions or risk assessments.

5.3 Validation Methodology and Approach

1. The VVB shall apply a systematic and evidence-based approach in conducting validation. This typically includes a desk-based examination of all submitted documentation, remote consultations with the Project Developer, and site visits when required by the methodology, the project’s risk profile, or at the discretion of the VVB. The VVB is responsible for confirming the accuracy of baseline assessments, the soundness of monitoring systems, the adequacy of data collection procedures, and the robustness of the project’s safeguard measures.

2. The validation approach must comply with principles of independence, impartiality, and due professional care. All findings must be traceable, supported by verifiable evidence, and clearly categorized within the Validation Report. The VVB ensures that all assumptions and methodological choices made by the Project Developer are transparent, justified, and consistent with PCS requirements.

5.4 Review of Methodology Applicability

1. Validation includes a detailed review of the methodology selected by the Project Developer. The VVB must confirm that the methodology is applicable to the proposed project type, geography, baseline conditions, technology class, and monitoring capabilities. If the methodology has been recently updated, the most current version available in the PCS methodology library must be applied unless otherwise specified.

2. The VVB examines all methodological tools and parameters referenced in the project design, ensuring that their application is consistent and accurate. Any deviation, omission, or ambiguity must be documented and addressed prior to the issuance of a validation opinion.

5.5 Assessment of Baseline and Additionality

1. The baseline scenario represents the emissions or removals that would occur in the absence of the project activity. Validation examines the baseline approach to ensure that it is credible, conservative, and aligned with methodological requirements.

2. The VVB also assesses additionality, ensuring that the project is not a result of legal obligations, common practice, or purely financial motivations unrelated to climate mitigation. The justification for additionality must be supported by verifiable evidence and consistent reasoning. Any gaps identified by the VVB must be resolved by the Project Developer before validation can proceed.

5.6 Review of Monitoring Plan

1. The monitoring plan defines the procedures for measuring, recording, and reporting parameters required by the applied methodology. Validation assesses whether monitoring systems are technically feasible, adequately resourced, and sufficiently robust to ensure accurate emission reduction reporting.

2. The VVB evaluates the monitoring frequency, instruments, calibration procedures, data management systems, and roles and responsibilities assigned by the Project Developer. The objective is to confirm that all required parameters can be monitored effectively and that uncertainties are minimized to acceptable levels under PCS requirements.

5.7 Environmental and Social Safeguards Assessment

1. Validation includes a comprehensive review of the project’s safeguard performance based on the PCS Environmental and Social Safeguards framework. The VVB examines evidence submitted by the Project Developer to demonstrate compliance with all applicable safeguard principles, including biodiversity protection, water stewardship, labor rights, community health and safety, indigenous rights, and cultural heritage preservation.

2. The VVB verifies that risks have been identified, mitigation measures have been developed, and monitoring procedures are integrated into the project design. Projects with potential high E&S risks must demonstrate stronger mitigation mechanisms. If safeguard requirements are not satisfactorily met, the VVB issues corrective actions.

5.8 Stakeholder Consultation Review

1. The VVB evaluates the stakeholder consultation process conducted by the Project Developer. This includes an examination of the methods used to engage stakeholders, the accessibility of project information, the relevance and adequacy of responses to stakeholder concerns, and compliance with PCS procedural requirements for transparency.

2. The VVB ensures that all comments submitted during the public consultation period have been duly reviewed and addressed. Failure to conduct an adequate consultation process results in corrective actions.

5.9 Corrective Actions, Clarifications, and Forward Actions

1. During the validation process, the VVB may identify issues that require additional information, clarification, or corrective measures. These issues are categorized as Corrective Action Requests, Clarification Requests, or Forward Action Requests. All such findings must be addressed by the Project Developer to the satisfaction of the VVB.

2. Corrective Action Requests reflect non-compliance with PCS or methodological requirements and must be resolved prior to the issuance of a final validation opinion. Clarification Requests refer to inconsistencies or ambiguities that require explanation. Forward Action Requests may be resolved during later verification stages but must be reflected in the Validation Report.

5.10 Validation Conclusion

1. Upon completion of its assessment, the VVB issues a Validation Report summarizing all findings, confirming whether the project satisfies PCS requirements, and providing a validation conclusion. A project may be validated without conditions, validated with conditions, or not validated. All decisions must be supported by evidence and clear reasoning.

2. The Validation Report is submitted to the PCS Secretariat through the PCS Registry. The Secretariat reviews the report to ensure procedural compliance before issuing a registration decision.

5.11 Validation Expiry and Revalidation

1. Validation remains valid for the duration established in the PCS Framework. If a project does not progress to registration within the validity period, the validation may expire and require revalidation. Revalidation is also required when significant changes occur in project design, methodologies, or safeguard assessments. In such cases, the PCS Secretariat determines whether a full or partial revalidation is required.

Chapter 6 - Monitoring And Reporting

6.1 Introduction to Monitoring under PCS

1. Monitoring constitutes the process through which a registered project measures and documents all parameters required to quantify greenhouse gas emission reductions or removals according to the approved methodology. It forms the basis for verification and issuance and must therefore be conducted with the highest degree of accuracy, transparency, and methodological discipline.

2. The monitoring process is continuous throughout the crediting period. It ensures that the project operates according to its validated design, that all relevant data are consistently recorded, and that environmental and social safeguard obligations remain fully in effect. Effective monitoring is essential for maintaining environmental integrity and upholding confidence in the Planetary Carbon Standard.

6.2 Monitoring Responsibilities

1. The primary responsibility for monitoring lies with the Project Developer. The Developer must implement the monitoring plan approved during validation, ensure that appropriate systems and procedures are in place, maintain reliable data records, and preserve all evidence required for verification. Personnel involved in monitoring activities must be adequately trained and equipped to conduct measurements, maintain instruments, review data, and identify anomalies.

2. The PCS Secretariat oversees compliance by ensuring that monitoring reports are prepared in accordance with PCS requirements and submitted within designated timelines. The Secretariat performs a completeness review of each monitoring submission prior to assigning the verification process. Validation and Verification Bodies subsequently assess the accuracy and integrity of the monitoring data.

6.3 Monitoring Plan Requirements

1. Each project must have an approved monitoring plan prepared in accordance with the applied methodology and validated during the registration stage. The monitoring plan describes all parameters to be measured, the frequency of measurement, the instruments or methods used, the procedures for calibration and maintenance, the data management system, the roles and responsibilities of monitoring staff, and the quality assurance and quality control provisions.

2. The plan must be practical, technically feasible, and sufficiently robust to allow for the accurate quantification of emission reductions or removals. Any deviations from the monitoring plan identified during implementation must be justified by the Project Developer and addressed in accordance with PCS post-registration change procedures.

6.4 Monitoring Period and Data Collection

1. Monitoring occurs over defined monitoring periods. The start and end dates of each monitoring period must comply with the timing rules established in PCS Framework v2.0 and the applicable methodology. Monitoring periods may not overlap and must be continuous except where explicitly permitted by methodology provisions.

2. Throughout the monitoring period, the Project Developer collects all required data and ensures that each parameter is measured or estimated as mandated. Data must be recorded promptly, preserved securely, and presented in a manner that enables full traceability. Any gaps or anomalies observed during the monitoring period must be documented, investigated, and explained in the Monitoring Report.

6.5 PCS Project Monitoring Report (PMR)

1. At the conclusion of each monitoring period, the Project Developer prepares a PCS Project Monitoring Report. The PMR is the primary document demonstrating the project’s performance and the quantity of emission reductions achieved. It must follow the official PCS template and include detailed information regarding monitored parameters, applied methodologies, monitoring equipment, calibration records, data management procedures, and all other relevant components of the monitoring plan.

2. In addition, the PMR must describe any deviations, non-conformities, corrective actions, or exceptional circumstances encountered during the monitoring period. Supporting records, raw data, and evidence must be maintained and made available to the VVB during verification. The PMR must be internally consistent and reflect the project’s validated design.

6.6 Data Integrity and QA/QC Procedures

1. Data integrity is central to PCS monitoring. All data must be complete, accurate, and collected using reliable and approved methods. The monitoring plan must include quality assurance and quality control measures that guide the implementation of monitoring activities. These may include calibration schedules, internal audits, peer reviews of data, system maintenance procedures, and cross-checking of data sources.

2. The Project Developer is responsible for ensuring that all instruments used in monitoring are calibrated according to manufacturer or methodological requirements, that calibration records are retained, and that equipment malfunctions are promptly addressed. The data management system must ensure that all records are protected from alteration, loss, or unauthorized access.

6.7 Environmental and Social Safeguards Compliance Monitoring

1. Monitoring is not limited to greenhouse gas parameters. Projects must also maintain compliance with environmental and social safeguard requirements, as outlined in the PCS Safeguards Instructions Annex. The Project Developer must monitor safeguards continuously, document the implementation of mitigation measures, and report any incidents, grievances, or non-compliances.

2. Safeguard monitoring must be summarized in the PMR. If safeguard incidents occur, the Developer must record the nature of the incident, its impact, the corrective actions undertaken, and the measures adopted to prevent recurrence. Persistent or unaddressed safeguard issues may affect verification and issuance outcomes.

6.8 Monitoring of Sustainable Development Contributions

1. For projects claiming Sustainable Development Goal contributions, monitoring must include the collection and analysis of indicators defined in the SDG Impact Assessment. The Developer must report progress and outcomes in accordance with the PCS SDG monitoring requirements. Evidence supporting each SDG claim must be maintained and provided to the VVB during verification.

2. SDG-related monitoring requirements may vary based on the project type, the nature of the contribution, and the methodology applied. All SDG claims must be credible, traceable, and substantiated with verifiable information.

6.9 Submission of Monitoring Reports

1. Once the Monitoring Report is complete, the Project Developer submits it through the PCS Registry. The Secretariat reviews the submission for completeness, confirms that the report follows the required format, verifies that safeguard and SDG updates are included, and ensures that all supporting documents are accessible to the VVB.

2. If the report is incomplete, the Secretariat issues a request for clarification or additional information. A Monitoring Report may not proceed to verification until it passes the completeness review.

6.10 Deviations and Corrective Actions

1. If deviations from the monitoring plan occur during the monitoring period, they must be recorded in the Monitoring Report. Deviations may relate to missing data, equipment malfunction, temporary inability to monitor parameters, or changes in project circumstances. The Project Developer must justify each deviation, describe the corrective actions taken, and explain how the integrity of the monitored data was maintained.

2. Major deviations that affect the accuracy of emission reduction calculations may trigger a Post-Registration Change process or require additional validation steps. The VVB will evaluate all deviations during verification and determine whether they compromise data credibility.

6.11 Recordkeeping Requirements

1. The Project Developer must maintain a complete archive of all monitoring-related documentation. This includes raw data, logs, calibration certificates, maintenance records, stakeholder communication documents, safeguard and SDG monitoring records, and any correspondence or clarifications issued during monitoring and verification.

2. All records must be retained for the minimum period specified in PCS Framework v2.0. The PCS Secretariat may request access to any monitoring-related documentation for oversight, audit, or investigation purposes.

6.12 Transparency and Public Disclosure

1. The final Monitoring Report, once verified, is made publicly available through the PCS Registry except where confidentiality rules apply. The publication of Monitoring Reports ensures transparency and enables external stakeholders to review the performance of registered projects. This contributes to accountability, market confidence, and alignment with international transparency frameworks, including Article 6 of the Paris Agreement.

Chapter 7 - Verification And Issuance

7.1 Introduction to Verification under PCS

1. Verification is the independent assessment of monitored results to confirm that the greenhouse gas emission reductions or removals reported by a project are accurate, credible, and in full conformity with the applied methodology and PCS Framework v2.0. Verification ensures the environmental integrity of Planetary Carbon Units and provides the assurance required for issuance. It is conducted by accredited or approved Validation and Verification Bodies operating under the PCS VVB Accreditation Procedure. Verification must be unbiased, transparent, evidence-based, and conducted in accordance with the principles of independence and due professional care.

7.2 Scope of Verification

1. Verification covers all aspects of monitored performance during the relevant monitoring period. This includes the review of data sources, measurement procedures, activity records, calibration documentation, operational logs, safeguard and SDG updates, and all supporting evidence necessary to confirm the accuracy of the Monitoring Report. Verification examines the proper application of the methodology, the integrity of calculation procedures, the treatment of missing data or anomalies, and the adequacy of corrective actions undertaken during the monitoring period.

2. The scope also includes a review of any deviations from the monitoring plan. Deviations must be assessed for their impact on data integrity and must be resolved before verification can be completed. The VVB determines whether such deviations require recalculation, corrective action, or additional evidence.

7.3 Verification Approach and Methodology

1. Verification may include both desk-based and on-site assessments, depending on the nature of the project, the methodology requirements, the complexity of the monitoring approach, and the risk profile associated with the reported emission reductions. The VVB determines the verification plan based on documented risk factors, the availability of supporting information, and the history of project performance.

2. The verification methodology involves reviewing raw data, cross-checking calculations, interviewing responsible personnel, examining operational records, inspecting facilities when necessary, and confirming the proper functioning and calibration of monitoring instruments. The VVB evaluates whether data collection procedures were followed correctly, whether uncertainties were managed appropriately, and whether all relevant assumptions are clearly justified.

7.4 Review of Monitoring Data and Calculations

1. During verification, the VVB conducts a thorough review of all monitored parameters used to quantify emission reductions or removals. This includes verifying the completeness and accuracy of data sets, examining calibration and maintenance records, confirming the authenticity of data sources, and evaluating the consistency of measured values.

2. The VVB must review the emission reduction calculations presented in the Monitoring Report to confirm that they follow the methodology precisely, use correct formulas, apply appropriate emission factors, and treat uncertainties and baseline assumptions consistently. Any discrepancies identified must be addressed by the Project Developer before the verification conclusion is issued.

7.5 Assessment of Safeguards and SDG Updates

1. Verification includes an assessment of the project’s performance in relation to environmental and social safeguards and Sustainable Development Goal contributions. The VVB examines the safeguard and SDG updates provided in the Monitoring Report, confirming the continued implementation of mitigation measures, the management of any safeguard incidents, and the substantiation of SDG claims.

2. If safeguard or SDG non-compliances are identified, the VVB may issue corrective actions or determine that verification cannot proceed until issues are resolved. Persistent or serious safeguard deficiencies may impact issuance eligibility.

7.6 Corrective Actions, Clarifications, and Forward Actions

1. The VVB may identify issues that require additional information or formal resolution. These issues are documented as Corrective Action Requests, Clarification Requests, or Forward Action Requests. Each request must be addressed by the Project Developer within the timeframe established by the VVB.

2. Corrective Action Requests indicate non-compliance with methodological or PCS requirements and must be resolved before verification can be finalized. Clarification Requests relate to inconsistencies or ambiguities that require explanation or additional documentation. Forward Action Requests identify issues that do not affect the current verification but must be addressed before subsequent monitoring or verification periods.

3. All requests, responses, and final resolutions must be summarized in the Verification Report.

7.7 Verification Findings and Conclusion

1. Upon completing its assessment, the VVB prepares a Verification Report. The report includes a summary of the verification process, findings relating to data integrity and methodological application, treatment of deviations, assessment of safeguard and SDG compliance, and the final quantity of verified emission reductions or removals for the monitoring period.

2. The verification conclusion must state whether the Monitoring Report is verified as accurate, verified with reservations, or not verified. All conclusions must be supported by evidence and clear reasoning. The report is submitted to the PCS Secretariat through the PCS Registry for further processing.

7.8 Secretariat Assessment Before Issuance

1. Following receipt of the Verification Report, the PCS Secretariat conducts a procedural assessment to confirm that verification requirements have been met. This assessment verifies that the VVB is accredited for the relevant sector and methodology, that the verification procedures followed PCS requirements, and that the documentation is complete and consistent.

2. If the Secretariat identifies procedural gaps, it may require additional clarification from the VVB or the Project Developer before proceeding with issuance. Only after all procedural matters are resolved may the issuance process advance.

7.9 Issuance of Planetary Carbon Units

1. Upon successful verification and Secretariat review, the PCS Secretariat approves the issuance of Planetary Carbon Units for the verified monitoring period. Issuance involves calculating the net emission reductions or removals confirmed by the VVB, assigning unique serial numbers to each unit, and recording these units in the PCS Registry.

2. Each PCU entry includes the project identifier, monitoring period, issuance date, quantity of issued units, and blockchain verification hash. Issuance is final once recorded on the PCS Registry. The issuance event is disclosed publicly on the PCS Registry unless confidentiality provisions apply.

7.10 Serial Numbering and Blockchain Integrated Registration

1. Every PCU issued under PCS carries a unique serial number following the official PCS serial coding structure. The structure embeds information on the project, the vintage, the host country, and the issuance batch. This ensures traceability across all future transactions, including transfers, retirements, and cancellations.

2. The blockchain registration process ensures immutability and transparency. Each issuance event is associated with a cryptographic hash stored on the PCS Registry, providing a permanent and tamper-resistant record. This supports both market confidence and compliance with international transparency mechanisms, including those under Article 6.

7.11 Treatment of Non-Issuance

1. If a project fails verification or if unresolved issues prevent issuance, the PCS Secretariat issues a non-issuance decision. The decision includes a detailed explanation of the reasons for non-issuance. The Project Developer may address the findings and request a new verification or may appeal the decision in accordance with Chapter 10. Non-issuance does not affect the project’s registration status but may require corrective actions prior to subsequent monitoring periods.

7.12 Public Disclosure of Verification and Issuance Information

1. All verification and issuance information, except that designated as confidential, is made publicly available through the PCS Registry. Public disclosure includes the Monitoring Report, the Verification Report, the issuance record, and the associated serial number ranges. This ensures transparency, accountability, and compliance with international reporting expectations.

Chapter 8 - Post-Registration Changes And Renewals

8.1 Introduction to Post-Registration Governance

1. After a project is registered under the Planetary Carbon Standard, its design, monitoring systems, ownership structure, or operational circumstances may evolve. PCS allows for such changes to be formally incorporated through a controlled and transparent process to ensure continued compliance with methodological, safeguard, and governance requirements. Post-registration changes must be managed carefully, as they may affect project eligibility, monitoring accuracy, or the credibility of emission reductions. This chapter sets forth the procedures for evaluating, validating, and approving modifications to registered projects, as well as renewing crediting periods.

8.2 Types of Post-Registration Changes

1. Post-registration changes may include modifications to project design, updates to the monitoring plan, adjustments to baseline assumptions, expansion or reduction of project boundaries, changes in project ownership, corrections of factual errors, updates to applied methodologies, or integration of new monitoring technologies. Any change that could influence the quantification of emission reductions, safeguard performance, or alignment with PCS requirements must be submitted through the official PCS Post-Registration Change Request procedure.

2. Projects must remain consistent with the approved methodology unless a revised or updated methodology has been formally approved for use. If a methodological update materially affects project performance, the Project Developer must request a review of applicability or revalidation where appropriate.

8.3 Submission of Post-Registration Change Requests

1. The Project Developer must submit a formal Post-Registration Change Request using the approved PCS PRC Form. The request must describe the nature of the change, the underlying justification, the expected impact on project performance, and the supporting evidence required for assessment. The request must be complete, clearly articulated, and supported by documentation demonstrating the technical and procedural necessity of the change.

2. Upon submission, the PCS Registry assigns a change reference number. The PCS Secretariat performs a completeness check to confirm that the request contains all required information. Incomplete submissions are returned to the Project Developer with a request for further clarification.

8.4 Secretariat Assessment of Change Requests

1. Following the completeness check, the PCS Secretariat reviews the submitted change request to determine whether the change is minor, material, or substantial. Minor changes may include administrative corrections, updated contact information, or typographical revisions that do not affect project eligibility or monitoring integrity. Material changes involve adjustments to project parameters, monitoring plans, or baseline approaches that require review by an accredited VVB. Substantial changes may alter project design, boundaries, or methodological applicability and may require partial or full revalidation.

2. The Secretariat evaluates the proposed change against the PCS Framework, the applied methodology, safeguarded performance, and the project’s validated design. The Secretariat determines whether VVB involvement is required and assigns the request accordingly.

8.5 Validation of Post-Registration Changes

1. Material or substantial changes require independent assessment by a Validation and Verification Body. The VVB conducts a focused validation limited to the aspects affected by the proposed change. This assessment examines the technical justification, the evidence supporting the modification, the implications for baseline and monitoring procedures, and any risks to data integrity or safeguard compliance.

2. The VVB issues a Validation Report for Post-Registration Changes summarizing the findings, confirming whether the change is acceptable, and identifying any corrective actions or clarifications required. The Project Developer must address all outstanding issues to the satisfaction of the VVB before the revised design can be accepted.

8.6 Secretariat Decision and Registry Update

1. Upon receipt of the VVB’s validation conclusion, the PCS Secretariat conducts a procedural review to ensure that all requirements have been met. The Secretariat then issues a formal decision approving, rejecting, or requesting further revision of the change request. Approved changes are recorded in the PCS Authorization Archive and reflected in the PCS Registry.

2. Where necessary, the Secretariat updates the project status, methodology reference, monitoring parameters, or ownership records. Changes affecting public information are published on the PCS Registry. All decisions are recorded permanently and include a blockchain verification hash to ensure traceability.

8.7 Impact of Changes on Monitoring and Verification

1. Approved Post-Registration Changes may influence subsequent monitoring and verification cycles. If modifications affect monitoring procedures, the Project Developer must revise the monitoring plan and implement any updated equipment, calibration practices, or data management systems. Changes affecting methodological parameters or baseline calculations may require adjustments to the PMR for the affected monitoring periods.

2. Verification bodies must consider approved changes when preparing for verification. They must confirm that the updated monitoring plan has been implemented correctly and that all associated data remain consistent with PCS requirements.

8.8 Crediting Period Renewals

1. Crediting periods must be renewed in accordance with the rules established in PCS Framework v2.0. Renewals require an assessment of continued methodological applicability, baseline validity, safeguard compliance, and alignment with national climate policies. Projects must not automatically assume renewal; they must demonstrate ongoing relevance and the ability to generate credible emission reductions or removals.

2. The Project Developer must submit a request for renewal prior to the expiration of the crediting period. This submission must include updated documentation, evidence of continuous safeguard performance, justification of baseline conditions, and confirmation that no significant project design changes have occurred without approval.

3. The PCS Secretariat reviews the renewal request for completeness and eligibility. If substantial changes to the baseline or methodology have occurred, the Secretariat determines whether revalidation is required. Renewed crediting periods are recorded in the PCS Registry, and the project may continue monitoring and verification activities.

8.9 Suspension or Withdrawal Due to Non-Compliance

1. Projects may be suspended or withdrawn from the PCS system if post-registration changes materially reduce project integrity, if deviations remain unresolved, or if safeguard or methodological non-compliances are discovered. Suspension halts issuance until issues are resolved, whereas withdrawal removes the project from active PCS status. Project Developers may respond to suspension by submitting corrective actions or adjustments for review.

2. The PCS Secretariat records all suspension or withdrawal decisions in the PCS Registry and ensures that all project stakeholders, including VVBs and host country authorities, are notified.

8.10 Transparency and Public Disclosure

1. All approved Post-Registration Changes, renewal decisions, and related validation reports are made publicly accessible through the PCS Registry, except information designated confidential in accordance with PCS policies. Public disclosure enables stakeholders to track modifications to the project’s design and performance, thereby enhancing the transparency and credibility of the standard.

Chapter 9 - Validation And Verification Body (VVB) Accreditation And Oversight

9.1 Introduction to VVB Governance under PCS

1. Validation and Verification Bodies play a central role in ensuring the environmental integrity and credibility of the Planetary Carbon Standard. The PCS system relies on independent, technically competent, and ethically governed VVBs to evaluate project design and performance. This chapter establishes the procedures for accreditation, approval, oversight, suspension, and termination of VVBs operating under PCS. The objective is to maintain a trusted assurance ecosystem that safeguards the integrity of all validation and verification outcomes.

2. The PCS VVB Accreditation System is based on internationally recognized principles of impartiality, competence, confidentiality, and consistent application of validation and verification practices. Accredited VVBs must demonstrate ongoing compliance with these principles throughout their engagement with PCS.

9.2 Accreditation Requirements

1. Entities seeking to operate as VVBs under PCS must demonstrate technical expertise, managerial capacity, and institutional independence sufficient to carry out validation and verification activities. Accreditation requires evidence of competence in relevant mitigation sectors, the methodologies applied under PCS, safeguard assessments, and data assurance systems. Applicants must maintain internal quality management systems aligned with recognized standards, uphold impartiality, and ensure that personnel are adequately qualified and free of conflicts of interest.

2. The accreditation process examines the organizational structure of the applicant, its policies governing independence, its monitoring of potential conflicts, and its systems for training, certification, and performance review of validation and verification personnel.

9.3 Application Process for VVB Accreditation

1. Applicants seeking VVB status must submit the official PCS VVB Application Form together with supporting documentation demonstrating compliance with PCS accreditation requirements. The PCS Secretariat conducts a completeness review to confirm that all necessary information has been provided. The Secretariat then evaluates the application in accordance with the criteria outlined in PCS governance rules.

2. The evaluation may include a review of the applicant’s experience in greenhouse gas auditing, technical competence in specific sectoral scopes, internal procedures for quality assurance, and track record in conducting validations and verifications under other recognized carbon standards. The Secretariat may request additional evidence or clarification from the applicant as needed.

3. Upon completion of the evaluation, the Secretariat prepares an accreditation recommendation for the PCS Regulatory Council, which issues the final accreditation decision. Successful applicants are added to the PCS list of approved VVBs and assigned sectoral scopes for which they are authorized to operate.

9.4 Approval of VVBs without Full Accreditation

1. PCS may authorize entities to conduct validation and verification activities on a provisional or limited basis where full accreditation is not immediately feasible. Such approval is granted only when the applicant demonstrates sufficient competence for the scope requested and agrees to comply with all PCS rules and oversight mechanisms.

2. Provisional approval does not replace the need for full accreditation and may be time-limited. The PCS Secretariat monitors approved VVBs closely and may require periodic reporting or additional oversight measures.

9.5 Scope of VVB Accreditation

1. Accreditation is granted for specific sectoral or methodological scopes, reflecting the technical expertise of the VVB. A VVB may only conduct validation and verification for project types within its approved scopes. If a VVB seeks to expand its scope, it must apply for reassessment, demonstrating additional competence or experience relevant to the new scope.

2. PCS may revise sectoral scopes periodically to reflect evolving methodologies and market requirements. VVBs are responsible for maintaining their competence in all scopes for which they hold accreditation.

9.6 Oversight and Performance Monitoring

1. PCS maintains a rigorous oversight system to ensure that accredited VVBs continue to operate with integrity and competence. Oversight activities may include reviews of validation and verification reports, assessments of compliance with PCS rules, audits of VVB internal procedures, observation of validation or verification activities, and evaluation of stakeholder feedback.

2. The PCS Secretariat conducts ongoing monitoring, identifying potential performance issues such as repeated technical errors, missed procedural requirements, or evidence of compromised independence. Significant findings are escalated to the PCS Regulatory Council for review.

9.7 Management of Conflicts of Interest

1. Independence is a core requirement of VVB operations. A VVB must be free from financial, operational, or organizational conflicts of interest that could influence validation or verification outcomes. PCS requires VVBs to establish documented procedures for identifying, managing, and mitigating conflicts of interest.

2. VVBs must disclose to the PCS Secretariat any circumstances that could compromise impartiality. The Secretariat may require reassignment of a validation or verification task or take corrective action if a conflict is found to exist. Persistent or intentional failures to manage conflicts may result in suspension or termination of accreditation.

9.8 Appeals, Complaints, and Reporting Obligations

1. VVBs must maintain internal procedures for addressing complaints regarding their services. These procedures must be transparent and accessible to Project Developers and affected stakeholders. VVBs must report all significant complaints, appeals, and internal investigations to the PCS Secretariat.

2. PCS may initiate its own review of VVB performance in response to complaints submitted through the PCS grievance mechanism. If systemic issues are identified, the Secretariat may impose additional oversight or refer the matter to the PCS Regulatory Council for action.

9.9 Suspension or Termination of Accreditation

1. The PCS Secretariat may recommend suspension or termination of VVB accreditation when evidence demonstrates repeated non-compliance, compromised integrity, inadequate performance, conflict of interest violations, or failure to maintain necessary competencies. The PCS Regulatory Council issues the final decision.

2. Suspension temporarily restricts the VVB from accepting new assignments, while termination revokes the VVB’s authority to operate within PCS entirely. Both actions are recorded in the PCS Registry and publicly disclosed. VVBs subject to suspension or termination may submit corrective actions or reapply for accreditation once deficiencies are resolved.

9.10 Renewal of Accreditation

1. Accreditation is valid for a specified period established by PCS governance rules. Prior to expiry, VVBs must submit a renewal application demonstrating ongoing compliance, updated qualifications, and evidence of satisfactory performance. The renewal process may require additional audits or assessments depending on the VVB’s operational history.

2. PCS reserves the right to deny renewal if the VVB fails to meet required standards. Renewal decisions are recorded in the PCS Authorization Archive and reflected in the PCS Registry.

9.11 Transparency and Public Disclosure

1. PCS publishes a list of all accredited and approved VVBs, including their sectoral scopes and accreditation status. Any changes to accreditation, including suspensions, terminations, or scope adjustments, are publicly disclosed through the PCS Registry to ensure transparency for market participants and stakeholders.

Chapter 10 - Grievances, Appeals, And Dispute Resolution

10.1 Introduction and Purpose

1. The Planetary Carbon Standard maintains a formal system for handling grievances, appeals, and disputes to ensure accountability, fairness, and transparency in the administration of the standard. This chapter outlines the procedures by which grievances may be submitted by affected persons, how appeals may be lodged against decisions taken by the PCS Secretariat or the PCS Regulatory Council, and how such matters are reviewed and resolved. The procedure is guided by principles of legitimacy, accessibility, predictability, equity, and independence, consistent with international best practices, including the UN Guiding Principles on Business and Human Rights.

2. Grievances and appeals are essential components of PCSs governance model, providing a means for individuals, organizations, and project proponents to raise concerns, contest decisions, and seek resolution through a structured, impartial process.

10.2 Scope of the Grievance and Appeal System

1. The PCS grievance and appeal system applies to all activities carried out under the standard, including project development, validation and verification, safeguard performance, issuance decisions, VVB accreditation matters, and registry operations. It is available to project developers, VVBs, affected stakeholders, host country authorities, and members of the public.

2. Grievances generally relate to concerns raised by affected persons or stakeholders in connection with project impacts, safeguard compliance, procedural misconduct, or other issues arising from project implementation. Appeals relate to formal challenges against decisions taken by the PCS Secretariat or the PCS Regulatory Council, including decisions regarding project registration, issuance, accreditation, or procedural determinations.

10.3 Submission of Grievances

1. A grievance may be submitted to the PCS Secretariat through the official communication channels specified in the PCS Registry. A grievance must describe the issue of concern, identify the relevant project or entity, and provide sufficient information for the Secretariat to understand the nature and context of the matter. Although specific formats may vary, the information must be clear, factual, and relevant.

2. The PCS Secretariat registers the grievance and acknowledges receipt. The Secretariat assesses whether the grievance falls within the scope of this chapter. If the grievance is outside the scope of PCS governance, the Secretariat notifies the submitter and, if appropriate, directs the matter to the appropriate external authority.

10.4 Handling and Review of Grievances

1. Once a grievance is accepted, the PCS Secretariat conducts a preliminary review to determine whether immediate corrective measures are required, whether further investigation is necessary, or whether the matter should be forwarded to the PCS Regulatory Council. The Secretariat may engage the Project Developer, VVB, Host Country Focal Point, or relevant stakeholders to obtain additional information.

2. The Secretariat aims to resolve grievances through dialogue, clarification, or corrective action where possible. If a grievance involves allegations of procedural misconduct, safeguard violations, or significant project-level harm, the Secretariat may initiate a deeper investigation. The findings of such investigations are documented and preserved.

3. Where a grievance affects project eligibility, issuance, or accreditation matters, the Secretariat may impose temporary suspensions or require corrective action plans.

10.5 Submission of Appeals

1. Appeals may be submitted when a Project Developer, VVB, or other stakeholder disagrees with a formal decision made by the PCS Secretariat or PCS Regulatory Council. Appeals must be submitted using the PCS Change Request and Appeals Form and must clearly identify the decision being challenged, the grounds for appeal, and the relief sought. Appeals must be substantiated with evidence and must demonstrate that the contested decision was inconsistent with PCS rules, unfair, erroneous, or not supported by the evidence.

2. Appeals must be submitted within the timeframe established in PCS Framework v2.0. Appeals submitted outside this period may be dismissed unless exceptional circumstances justify reconsideration.

10.6 Review of Appeals

1. The PCS Secretariat conducts an initial assessment of the appeal to confirm completeness and verify whether the appeal falls within the jurisdiction of PCS governance. Appeals concerning procedural matters or technical decisions made during validation or verification may be forwarded to an independent review panel or delegated to the PCS Regulatory Council, depending on the nature of the issue.

2. The appeal review process involves examining the original decision, evaluating the evidence provided by the appellant, consulting relevant stakeholders if necessary, and determining whether procedural or substantive errors occurred. The review is carried out in a manner that ensures impartiality and independence, without involvement from individuals who participated in the original decision-making process.

10.7 Decisions on Appeals

1. The PCS Regulatory Council issues the final decision on appeals unless the matter falls under the specific delegated authority of the PCS Secretariat. Decisions may confirm, amend, or overturn the original decision, or may require further investigation or corrective actions. All decisions are documented and recorded in the PCS Authorization Archive.

2. Appeal decisions are communicated to the appellant and published in the PCS Registry unless confidentiality provisions apply. Decisions of the PCS Regulatory Council are final within the PCS governance system.

10.8 Confidentiality and Protection of Complainants

1. PCS ensures that grievances and appeals are handled with respect for confidentiality and the protection of complainants. Identities of complainants are protected unless disclosure is required for procedural fairness or mandated by law. The Secretariat ensures that individuals submitting grievances or appeals do not face retaliation or adverse consequences for engaging in these processes.

10.9 Integration with Safeguards and Monitoring

1. Grievances related to environmental and social impacts are integrated into project monitoring and safeguard compliance assessments. Project Developers must address and document all grievances related to project operations, including corrective actions taken, and report these matters in the PCS Monitoring Report. Unresolved or repeated grievances may affect verification outcomes or trigger additional oversight.

10.10 Recordkeeping and Transparency

1. All grievances and appeals, including their outcomes, must be recorded by the PCS Secretariat. The Secretariat maintains a permanent archive of all submissions, correspondence, investigations, and decisions. Summary information on grievances and appeals is published in the PCS Registry to promote transparency and accountability.

2. Records are retained in accordance with PCS document retention policies, and blockchain verification hashes may be applied to ensure the integrity of formal decisions.

10.11 Resolution Timelines

1. PCS strives to resolve grievances and appeals in a timely manner. Resolution timelines are established in PCS Framework v2.0 and may be extended only when necessary to ensure thorough and fair review. The Secretariat informs complainants and appellants of expected timelines and provides updates during the review process.

Chapter 11 - Methodology Development, Revision, And Clarification

11.1 Introduction

1. Methodologies form the technical foundation of the Planetary Carbon Standard by providing the rules for baseline establishment, monitoring, quantification of greenhouse gas emissions and removals, and assessment of project boundaries and applicability conditions. To maintain scientific rigor, consistency, and environmental integrity, PCS employs a structured system for developing new methodologies, revising existing methodologies, and issuing clarifications. This chapter establishes the governance processes and institutional responsibilities governing these activities.

2. Methodology development and revision must reflect the highest standards of scientific accuracy, transparency, and alignment with international best practices. PCS ensures that methodologies remain current with technological advancements, updated emission factors, evolving greenhouse gas accounting practices, and emerging research on environmental and social safeguards.

11.2 Principles Governing Methodology Governance

1. All methodological actions under PCS follow principles of scientific validity, transparency, conservativeness, practicality, consistency, and environmental integrity. Methodologies must ensure that emission reductions are real, measurable, verifiable, additional, and permanent. They must be applicable across relevant project contexts, clearly structured, and free of ambiguity. Methodological procedures must enable equitable application across diverse regions and project types while maintaining the precision necessary to prevent overestimation or double counting of emission reductions.

11.3 Submission of Methodology Concept Notes

1. Development of new methodologies begins with the submission of a Methodology Concept Note. The Concept Note provides a preliminary description of the proposed methodology, including the project category, baseline approach, monitoring framework, data requirements, applicability conditions, additionality considerations, and preliminary justification for the methodology’s necessity. The Concept Note must be submitted using the PCS Methodology Concept Note template.

2. The PCS Secretariat conducts an initial review to assess completeness and relevance. The Secretariat determines whether the proposed methodology aligns with PCS strategic priorities, addresses an identified gap, and supports the integrity of the standard. The Secretariat may consult technical experts or request additional information from the proponent.

11.4 Approval of Methodology Development

1. If the Secretariat determines that the Concept Note warrants further development, it recommends approval to the PCS Regulatory Council. Upon approval, the methodology enters the development stage. The methodology proponent may prepare the full methodology, including detailed baseline procedures, quantification equations, monitoring requirements, data quality provisions, and safeguard considerations.

2. The PCS Secretariat oversees the development process to ensure consistency with PCS methodology structure and formatting standards. Methodology development may involve consultations with subject matter experts, peer reviewers, or host country representatives to ensure scientific robustness and applicability across diverse contexts.

11.5 Public Consultation for New Methodologies

1. Before a new methodology is finalized, it must undergo a public consultation process. The PCS Secretariat publishes the draft methodology on the PCS Registry for a defined consultation period. Stakeholders, including technical experts, Project Developers, civil society organizations, and host country authorities, may submit comments or recommendations.

2. The consultation process ensures transparency, encourages broad participation, and allows the identification of weaknesses, omissions, or unintended consequences. All comments received must be documented and reviewed, and responses must be incorporated into the methodology finalization process.

11.6 Independent Technical Review

1. Following public consultation, the methodology undergoes an independent technical review. The PCS Secretariat appoints qualified experts to assess the scientific and technical rigor of the methodology. Reviewers evaluate baseline approaches, monitoring procedures, emission factors, data sources, and safeguard integration. They also confirm that the methodology reflects conservative assumptions and prevents overestimation of emission reductions.

2. The independent review may result in recommendations for revision. The methodology proponent must address all findings before the methodology can proceed to approval by the PCS Regulatory Council.

11.7 Approval and Publication of New Methodologies

1. Upon satisfactory completion of public consultation and independent technical review, the final methodology is submitted to the PCS Regulatory Council for approval. The Council reviews the methodology to ensure alignment with PCS Framework v2.0 and international best practices. Upon approval, the methodology is published in the PCS Methodology Library and becomes available for use by Project Developers.

2. Each approved methodology is assigned a unique identifier and version number. A summary of the methodology, including its applicability, key parameters, and monitoring requirements, is published to facilitate stakeholder understanding.

11.8 Revision of Existing Methodologies

1. Revisions to existing methodologies may be necessary to incorporate new scientific findings, updated emission factors, improved monitoring technologies, or procedural enhancements. Revisions may also address ambiguities, correct errors, or reflect updates in international accounting frameworks.

2. Revisions may be initiated by Project Developers, VVBs, host country authorities, or the PCS Secretariat. The proponent must submit a Methodology Revision Request using the official PCS template, describing the nature, justification, and scope of the proposed revision. The Secretariat evaluates whether the revision is minor, moderate, or substantial. Minor revisions may be approved through a streamlined process, while substantial revisions require public consultation and technical review similar to new methodology development.

3. Revised methodologies receive new version numbers. PCS publishes detailed revision histories to ensure transparency.

11.9 Clarification of Methodological Requirements

1. Clarifications may be issued to resolve interpretational questions or address ambiguities in existing methodologies. Clarification Requests may be submitted by Project Developers, VVBs, or other stakeholders. The PCS Secretariat evaluates the request, consults technical experts where appropriate, and issues official clarifications that are published on the PCS Registry.

2. Clarifications do not alter the methodology; they provide authoritative guidance on how existing provisions should be applied. All clarifications are archived to ensure consistent interpretation across projects.

11.10 Interaction with Validation and Verification

1. Methodologies and their revisions have direct implications for validation and verification processes. The VVB must confirm that the methodology selected for a project is applicable and used correctly. When methodologies are revised, the VVB must confirm whether the revised version applies to new monitoring periods or whether transition rules are in effect.

2. If clarification requests affect ongoing validation or verification activities, the VVB must apply the guidance provided in the clarification to ensure consistency and accuracy in project assessments.

11.11 Governance Decisions and Appeals Related to Methodologies

1. All decisions regarding methodology approval, revision, and clarification are formal governance decisions recorded in the PCS Authorization Archive. Project Developers or other stakeholders may appeal methodology-related decisions in accordance with Chapter 10. Appeals must demonstrate that the decision was inconsistent with PCS governance rules, lacked sufficient justification, or materially affected project eligibility or performance.

11.12 Publication and Transparency

1. PCS ensures that all methodologies, revisions, clarifications, consultation comments, technical review summaries, and associated decisions are published in the PCS Registry. Transparency in methodology governance strengthens credibility, supports stakeholder trust, and enables consistent application across all projects.

CHAPTER 12 — Digital Registry And Blockchain Integration

12.1 Introduction

1. The PCS Digital Registry serves as the official information system through which all project-related records, decisions, monitoring submissions, validation and verification reports, issuance events, and credit transfers are managed. It provides the authoritative repository for all data generated within the PCS project cycle and ensures transparency, traceability, and integrity across all procedural stages. The Registry operates in conjunction with an integrated blockchain architecture that records immutable verification hashes and ensures that each Planetary Carbon Unit is permanently traceable. This chapter describes the structure, functions, and operational requirements of the PCS Registry and its blockchain components.

12.2 Purpose of the PCS Digital Registry

1. The Registry exists to safeguard the integrity of PCS-certified mitigation outcomes by maintaining comprehensive, accurate, and auditable records of all project activities. It serves as the platform through which Project Developers submit documentation, VVBs upload validation and verification reports, the Secretariat issues decisions, and stakeholders access publicly disclosed information. The Registry ensures that projects are administered consistently, that issuance and transfer events are transparent, and that all units are uniquely identifiable and protected against double counting, duplication, or unauthorized alteration.

2. The Registry also facilitates alignment with domestic and international reporting frameworks, including Nationally Determined Contributions and Article 6 mechanisms, by providing structured, verifiable data exports and secure audit trails.

12.3 Structure and Architecture of the Registry

1. The PCS Registry is structured as a modular, digital environment consisting of several interconnected components. These include the project database, the document management system, the VVB portal, the public transparency interface, and the blockchain-linked issuance ledger. All system components are designed to maintain integrity, ensure secure access, and enable efficient workflow management.

2. Registry architecture incorporates tiered access controls to differentiate between Project Developers, VVBs, Secretariat staff, and public stakeholders. All sensitive information is protected through data encryption, and all transactions are logged with metadata including timestamps, user identifiers, and system location.

3. The Registry also incorporates automated validation checks that flag inconsistencies or incomplete submissions, prompting users to provide corrections before proceeding.

12.4 Project Records and Lifecycle Management

1. Each PCS project receives a unique Project Identifier at the time of initial submission. This identifier remains associated with the project throughout its lifecycle. The Registry stores project information from the earliest submission of the Project Submission Form through all subsequent stages, including validation, registration, monitoring, verification, issuance, and updates related to post-registration changes or crediting period renewals.

2. All records must be complete, internally consistent, and retained for the minimum period required under PCS document retention policies. The Registry preserves historical versions of documents and decisions, ensuring that the full audit trail of each project is available for review.

12.5 Document Management and Public Access

1. The Registry maintains all documents in digital form and distinguishes between confidential and publicly accessible information. Project documents such as Project Submission Forms, Monitoring Reports, Validation and Verification Reports, Post-Registration Change decisions, and issuance announcements are made accessible to the public unless confidentiality restrictions apply. Sensitive business information may be designated as confidential by the Project Developer and reviewed by the PCS Secretariat prior to approval.

2. The public interface of the Registry provides summaries of project information, stakeholder consultation records, VVB accreditation status, issuance histories, and details of any governance decisions. Transparency through the Registry is essential to maintaining confidence in the PCS system.

12.6 Serial Number System for Planetary Carbon Units

1. The Registry assigns a unique serial number to every Planetary Carbon Unit issued under PCS. The serial number structure encodes key attributes, including project identifier, project type, host country, vintage year, monitoring period, and issuance batch. The purpose of this structured approach is to ensure unambiguous identification, prevent duplication, enhance traceability, and enable consistent reporting in line with national and international carbon accounting mechanisms.

2. Serial numbers are issued sequentially within each issuance batch and cannot be reused. Once assigned, they become permanent entries in the Registry and the associated blockchain ledger. All subsequent transactions involving a PCU, including transfers, retirements, cancellations, or conversions to other unit types, must reference the original serial number.

12.7 Blockchain Integration and Immutable Records

1. A core component of the PCS Registry is its integrated blockchain-based verification layer. Each significant project event, including project registration, issuance of Planetary Carbon Units, validation and verification certifications, and credit retirement, generates a cryptographic hash that is permanently recorded on the blockchain Ledger. This ensures that all data associated with these events can be independently verified and cannot be altered retroactively.

2. Blockchain integration provides immutability, tamper resistance, and transparency. The cryptographic hash operates as a digital fingerprint that corresponds to a specific version of a document or issuance event. Any modification to data would result in a different hash and would be immediately detectable. This mechanism enhances trust in the PCS system and enables seamless integration with external systems seeking to verify the authenticity of PCS records.

12.8 Prevention of Double Counting

1. The Registry incorporates controls designed to prevent all forms of double counting, including double issuance, double claiming, and double use. The combination of structured serial numbering, blockchain verification, tracking of retirement events, and host country authorization tagging ensures that mitigation outcomes are used only once for a specific purpose.

2. Projects eligible for Article 6-authorized issuance have additional metadata fields to capture corresponding adjustment requirements, authorized use categories, and reporting obligations. This ensures alignment with UNFCCC transparency frameworks and national tracking systems.

12.9 Registry Actions Managed by the PCS Secretariat

1. The PCS Secretariat is responsible for managing all registry actions, including but not limited to project registration, issuance, post-registration updates, crediting period renewals, suspension or withdrawal decisions, and resolution of discrepancies. Each action undertaken by the Secretariat is recorded in the Registry with a corresponding blockchain verification hash to preserve transparency and accountability.

2. Secretariat users operate under controlled permissions based on their responsibilities and must adhere to internal security protocols. Sensitive updates require multi-level approvals, and all actions are subject to internal audit.

12.10 Transfers, Retirements, and Cancellations

1. Once issued, Planetary Carbon Units may be transferred, retired, or canceled through the PCS Registry. Transfers occur between registry accounts authorized to hold units. Retirements permanently remove units from circulation, preventing any further use or transfer. Cancellations occur when units are invalidated, reversed, or returned voluntarily by the account holder.

2. All such actions are recorded with timestamps, account identifiers, and associated documentation. Blockchain hashes reinforce the permanence of records and ensure that no retired or cancelled unit can re-enter circulation.

12.11 Interoperability and Article 6 Compatibility

1. The PCS Registry is designed to support interoperability with national registries, international carbon registries, and Article 6-compliant tracking systems. The Registry’s structured data architecture and blockchain verification framework allow external systems to verify unit integrity and ensure that transfers and use claims are valid.

2. Host country authorizations and corresponding adjustment information are recorded directly within the Registry, enabling transparent and verifiable reporting under Nationally Determined Contributions and international cooperative approaches. The Registry can generate standardized data sets compatible with Biennial Transparency Reports and with reporting systems of Article 6.2 arrangements.

12.12 Data Integrity, Security, and Auditability

1. Data integrity is maintained through encryption, controlled access permissions, version tracking, and immutable blockchain records. Regular internal audits ensure that Registry operations comply with PCS governance requirements. External audits may also be performed to validate system integrity or investigate potential anomalies.

2. Audit trails include complete histories of document uploads, user actions, modifications, issuance decisions, and transfers. System logs preserve metadata associated with each action, enabling full reconstruction of events when required.

12.13 Record Retention and Archival Policies

1. All Registry records must be retained for the minimum period specified under PCS Framework v2.0. This includes project documentation, Secretariat decisions, VVB reports, issuance logs, transfer records, and blockchain verification hashes. Records may be archived after retirement or cancellation of units but must remain accessible for auditing or review purposes.

2. Archival procedures ensure that long-term digital preservation requirements are met and that all information remains verifiable, regardless of technological changes.

12.14 Transparency Requirements

1. PCS maintains a strong commitment to transparency. Except where confidentiality applies, project and issuance information is publicly available through the Registry. Public transparency enhances market confidence, supports stakeholder engagement, and aligns PCS with global best practices in carbon market governance.

Annex A - PCS Project Lifecycle Flow Descriptions

A.1 Complete PCS Project Lifecycle Flow

The PCS project lifecycle begins at the point of submission and continues until final issuance, retirement, or withdrawal. The process commences when a Project Developer submits the Project Submission Form and supporting documentation through the PCS Registry. The PCS Secretariat conducts a completeness check to ensure that all required documents are present. Once completeness is confirmed, an eligibility review is performed to ensure conformity with PCS Framework v2.0 and the selected methodology.

Following eligibility confirmation, the project enters the public consultation stage. Stakeholders may submit comments, and the Project Developer must address them prior to validation. The PCS Secretariat subsequently assigns an accredited or approved Validation and Verification Body to conduct validation. The VVB reviews the project design, assesses methodology applicability, examines safeguard performance, and confirms that the monitoring plan is credible.

If the validation opinion is positive and any corrective actions have been addressed, the PCS Secretariat issues a registration decision and publishes it in the PCS Registry. The project then progresses into implementation and monitoring.

During the monitoring phase, the Project Developer carries out the monitoring plan and compiles the Monitoring Report. The report is submitted to the PCS Registry for completeness review. Upon acceptance, the report is forwarded to a VVB for verification. The VVB assesses all data, reviews calculations, and confirms emission reductions or removals.

If verification is successful, the PCS Secretariat proceeds with issuance. Planetary Carbon Units are generated, assigned serial numbers, and recorded permanently on the PCS Registry and blockchain ledger. The project then enters the next monitoring period or prepares renewal submissions as required.

A.2 Validation and Verification Process Flow

The validation and verification flow initiates when the VVB receives project documentation. The VVB performs a systematic evaluation of the project description, the applied methodology, and the demonstration of additionality. If inconsistencies arise, the VVB requests clarification or corrective actions. The Project Developer responds with updated or supplementary information.

Once the VVB concludes that all requirements are met, it issues a Validation Report that is submitted to the PCS Registry. After registration, the VVB later evaluates the implementation phase through verification. It examines monitoring results, reviews raw data, assesses safeguard and SDG performance, and recalculates greenhouse gas reductions where necessary. Any discrepancy leads to corrective action requests. Upon satisfactory resolution, the VVB issues the Verification Report, which serves as the basis for issuance.

A.3 Issuance and Registry Flow

After the PCS Secretariat reviews and accepts the Verification Report, it prepares the issuance decision. Verified emission reductions or removals are converted into Planetary Carbon Units. Each unit is assigned a unique serial number that encodes the project identifier, monitoring period, vintage year, and issuance batch.

The issuance batch is then recorded in the PCS Registry. A corresponding blockchain verification hash is generated and published alongside the issuance entry, ensuring immutability. Issued PCUs may subsequently be transferred, retired, or canceled in accordance with registry permissions and user actions.

Annex B - Index Of PCS Forms And Templates

Category	Annex B item (PP-013)	Internal ID(s)	Uploaded file(s)	Status	Remarks
B.1 Project design & registration	Project Submission Form	PCS-PSF	PCS-PSF-Project Submission Form_v1.0.docx	Active	Primary intake form for project registration submissions.
B.1 Project design & registration	Letter of Authorization template	PCS-LOA	PCS-LOA-Letter of Authorization (Regular)_v1.0.docx	Active	Host Party authorization letter template.
B.1 Project design & registration	Methodology concept forms	PCS-METH-*	PCS-METH-CN / PCS-METH-AF / PCS-METH-CL / PCS-METH-DEV / PCS-METH-RR / PCS-METH-Intro / PCS-METH-TPL (all v1.0 .docx)	Active	Complete methodology submission/assessment/change package.
B.1 Project design & registration	Project description formats	PCS-PDD-* (sector)	PCS-PDD-NBS-Project Design Document_v1.0.docx	Active	Currently implemented as sector-specific PDD (NBS). Consider adding a cross-sector ‘Master PDD’ shell.
B.2 Monitoring & verification	Project Monitoring Report template	PCS-MP(RT)-001 (master) + PCS-MR-NBS (sector)	PCS-MP(RT)-001-Project Monitoring & Performance Report_v1.0.docx; PCS-MR-NBS-Monitoring Report_v1.0.docx	Active	Recommend designating PCS-MP(RT)-001 as the master template; keep PCS-MR-NBS as sector annex/variant.
B.2 Monitoring & verification	Validation Report template	PCS-VV-001	PCS-VV-001-Project Validation Report_v1.0.docx	Active	Core validation reporting template for VVBs.
B.2 Monitoring & verification	Verification Report template	PCS-VV-003	PCS-VV-003-Emission Reduction Verification Report_v1.0.docx	Active	Core verification reporting template for VVBs.
B.2 Monitoring & verification	Validation Report for Post-Registration Changes	PCS-VV-002	PCS-VV-002-Validation Report for Post-Registration Changes_v1.0.docx	Active	Used for assessing design/parameter changes after registration.
B.3 Safeguards & SDG	Environmental and Social Safeguards Form	PCS-SF-001	PCS-SF-001-Environmental & Social Safeguards Assessment Form_v1.0.docx; PCS-SF-001-...v1.0.xlsx	Active	Dual-format (DOCX + XLSX) is good—ensure the registry clearly indicates which is authoritative for submission.
B.3 Safeguards & SDG	SDG Impact Assessment Form	PCS-SF-002	PCS-SF-002-Sustainable Development Impact Assessment Form_v1.0.docx; PCS-SF-002-...v1.0.xlsx	Active	Align naming: PP-013 says ‘SDG Impact Assessment’; your internal name is ‘Sustainable Development Impact’ (OK but standardize wording).
B.3 Safeguards & SDG	Safeguards Instructions Annex	PCS-SG	PCS-SG-Safeguards Instructions Annex_v1.0.docx	Active	Referenced supporting annex for safeguards/SDG forms.
B.4 Governance & legal	Change Request and Appeals Form	TBD (candidate: PCS-GF-001)	— (not uploaded as a dedicated ‘Change Request & Appeals’ form)	Draft / Missing	PP-013 explicitly requires this form. Consider repurposing/renaming PCS-GF-001 Governance Case Submission Form to cover appeals, or create a dedicated Appeals/Change Request form.
B.4 Governance & legal	Authorization Archive template	TBD (candidate: PCS-RG-A01)	PCS-RG-A01-Authorization & Digital Ledger Template_v1.0.docx	Draft (needs alignment)	PP-013 describes an archive of Secretariat decisions for blockchain entry; confirm PCS-RG-A01 fully matches this scope or create a separate ‘Authorization Archive’ record.
B.4 Governance & legal	VVB Accreditation Application	PCS-VVB-Application	PCS-VVB-Application Form_v1.0.docx	Active	VVB application form referenced by PP-013.
B.4 Governance & legal	VVB Agreement Template	PCS-VVB-Agreement	PCS-VVB-Agreement Template_v1.0.docx	Active	VVB contracting template referenced by PP-013.

Note:

Only the most recent versions of PCS Forms and Templates published on the PCS Registry are valid for use. Superseded versions are retained in the archive for recordkeeping and traceability purposes.

Annex C - Glossary Of Terms

C.1 Glossary

The following glossary defines key terms used throughout the PCS Operational Process Manual and associated governance documents.

Accredited Validation and Verification Body refers to an independent organization officially authorized to undertake validation and verification under PCS requirements.

Additionality refers to the principle that emission reductions would not have occurred in the absence of the PCS project.

Baseline Scenario refers to the reference situation against which emission reductions or removals are measured.

Blockchain Verification Hash refers to the cryptographic value recorded on the PCS blockchain ledger to ensure immutability of registry records.

Crediting Period refers to the time interval during which a project is eligible to generate Planetary Carbon Units.

Eligibility Review refers to the Secretariat’s assessment of whether a submitted project meets PCS Framework requirements prior to validation.

Emission Reduction refers to the measurable decrease in greenhouse gas emissions attributable to a PCS project.

Issuance refers to the creation of Planetary Carbon Units following successful verification.

Material Discrepancy refers to any error or omission in monitoring or reporting that may significantly affect reported emission reductions.

Monitoring Period refers to the duration during which project data is collected for verification.

Planetary Carbon Unit (PCU) refers to the standardized unit issued under PCS representing one tonne of verified emission reduction or removal.

Post-Registration Change refers to any modification to a registered project that requires formal submission, review, and approval.

Project Developer refers to the entity responsible for designing, implementing, and reporting on PCS projects.

Safeguard Compliance refers to adherence to environmental and social protection requirements defined under PCS.

Serial Number refers to the permanent identifier assigned to each PCU issued under PCS.

Validation refers to the independent assessment of a project’s design.

Verification refers to the independent confirmation of monitored emission reductions or removals.

Annex D - Document Control And Revision History

D.1 Document Ownership

The PCS Operational Process Manual is maintained by the PCS Secretariat under the authority of the PCS Regulatory Council. The Secretariat is responsible for ensuring that the manual reflects current policies, methodologies, administrative procedures, and registry operations.

D.2 Revision Process

Revisions to the manual may be proposed by the Secretariat, VVBs, Project Developers, or host country stakeholders. Proposed revisions undergo review by the Secretariat and, where applicable, independent technical advisors. All revisions require approval by the PCS Regulatory Council. Once approved, the updated version is published on the PCS Registry and supersedes all earlier versions.

D.3 Version Numbering

Each official release includes a version number, issuance date, and a summary of changes. Version numbers consist of a major and minor identifier. Major revisions indicate structural or procedural changes; minor revisions reflect editorial corrections or clarifications.

D.4 Archiving

All previous versions of the manual are archived and remain accessible for audit or investigative purposes. Archival entries include blockchain verification hashes to ensure authenticity.