Designing a project
What goes into the Detailed Project Document (DPD) and the decisions to make before validation.
A project is described in a Detailed Project Document (DPD) and a Stakeholder Consultation Report (SCR). These articles explain what each part of the design must cover.
The DPD is the main design document for a project. It is prepared on the CR-I template, together with a Stakeholder Consultation Report (SCR), and submitted to an empanelled VVB for validation.
The DPD must name the owners of the project with evidence. A Delegate Entity (DE) must be appointed to coordinate the project and communicate with the VVB and NCCF.
Before validation, a project consults local stakeholders, including at least one physical meeting, and records the results in the Stakeholder Consultation Report (SCR).
The start date is when a project begins generating reductions or removals. Carbon Standard v1.1 sets how soon validation must follow it; the Registration and Issuance Procedure sets listing and registration deadlines.
Choose a fixed or a renewable crediting period. Non-AFOLU projects: up to 10 years fixed, or up to three periods of 7 years. AFOLU projects: up to 30 years fixed, or up to three periods of 20 years.
The DPD defines the project boundary, the baseline scenario and estimates of net reductions or removals, all following the applied methodology and the principle of conservativeness.
The monitoring approach sets out what is measured and how, who is responsible and how quality is controlled. Monitored data must be kept for at least five years after the final crediting period or the last issuance.
A project may deviate from its methodology only for fixed data, monitored data or the monitoring strategy, and only if the result stays conservative. Deviations are requested through a Methodology Deviation Form.
