# Project Proposal Flow

A Project Developer **proposes a new project** using **new or existing OCP methodologies**.

_Project developers who wish to propose a new project must_ [_make an account_](https://pilot.ocp.earth) _and fill out the proposal questions on the OCP platform. See our project proposal flow below._

{% file src="https://2657567075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliKVc60bXYNfBciAKA8%2Fuploads%2F9gOk0CH6YerfORWQnOAM%2FOCP-Project_Proposal_Form.pdf?alt=media&token=0aef36c2-3fe9-4936-ad18-520e59f46e65" %}

The PD provides **evidence of validity:**

* Eligibility under the selected methodology + any applicability concerns
* Baseline scenario
* Permanence
* Additionality
* Leakage
* Prior Public Engagement / Consultations

as well as setting **monitoring dates** for the project timeline.

They **work together with dMRV and validator partners,** and optionally with experts and/or consultants, to agree on a high-quality project plan + dMRV plan.

{% content-ref url="third-party-validation-and-verification/dmrv-digital-monitoring-reporting-and-verification" %}
[dmrv-digital-monitoring-reporting-and-verification](third-party-validation-and-verification/dmrv-digital-monitoring-reporting-and-verification)
{% endcontent-ref %}

All documents, APIs, and communications are **publicly and transparently stored on the blockchain** as a single source of truth for future reference. We are moving away from long spreadsheets and pdfs, making sure all documentation and ingested data relating to the project proposals is publicly accessible.&#x20;

<figure><img src="https://2657567075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliKVc60bXYNfBciAKA8%2Fuploads%2F9IR7KndrzcuxvzbAXjvr%2Fimage.png?alt=media&#x26;token=2218dd92-7b4e-4a3e-a59f-6e9370b0d3f6" alt="" width="563"><figcaption></figcaption></figure>

### Project Public Commentary

While a proposed project is undergoing third-party validation, the project proposal will be published on the OCP for 15 days of public commentary. The Project Developer must respond to all public commentary as part of the approval process. All comments will be made publicly available with the project page on the registry.

We also include sections in the project proposal form for project developers to demonstrate they have conducted public engagement and consultation to assess social and environmental impacts prior to project implementation.

### Project Eligibility

The Open Carbon Protocol has the flexibility to incorporate a variety of activity types, though the primary focus is project-based. The OCP is sector and geographically agnostic.

### **Renewal of Crediting Period**

The maximum crediting period allowed on the OCP is 10 years, although some methodologies will set shorter crediting periods. Once an initial crediting period is complete, the project developer will have to submit a new project proposal if they wish to 'renew'. This project proposal will include reassessment of baseline scenarios and will need revalidation by a different third-party Validator than any previous projects using the same methodology.&#x20;

This process greatly reduces the chance for low-integrity projects or project fraud to operate on the OCP. In today's frequently changing carbon markets, we ask project developers to consider all projects as 'new', even if some of the underlying documents and information will be the same.

### Project Deviations

If a project deviation is noted in the Project Proposal Form, there will be a 4-step escalating process:

1. _**VVB approved deviation**_: If the validator is convinced that the deviation was (a) unavoidable (b) addressed in a manner consistent with industry best practices, and (c) doesn't impact the belief that the action conservatively reduces or removes one tonne of carbon, then the project can be validated through a normal process. The deviation will be noted as approved under this method in the validation report.
2. _**OCP Precedent**_: If the VVB is unable or unsure of attesting under step 1, the OCP team can point to previous deviation precedents within other OCP-approved projects to allow for approval.
3. _**OCP Expert Review**_: If there is no precedent, the OCP will convene an Expert Review panel of at least two (2) experts to consider the deviation in one round of review. A super-majority (80%) of experts must approve the deviation within one (1) round of review. The decision will be published along with the validation document.
4. _**Methodology Module**_: If an Expert panel does not agree that this deviation fits under the current methodology, a module of the Methodology can be proposed. This commences a new methodology review process as described in the Methodology section above. This will require a panel of a minimum of four (4) experts, two (2) rounds of feedback, public commentary, and a super-majority positive decision. The methodology module will be published and no deviation will be required.

***

## Data Partnerships

We are proud to work with **RMI** on integrating their [Carbon Crediting Data Framework](https://rmi.org/our-work/climate-intelligence/carbon-markets-initiative/the-carbon-crediting-data-framework/) into our data schema, especially their work on [safeguards and co-benefits](safeguards-co-benefits-and-sdgs).

We are also working closely to integrate with the [Climate Action Data (CAD) Trust](https://climateactiondata.org/) and [CDOP data standardization](https://www.cdop.info/) efforts.

***

## Deep Dives

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Safeguards, Co-Benefits &#x26; SDGs</td><td></td><td></td><td><a href="safeguards-co-benefits-and-sdgs">safeguards-co-benefits-and-sdgs</a></td><td><a href="https://2657567075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliKVc60bXYNfBciAKA8%2Fuploads%2F519DHKC0nuOHpI7RpV9G%2Fandrew-pons-lylCw4zcA7I-unsplash.jpg?alt=media&#x26;token=7260aaa2-0c75-459b-bc46-e4c1eec0986e">andrew-pons-lylCw4zcA7I-unsplash.jpg</a></td></tr><tr><td>MRV: Monitoring, Reporting and Verification</td><td></td><td></td><td><a href="third-party-validation-and-verification/dmrv-digital-monitoring-reporting-and-verification">dmrv-digital-monitoring-reporting-and-verification</a></td><td><a href="https://2657567075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliKVc60bXYNfBciAKA8%2Fuploads%2FlFHvy4EXSHodRmCdtz0v%2Fchris-liverani-dBI_My696Rk-unsplash.jpg?alt=media&#x26;token=508d6fb1-9669-4883-a9f2-1409914d3923">chris-liverani-dBI_My696Rk-unsplash.jpg</a></td></tr><tr><td>Third-Party Project Validation</td><td></td><td></td><td><a href="third-party-validation-and-verification">third-party-validation-and-verification</a></td><td><a href="https://2657567075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQliKVc60bXYNfBciAKA8%2Fuploads%2FmpMmPUU40yT6xHbhdzIO%2Fahsanization-CUTeHQGDaJ0-unsplash.jpg?alt=media&#x26;token=aba2ca33-c4bc-44a7-800b-94743cd22df6">ahsanization-CUTeHQGDaJ0-unsplash.jpg</a></td></tr></tbody></table>

