Validation, Verification and VVBs
Project Validation and Data Verification
Validation of projects and verification of data by an independent third-party 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.
More information in the OCP Handbook.
Organizations can apply to become a VVB on the OCP Registry if they meet the Application Requirements, including accreditation. Full detail can be found in the OCP Handbook.
Project Validation
VVBs check each section of the Project Proposal for accuracy and compliance to the methodology, including requesting & auditing any required documentation, data or paperwork. Validation must ensure the project meets all of the Minimum Requirements for Project Validation, which can be found in the OCP Handbook. If any are not met, the project cannot be registered.
Data Verification
Depending on the project design and available technologies, the PD must select from one of the three Verification pathways during Project Proposal:
- 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.
- 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 the OCP.
- dMRV Pre-Verification [PILOT]: 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.
Verification must ensure the monitored data meets all of the following Minimum Requirements for Data Verification, which can be found in the OCP Handbook.