# Third-Party Validation and Verification {% hint style="success" %} **Want to apply to be a VVB on the OCP?** [Fill in our application form here.](https://form.jotform.com/240724162555050) {% endhint %} ## Introduction **Validation of projects** and **verification of data** by an accredited, independent Validation and Verification Body (VVB) ensures that OCP projects and credits are high-integrity, additional, and conservatively reduce or remove one tonne of CO2e per credit. Every project must undergo Validation before being Registered on the OCP Registry; all projects must also undergo 1 of 3 pathways to Data Verification for every **monitored data** submission and **credit issuance**. [The OCP works with a number of Validation and Verification Bodies (VVBs) globally to carry out these independent assessments](https://www.ocp.earth/validators). Below, validation and verification requirements and outputs are laid out in detail: 1. **Project Validation** 1. Minimum Requirements for Project Validation 2. Site Visit Requirement 3. Output: Validation Statement and Validation Report 2. **Data Verification** 1. Selecting from the 3 Verification pathways 2. Minimum Requirements for Data Verification 3. Minimum Requirements for dMRV *(additional to Data Verification)* 4. Data Verification Approval 3. **OCP Review** The sub-page **"**[**Working as a VVB on the OCP**](/ocp-handbook/projects/third-party-validation-and-verification/working-as-a-vvb-on-the-ocp.md)**"** covers: 1. Application Requirements, including Accreditation 2. Onboarding and Training 3. Selection of VVB for Project Validation and/or Data Verification 4. Oversight 5. Fees ### Relevant Definitions *For more terms,* [*see the Glossary*](/ocp-handbook/glossary.md)*.*

Term	Definition
Validation (also, Project Validation)	The process of independent, third-party evaluation of a project requesting registration (see: Registered Project) on the OCP Registry by an accredited VVB against the relevant OCP Methodology and OCP requirements set out in this OCP Handbook. If successful, the project will be registered on the OCP Registry.
Agreed-Upon-Procedures	A type of Project Validation performed by an accredited VVB, such as EY. This must align with ISO 14064-3 and 14065 and met the Minimum Requirements for Validation and/or Verification below.
Registered Project	A project that has successfully undergone Validation and been approved for registration by an independent VVB. These projects are publicly available on the ‘Registered Projects’ tab of the OCP Registry.
Verification (also, Data Verification)	The process of independent, third-party ex-post evaluation by a VVB of monitored data by a registered project to issue carbon credits against the Minimum Requirements for Verifications on the OCP. If successful, the associated carbon credits will be issued to the Project Developer's account.
VVB	An independent third-party entity that is accredited for performing project validation and/or data verification activities. VVB = Validation and Verification Body

### Validation and Verification Process:

*** ## **Project Validation** ### Minimum Requirements for Project Validation * VVBs check each section of the [Project Proposal](/ocp-handbook/projects/project-proposal-process.md) for accuracy and compliance to the methodology, including requesting & auditing any required documentation, data or paperwork. Validation must be carried out in line with ISO 14064-3 and ISO 14065. VVBs may also use additional frameworks in this work (e.g. ISAE, GHG Protocol, other climate or social impact standards). * Validation **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 of 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. * Validation **must ensure the project meets all of the following Minimum Requirements for Project Validation**. If any are not met, the project cannot be registered. **Minimum Requirements for Project Validation:** > **To a reasonable level of assurance:** > > 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 risks** been fairly outlined and calculated? Have mitigation plans been proposed, including requirements for ongoing monitoring? > 4. Have **leakage risks** been fairly outlined and calculated? Have mitigation plans been proposed, including requirements for ongoing monitoring? > 5. Have **project boundaries** been accurately identified? Do these overlap with other voluntary or compliance carbon projects? > 6. Can the planned project be **expected to achieve planned emission reduction or removal**? > 2. Does the project follow all laws and regulations in the project geography? > 3. Has the Project Developer responded to all OCP public commentary and run a robust stakeholder engagement process in line with the [OCP Robust Stakeholder Engagement Process](/ocp-handbook/projects/safeguards-co-benefits-and-sdgs.md#have-a-robust-stakeholder-engagement-processes)? > 4. Have **safeguard and co-benefit** **risks and mitigation plans**, as well as contribution to SDGs, been fairly documented? > 1. Have environmental and social risk assessments been conducted in alignment with[ IFC Safeguard Standards](/ocp-handbook/projects/safeguards-co-benefits-and-sdgs.md#environmental-and-social-risk-assessments)? > 2. Has the project developer implemented [management plans to effectively minimize these risks](/ocp-handbook/projects/safeguards-co-benefits-and-sdgs.md#mitigating-risks-with-safeguards)? > 3. Has the project developer accurately assessed how their activities align with Sustainable Development Goals? > 4. If appropriate, has a benefit-sharing plan been developed equitably and in accordance with the [OCP Handbook](https://open-carbon-protocol.gitbook.io/ocp-handbook/projects/safeguards-co-benefits-and-sdgs#have-a-robust-stakeholder-engagement-processes)? ### Certifications and Labels * If a Project Developer has requested any [additional certifications and labels](/ocp-handbook/registry/certifications-and-labels.md), the VVB will review any additional requirements and confirm compliance as part of Project Validation. * For the '[CCP-Approval](/ocp-handbook/registry/certifications-and-labels/ccp-core-carbon-principles.md)' label, this including checking if the project meets all additional requirements for CCP labelling that may have been decided by ICVCM for a specific methodology. These additional requirements will be highlighted in the methodology and the project proposal form. ### Site Visit * During Project Validation, the VVB **must visit at least one site** (project location), accompanied by the PD (and optionally with other partners as well). This site visit should including in-person team interviews and observation of at least one measurement being taken. There may be additional requirements for the site visit in the specific methodology. * If the PD has selected the ‘*dMRV pre-verification*’ Verification pathway, the VVB **must perform at least one in-person assessment of the dMRV set-up and procedures**. This can be done at the same time as the Validation site visit. * The VVB and PD may conduct additional site visits virtually, as long as at least one of the site visits is in person. * If the PD has selected the ‘*Per Issuance*’ or ‘*dMRV pre-verification*’ Verification pathway, the VVB **must decide whether additional site visits are required** during the Verification process, based on an internal risk assessment. ### Output: Validation Statement and Validation Report * As the final output of the Validation process, the VVB **must either ‘Accept’ or ‘Reject’ the** **Validation Statement** (‘[**Minimum Requirements for Validation**](#minimum-requirements-for-project-validation)’) **.** If they accept, the project will be Registered on the OCP Registry (after [**OCP Review**](#ocp-review)), and be able to submit monitored data for the issuance of credits (after [**Data Verification**](#data-verification)). * If the VVB rejects the Validation Statement, the project will not be Registered and will not be able to issue credits. If the PD wants to re-submit their project, they will have to complete the entire Project Proposal flow from the start, including documenting how they have fixed the issues raised in the Validation Report. * The VVB must also submit a **Validation Report**, summarizing their assessment process and findings. They must submit a Validation Report even if they reject the Validation Statement, detailing why the project has not met the Requirements for Validation. For Registered Projects, this report will be publicly available on the Registered Project page on the OCP registry. For rejected projects, this report will only be available to the PD and the OCP. * If the PD has selected the ‘*In Tandem with Validation*’ Verification pathway, the [**Verification Report** (see below)](#output-verification-statement-and-verification-report) can be combined with the **Validation Report** and submitted as one document. The combined document must document all the "[**Minimum Requirements for Project Validation**](#minimum-requirements-for-project-validation)” and “[**Minimum Requirements for Data Verification**](#minimum-requirements-for-data-verification)”. * VVB can use either the OCP Templates ([Validation Report](https://docs.google.com/document/d/1gkJbL7d-l0kqyAEpMDCv7qF6pm5giAUgCw4c7JSs9Bs/edit?usp=sharing), Verification Report), or submit using their own format as long as **all the same sections and requirements are met**. * The **Validation Statement** and **Validation (and/or Verification) Report** is submitted digitally on the OCP platform by the VVB.

*OCP Validation Report Template* *v2.0*
*Previous versions can be found in* *Handbook Version History*

*** ## **Data Verification** ### Selecting from the 3 Verification pathways Depending on the project design and available technologies, the PD must select from one of the three Verification pathways during [Project Proposal](/ocp-handbook/projects/project-proposal-process.md): 1. **In Tandem with Project Validation****:** If the project has only one issuance, and all monitored data will be collected before Project Validation, the PD can submit the monitored data at the same time as the project proposal submission. 1. The VVB will perform both Project Validation and Data Verification at the same time (’in tandem’) against both the ‘[**Minimum Requirements for Validation**](#minimum-requirements-for-project-validation)’ and ‘[**Minimum Requirements for Verification**](#minimum-requirements-for-data-verification)’. 2. The VVB must submit both a [**Validation Report**](#output-validation-statement-and-validation-report) **and** [**Verification Report**](#output-verification-statement-and-verification-report) (which can combined into one file: the **Validation and Verification Report)**, as well as both the [**Validation Statement**](#output-validation-statement-and-validation-report) and [**Verification Statement**](#output-verification-statement-and-verification-report) at the same time. 3. After OCP Checks, the project will be Registered on the OCP Registry and immediately trigger the [Credit Issuance](/ocp-handbook/registry/credit-issuance-transfer-retirement.md#credit-issuance) process. 2. **Per Issuance**: If the project has multiple issuances, the monitored data must be collected and reported by the PD over each Crediting Period and submitted to the OCP. 1. After a project has been Registered on the OCP Registry, PD will be notified on each Monitoring Event (i.e. at the end of each Reporting Period) to submit monitored data. This data will then be Verified by a VVB against the ‘[**Minimum Requirements for Verification**](#minimum-requirements-for-data-verification)’. The VVB must submit a [**Verification Report**](#output-verification-statement-and-verification-report) and [**Verification Statement**](#output-verification-statement-and-verification-report) on the OCP platform. 2. After OCP Checks, the [Credit Issuance](/ocp-handbook/registry/credit-issuance-transfer-retirement.md#credit-issuance) process will be triggered. 3. The ongoing Verification of monitored data can be performed by either the same VVB who performed Project Validation, or a different VVB. This decision will be proposed by the PD and approved by the OCP. 3. **dMRV Pre-Verification** **\[IN PILOT, NOT ICVCM COMPLIANT - SEE NOTE BELOW]**: If the project works with an independent third party digital MRV provider (dMRV), they can choose to undergo dMRV pre-verification instead of verification per issuance. 1. During [**Project Validation**](#project-validation), the VVB will assess the proposed dMRV process, technology, and partnering organization against the ‘***Minimum Requirements for dMRV***’. This must include a site visit to assess the dMRV set-up in person (which can be done at the same time as Project Validation). 2. The VVB must submit both a **Validation Report** and **dMRV Report** (which can be combined into one file: **Validation and dMRV Report**), as well as both the **Validation Statement** and **dMRV Statement** at the same time. The project will be Registered but no credits will be issued at that point. 3. The dMRV will be notified (either manually or digitally via API) on each Monitoring Event (i.e. at the end of each Reporting Period) to submit monitored data. This data undergoes OCP Data Checks, and if approved, the [Credit Issuance](/ocp-handbook/registry/credit-issuance-transfer-retirement.md#credit-issuance) process will be triggered. 4. The dMRV partner and process will be audited at least once per year by the OCP as part of the Annual Audit process. This process may include the initial or a different VVB, as required. {% hint style="warning" %} The **dMRV pre-verification pathway** is currently in pilot and can only be used with permission from the OCP Team. The OCP will be working closely with pilot PDs, dMRV providers and VVB/Auditors to ensure all data reaches the same or higher level of data verification as other pathways. This pathway will be updated based on feedback and results from these pilots, so both the procedure and report may change during and after the pilot.\ \ This pathway is currently **not fully compliant with** [**ICVCM's Core Carbon Principles**](/ocp-handbook/registry/certifications-and-labels/ccp-core-carbon-principles.md)**.** Any project using the dMRV pre-verification pathway will currently not be eligible for CCP-Approval labelling for their credit issuances. We are working with the ICVCM team to ensure that this pathway will be CCP complaint in the future. {% endhint %} ### Minimum Requirements for **Data Verification** * VVBs review submitted Monitored Data to ensure completeness and accuracy. Verification must be carried out in line with ISO 14064-3 and ISO 14065. VVBs may also use additional frameworks in this work (e.g. ISAE, GHG Protocol, other climate or social impact standards). * Monitoring events, and therefore data verification, **must happen at least once a year.** PDs can select more frequent monitoring and verification. * Verification **must ensure the monitored data meets all of the following Minimum Requirements for Data Verification**. If any are not met, the credits cannot be issued. **Minimum Requirements for Data Verification:** > **To a reasonable level of assurance:** > > 1. Is the monitored data provided complete? > 2. Is the monitored data provided accurate? > 3. Was the sampling approach appropriate for the project design and calculations? > 4. Does the Net Reduction or Reduction calculated from the provided monitored data represent a conservative tonne of CO2e reduced or removed? ### Output: Verification Statement and Verification Report * As the final output of the Verification process, the VVB **must either ‘Accept’ or ‘Reject’ the Verification Statement** (the "[**Minimum Requirements for Data Verification**](#minimum-requirements-for-data-verification)*"*, above). If they accept, the data will be accepted and the Credit Issuance process will be triggered. * If the VVB rejects the Verification Statement, the credits will not be issued. * The VVB **must also submit a Verification Report**, summarizing their assessment process and findings. They must submit a Verification Report even if they reject the Verification Statement, detailing why the project has not met the Requirements for Verification. This report will be publicly available on the Registered Project page on the OCP registry. * If the PD has selected the ‘*In Tandem with Validation*’ Verification pathway, the **Verification Report** can be combined with the [**Validation Report**](#output-validation-statement-and-validation-report) and submitted as one document. The combined document must document all the "**Minimum Requirements for Project Validation**” and “**Minimum Requirements for Data Verification**”. * VVB can use either the OCP Templates (Validation Report, Verification Report), or submit using their own format as long as all the same sections and requirements are met. * The **Verification Statement** and **Verification (and/or Verification) Report** is submitted digitally on the OCP platform by the VVB.

*OCP Verification Report Template* *v1.0*

### Minimum Requirements for dMRV Verification {% hint style="warning" %} The **dMRV pre-verification pathway** is currently in pilot and can only be used with permission from the OCP Team. The OCP will be working closely with pilot PDs, dMRV providers and VVB/Auditors to ensure all data reaches the same or higher level of data verification as other pathways. This pathway will be updated based on feedback and results from these pilots, so both the procedure and report may change during and after the pilot.\ \ The dMRV pre-verification pathway is currently **not fully compliant with** [**ICVCM's Core Carbon Principles**](/ocp-handbook/registry/certifications-and-labels/ccp-core-carbon-principles.md)**.** Any project using the dMRV pre-verification pathway **will not be eligible for CCP-Approval labelling** for their credit issuances. We are working with the ICVCM team to ensure that this pathway will be CCP complaint in the future. {% endhint %} dMRV Pre-Verification must ensure the monitored data meets all of the following Minimum Requirements for dMRV. If any are not met, the pathway will not be approved. **Minimum Requirements for dMRV Verification:** > **To a reasonable level of assurance:** > > 1. The dMRV system is correctly configured to measure, report, and transmit project data in accordance with the applicable OCP Methodology. > 2. The dMRV system can provide monitored data that allows the calculation of the Net Reduction or Reduction that represents a conservative tonne of CO2e reduced or removed. > 3. The dMRV partner meets OCP accreditation and technical requirements. > 4. The data outputs from the dMRV system during the assessment period are accurate and consistent with the methodology's quantification requirements. > 5. The dMRV pathway is suitable and sufficient as an ongoing MRV mechanism for this project, and the VVB recommends pre-approval of the dMRV pathway. ### dMRV Partner Accreditation and Technical Requirements *In Development* ### Output: dMRV Statement and dMRV Report * As the final output of the dMRV Verification process, during Project Validation the **VVB must either ‘Accept’ or ‘Reject’ the dMRV Statement** (the "[**Minimum Requirements for dMRV Verification**](#minimum-requirements-for-dmrv-verification)**"**, above). If they accept, the project will be approved for Registration with the dMRV procedures proposed. * If the VVB rejects the dMRV Statement, the project will not be approved for Registration. * The VVB must also submit a **dMRV Report**, summarizing their assessment process and findings. They must submit a dMRV Report even if they reject the dMRV Statement, detailing why the proposed dMRV process has not met the Minimum Requirements for dMRV Verification. This report will be publicly available on the Registered Project page on the OCP registry. This report can be combined with the [**Validation Report**](#output-validation-statement-and-validation-report) into one file: **Validation and dMRV Report**, as both are submitted during Project Validation. * The **dMRV Statement** and **dMRV Report** is submitted digitally on the OCP platform by the VVB during Project Validation.

*OCP dMRV Pre-Verification Report Template* *v1.0*

*** ## OCP Review **Validation and dMRV**: The OCP team (led by Rio Richardson, CPO) will review the Validation Statement, dMRV Statement, Validation Report and dMRV Report for accuracy and completeness before approving the project for registration the OCP Registry. They may require the VVB to add additional information to the Report if anything is missing or not clear. They will also confirm the project has not been registered in another registry. **Verification**: The OCP platform runs both manual and automated checks of submitted, verified project data to ensure the data is clean (in the correct format, using the correct units) and complete before credits are issued. The OCP team will also re-run [Double Issuance](/ocp-handbook/projects/no-double-counting.md#avoiding-double-issuance) checks. *** ## OCP Report Templates

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://open-carbon-protocol.gitbook.io/ocp-handbook/projects/third-party-validation-and-verification.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.