*Bagepalli CDM Biogas Programme

Integrity

The project uses a project-specific baseline methodology (AMS.I.E ver.5) with a baseline reassessment in 2017 (verification report), which supports baseline validity. However, reversal treatment is weak: reversal events are recorded as not addressed in the merged record and no buffer pool percentage is provided, increasing permanence risk. Several corrective actions (CAR-01, CAR-02, CAR-03) were raised and some closed, which shows issues were found during verification (verification report 2019). Additionality is reported as a combined test but the extracted record does not state that the VVB explicitly confirmed additionality, creating uncertainty.

Transparency

A named VVB (Carbon Check India) and monitoring period (2020-09-01 — 2021-08-31) are provided and total ERR claimed equals the total ERR verified (11761), which is a transparency positive (verification report). The project has 18 documents and includes PDD, validation, verification and monitoring reports. However, the extracted record has medium extraction confidence and notable contradictions across documents (usage rates, fnrB, leakage deduction), reducing clarity and auditability.

Claim Safety

There is a material risk of over-crediting because key parameters conflict between documents: usage rate is recorded as 54.59 in the most recent monitoring report but 80.68 in an earlier verification report, and fnrB is reported as 0.95 in one verification and 0.85 in a monitoring report. CORSIA/CCP eligibility is not stated. While a leakage deduction of 5% is reported in a verification report (2017), earlier documents show 0%, demonstrating inconsistent treatment of leakage across time and documents.

Documentation

Documentation coverage is moderate: evidence includes PDD, validation, verification and monitoring reports and 18 documents were used. The latest verification report in the extracted record is dated 2019, and monitoring data for 2020–2021 are provided. However, min_extraction_confidence is medium and several corrective actions remain listed as required, and safeguards are inconsistently documented across reports, which reduces the documentation score.

Overall

I privileged the most recent, clearly dated documents where possible: for usage rate I relied on the monitoring report (2023 entry showing 54.59) over older verification figures because monitoring is the closest source to operational data; for fnrB I privileged the most recent monitoring report value (0.85) over an earlier verification value (0.95) because the monitoring report reflects post‑verification operational factors. For leakage deduction, I treated the 5% deduction reported in a 2017 verification report as more conservative than an earlier 0% figure but note the inconsistency across documents. These contradictions (usage, fnrB, leakage, safeguards, crediting period) lower confidence in the dataset and have been explicitly considered in scoring, reducing integrity and claim safety. Because integrity is above 4.0, the post‑scoring integrity gate is not triggered; documentation is above the threshold for the transparency cap. Overall score reflects moderate documentation and transparency but material reliability concerns from contradictions and unresolved reversal treatment.