GS1247 VPA 129 Zoba Anseba Community Safe Water
Score Breakdown
Integrity
verified Additionality was confirmed by the VVB, and the baseline was reassessed in 2024.
missing Leakage justification is not addressed, and reversal treatment is only a generic no-extreme-event statement with no buffer pool information found.
Transparency
verified The monitoring period is clearly stated as 2023-01-01 to 2024-12-31, and the VVB is named.
missing Total ERs claimed and verified are not found in the extracted record, and extraction confidence is low.
Claim Safety
verified The verified and assumed usage rates are both reported at 95, which at least suggests internal consistency within the latest record.
missing The FNRB value of 0.85 conflicts with an earlier national-default value in the contradiction log, and leakage is not well justified.
Documentation
verified The record includes many source documents, with 31 documents used, and it notes FPIC, grievance, and benefit-sharing information.
missing Extraction confidence is low, and several corrective actions and forward actions indicate unresolved monitoring and evidence gaps.
Detailed Analysis
Integrity
The project benefits from VVB-confirmed additionality and a baseline that was reassessed in 2024, which supports the core project design. Still, leakage is weak because the extracted record shows a 0% deduction while the justification is not addressed, and no buffer pool percentage was found. Reversal risk is also only lightly handled: the validation report says no extreme event caused reversal, but there is no stronger permanence mechanism documented.
Transparency
The monitoring period is clearly stated and the VVB is identified as Earthood Services Limited, which helps traceability. However, total ERs claimed and verified are not found in the extracted record, limiting public accounting clarity. The low extraction confidence further reduces confidence that the documentation is complete and readable.
Claim Safety
Claim safety is weakened by the lack of a clear leakage rationale and by contradictions in the record. The contradiction log shows different FNRB values across documents, and the latest extracted value of 0.85 is not clearly reconciled against the earlier national-default figure. The usage rate is reported as 95 in the latest record, but the presence of multiple conflicting versions of key assumptions raises over-crediting risk.
Documentation
The file set is fairly broad, with 31 documents used, and it includes safeguards, FPIC, grievance, and benefit-sharing references. Even so, the extraction confidence is low, which suggests at least one key document was hard to read. The validation report also lists several closed CARs and FARs, showing that the project required multiple rounds of clarification and follow-up evidence.
Overall
I privileged the most recent validation report for reversal treatment, leakage wording, benefit sharing, and the current crediting period because it is the latest dated source in the record. I also privileged the latest FNRB and usage-rate values where the contradiction log showed older alternatives, but the presence of these contradictions still lowers reliability and the scores. The record is not strong enough for a high-confidence assessment because several core items are either not addressed or conflict across documents, including reversal events, FNRB, leakage justification, usage rates, and the crediting period.
Audit Analysis
The project has some positive signs, including VVB-confirmed additionality, FPIC, a grievance mechanism, and a recent baseline reassessment. However, several core risk items are weakly documented or not addressed, especially leakage justification, reversal treatment, and the reliability of key monitoring figures. The low extraction confidence and multiple document contradictions reduce confidence in the record.
Project Description
Developer: CO2balance UK ltd Type: Energy Efficiency - Domestic Size: Micro Scale Crediting period: 2020-02-18 → 2027-02-17 Estimated annual credits: 10000 tCO2e SDGs: Goal 13: Climate Action, Goal 3: Good Health and Well-Being, Goal 6: Clean Water and Sanitation
Red Flags
- Leakage is shown as a 0% deduction, but the justification is not addressed in the extracted documents.
- Key figures and project terms conflict across documents, including FNRB, usage rates, benefit sharing, and the crediting period.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2020 | 7,931 | 7,505 | 426 | |
| 2021 | 9,180 | 4,910 | 4,270 | |
| 2022 | 8,719 | 1,000 | 7,719 | |
| 2023 | 7,412 | 0 | 7,412 | |
| 2024 | 6,191 | 0 | 6,191 | |
| Total | 39,433 | 13,415 | 26,018 |
Cosa migliorerebbe questo punteggio
- Provide a clear, quantified leakage assessment and explain why the 0% deduction is justified.
- Publish reconciled monitoring tables for ERs, usage rates, FNRB, and the crediting period, with a document-by-document contradiction resolution.
Questi suggerimenti indicano quali prove pubbliche aggiuntive potrebbero migliorare il livello di confidenza di questa valutazione. Non garantiscono un punteggio futuro più alto.
Risk Indicators
VVB-confirmed additionality
no reversal event, weak permanence detail
0% deduction without justification
project baseline, reassessed in 2024
FPIC and grievance mechanism present
CORSIA/CCP status not stated
Where to buy
+ Know where to buy this?
Listing multiple projects? Send us a CSV at [email protected].
⚑ Dispute this rating
Registry Documents
monitoring
pdd
registry_page
validation
- CO2b User Numbers Deviation-Request-Form v1_Final decision.pdf
- Final-Verification-Report-GS5951-55-MP5-GS6041-42-MP3-POA-GS1247(7).pdf
- (1)GS5951-55_GS6041-42_MR_MP3-MP1_v6 CLEAN.pdf
- GS1247_PoA-DD Clean_CP2_Improved Kitchen_19-02-2025.pdf
- GS1247_Internal_Validation_PoA_13062013_final.pdf
- DEV_255 (1).pdf
- +8 more
Sei il proprietario di questo progetto?
Correzione metadati (gratuita)
Nome, paese, marketplace o link errati? Segnalacelo.
Non modifica lo score.
[email protected] →Rivalutazione con nuovi documenti
Hai documentazione aggiornata non ancora inclusa? Puoi richiedere un nuovo run della pipeline con i nuovi input.
Invia Documenti →