Himalayan Rocket Stove Project in India
Score Breakdown
Integrity
verified Additionality was confirmed by the VVB in the validation record, which supports the project’s core eligibility case.
missing The baseline is project-specific rather than a more robust standardized or jurisdictional baseline, and the FNRB evidence is internally inconsistent across documents.
Transparency
verified The monitoring report provides a named VVB, a defined monitoring period, a quantified leakage deduction, and a stated usage monitoring method based on annual surveys.
missing Total ERR claimed and verified are not stated in the extracted record, and the low extraction confidence reduces trust in the completeness of the public documentation.
Claim Safety
verified The monitoring report states a leakage deduction of 5% and no reversal events were reported, which helps reduce over-crediting risk.
missing The project relies on a project-specific baseline and the FNRB inputs conflict between a local field value of 90 and a national default of 30, which weakens claim robustness.
Documentation
verified Multiple official documents were used, including a monitoring report, validation report, and PDD, and several corrective actions were closed.
missing The extraction confidence is low, one document source is unidentified, and key fields such as total ERR figures and buffer pool coverage were not found in the available record.
Detailed Analysis
Integrity
The validation record confirms additionality by the VVB, which is a meaningful positive signal. The monitoring report also reports a quantified leakage deduction of 5% and no reversal events, supporting permanence and leakage treatment. On the other hand, the baseline is project-specific, and the FNRB inputs are inconsistent across documents, which reduces confidence in the robustness of the crediting logic.
Transparency
The monitoring report identifies EcoLance Pvt. Ltd. as the VVB, gives a monitoring period from 2023-03-01 to 2024-07-04, and describes annual survey-based usage monitoring. However, the extracted record does not state total ERR claimed or verified, and the low extraction confidence suggests at least one key document was difficult to read. That combination limits transparency even though the reporting structure is reasonably detailed.
Claim Safety
Claim safety is helped by the stated 5% leakage deduction, the reported 75% usage rate, and the absence of reported reversal events. Still, the project uses a project-specific baseline and the FNRB evidence conflicts between the monitoring report and validation report, with 90 from local field work versus 30 from a national default. Those contradictions increase the risk of over-crediting or overstated climate benefit.
Documentation
The evidence set includes a monitoring report, validation report, and PDD, and several corrective actions were closed, which is a positive sign that issues were at least addressed. But the extraction confidence is low, one source is unidentified, and important items such as total ERR figures and buffer pool coverage were not found in the available record. The crediting period also conflicts across documents, which further weakens documentation quality.
Overall
I privileged the more recent monitoring report for operational details such as the 75% usage rate, the local-field FNRB method, and the 5% leakage deduction because it is later and more specific to the monitored period. I did not fully privilege it on crediting-period scope because the monitoring report’s period appears to conflict with the validation report’s later crediting window, so that discrepancy remains unresolved and lowers confidence. Overall, the project looks plausible but not high-confidence due to the FNRB and crediting-period contradictions, the project-specific baseline, and the low extraction confidence.
Audit Analysis
The project has some positive integrity signals, including VVB-confirmed additionality, a quantified leakage deduction, and no reported reversal events. However, the record contains important inconsistencies on FNRB, usage assumptions, and the crediting period, and the extraction confidence is low, which weakens confidence in the documentation and claim safety.
Project Description
Developer: South Pole Ltd SCV Type: Energy Efficiency - Public Sector Size: Large Scale Crediting period: 2019-07-05 → 2029-07-04 Estimated annual credits: 196195 tCO2e SDGs: Goal 3: Good Health and Well-Being, Goal 7: Affordable and Clean Energy, Goal 13: Climate Action
Red Flags
- The FNRB value and method conflict across documents, with the monitoring report using a local field value of 90 while the validation report cited a national default of 30.
- The crediting period differs between documents, and the monitoring report appears to show an earlier period than the validation report, creating uncertainty about which issuance window applies.
- Low extraction confidence and several closed corrective actions indicate the documentation set is not fully clean or easy to verify.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2021 | 1,467 | 1,467 | 0 | |
| 2022 | 10,680 | 10,680 | 0 | |
| 2023 | 30,065 | 12,727 | 17,338 | |
| 2024 | 18,693 | 397 | 18,296 | |
| Total | 60,905 | 25,271 | 35,634 |
Cosa migliorerebbe questo punteggio
- Publish a reconciled statement explaining the FNRB discrepancy and clearly justify which value applies for issuance.
- Provide a clean, cross-referenced schedule of total ERR claimed and verified, along with the correct crediting period and registry status.
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 reversals reported
5% leakage deduction stated
Project-specific baseline
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
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 →