Insights · Project development
The project design document (PDD) for an ARR carbon project
The project design document is the file an independent auditor checks before a carbon project can be registered. For a tree-planting project under Verra, it applies VM0047 to your land and commits you to a monitoring plan for decades. This post walks through what it contains, which parts a feasibility study already answers, and what needs people on the ground.
PDD or project description: two names, one document
Project design document, or PDD, is the term from the UN Clean Development Mechanism, and it is still what most people say. Under the Verra VCS Program the same document is called the project description. The VCS Standard requires project proponents to use the VCS Project Description Template, or an approved combined template such as the VCS and CCB version, and to follow all of its instructions.
Verra currently publishes the template in versions 5.0A and 5.0B. Version 5.0A is for projects that apply the relevant sections of VCS Standard v4.7 and have a project start date before 1 July 2027. Check the program details page for the version that applies to your project before you start writing.
- Verra nameProject description
- Methodology for ARRVM0047
- Audited byAn accredited VVB
What a project design document contains
The VCS template has five main parts, plus appendices for sensitive information and data parameters. For a tree-planting project, this is what each part asks.
- Project details. A summary, the project proponent and other entities, ownership and its evidence, the project start date and crediting period, the project location, conditions before the project (ecosystem type, current and historical land use, climate, hydrology, topography and soils), a description of each planting or management measure, AFOLU eligibility, compliance with laws, double counting, sustainable development contributions and leakage management.
- Safeguards and stakeholder engagement. Who the stakeholders are, how they were consulted, how free, prior and informed consent was obtained, the grievance procedure, risks to people and the environment, labour and human rights, Indigenous Peoples, property rights, benefit sharing, and ecosystem health, including endangered species, introduced species and ecosystem conversion.
- Application of methodology. Why VM0047 applies, the project boundary and carbon pools, the baseline, additionality and any deviations from the methodology.
- Quantification. Baseline and project emissions, leakage, the non-permanence risk analysis and buffer, the long-term average for projects with harvesting, and the estimated removals year by year.
- Monitoring. Data and parameters, the monitoring plan, sampling, quality control and who does what.
VM0047 adds its own requirements. The project description must include an ex-ante estimate of removals for the whole crediting period, from growth and yield models that conservatively represent the project, with a minimum uncertainty deduction of 10%. For census-based planting the ex-ante baseline is zero. For the area-based approach it must document the performance benchmark procedure in enough detail to be repeated, including the location of every project and control plot, and forecast the benchmark from the control plots' recent trend. More on this in VM0047 explained.
Which PDD sections a feasibility study already informs
A desktop carbon feasibility study is not a PDD, but several of its sections give the PDD writer a tested starting point.
| PDD section | What a feasibility study gives | What the PDD still needs |
|---|---|---|
| Project location and boundary | Boundary checked, areas and roles of each zone | Final parcels, and ownership evidence for each |
| Conditions before the project | Land cover, climate, terrain, ecoregion from published data | Field descriptions, soils, current land use confirmed on the ground |
| AFOLU and methodology eligibility | Forest in 2000, recent loss, built-up, water, slopes, recent conversion | Historical imagery and evidence that any degradation was not caused by the project |
| Project activity | Species shortlist for the ecoregion | Nursery, planting and protection plan, and species choice tested on site |
| Leakage | First estimate with VMD0054 default values | Survey of who uses the land today and where that use goes |
| Non-permanence buffer | A planning figure (15%, the median of 198 registered ARR projects) | The AFOLU Non-Permanence Risk Tool assessment |
| Estimated removals | Gross IPCC Tier 1 range and a net screening estimate | Conservative growth and yield models with site data, and the forecast benchmark |
Take the anonymised sample study we publish. It mapped a dryland boundary of 1,698 hectares, found 1,608 hectares eligible, and estimated 69,779 tCO2e gross over 40 years on that eligible land, falling to a net screening estimate of −2,976 tCO2e after uncertainty, buffer and leakage. None of those numbers can be pasted into a PDD. But they tell the developer that the site is below the platform's 5,000 ha size screen, that leakage is the line to work on (the land use was never given, so the mapped crops and rangeland counted as displaced), and that without a planting plan the gross figure is only an upper bound. See how the deductions work in gross vs net carbon credits.
What needs fieldwork and consultation
Most of what an auditor tests cannot be done from a desk:
- Starting carbon stocks. Under VM0047's area-based approach, where site preparation starts the project, the starting stock must be measured in plots no more than two years before it.
- Ownership. Documents that show the proponent has the right to run the project and claim the credits.
- Stakeholder consultation and consent. Meetings, records, language, a grievance procedure, and consent from Indigenous Peoples, local communities and customary rights holders where they are concerned.
- Additionality evidence. Regulatory surplus and, where required, an investment analysis. See additionality for tree-planting projects.
- Risk assessment. The non-permanence risk analysis: management, finance, tenure, community and natural risks such as fire. See the non-permanence buffer.
- The monitoring plan. Plot design, the stocking index and control plots for the benchmark, staff and quality control.
Drafts, pipeline listing and versions
A project description is not written once. The VCS template sets file names for each stage, and they show the life of the document. A draft submitted for pipeline listing as “under development” is a VCS_PD_DRAFT. When the project is listed as “under validation” it becomes VCS_PD_PCP. The version approved by the VVB for registration is the VCS_PD. Later changes, such as a deviation, a methodology change or a baseline reassessment, produce an updated project description, and each renewal of the crediting period gets its own.
Version numbers inside each file also follow the audit: the second digit goes up for answers to the VVB's clarification and corrective action requests, the first for answers to findings raised by Verra. Expect several rounds.
The methodology version matters as much as the template version. Under Verra's grace rules for VM0047, projects still on version 1.0 had to request pipeline listing as “under validation” by 31 December 2025 and must request registration by 31 December 2026. A project starting design now writes against version 1.1. The crediting period is a commitment too: for tree planting under the VCS Standard v4.7, the initial crediting period is at least 20 years and at most 100, and the PDD has to show a credible plan for managing the project over all of it.
Validation by a VVB
Once the project description is ready, an accredited validation and verification body (VVB) audits it against the VCS Standard and VM0047. Under the VCS Standard (v4.7 and v5.0), every project is subject to a 30-day public comment period. Validation cannot begin before that period has begun, the VVB cannot complete validation until it has ended, and it evaluates how the proponent responded to the comments. The VVB also assesses the non-permanence risk analysis.
The VVB raises findings, the proponent answers them and revises the document, and only then is the validated project description submitted for registration. The steps after that, implementation, monitoring and issuance, are in carbon project development.
Why feasibility comes before the PDD
A PDD takes field teams, consultation and months of work. Most of the reasons a tree-planting project fails are visible earlier: land already classed as forest, a climate where Tier 1 growth is slow, leakage that takes most of the gross figure, or too few eligible hectares to carry the fixed costs. A feasibility study finds those first, for $500 (eligibility) or $7,500 (full study).
Frequently asked questions
A project design document is the main technical document of a carbon project. It describes the project, applies a methodology to the site, estimates the expected reductions or removals and sets out the monitoring plan. The term comes from the UN Clean Development Mechanism. Verra calls the same document the project description and requires its own template for VCS projects.
In practice, yes: both terms mean the document a validation body audits before a project is registered. Under the Verra VCS Program the official name is project description, and the VCS Standard requires the VCS Project Description Template or an approved combined template. Many developers and buyers still say PDD out of habit.
An accredited validation and verification body (VVB), an independent auditor. Under the VCS Standard (v4.7 and v5.0), every project goes through a 30-day public comment period, validation cannot start before that period has begun, and the VVB cannot finish validation until it has ended. The VVB also assesses the non-permanence risk analysis that sets the buffer contribution.
No. A feasibility study is a desktop screening that tells you whether a project is worth designing. A PDD needs field inventories, evidence of ownership, stakeholder consultation and consent, a monitoring plan and conservative growth models. A good feasibility study gives the PDD writer a head start on the site description, eligibility evidence and a first carbon estimate.