Vai al contenuto principale
VCS avoidance Türkiye Registry: Registered Documentazione completa General Methodology v2.0

Otluca Hpps Run-Of-River Hydro Project

VCS-755 ↗

6.6 / 10
Integrity
6.2
Transparency
6.8
Claim Safety
6.4
Documentation
7.6

Score Breakdown

Integrity

verified Additionality is confirmed by the VVB using an investment test (validation/verification documentation referenced in the extracted record).

missing Leakage is deducted at 0% but the monitoring report (2023-03-10) does not address leakage justification.

Transparency

verified The monitoring report (2023-03-10) provides a clear monitoring period (2019-08-01 to 2022-05-31) and reports ERs that match claimed and verified totals (532,381).

missing Key baseline inputs are incomplete in the extracted record (e.g., grid EF year not stated), and several headline figures conflict across documents.

Claim Safety

verified The project is explicitly not CORSIA-eligible, reducing certain double-claim/eligibility marketing risks.

missing Contradictory ER totals and crediting-period dates increase over-crediting and misrepresentation risk for downstream claims.

Documentation

verified A relatively complete document set is referenced (PDD, monitoring report, validation report, issuance) with high extraction confidence and 18 documents used.

missing Multiple contradictions between older and newer documents indicate record-keeping/version-control weaknesses.

Detailed Analysis

Integrity

Additionality appears reasonably supported because the extracted record indicates an investment test and that additionality was confirmed by the VVB (Applus+). Baseline setting is project-specific under ACM0002 and the baseline was last reassessed in 2020, which is a positive sign but still less robust than a standardized/jurisdictional baseline. Leakage treatment is a weakness: the monitoring report (2023-03-10) does not address leakage justification while applying a 0% leakage deduction, which reduces confidence that all relevant effects were considered. No material findings or corrective actions are reported in the extracted record, which supports integrity but does not offset the leakage and inconsistency issues.

Transparency

The monitoring report (2023-03-10) specifies the monitoring period (2019-08-01 to 2022-05-31) and reports total emission reductions where claimed and verified totals match (532,381), supporting MRV clarity for that period. The VVB is named (LGAI Technological Center, S.A. (Applus+)), which helps trace assurance. However, some key parameters are not fully specified in the extracted record (e.g., the grid emission factor year is not stated), and multiple cross-document contradictions (ER totals, crediting period, safeguards) reduce transparency and user confidence in which version is authoritative.

Claim Safety

The project is explicitly not CORSIA-eligible, which lowers the risk of certain high-stakes aviation-related claims and reduces one pathway for double-claim concerns. Nonetheless, over-crediting/claim risk is elevated by inconsistencies in reported ER totals across validation documents and by conflicting crediting-period dates across monitoring reports, which can confuse what vintage/period the credits represent. Leakage is another claim-safety concern because a 0% deduction is applied while the monitoring report (2023-03-10) does not provide a leakage justification, making it harder for buyers to defend claims against scrutiny. CCP status is not stated in the extracted record, leaving an evidence gap on high-integrity label alignment.

Documentation

Documentation coverage is relatively strong: the extracted record references a PDD, monitoring report, validation report, and issuance, with 18 documents used and high extraction confidence. The monitoring report (2023-03-10) includes safeguards-related elements (FPIC conducted, grievance mechanism, benefit sharing described), which improves completeness for social risk documentation. However, repeated contradictions between older and newer documents (including safeguards presence and key quantitative figures) indicate version-control and consistency problems that reduce documentation reliability even when documents exist.

Overall

Overall performance is moderate: VVB-confirmed additionality and a clean match between claimed and verified ERs for the latest monitoring support credibility, but contradictions materially reduce confidence. For ER totals, the 532,381 figure is privileged because it aligns with the monitoring report (2023-03-10) and the more recent validation documentation (2022-09-05), whereas the 241,701.5 figure comes from an older validation report (2013-10-10) and likely reflects an earlier scope/period. For leakage justification, the monitoring report (2023-03-10) is privileged over the validation report (2022-09-05) because monitoring should evidence operational-period assumptions; its lack of justification is treated as a current evidence gap. For safeguards/FPIC/grievance/benefit sharing, the newer monitoring report (2023-03-10) is privileged over the 2013 validation report as it reflects updated practices, but the inconsistency still lowers confidence. For the crediting period, the 2023 monitoring report’s 2021–2031 dates are privileged as the most recent, yet the conflict with the 2022 monitoring report (2011–2021) is a significant red flag and drives a downward adjustment to all scores.

Audit Analysis

This VCS run-of-river hydro project shows moderate integrity: additionality is VVB-confirmed via an investment test and the verified ERs match the claimed ERs for the latest monitoring. However, leakage treatment is weakly evidenced and multiple cross-document inconsistencies (ER totals, crediting period, safeguards) reduce confidence in the reliability of the record.

Project Description

This project falls under scope 1: "Energy Industry - Renewable/Non-Renewable Sources" and has an installed capacity of 46 MW, making it a large-scale project.

Red Flags

  • Conflicting ER totals across validation documents (241,701.5 vs 532,381) create over-crediting and data reliability risk.
  • Crediting period is inconsistent across monitoring reports (2011–2021 vs 2021–2031), raising questions about period alignment and issuance basis.
  • Leakage is taken as 0% while the monitoring report does not address leakage justification, weakening baseline/leakage robustness.

Credit Vintages

Issued Retired Available
2011
61,734 61,734 0
2012
100,466 0 100,466
2013
79,501 77,747 1,754
2014
41,453 41,453 0
2015
91,704 7,703 84,001
2016
80,248 0 80,248
2017
187,034 0 187,034
2018
189,824 0 189,824
2019
213,915 213,915 0
2020
101,563 101,563 0
2021
69,247 68,916 331
2022
52,006 22,455 29,551
Total 1,268,695 595,486 673,209

Cosa migliorerebbe questo punteggio

  • Publish a clear, reconciled statement explaining the ER total discrepancy (241,701.5 vs 532,381) and how it maps to monitoring periods, vintages, and issuance.
  • Provide explicit leakage assessment and justification in the monitoring report (even if deemed negligible) consistent with ACM0002 requirements and project context.

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

Additionality

VVB-confirmed investment test

Permanence

Avoidance project; no reversals reported

Leakage

0% leakage with weak/absent justification

Baseline

Project-specific baseline; reassessment timing limited

Safeguards

Safeguards reported but inconsistent across documents

Double-claim

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
Analysis Provenance Scored 2026-04-02 General Methodology v2.0 Documentazione completa

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