Project Development

Inside a Carbon Project PDD: Structure, Methods and Key Risks

A project design document turns a climate activity into an auditable carbon project. Here is what it contains and where validation often stalls.

Inside a Carbon Project PDD: Structure, Methods and Key Risks

A project design document, commonly called a PDD, is the technical foundation of a carbon project. It explains what the activity will do, why it is eligible, how the baseline is constructed, how reductions or removals are quantified and how results will be monitored over time.

Different programmes use slightly different names, but the function is consistent: the document gives an independent validation and verification body enough evidence to test the project against the selected standard and methodology.

Core sections of a PDD

Most documents cover project identity, location, start date, crediting period and participants before moving into the methodology application. The technical core normally includes:

  • Project boundary and sources, sinks and reservoirs.
  • Baseline scenario and baseline emissions.
  • Additionality demonstration.
  • Project emissions and leakage.
  • Quantification equations and input parameters.
  • Monitoring plan, instruments, frequency and quality controls.
  • Environmental and social safeguards.
  • Stakeholder consultation and grievance procedures.
  • Data management, uncertainty and record retention.

Land projects add carbon pools, stratification, sampling design and permanence risk. Technology projects may add equipment specifications, calibration, destruction efficiency, mass balance or energy consumption.

Where quantification becomes vulnerable

The methodology defines the calculation framework, but the PDD determines how it is applied to one real activity. Validation often focuses on whether the selected baseline remains credible, whether assumptions are supported by local evidence and whether the monitoring system can collect every parameter required by the equations.

A project can fail even with a valid methodology if the activity started too early, the applicability conditions are not met or the additionality case does not reflect current regulation and common practice.

Common causes of delay

Frequent issues include incomplete ownership evidence, inconsistent dates, weak financial analysis, unclear project boundaries, unresolved leakage, unsupported default factors and monitoring plans that rely on data the operator cannot reliably obtain.

For grouped projects, inclusion criteria and participant onboarding require particular care. For Article 6 activities, the PDD also needs to align with host-country requirements and the intended international transfer framework.

Why buyers should read it

The PDD is where marketing claims become testable assumptions. It reveals which parameters drive volume, how uncertainty is treated and what the project is required to monitor after registration.

Sentinel Earth manages this work as part of the full carbon project development lifecycle, from feasibility and methodology selection through validation, finance, monitoring and issuance.

Linden Felder

About the author

Linden Felder

Leads market communications, research publishing and brand strategy.

Keep reading

Related insights.

All insights