The Cevizlik Run-Of-River Hydroelectric Power Plant
Score Breakdown
Integrity
verified The validation/verification record confirms additionality using an investment test and reports no material findings or corrective actions.
missing Baseline is project-specific and the timing of any baseline reassessment is not stated; leakage treatment is inconsistent across documents.
Transparency
verified A recent monitoring report (2023-12-27) provides a defined monitoring period (2020-05-29 to 2023-06-30) and the claimed and verified ERs match in the extracted record (414,078).
missing Key figures vary across documents (grid emission factor and ER totals), reducing MRV clarity and comparability.
Claim Safety
verified The project is explicitly not CORSIA-eligible, lowering aviation-claim double-claiming risk.
missing Contradictory ER totals and inconsistent leakage justification increase over-crediting and greenwashing risk.
Documentation
verified A relatively complete document set is referenced (PDD, monitoring report, validation report, issuance) with high extraction confidence and 17 documents used.
missing Multiple internal inconsistencies across official documents indicate documentation control/versioning weaknesses.
Detailed Analysis
Integrity
The validation/verification record confirms additionality via an investment test, and the extracted record shows no material findings and no corrective actions required (validation/verification documentation referenced in the merged record). The baseline approach is project-specific under ACM0002, and the timing of any baseline reassessment is not stated in the available documents, which weakens baseline robustness. Leakage is applied as a 0% deduction, but the monitoring report (2023-12-27) does not address leakage justification, creating uncertainty about whether leakage was appropriately assessed.
Transparency
The monitoring report dated 2023-12-27 clearly states the monitoring period (2020-05-29 to 2023-06-30) and the extracted record shows the same total ERs claimed and verified (414,078), which supports MRV consistency within that document set. However, transparency is reduced by cross-document discrepancies in key parameters, including the grid emission factor and ER totals between validation/monitoring records. The VVB is identified (Rüzgar Danışmanlık), but the conflicting values suggest version control issues that make it harder for third parties to reconcile the public record.
Claim Safety
The project is marked as not CORSIA-eligible, which reduces the risk of high-impact aviation-related claims. Over-crediting risk remains moderate because the ER totals differ across validation reports (335,015 vs 414,078) and because leakage justification is inconsistent (monitoring report says it is not addressed while a validation report says it was quantified). The baseline is project-specific and the baseline reassessment timing is not stated, which further increases uncertainty around the conservativeness of credited reductions.
Documentation
The extracted record references a broad evidence set (PDD, monitoring report, validation report, issuance) and indicates 17 documents were used with high extraction confidence, supporting a relatively strong documentation score. Nonetheless, multiple contradictions across official documents (including crediting period, safeguards, and key quantification parameters) indicate weaknesses in document consistency and traceability. No corrective actions are listed in the extracted record, but the inconsistencies themselves warrant caution.
Overall
Overall quality is moderate, driven by VVB-confirmed additionality and a recent monitoring period with matching claimed vs verified ERs in the latest extracted record. Contradictions materially reduce confidence: for ER totals (335,015 in the 2022-12-05 validation report vs 414,078 in the 2023-12-27 validation report), the more recent 2023-12-27 figure is privileged as it likely reflects the latest determination, but the discrepancy still signals reliability risk and lowers scores. For leakage justification, the monitoring report (2023-12-27) stating leakage is not addressed is privileged over the validation report claim of quantification because monitoring should evidence what was actually assessed/applied during MRV; this inconsistency reduces integrity and claim safety. For safeguards/FPIC/grievance/benefit sharing, the more recent 2023-12-27 monitoring report is privileged over the 2012-10-18 monitoring report, but the reversal in statements suggests evolving or inconsistently documented safeguards. For the grid emission factor (0.559 in the 2022-12-05 validation report vs 0.492925 in the 2023-12-27 monitoring report), the monitoring-period-specific value is privileged as more likely aligned to the credited period, but the difference increases over-crediting uncertainty. For the crediting period (2010–2020 vs 2020–2030), the 2023-12-27 monitoring report is privileged as the latest, yet the conflict raises concerns about correct period alignment and is scored as a documentation/transparency weakness. (Gate rules note: integrity is above 4.0 and documentation is above 3.0, so no deterministic caps would be triggered.)
Audit Analysis
This VCS run-of-river hydro project shows moderate integrity: additionality is confirmed by the VVB via an investment test and the latest monitoring/verification record reports no material findings. However, baseline and leakage treatment are weakly evidenced, and multiple cross-document inconsistencies (ERR totals, grid emission factor, crediting period, and safeguards) reduce confidence in the underlying data quality.
Project Description
The Cevizlik Hydroelectric Project in Turkey's Eastern Blacksea Region is a Greenfield 93 MW run-of-river hydroelectric power plant constructed underground, utilizing the 230 m of head between the tailwater level of the upstream existing Ikizdere HEPP and the Kalkandere HEPP project. It generates approximately 335 GWh/year of renewable energy, reducing greenhouse gas emissions by an estimated 187.471 tonnes of CO2e annually.
Red Flags
- Conflicting ERR totals across validation reports (335,015 vs 414,078) create over-crediting and data reliability risk.
- Leakage is taken as 0% while the monitoring report does not address leakage justification, conflicting with a validation report that says leakage was quantified.
- Crediting period is inconsistent across monitoring reports (2010–2020 vs 2020–2030), raising concerns about period alignment and issuance basis.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2010 | 199,710 | 199,108 | 602 | |
| 2011 | 228,735 | 152,689 | 76,046 | |
| 2012 | 49,714 | 49,714 | 0 | |
| 2013 | 147,779 | 147,779 | 0 | |
| 2014 | 140,709 | 140,709 | 0 | |
| 2015 | 154,487 | 123,781 | 30,706 | |
| 2016 | 168,635 | 0 | 168,635 | |
| 2017 | 159,774 | 0 | 159,774 | |
| 2018 | 162,910 | 0 | 162,910 | |
| 2019 | 135,446 | 0 | 135,446 | |
| 2020 | 137,467 | 0 | 137,467 | |
| 2021 | 106,602 | 0 | 106,602 | |
| 2022 | 140,675 | 0 | 140,675 | |
| 2023 | 94,936 | 0 | 94,936 | |
| Total | 2,027,579 | 813,780 | 1,213,799 |
Cosa migliorerebbe questo punteggio
- Publish a clear reconciliation note (or updated verification/issuance statement) explaining the change in ER totals (335,015 vs 414,078) and which figure was ultimately issued for which monitoring period.
- Provide explicit leakage assessment text consistent across validation and monitoring reports (even if leakage is negligible) and cite the applicable ACM0002 leakage provisions used.
- Clarify and standardize the crediting period across all public documents and registry entries, including any renewal/transition rationale and the exact periods covered by each monitoring report.
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 reported
0% leakage with inconsistent justification
Project-specific baseline; reassessment timing unclear
Safeguards reported recently but inconsistent historically
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 →