Getting a project through validation can easily take several rounds of feedback and months of work. After analysing hundreds of projects and validation reports with our proprietary AI engine, we've identified the most frequent issues that slow developers down.
In short, most issues fall into five recurring categories: inconsistent documentation, weak baselines, flawed GHG accounting, missing evidence, and non-compliant monitoring or social safeguards.
Here's a closer look at what typically goes wrong - and how to avoid it.
Systemic data inconsistencies and version discrepancies
This is by far the most common issue. Both project proponents and auditors often struggle to manage multiple document versions, data sources, analyses, and spreadsheets, each created and updated at different stages of the project cycle. It's therefore no surprise that key figures end up conflicting across documents (or even within the same one). Common errors are:
Conflicting project area: The total project area is cited with different values across the PDD, spreadsheets, and maps.
Inconsistent GHG estimates: The total estimated GHG emission reductions change between sections, or the PDD's headline number does not match the sum in the calculation spreadsheets.
Contradictory project details: Key project definitions, such as start dates, crediting periods, and even the project's scale (e.g., "grouped project" vs. not) are inconsistent.
Errors in baseline and contextual data
Defining the baseline is one of the most critical - and challenging - aspects of any carbon project. Auditors frequently find that projects oversimplify or misrepresent their baseline scenario, which can lead to inflated emission-reduction estimates. A robust baseline requires integrating data from multiple sources - project-area surveys, satellite imagery, government statistics, and peer-reviewed studies - and ensuring that all these inputs remain consistent and traceable over time.
Because these datasets often come from different origins and moments in time, discrepancies are common:
Baseline inconsistencies: Many PDDs fail to justify the baseline scenario with sufficient, up-to-date data. Baselines are often defined using generalized assumptions or outdated land-use data, without evidence from recent field assessments, satellite imagery, or government statistics.
Incorrect legal citations: PDDs reference outdated laws, misquote legal frameworks, or for example, incorrectly state the project is not covered by a jurisdictional REDD+ program when it is.
Environmental inaccuracies: Wrong IUCN Red List status for species, incorrect classification of invasiveness, or use of outdated ecological surveys.
Socio-economic errors: Using obsolete poverty lines, census data, or demographic indicators to support community context or additionality claims.
Flawed GHG accounting and parameter use
The core carbon accounting is one of the most frequent and consequential sources of error. Issues range from simple arithmetic mistakes to deeper methodological inconsistencies that can significantly distort emission-reduction estimates. Commonly detected issues are:
Incorrect parameters: Many projects apply scientific parameters that deviate from IPCC or methodology defaults - for example, using inaccurate root-to-shoot ratios, soil organic carbon fractions, or emission factors for N₂O and CH₄. Even small deviations can compound into major discrepancies across the crediting period.
Calculation and formula errors: Audits find arithmetic errors (e.g., "35x0,7=25"), broken formulas, mathematically incorrect allometric equations, and incorrect transcriptions of parameters from source literature.
Contradictory baseline definitions: The baseline scenario is described inconsistently, such as being "grasslands without any inputs" in one section and "used by locals for farming" in another.
Critical omissions and documentation gaps
Missing or incomplete documentation is one of the fastest ways for a project to stall during validation. Validators often find that mandatory sections or evidence are simply not there - or don't support the claims being made. For example:
Missing PDD sections: The Project Description Document simply fails to include sections required by the VCS template, such as socio-cultural information, community benefits, or land tenure details.
Lack of evidence: Projects make claims without providing the required proof, such as failing to provide evidence for stakeholder consultations, legal agreements, or technical reports supporting eligibility.
Improper evidence: A recurring procedural failure is the use of one document (like a legal deed of representation) as "evidence" for a technical claim it does not support.
Poor monitoring plans and social safeguards
Monitoring and community engagement plans are among the most frequently non-compliant sections in validation reviews. Weak designs or missing safeguards not only delay approval but can also jeopardize the project's long-term credibility. Main issues found here are:
Flawed monitoring design: Monitoring plans are not following the methodology, for instance by proposing to conduct the baseline usage survey after project implementation has already begun.
Non-compliant clauses: Plans include clauses that violate VCS rules, such as a "stop monitoring" clause that allows monitoring to cease once a confidence level is met, rather than continuing for the full crediting period.
Stakeholder engagement failures: Projects don't document stakeholder consultations or demonstrate that Free, Prior, and Informed Consent (FPIC) was obtained.
There's no question compliance automation has the potential to cut down project development timelines. Curious to see how your project might do? Generate a free validation report with Genvision.
