Vai al contenuto principale
VCS Energy industries (renewable/non-renewable sources) Turkey Registry: Registered Documentazione completa General Methodology v2.0

Buyukduz Hydroelectric Power Plant, Turkey

VCS-1322 ↗

5.0 / 10
Integrity
5.6
Transparency
4.8
Claim Safety
5.1
Documentation
3.7

Score Breakdown

Integrity

verified Additionality was confirmed by the VVB using an investment test in the verification report.

missing The verification report lists twelve assessment findings and says they must be addressed to Verra’s satisfaction; reversal risk is not addressed and no buffer pool is stated.

Transparency

verified The project has a named VVB, a defined monitoring period, and reported claimed versus verified issuance figures in the verification report.

missing Extraction confidence is low and only one evidence document is clearly identified, with several key fields not stated in available documents.

Claim Safety

verified The verified issuance is slightly below the claimed amount, which is a modest sign against over-crediting.

missing Leakage justification is marked as not addressed in the verification record, and the project’s CORSIA/CCP status is not stated.

Documentation

verified The record includes a recent verification report dated 2023-12-19 and references 21 extracted documents.

missing Low extraction confidence and unresolved corrective actions reduce confidence in the completeness and reliability of the documentation set.

Detailed Analysis

Integrity

The verification report confirms additionality through an investment test and shows a quantified leakage deduction of 0%, which supports the project’s core crediting logic. However, the same report lists twelve assessment findings and requires corrective actions, while reversal events are not addressed and no buffer pool is stated, so permanence and robustness are only moderate.

Transparency

The project has a named verifier, Earthood Services Private Limited, and the monitoring period and issuance figures are reported in the verification report. Still, extraction confidence is low, several fields are not stated in available documents, and the evidence list is not clearly populated, which limits document-level transparency.

Claim Safety

Claim safety is helped by the fact that verified emissions reductions are slightly lower than claimed reductions, suggesting no obvious inflation in the final verified amount. That said, leakage justification is inconsistent across documents, and the project’s CORSIA eligibility and CCP status are not stated, leaving residual greenwashing and double-claim uncertainty.

Documentation

The documentation set includes a recent verification report and a relatively large number of extracted documents, which is a positive sign. But low extraction confidence indicates at least one key document was poorly readable, and the unresolved corrective actions mean the record is not fully clean or complete.

Overall

I privileged the later verification report dated 2023-12-19 over earlier records when there was a conflict, because it is more recent and should reflect the final verified status; this is why I treated leakage as not addressed and used the later grid emission factor and crediting-period information. The contradictions around leakage treatment, grid emission factor, and crediting period reduce reliability and pull scores down, even though the project has some strong points such as VVB-confirmed additionality. Under the gating logic, documentation is below a strong threshold and integrity is not high enough to warrant a top-tier overall score, so the project lands in the middle range.

Audit Analysis

This hydro project has some positive integrity signals, including VVB-confirmed additionality and a quantified leakage deduction of 0%, but the verification report also records twelve assessment findings that still need to be resolved. Transparency is weakened by low extraction confidence, limited public-document completeness, and unresolved questions around leakage and reversal treatment.

Project Description

Proponent: Ayen Enerji A.S. Protocol categories: Energy industries (renewable/non-renewable sources) Protocols: ACM0002 Estimated annual GHG reductions: 88708 tCO2e Region: Middle East Registration date: 2020-04-06

Red Flags

  • The verification report records twelve assessment findings and requires corrective actions before issues are fully closed.
  • Leakage treatment is inconsistent across documents: one record says leakage was quantified, while the later verification record says it was not addressed.

Credit Vintages

Issued Retired Available
2012
34,523 34,523 0
2013
70,633 22,384 48,249
2017
71,628 68,272 3,356
2018
90,144 0 90,144
2019
72,669 0 72,669
2020
65,970 0 65,970
2021
56,318 0 56,318
2022
73,500 0 73,500
Total 535,385 125,179 410,206

Cosa migliorerebbe questo punteggio

  • Provide a clean, fully legible verification and monitoring package that resolves the twelve assessment findings and clearly identifies all source documents.
  • Publish explicit, consistent statements on leakage treatment, reversal risk management, buffer pool coverage, and CORSIA/CCP 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

Additionality

VVB-confirmed investment test

Permanence

No buffer pool stated

Leakage

Leakage treatment inconsistent

Baseline

Project baseline with reassessment timing

Safeguards

FPIC and grievance mechanism present

Double-claim

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
Analysis Provenance Scored 2026-04-19 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