Happy Meal To Go

Integrity

The validation documentation indicates additionality was assessed and confirmed by the VVB (CIRCODU), which supports additionality robustness. However, the baseline method is not found in the extracted record, and the baseline reassessment timing is also not stated, weakening confidence in baseline validity. Leakage handling is inconsistent across monitoring reports (one states leakage was quantified, another indicates it was not addressed), which raises integrity risk for a cookstove activity where leakage can be material. No material findings or corrective actions are reported, which is positive, but the scale of cross-document ERR inconsistencies suggests underlying quantification or version-control problems.

Transparency

The monitoring report clearly defines the monitoring period (2017-10-01 to 2018-09-30) and describes usage monitoring via annual surveys, with a verified usage rate of 81.25%. The VVB is identified (CIRCODU), and the document set is relatively complete (PDD, monitoring, validation among 14 documents). However, transparency is reduced by the inability to reconcile claimed and verified emissions reductions across different versions of validation documentation. Missing extracted details on baseline method and leakage deduction also limit third-party reproducibility from the extracted record.

Claim Safety

Over-crediting risk is elevated because the extracted record shows major inconsistencies in emissions reduction numbers across validation reports, and leakage treatment is not consistently described across monitoring reports. The project applies a national default fraction of non-renewable biomass of 0.88, which is at least a defined parameter choice, but without the baseline method and leakage deduction clearly captured, it is hard to judge conservativeness. CORSIA eligibility and CCP status are not stated in the extracted record, so buyers cannot easily assess alignment with higher-integrity claim frameworks. Overall, the combination of missing quantification details and contradictory ERR figures increases greenwashing risk for end-user claims.

Documentation

Documentation coverage appears strong: 14 documents were used, including a PDD, monitoring report, and validation report, and extraction confidence is high. The monitoring report is relatively recent (2019-09-23), and it reports no material findings and no corrective actions required. Nonetheless, several key quantification fields are not found in the extracted record (baseline method, leakage deduction percentage, buffer pool percentage), which limits completeness. The presence of multiple contradictory values across documents suggests versioning or document-control weaknesses despite the overall document volume.

Overall

Overall quality is moderate, supported by VVB-confirmed additionality and documented safeguards (FPIC and a grievance mechanism), but weakened by significant internal inconsistencies. For the verified emissions reductions, I privilege the more recent validation report value (2,087,069 from 2019-09-24) over the older validation report value (729,309 from 2017-07-13) because later documents typically reflect updated verification/issuance context; however, the magnitude of the discrepancy materially reduces confidence and lowers scores. For leakage justification, I privilege the later monitoring report (2019-09-23) stating leakage was quantified over the earlier monitoring report (2017-07-13) stating it was not addressed, again due to recency, but the contradiction signals reliability risk. For additionality test type, I privilege the later validation report describing a barrier test (2015-11-23) over the older investment test (2009-03-24), but the shift suggests evolving narratives. For claimed ERR and crediting period, I privilege the later documents (2019 validation/monitoring) over earlier ones, yet these inconsistencies collectively indicate elevated uncertainty and potential over-crediting risk.