Salto Pilão Hydropower Plant Project Activity
Score Breakdown
Integrity
verified The validation/verification record indicates additionality was confirmed by the VVB using an investment test.
missing Numerous corrective actions in monitoring/verification materials (e.g., grid emission factor revisions, net generation corrections, metering inconsistencies) suggest elevated risk of baseline/MRV errors affecting credited volumes.
Transparency
verified Key project identifiers and MRV elements are present (VCS registry, methodology ACM0002 v20.0, VVB named, monitoring period stated).
missing Material contradictions in claimed/verified ERs and crediting period dates reduce confidence that public-facing numbers are consistently reported.
Claim Safety
verified The project is explicitly not CORSIA-eligible, reducing certain downstream double-claiming risks.
missing Over-crediting risk is elevated due to inconsistent ER totals and repeated corrections to emission factors and generation data.
Documentation
verified A relatively broad document set is referenced (monitoring report, validation report, PDD, issuance) with high extraction confidence and many documents used.
missing The record contains multiple internal inconsistencies across documents (ER totals, safeguards/FPIC/grievance statements, crediting period), indicating documentation quality/control issues.
Detailed Analysis
Integrity
The validation/verification record confirms additionality via an investment test, as reflected in the extracted data and VVB attribution (Earthood Services Private Limited). However, the monitoring/verification trail includes many corrective actions—such as revisions to grid emission factors, corrections to net electricity generation, and observed metering location inconsistencies during a site visit—indicating weaknesses in MRV implementation that can directly affect baseline emissions and credited ERs. Leakage is not robustly handled in the extracted record: no leakage deduction percentage is found, and later monitoring information indicates leakage was not addressed, which is conservative but signals incomplete integrity treatment.
Transparency
The extracted record provides core MRV descriptors (methodology ACM0002 version 20.0, monitoring period 2020-01-19 to 2021-10-31, VVB name, and a substantial set of evidence document types). Transparency is undermined by major inconsistencies in reported ER quantities across different documents and dates, and by conflicting crediting period statements across monitoring reports. The presence of many corrective actions also suggests that earlier public numbers may have been revised materially, making it harder for third parties to reconcile figures.
Claim Safety
The project is marked as not CORSIA-eligible, which reduces the risk of certain aviation-related double-claiming channels. Nonetheless, claim safety is weakened by the large spread between claimed and verified ER figures across documents and by repeated corrections to key inputs (grid emission factors and generation data) noted in corrective actions, both of which increase perceived over-crediting/greenwashing risk. Leakage treatment is inconsistent between validation and later monitoring records, adding uncertainty to the completeness of the credited impact claims.
Documentation
Documentation coverage is relatively strong in breadth (monitoring report, validation report, PDD, and issuance are all referenced; 27 documents used; extraction confidence is high). However, the internal consistency of the documentation set is poor: safeguards/FPIC/grievance and benefit-sharing statements vary across monitoring reports, and key quantitative outcomes (claimed/verified ERs) conflict across validation/monitoring sources. The volume and nature of corrective actions further indicate that document versions and calculations required repeated fixes, lowering confidence in document control and reliability.
Overall
Overall quality is constrained primarily by reliability issues: (1) for claimed ERs, the higher figure (1,980,116) from the later monitoring report dated 2019-07-03 conflicts with 235,542 from the 2012-06-26 monitoring report; I privilege the more recent monitoring report for recency but treat the contradiction as a major credibility hit because both are monitoring reports and the difference is very large. (2) For leakage, I privilege the 2022-12-02 monitoring report stating leakage was not addressed over the 2022-02-24 validation report deeming leakage negligible, because monitoring should reflect implemented MRV; this reduces integrity/claim safety. (3) For safeguards/grievance/benefit sharing/FPIC, I privilege the 2022-12-02 monitoring report (more recent) over the 2014-01-24 monitoring report, but the contradiction signals inconsistent social safeguards reporting. (4) For verified ERs, I privilege 229,534 from the 2022-12-02 document over 518,810 from 2022-02-24 due to recency, but the fact that two validation/verification-era documents disagree materially lowers confidence. (5) For the crediting period, I privilege 2020-01-19 to 2030-01-18 from the 2022-12-02 monitoring report over the 2010-01-19 to 2020-01-18 statement in the 2022-02-14 monitoring report, again due to recency, while penalizing for inconsistency.
Audit Analysis
The project has VVB-confirmed additionality via an investment test and uses an established grid-connected renewable methodology (ACM0002), but the extracted record shows major inconsistencies in reported and verified emission reductions across documents. Leakage treatment is unclear and frequently not evidenced, and numerous corrective actions point to recurring MRV and calculation weaknesses, increasing over-crediting risk.
Project Description
The Salto Pilão project in Brazil involved building a hydropower plant with a reservoir covering 0.15 km2 and generating 191.8 MW of power. The plant is located in the state of Santa Catarina and has been licensed for construction.
Red Flags
- Large contradictions in emission reduction figures across monitoring/validation documents (claimed and verified totals differ materially).
- Leakage is inconsistently treated (validation deems negligible, later monitoring record shows leakage not addressed) with no quantified deduction found.
- Extensive corrective actions (including grid emission factor revisions and metering inconsistencies) indicate MRV/calculation reliability issues.
- Crediting period dates conflict across monitoring reports, raising concerns about boundary/period consistency.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2011 | 235,542 | 150,909 | 84,633 | |
| 2012 | 312,509 | 303,484 | 9,025 | |
| 2013 | 413,653 | 413,653 | 0 | |
| 2014 | 508,895 | 498,607 | 10,288 | |
| 2015 | 534,441 | 533,645 | 796 | |
| 2016 | 487,181 | 218,970 | 268,211 | |
| 2017 | 242,920 | 35,132 | 207,788 | |
| 2018 | 5,000 | 4,412 | 588 | |
| 2020 | 9,105 | 5,259 | 3,846 | |
| 2021 | 13,898 | 8,084 | 5,814 | |
| Total | 2,763,144 | 2,172,155 | 590,989 |
Cosa migliorerebbe questo punteggio
- Publish a clear reconciliation table across document versions showing claimed vs verified ERs by monitoring period, with reasons for changes and final issued volumes.
- Provide explicit leakage assessment consistent across validation and monitoring (including justification and, where applicable, a quantified deduction).
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 investment test
Avoidance project; no reversals evidenced
Leakage not consistently addressed
Project-specific baseline; reassessment timing unclear
Safeguards/FPIC reporting inconsistent
Not CORSIA-eligible; CCP status not stated
Where to buy
Marketplaces
+ 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 →