Third-Party Validation and Verification

Want to apply to be a Validator on the OCP? Fill in our application form here.

For projects to get approved and published in the OCP Registry, they must go through Project Validation or Assurance.

Project Developers can choose whether to go through the Validation process with a VVB or an Assurance/Agreed-Upon-Procedures process with a registered Auditor. Both are acceptable for project approval, and Project Developers should select the process that best fits their needs and project design.

Validation must happen within a year of project registration, though we're looking for ways and partners to reduce bottlenecks so that the process can be completed efficiently.

The OCP uses the term 'Validator' to refer to all organizations performing Project Validation, Project Assurance and/or Data Verification (i.e. both VVBs or Auditors).

Project Validation

• Definition: Validation involves a “rigorous assessment of the data, systems, processes and methodologies used to generate climate disclosures” [source].

• This is a vital auditing process that assesses the design of the mitigation activity and the associated GHG emission reductions or removals, ensuring compliance with the appropriate OCP methodology.

• The process will validate reliability and accuracy of data, documentation and other information by comparing it to established frameworks, standards and controls, such as: GHG Protocol, ISO 14064-3, ICVCM Guidance & other climate standards.

Project Assurance/Agreed-Upon-Procedures

• Definition: Assurance "takes the verification process a step further by requiring that the data checking processes are undertaken by an independent and accredited auditing professional acting" [source].

• Assurance of climate disclosures is held to the same standard as the audit of financial statements.

• Project developers can seek pre-assessment from an accredited auditor (e.g., ISAE), aligning with the GHG protocols and ISO 14064-3 as Validation. This pre-assessment will review alignment and compliance with the proposed methodology, including quality of data collection, aggregation, and reporting. Once pre-assessment has been completed, all future projects under that methodology can be assured within that framework using agreed-upon-procedures.

Data Verification

All project data must be verified by a third-party before the OCP issues credits. Data can be verified in two ways:

1. Per Issuance: manually verified by a VVB / auditor every time data is submitted. This will be in tandem with validation if projects only have one issuance. The same VVB / auditor can perform subsequent data verification. Projects must issue at least annually, although they can issue more frequently. If more than 1 year has passed since the last issuance, the project must be re-proposed.

2. Pre-Verified dMRV Process: the process & dMRV partner is pre-verified during project approval by the Project Validator. Future data is then received directly from the dMRV partner and after an additional check by the OCP, credits get issued immediately.

• See dMRV for more details.

Third-Party VVB Assessment Process

Timing

• Monitoring and issuance must happen at least once a year. Validation/verification processes must be completed within a year of project registration unless an extension was pre-discussed with OCP Admin (Rio Richardson).

  • Extensions are only granted for cases where validation or verification could not be completed within a year for external reasons (e.g. access to site, change in validator due to ceasing of operations) and not due to project developer or validator internal timelines. Extensions must be approved by the OCP Board.

• If there is a gap of more than a year between project proposal and the start validation, then the project will need to redo the project proposal process with current information to make sure all updated regulations and public consultations are accounted for.

Platform Use

• All discussions, including the sharing of documents and data, happens on platform, streamlining & speeding up the validation process and allowing better version-tracking, communication and data security than sending via email or other services. The results of the third-party validation and verifications, including the Validation Report, will be made publicly available on the OCP Registry.

Scope of Review

• VVBs / Auditors check each project section for accuracy and compliance to the methodology, including requesting & auditing any required documentation, data or paperwork. They also confirm that the project has set up MRV to accurately measure and report climate impact.

• They must perform an in-person site visit during first Project Validation, but otherwise all communication and work is done on the OCP Platform, as demonstrated above.

• As a final output they will provide a recommendation as to whether the project should go on the OCP Registry and issue credits. They will summarize findings in a Validation Report (template found below) that gets published on the project page on the OCP registry.

What is the objective of the Validation Report?

The Validation process aims to assess three main questions:

1. Does the project correctly apply the relevant OCP Methodology

   1. Is the baseline scenario valid?

   2. Have additionality requirements been met?

   3. Have permanence and leakage been fairly calculated?

   4. Can the planned project be expected to achieve planned emission reduction or removal?

2. Have safeguards and co-benefits been fairly documented?

   1. Have environmental and social risk assessments been conducted in alignment with IFC Safeguard Standards?

   2. Has the project developer implemented management plans to effectively minimize these risks?

   3. Has the developer accurately assessed how their activities align with Sustainable Development Goals?

   4. Has a benefit-sharing plan been developed equitably and in accordance with the OCP Handbook?

3. Given the proposal, will project data be accurately measured and reported?

See our Validation Report Template.

VVB & Auditor Selection Requirements

Accreditation

• All validators are required to be recognized under an international standard such as:

  • accreditation under ISO 14065 by a International Accreditation Forum (IAF) member

  • accreditation under the UNFCCC Kyoto Protocol Clean Development Mechanism, or the Paris Agreement Article 6, paragraph 4 Supervisory Body

  • IAF or ISAE for accredited auditors.

• Accreditation status is checked upon registration by the OCP, and is publicly available on the List of Active Validation Partners.

Matching Process

• The OCP team works with Project Developers to approve an appropriate VVB or auditor for the specific project based on:

  • Sector expertise,

  • Accreditation status,

  • Geography and capacity,

  • Potential conflicts of interest,

  • Data verification scope.

Conflict of Interest Policy

• VVBs & Auditors must comply with OCP's conflict of interest policy to ensure independent review.

  • If there's a conflict of interest between VVB/Auditor and the project proponent, they will not be approved for that project.

• VVBs & Auditors must disclose familial relationships with the project developer, methodology curator, or OCP leadership in their conflict of interest attestation.

• If the VVB & Auditors have their own internal COI policy, they can upload their procedural documents in our form.

Performance Oversight

• Accreditations, expertise and performance is checked upon registration and audited yearly.

  • Every year, the OCP team will require an information update on accreditations, expertise and potential COIs. We will then run internal due diligence with the relevant accreditors.

  • In addition, the OCP team will work with independent third-party assessors to review a random selection of validation reports and processes to assess performance, accuracy and completeness.

• Instances of non-compliance or misconduct are reported to the relevant accreditation body.

• The OCP reserves the right to restrict partnerships and suspend VVB accounts in the event of poor performance or behavior. These instances and path forward will be discussed with the Board.

• All validators must follow our conflict of interest policy, ensuring independence (financial or otherwise) from any project developer they work with, and comply with our annual audit process to assess protocol compliance and validation performance.

• Responsibility for Validator oversight (including conflict of interest management, audits and accreditation checks) lies with Rio Richardson, Chief Product Officer.

Fees

• Fees are arranged by a project-by-project basis, based on time & travel commitment by VVB.

• Fees for validation are paid by the Project Developer.

• Payment structure is agreed at the time of the project-specific contract.

• See also Business Model & Financial Transparency