SAFE WATER PROJECT IN RWANDA V

Integrity

The verification report confirms additionality was checked by the VVB, which supports the project’s core environmental claim. Leakage is treated with a quantified deduction of 0%, but the report also says findings were not closed and lists several corrective actions, including inconsistencies between baseline survey forms and the SDG calculation sheet. The baseline method is project-specific, and reversal events are not addressed, so permanence and baseline robustness are only moderate.

Transparency

The record identifies the VVB, the monitoring period, and the annual survey method for usage monitoring, which helps traceability. However, total ERs claimed and verified are not stated in the extracted record, and the extraction confidence is only medium because at least one key document was poorly readable. The documentation set is broader than a single report, but the missing quantitative issuance figures limit transparency.

Claim Safety

The project is an avoidance activity with a quantified leakage treatment, which is better than an unaddressed leakage case. Still, the project is marked CORSIA-eligible, while CCP status is not stated, so dual-market claim risk is not fully resolved. The contradictions on usage rates, FNRB presentation, and the crediting period also weaken confidence that the claimed reductions are fully conservative.

Documentation

The evidence base includes validation, monitoring, PDD, and verification documents, and safeguards such as FPIC, a grievance mechanism, and benefit sharing are explicitly mentioned. Even so, several key fields are not stated in available documents, and the verification report records unresolved findings and multiple corrective actions. The medium extraction confidence further suggests that the documentation package is usable but not fully robust.

Overall

I privileged the most recent verification report for leakage treatment, usage rate verification, and the unresolved findings because it is the latest and most specific source. Where contradictions exist, I treated them as reliability issues rather than resolving them in favor of the project: usage rate assumptions differ across documents, leakage justification shifts from deemed negligible to quantified, FNRB is presented differently across reports, and the crediting period is inconsistent. These discrepancies, together with open findings and missing issuance data, keep the project in a mid-range quality band rather than a strong one.