A weathered two-storey wooden building painted pale green and teal with an upper balcony, a red pickup truck with a roof rack parked in front on grass, trees behind in soft evening light.
← Back to blog

Anatomy of a CDM Validation Report: What an Auditor Actually Wrote

Sustainability•18 November 2026•TREEO Indonesia•5 min read

When a project asks to be registered under the Clean Development Mechanism, an independent auditor has to write down why it agrees. That document is the validation report. It is long, dry and more useful than most people expect. This post walks through the structure of one report for an afforestation and reforestation project, so you know what each part is for.

What validation is

The report opens by defining the task. Validation is an independent assessment by a third party, a Designated Operational Entity, of a proposed project against the criteria for CDM registration. Its result is a conclusion on whether the project is valid and should be submitted for registration. The report is clear that the final decision on registration belongs to the CDM Executive Board and the parties involved, not to the auditor.

It also states what validation is not. It is not consulting for the project participant. Requests for clarification and corrective action may help improve the design, but the auditor is not there to design the project. For the role of these entities, see our post on designated operational entities.

The report at a glance

PartWhat it covers
1 IntroductionObjective and scope
2 MethodologyAssessment team, document review, interviews, cross-check, resolving requests, internal quality control
3 SummaryFindings per topic, from approval to environmental and socio-economic impacts
4 CommentsStakeholder comments received and the auditor's response
5 Validation opinionThe conclusion
Annex 1Validation protocol, a requirement checklist
Annex 2List of documents and proofs reviewed
Annex 3Appointment certificates of the team

The scope list

The scope is a useful checklist of what the auditor tests against. In the report it includes the Kyoto Protocol article on the CDM, the relevant decisions of the meetings of the Parties, guidance of the Executive Board, the PDD form guidelines, the approved baseline and monitoring methodology, management systems and auditing methods, and the environmental and social aspects of the activity. If your PDD cites none of these, the auditor will.

Part 2: how the work was done

Part 2 reads like an audit programme. The steps, in order:

- Team appointment. The auditor staffs a team under its own appointment rules, with an assessment team leader, validators, a technical reviewer and sometimes experts. The report includes a table showing how the team covers sectoral scope, technical area, financial aspects and host country experience. - Document review. The auditor reviews the PDD submitted for the stakeholder consultation and the background documents, and cross-checks information against other sources where available. - Follow-up interviews and site visit. In the report, interviews and a physical site inspection took place in a one-week window. The interviewee list covers the project operators, the managers of the participating company and the funding side. In addition, 60 landowners with parcels in the project area were interviewed. - Cross-check. The documentation is compared with similar projects and with the approved methodology, to test formulae and calculations. - Resolution of requests. Clarification Requests (CRs) and Corrective Action Requests (CARs) are resolved through exchange with the participant. The detail is kept in the protocol annex. - Internal quality control. The head of the certification body, or a deputy, approves the final documents. If the head sits on the team, the deputy approves instead.

The report notes that the final PDD, submitted in February 2011, was the basis of the final assessment. The PDD the auditor first saw was version 01 from February 2009. The final one was version 06. That gap is a fair picture of how much a design can change during validation.

Part 4: the 45-day consultation

The report explains that once the auditor receives the PDD, it is made public on the UNFCCC site and on the auditor's own site, starting a 45-day global stakeholder consultation. If the project design changes in a significant way, this consultation may need to be repeated.

Part 4 records each comment and the auditor's response. In the example, one commenter asked for GPS coordinates of each parcel in the PDD and for livestock displacement to be discussed under leakage. The auditor answered with a pointer to the overview map, the GIS files uploaded with the PDD, and the leakage section of both the PDD and its own report. A comment is not a rejection, but it does force a written reply.

The opinion and the protocol

The opinion is short. In the report it says that the evidence is sufficient to determine fulfilment of the criteria in the protocol, that the project meets the relevant UNFCCC requirements if the underlying assumptions do not change, and that the auditor recommends it for registration. It adds that the removals are additional to those that would occur without the project, and that the project is likely to achieve its estimated removals if implemented as designed. It is signed by the head of the certification body and the team leader.

The protocol in Annex 1 is where the real work is visible. It follows the PDD section by section, A to H. Each checklist question has a reference, the auditor's comments, and a conclusion column that shows the draft finding and the final one. Examples in the report include a check that the version number and date of the PDD are consistent, a check that the approach to non-permanence is specified, and a CAR asking the participants to correct figures after a change in project area. A further CAR asked for a document confirming that no official development assistance from an Annex I country was involved in the project.

What to take from it

- Read the protocol before the summary. It shows exactly where a design was challenged. - Expect the PDD to change between the first and final versions. - Prepare answers on leakage, land eligibility and funding early. These produced requests in the example. - Keep a clean document list. Annex 2 is the auditor's index of your evidence.

TREEO can help you build the evidence index and answer log before an audit starts.

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.

Related Articles