How to Write a PDD and Pass Validation and Verification

Who this page is for. Project developers and sponsors who need a PDD that clears validation and sets up fast verification and issuance. Not legal or tax advice. All steps depend on rights, host country rules, and program requirements.

How to Write a PDD and Pass Validation and Verification

Your PDD is an audit document. Treat it like a case file. State what you will do, show the evidence, keep traceable data, and map every claim to a method clause. Do this and validators close findings quickly and verifiers issue on schedule.

Standards: Verra VCS, Gold Standard, ART where relevant Project types: AFOLU, cookstoves, biochar, methane Outputs: PDD draft, MRV and sampling plans, audit pack

1) The Audit Logic of a PDD

  • Traceability: every statement links to a source file or dataset.
  • Reproducibility: a second analyst can repeat your steps and get the same numbers.
  • Completeness: the PDD covers all method clauses with page indexed evidence.
  • Consistency: tables, figures, and appendices match across the document.

2) PDD Structure Mapped to the Method

PDD section What to include Evidence
Project description and boundary Objective, activities, coordinates, area, start date rules GIS files, maps, photos, permits
Eligibility and additionality Method eligibility tests, barriers or investment test, start date compliance Financial model extracts, policy scans, board minutes
Baseline Approach, data sources, assumptions, calculations Remote sensing sources, surveys, scripts, raw data
Project scenario Activity model, adoption rates, survival or performance assumptions Pilot data, literature, device specs, field logs
Leakage Drivers, displacement routes, quant approach Transport and market data, maps, studies
Permanence and risk Risk assessment and buffers, prevention and response plan Fire and drought records, patrol plans, insurance options
MRV and sampling Strata, frames, plots, devices, QA QC, data schema Sampling calculator, SOPs, calibration logs
Safeguards and FPIC Stakeholders, consent process, grievance channel Attendance sheets, minutes, photos, signed forms
Emission reductions and removals Formulas, parameters, uncertainty, results Spreadsheet with version control, parameter table
Monitoring plan What, who, when, how, and data storage Calendar, role matrix, database screenshots

3) Build the Evidence Pack and Data Room

  • Folder tree by PDD section and method clause.
  • File naming with version and date. No duplicates.
  • Data dictionary that defines each field, unit, and source.
  • Audit sheet that maps PDD pages to file paths.

4) MRV and Sampling Plans That Pass

  • State the population, strata, frames, and expected variance.
  • Show sample size calculation with formulas and inputs.
  • Define plot layout, devices, calibration, and handling of outliers.
  • Write SOPs for fieldwork, data entry, QA, and backups.
  • Lock a monitoring calendar that aligns with validation and first verification.

5) Validation Plan and Timeline

Phase Weeks What happens
RFP and VVB selection 2 to 3 Scope, sites, language, logistics, data access, conflicts check
Desk review 2 to 4 VVB sends findings list. You respond with references and files
Site visit 1 Interviews, spot checks, plot checks, community meetings
Findings close out 1 to 3 Address CARs and CLs with proof and page numbers
Validation report Registry queue Respond to registry queries fast with one point of contact

6) Common Non Conformities and How to Fix Them

Finding Cause Fix
Tables do not match appendices Multiple authors and poor version control Single source spreadsheet with locked parameters and change log
Additionality not proven Weak barriers or missing investment test trail Add board minutes, lender emails, and cost curves that show the gap
Sampling plan unclear No variance estimates or stratum logic Provide calculator, list assumptions, and show sensitivity
Baseline sources not reproducible Broken links and undocumented processing Archive sources, store hashes, and document processing steps
FPIC evidence thin No attendance sheets or clear grievance path Upload signed minutes, photo logs, and grievance register

7) Prepare for the Site Visit

  • Logistics and permits for the audit team and translators.
  • Interview schedule with named roles and documents on hand.
  • Plot list with coordinates and access plans.
  • Community meetings confirmed with local leaders.
  • Data room open with read access and a help desk contact.

8) First Verification and Issuance Readiness

  • Collect monitoring data per SOP and lock the cut off date.
  • Run calculations from the same spreadsheet used for validation.
  • Prepare an issuance request pack that cites sections and files.
  • Control serial numbers and prepare transfer or retirement plans.

9) Document Checklist

Bucket Documents
PDD core Full PDD, parameter table, figures list, references, appendices
Evidence Rights pack, baseline sources, surveys, device logs, calibration, photos
MRV Sampling calculator, SOPs, data dictionary, QA QC plan, monitoring calendar
Community Stakeholder map, FPIC records, grievance register, benefit sharing terms
Audit VVB contract, site agenda, findings log, responses with page references

10) Pitfalls to Avoid

  • Writing first and gathering evidence later.
  • Changing parameters mid draft without a log.
  • Using screenshots as the only proof for data sources.
  • Letting the model and the PDD drift apart.
  • Leaving FPIC to the end.

Need a PDD that clears validation and a plan for first verification and issuance

Request a Proposal Book a Consultation

Disclaimers

  • We advise and arrange. We are not your lawyer or tax advisor.
  • Standards and policies change. Final steps depend on diligence and documentation.
  • Host country approvals and Article 6 processes vary by jurisdiction.