PCS GF 002 Post Registration Project Change Form_v1.0

• Document code: PCS-GF-002

• Title: Post-Registration Project Change Form

• Scope: Used by Project Developers to request changes to registered PCS projects (Regular and NBS tracks), with supporting evidence and traceable PCS decision fields.

• Outcome: Ensures post-registration changes are submitted, reviewed, validated (where required), and recorded consistently and auditably.

Version history and change log

Table DC-1. Revision history

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

Superseded versions

No superseded versions for v1.0.

Governance note on versioning and archiving:

Only the latest approved version of this form shall be used. Superseded versions shall be archived and retained for traceability and audit purposes. Printed or downloaded copies are uncontrolled; the PCS published version is the authoritative current version.

1

Purpose

This form shall be used by Project Developers to request changes to registered projects under the Planetary Carbon Standard (PCS). This form applies to Regular (Type A/B) and Nature-Based Solutions (Type C) tracks.

2

Section A – Project Identification

PCS Project ID
Project Title
Project Category / Track	☑ Regular (Type A/B) ☐ NBS (Type C) ☐ Other: ___________
Host Country
Sectoral Scope(s)
Registration Date
Project Developer / Organization

3

Section B – Nature of the Requested Change

Select and describe the type(s) of post-registration change being requested. Attach supporting evidence or documentation where applicable.

Type of Change	☐ Project Design ☐ Methodology Update ☐ Crediting Period Extension ☐ Ownership Transfer ☐ Monitoring Plan Update ☐ Other: ___________
Summary of Change Requested
Effective Date (if applicable)
Reason / Justification for Change
Expected Impact on Emission Reductions (if any)
Supporting Documents Attached	☑ Yes ☐ No
Linked Methodology / Tool (if applicable)
Reference to Previous Validation or Issuance

4

Section C – Supporting Evidence and Attachments

Provide a list of all supporting documents attached to this request, including updated project documentation, validation or monitoring data, and any letters of consent from involved entities.

Document Title	Reference / Version	Attachment Reference (Filename or Link)

5

Section D – Declaration by Project Developer

By signing below, the Project Developer confirms that the information provided is accurate and complete, that all supporting documentation is attached, and that the requested change does not alter the fundamental scope or integrity of the registered project.

Authorized Representative (Name)
Organization
Signature / Digital Authorization Token
Date (DD/MM/YYYY)

6

Section E – PCS Secretariat Use Only

To be completed by the PCS Secretariat upon review of the submitted Post-Registration Change Request.

Date of Receipt
Reviewed By
Initial Review Outcome	☑ Accepted for Validation ☐ Rejected ☐ Additional Information Required
Validation Entity Assigned
Final Decision	☑ Approved ☐ Rejected ☐ Pending Validation
Date of Decision
PCS Blockchain Verification Hash