Guazhou Beidaqiao No.1 Wind Farm Project In Gansu Province, China
Score Breakdown
Integrity
verified The validation/verification record indicates additionality was confirmed using an investment test (validation/verification documentation referenced in the merged record).
missing Leakage is applied as 0% with inconsistent justification across documents, and baseline reassessment timing is not stated in the extracted record.
Transparency
verified Key MRV elements are present (VVB identified as Applus+, monitoring period 2021-03-01 to 2022-08-31, and a stated grid emission factor of 0.92928).
missing Reported ER numbers are inconsistent across documents, reducing transparency and auditability of the final credited quantity.
Claim Safety
verified The project is explicitly not CORSIA-eligible, reducing certain double-claiming/dual-channel risks.
missing Over-crediting risk is elevated by contradictions in verified ERs and unclear leakage justification despite a 0% deduction.
Documentation
verified A relatively complete document set is referenced (PDD, monitoring report, validation report, issuance) with 22 documents used and high extraction confidence.
missing Internal inconsistencies across official documents (safeguards, grievance mechanism, benefit sharing, FPIC, crediting period, and ER totals) weaken document reliability.
Detailed Analysis
Integrity
Additionality appears reasonably supported: the extracted record indicates the VVB confirmed additionality using an investment test (validation/verification documentation). The baseline is project-specific under ACM0002, but the timing of any baseline reassessment is not stated in the extracted record, which weakens robustness over a long crediting period. Leakage is scored down because the monitoring report (2022-09-27) does not address leakage justification while a validation report (2022-09-28) indicates leakage was quantified, yet the applied leakage deduction is 0%. No material findings or corrective actions are reported in the extracted record, which is a positive signal for implementation quality.
Transparency
The extracted record provides core MRV identifiers: the VVB is Applus+ Certification, the monitoring period is 2021-03-01 to 2022-08-31, and a grid emission factor of 0.92928 is reported in the monitoring documentation (2022-09-27). However, transparency is reduced by conflicting ER figures across validation reports, making it difficult to trace which number is ultimately used for issuance without further reconciliation. Public-facing completeness is otherwise moderate given the presence of PDD, monitoring, validation, and issuance in the evidence list.
Claim Safety
The project is explicitly not CORSIA-eligible, which lowers the risk of certain aviation-related double claiming. CCP status is not stated in the extracted record, leaving uncertainty about alignment with higher-integrity labels. The largest claim-safety concern is potential over-crediting driven by inconsistent verified ER totals across validation reports and inconsistent leakage justification paired with a 0% leakage deduction. These issues increase the risk that credited volumes could be challenged by buyers or stakeholders.
Documentation
Documentation coverage is relatively strong: the evidence list includes PDD, monitoring report, validation report, and issuance, with 22 documents used and high extraction confidence. The monitoring report is dated 2022-09-27, indicating recency for the latest monitoring period. Nonetheless, multiple contradictions across official documents (including safeguards/FPIC and crediting period dates) indicate either version control problems or inconsistent reporting, which reduces confidence in the documentation set as a coherent audit trail.
Overall
Overall quality is moderate: additionality is VVB-confirmed and the project type (grid-connected wind) has no reversal risk typical of land-based sequestration. However, the extracted record contains several material contradictions that undermine reliability: (1) leakage justification is 'not addressed' in the monitoring report (2022-09-27) but 'quantified' in the validation report (2022-09-28); I privilege the monitoring report for how leakage was treated in the monitored period, and score down because the justification is missing while a 0% deduction is applied. (2) Safeguards, grievance mechanism, benefit sharing, and FPIC are reported as present in the 2022 monitoring report but absent in the 2012 monitoring report; I privilege the more recent monitoring report for current practice but still penalize inconsistency. (3) Verified ERs conflict between validation reports (452,938 in 2022-09-28 vs 796,594 in 2022-07-15); I privilege the later-dated validation report as the most recent figure, but the discrepancy is large and materially increases over-crediting/credibility risk. (4) Crediting period dates conflict (2011-01-03—2032-01-02 in the 2022 monitoring report vs 2021-01-03—2031-01-02 in the 2022 validation report); I privilege the monitoring report’s stated crediting period for operational reporting, but penalize the inconsistency because it affects eligibility and volume expectations.
Audit Analysis
This is a VCS wind project using ACM0002 with additionality confirmed by the VVB and no reported material findings or corrective actions in the extracted record. However, multiple cross-document inconsistencies (including verified ERs and crediting period dates) and weak/unclear leakage treatment reduce confidence and increase over-crediting risk.
Project Description
The Guazhou Beidaqiao No.1 Wind Farm Project in Gansu Province, China aims to generate renewable electricity to meet the growing demand in the Gansu Grid and Northwest China Power Grid. The project has a total installed capacity of 201MW, with 67 sets of SL1500 wind turbine units and 67 sets of GW1500 wind turbine units. It is expected to supply 461,464 MWh of electricity annually to the NWPG, reducing the reliance on thermal power plants.
Red Flags
- Large inconsistency in verified emission reductions across validation reports (452,938 vs 796,594), indicating data reliability risk.
- Leakage treatment is inconsistent: the monitoring report does not address leakage justification while the validation report indicates leakage was quantified, yet a 0% leakage deduction is applied.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2011 | 309,444 | 280,283 | 29,161 | |
| 2012 | 130,336 | 130,336 | 0 | |
| 2013 | 332,513 | 235,356 | 97,157 | |
| 2014 | 282,097 | 282,097 | 0 | |
| 2015 | 203,798 | 203,798 | 0 | |
| 2016 | 180,154 | 180,154 | 0 | |
| 2017 | 239,862 | 239,862 | 0 | |
| 2018 | 168,041 | 168,041 | 0 | |
| 2019 | 280,172 | 280,172 | 0 | |
| 2020 | 347,219 | 347,218 | 1 | |
| 2021 | 1,162 | 1,161 | 1 | |
| Total | 2,474,798 | 2,348,478 | 126,320 |
Cosa migliorerebbe questo punteggio
- Publish a reconciliation note (or updated verification/issuance statement) clearly explaining which ER total is correct and why earlier validation figures differ, with traceable calculations for the monitoring period.
- Provide a consistent leakage section across validation and monitoring reports (even if 0%) with explicit justification under ACM0002 and clear version control for crediting period dates and safeguards disclosures.
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 reversal buffer needed
0% deduction with inconsistent justification
Project-specific baseline; reassessment timing unclear
Safeguards/FPIC reported but inconsistent over time
Not CORSIA-eligible; no dual-channel signal
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 →