Myanmar Stoves Campaign - Soneva in Myanmar - VPA No. 019
Score Breakdown
Integrity
verified Additionality was tested using a combined approach and was confirmed by SustainCERT in the verification report.
missing The baseline is project-specific rather than a more robust standardized or jurisdictional baseline, and reversal risk is not clearly addressed because reversal events are marked as not addressed.
Transparency
verified The monitoring period, VVB name, usage monitoring method, and verified usage rate are stated in the verification report.
missing Total emissions reductions claimed versus verified are not found in the extracted record, and the extraction confidence is low, which weakens documentation clarity.
Claim Safety
verified The verification report reports a quantified leakage treatment with a 0% deduction, and the verified usage rate of 95.45% is close to the assumed 100%.
missing The project uses a project-specific baseline and the record contains a crediting-period contradiction between the verification and validation documents, which raises over-crediting and record-consistency concerns.
Documentation
verified Twenty documents were used, and the record includes a verification report, validation report, monitoring report, and stakeholder consultation material.
missing Extraction confidence is low, and the crediting period contradiction suggests the documentation set is not fully consistent across sources.
Detailed Analysis
Integrity
The verification report from SustainCERT confirms additionality using a combined test, which is a meaningful positive signal. No material findings or corrective actions were reported, and the report also states a quantified leakage treatment with a 0% deduction. On the weaker side, the baseline is project-specific, baseline reassessment timing is only partially clear, and reversal events are marked as not addressed, so permanence and baseline robustness are not fully strong.
Transparency
The verification report provides the VVB name, monitoring period, usage monitoring method, and a verified usage rate of 95.45%, which supports traceability. The record does not include total emissions reductions claimed versus verified, so it is not possible to check consistency on the core issuance figures from the extracted data. Because the extraction confidence is low, the transparency score is reduced further.
Claim Safety
Claim safety is helped by the verified usage rate being close to the assumed 100% and by the verification report’s quantified leakage treatment. However, the baseline remains project-specific rather than standardized, which is weaker for over-crediting control. The contradiction on the crediting period between the verification and validation documents also creates a reliability concern, so I privileged the later verification report because it is more recent and appears to reflect the final audited position.
Documentation
The record includes multiple document types, including validation, verification, monitoring, and stakeholder consultation materials, which is a positive sign for completeness. FPIC, grievance mechanism, and benefit-sharing are all mentioned, supporting a reasonably documented safeguards package. Still, the extraction confidence is low, and the conflicting crediting-period entries show that the documentation set is not fully clean or internally consistent.
Overall
Overall, this is a mid-quality project record with some strong positives, especially VVB-confirmed additionality and no reported material findings. I privileged the verification report over the earlier validation report for the leakage treatment because it is later and more specific, but I still penalized the score because the contradiction shows the record is not fully reliable. I also privileged the verification report’s crediting-period framing over the validation report’s different range for the same reason, while noting that the inconsistency itself lowers confidence.
Audit Analysis
This project has some solid quality signals: the VVB confirmed additionality, no material findings were reported, and safeguards such as FPIC and a grievance mechanism are documented. However, there are reliability concerns around document quality, a project-specific baseline, and a contradiction on the crediting period that reduces confidence in the record.
Project Description
Developer: Soneva Foundation Type: Energy Efficiency - Domestic Size: Micro scale Methodology: GS MS Simplified Methodology for Efficient Cookstoves v1. Crediting period: 2021-10-30 → 2026-10-29 Estimated annual credits: 10000 tCO2e SDGs: Goal 7: Affordable and Clean Energy, Goal 3: Good Health and Well-Being, Goal 13: Climate Action
Red Flags
- The crediting period differs between documents, with the verification record aligning to one range and the validation record showing a different range.
- Leakage treatment was described as quantified in the verification report, but the earlier validation report said leakage was not addressed.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2021 | 1,601 | 0 | 1,601 | |
| 2022 | 7,677 | 0 | 7,677 | |
| Total | 9,278 | 0 | 9,278 |
Cosa migliorerebbe questo punteggio
- Provide a fully reconciled issuance and crediting timeline across validation, monitoring, and verification documents.
- Publish a clearer baseline and permanence rationale, including explicit treatment of reversal risk and any buffer or equivalent safeguard.
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 combined test
reversal risk not clearly addressed
quantified 0% deduction
project-specific baseline
FPIC and grievance mechanism documented
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 →