Certification Procedures

💡 This section outlines the key principles of the certification procedure. ERS has developed an App to streamline Project certification. The App guides Developers through the step-by-step process of completing Project documentation, ensuring alignment with Programme and Methodology requirements.

PROJECT FEASIBILITY REVIEW

1. Developer KYC

   1. ERS performs a Developer's Due Diligence to determine their capacity to execute the proposed Project, their compliance with jurisdictional legal requirements, and their financial, legal and moral standing. Developers must submit the requested documentation to the Certification team.
      1. If after finalising the Due Diligence ERS deems the Developer needs to remediate a shortfall in one or more aspects, the Certification Agent will issue a Corrective Action Request (CAR) and the certification process is halted.
         • When given a CAR, the Developer must demonstrate that all issues have been resolved. The Certification Agent will then review the corrections and decide if they are adequate. If the actions are sufficient, the certification process will continue. 
         • Failure to address all CARs and/or CLs after three (3) rounds (three submissions and respective feedback) will result in the certification process’ termination.

💡 Multiple platforms and technologies might be used to verify the information and documentation requested in this section. The most relevant are Refinitv, Dun & Bradstreet, local and national judiciary databases, corporate and civil registries, and satellite imagery.

2. Project Feasibility

   1. A Feasibility Study must be submitted per Project. 
   2. The Feasibility Study allows ERS to verify the Project’s adherence to Methodology-specific requirements and to the following Programme requirements:
      • Geography and Project Boundaries;
      • Ownership and Carbon Rights;
      • Start Date and Crediting Period; 
      • Stakeholder Participation;
      • No Double-Counting. 
   3. ERS performs a first estimation to determine the net GHG removal capacity of the Project. Such estimation can be performed using one of the following methods, depending on the Project Zonation: 
      1. On a per-hectare basis, using a land-cover approach.
      2. Using the applicable Quantification Methodology.

      3. Using any method deemed suitable and agreed upon with the Developer.

         💡Due to the variety of Project Zonations received during the Feasibility stage, ERS reserves the right to perform initial estimations using the most appropriate method. Final estimates, at the Project Design Review stage, must however always follow the applicable Quantification Methodology.

   4. If all information is cleared, the Project is qualified to advance to the Project Design Review phase of the Certification.
      1. ERS may decide to initiate the Project Design Review phase of a Project if one or more Project Feasibility documents are missing, on the sole condition that the Developer is capable of providing said documents before the end of the Project Design Review. Documents eligible to this exception are: 
         • Signed agreements with landowners, rights holders, including customary rights holders, or evidence that the Developer can prove the contract is being negotiated.
         • Government authorisation letters, attestations or certificates if the Developer can prove the letter was requested to the competent authorities.
         • Signed contracts with carbon rights holders, if the Developer can prove the contract is being negotiated.
      2. If the Certification Agent requires further clarification or proofing regarding a document or any information, they will issue a Clarification Request (CL). If the Agent identifies a shortfall in one or more aspects of the Project that needs remediation, they will issue a Corrective Action Request (CAR). In both cases, the certification process is halted until all issues are addressed.
         • Failure to address all CARs and/or CLs after three (3) rounds (three submissions and respective feedback) will result in the certification process termination.

PROJECT DESIGN REVIEW

1. Documentation 

   1. Upon completion of the Project Feasibility Review, ERS notifies the Developer, who must prepare the required documentation for ERS to assess and endorse the Project's design. 

   2. The required documents and procedures for completing them are detailed at the Methodology level and throughout the App.

      Assessment

   3. Information Screening. ERS undertakes a screening process to assess the information's completeness, clarity and veracity. 
      1. If CARs or CLs are identified, Developers must address them directly in the Project Design Document (PDD). Failure to address all CARs and/or CLs after three (3) rounds (three submissions and respective feedback) will result in the PDD’s rejection. 
   4. Carbon Calculation. Based on the documentation provided,  ERS will estimate the Project’s net GHG removals, following the applicable Quantification Methodology. The GHG Quantification Report is then integrated into the PDD. 
   5. Risk Assessment. ERS assesses the Project risks using the Risk Assessment Matrix.
   6. The Project Design Review is completed when:

• The Preliminary PDD has been cleared of all CARs and CLs;
• The Risk Matrix has been cleared of any “Blocker” risk, and necessary surveillance and mitigation plans have been validated by ERS. 

5. The Developer signs a PDF copy of the Preliminary Project Design Document via a secured digital signature platform, attesting to the veracity of the document’s content. 
6. Public Disclosure. The Preliminary PDD is published by ERS on the Project’s page in the ERS Registry. 

PROJECT PUBLIC COMMENT PERIOD

1. Comment Period

   1. Following the publication of the Preliminary PDD and before Validation, Projects must undergo a thirty-calendar-day Public Comment Period.
   2. ERS must publish a dedicated form for public comments on its website.
   3. At the end of the Project Public Comment Period: 
      1. ERS must compile all comments in the Project Public Comment Digest within fifteen (15) working days following the end date and share the document with the Developer.
      2. If grievances, infractions or other topics of concern arise, the Certification Agent can issue Corrective Actions Requests (CAR) and/or Clarification Requests (CL).
   4. Developers must address all feedback within twenty (20) working days directly in the Project Public Comment Digest.
   5. When ERS requests Corrective Actions, Developers must indicate their resolution in the Project Public Comment Digest document and make all necessary modifications in the PDD and related certification documentation. 
      1. All changes must be indicated to the ERS Certification Agent, who must validate them within five (5) working days from submission by the Developer.
      2. Developers have three (3) rounds of submission to address all CARs. If they fail to address them within this timeframe, the Project must restart the Project Design Review phase.
   6. The Project Public Comment Period is considered closed once all feedback, CARs and CRs are addressed by the Developer.
   7. A final report of the Project Public Comment Digest will be added as an Appendix to the PDD.

VALIDATION

1. General Principles 

   1. The Project must undergo third-party Validation following the Validation and Verification Procedure. 
   2. In the event of a successful Validation:
      1. The Project is officially certified. 
      2. The Validation Report and the final Project Design Document are publicly published on the ERS Registry. 
      3. PRUs are transferred into the Developer’s account. Refer to Units & Issuance for more details. 

Refer to the Validation and Verification Procedure for more details.