Every BioCarbon project writes a Project Description Document, and the programme gives a template for it. Our reference notes, built from the template and from a scan of 97 registered PDDs, lay out 23 sections in a fixed order. This post lists them, explains what each asks, and shows which ones real projects nearly always include.
The 23 sections in order
| No. | Section | What it holds |
|---|---|---|
| 1 | General details | Project name, holder, contacts, version and date |
| 2 | Project proponents and other entities | Participants and legal representatives |
| 3 | Project design | Objectives, activities, a grouped project flag |
| 4 | Project location | City, region, country, geospatial boundary and maps |
| 5 | Duration and crediting period | Start date, duration, quantification periods |
| 6 | Sectoral scope | AFOLU or non-AFOLU |
| 7 | AFOLU or non-AFOLU specifics | Eligible areas and stratification for AFOLU |
| 8 | Eligibility under the BCR Standard | Scope, type and scale |
| 9 | Activity description | Detail per activity |
| 10 | Project boundary | Project, reference and leakage areas, sources, sinks and reservoirs, time limits |
| 11 | Baseline or reference scenario | Selection criteria, similarity, representativeness |
| 12 | Additionality | Tool application |
| 13 | Quantification | Methodology applicability, deviations, factors, activity data, ex ante results |
| 14 | Leakage and non-permanence | Leakage management and reversal risk, including a loss event report |
| 15 | Normative framework | Standard version, methodology code and version, mandatory tools |
| 16 | Laws and regulatory compliance | Applicable law |
| 17 | Carbon ownership and rights | Owner, participants, agreements, land tenure |
| 18 | Climate adaptation and risk management | Legal, environmental, financial, governance and engagement risks |
| 19 | Environmental and socio-economic impact | Impact assessment |
| 20 | Consultation | Stakeholder participation and observations received |
| 21 | Sustainable development | Tools for sustainable development safeguards and SDGs, SDGs claimed |
| 22 | REDD+ safeguards and declarations | REDD+ only, plus co-benefits, grouped, other-programme and double counting declarations |
| 23 | Monitoring plan | Boundary, activity and quantification monitoring, QA/QC, fixed and monitored parameters, sensitive information, appendices, references |
The numbering was checked against the contents page of one REDD PDD, which runs sections 1 to 18 plus an appendix and references and reads the same way. So treat the exact numbers as a guide, not as a rule.
What the scan of 97 PDDs shows
Our reference notes counted how often certain keywords appear in 97 registered PDD texts. The corpus held 106 registry projects, of which 97 had text. The mix by type:
- reduced emissions from deforestation and degradation: 32 - reforestation: 18 - agriculture, forestry and other land use: 15 - renewable energy: 6 - waste handling and disposal: 6 - afforestation: 4 - forest restoration: 4 - organic waste digestion: 3 - energy industries, renewable and non-renewable sources: 2 - transport: 2
The most common keywords, out of 97 texts:
- baseline: 79 - methodology: 78 - quantification: 75 - additionality: 75 - stakeholder: 75 - sustainable development: 74 - uncertainty: 73 - leakage: 72 - consultation: 72 - monitoring plan: 71 - start date: 70 - safeguard: 70 - risk management: 69 - eligibility: 69
Other topics appear in 60 to 65 texts: project area, reversal, land tenure, climate change adaptation, general description and environmental impact.
The least common were commercially sensitive information (11), normative framework (10), sectoral scope (22), reference region (24) and leakage area (27).
How to read those numbers
- The count is of keyword hits, not of formal sections. A text can discuss leakage without a section titled leakage. - The notes give a working rule: a draft missing a section that 70 or more of 97 PDDs contain is suspect without a written reason. A section that 27 or fewer contain may depend on project type. - Low counts for normative framework and sectoral scope likely reflect texts that state this in a table or a short paragraph, not under a heading. The notes do not say, so treat that as a guess. - Sections 6 and 7 split by sector. A solar or waste project will have no AFOLU specifics.
Practical points
- Start from the 23-section outline and keep the order. Verifiers know it. - Do not delete a section because it does not apply. State that it does not apply and say why. - Fill the common sections first: baseline, additionality, quantification, uncertainty, leakage, monitoring. - Add a normative framework table early. It sets the standard version, methodology version and tools, and it keeps the rest consistent. - Check the current official template. A PDD in our set uses a version dated February 2026 with the BCR Standard at version 4.0.
For how the programme compares with other registries in structure, see our post on the structural differences with Verra.
TREEO can map your data to the template and flag gaps before you write.
Move beyond estimates
Verifiers test sampling design, uncertainty and whether a number traces back to the field. TREEO dMRV captures that evidence in real time, in one auditable chain.



