Vai al contenuto principale
VCS Forestry China Registry: On Hold - see notification letter Documentazione completa General Methodology v2.0

Fujian Yong’An Improved Forest Management Project

VCS-1577 ↗

5.5 / 10
Integrity
3.9
Transparency
6.2
Claim Safety
6.0
Documentation
7.1

Score Breakdown

Integrity

verified Additionality is confirmed by the VVB using an investment test (validation/verification record; VVB: CQC).

missing Leakage is treated as 0% with weak/inconsistent justification across documents, and baseline reassessment timing is not stated in the extracted record.

Transparency

verified Monitoring period and verified ERs are clearly stated (monitoring report dated 2022-06-01 reports 2016-07-01—2021-06-30 and 287,276 tCO2e verified).

missing Claimed ERs are not found in the extracted record, and CAR01 suggests data quality issues in stratification/inventory inputs.

Claim Safety

verified The project is explicitly not CORSIA-eligible, reducing aviation-claim channel risk (registry extract).

missing Over-crediting risk is elevated by the stratification corrective action and by unresolved leakage treatment (0% deduction with inconsistent justification).

Documentation

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

missing Multiple cross-document contradictions (safeguards/FPIC/grievance/benefit-sharing; leakage; reversals) reduce reliability of the narrative.

Detailed Analysis

Integrity

The validation/verification record indicates additionality was assessed via an investment test and confirmed by the VVB (CQC), which supports additionality robustness. Permanence provisions appear reasonably strong for a VCS IFM project, with a 25% buffer contribution and no reversals reported in the monitoring report (2022-06-01). However, leakage is deducted at 0% while the monitoring record does not consistently justify why leakage is negligible, and the baseline is project-specific with no baseline reassessment date found in the extracted record—both weaken integrity.

Transparency

The monitoring report (2022-06-01) provides a clear monitoring period (2016-07-01—2021-06-30) and a verified ER figure of 287,276 tCO2e, which supports MRV transparency. At the same time, the claimed ER figure is not found in the extracted record, limiting the ability to reconcile claims versus verification. The presence of CAR01 in the monitoring/verification package indicates the auditor found inconsistencies in stratification versus forest investigation data, which reduces confidence in the underlying activity data transparency.

Claim Safety

The project is explicitly not CORSIA-eligible, which lowers the risk of high-impact aviation claims being made from these credits. Nonetheless, claim safety is constrained by potential over-crediting signals: CAR01 flags stratification inconsistencies (monitoring/verification package), and leakage is treated as 0% with inconsistent justification across monitoring reports. CCP status is not found in the extracted record, leaving uncertainty about alignment with higher-integrity label claims.

Documentation

The extracted record references a substantial set of documents (including PDD, validation report, monitoring report, and issuance) and indicates high extraction confidence with 14 documents used, supporting a solid documentation score. However, several key statements differ between the validation report (2016-08-02) and the later monitoring report (2022-06-01), especially on safeguards-related items, which undermines document consistency. Corrective actions are explicitly listed (CAR01), which is good for audit trail completeness but indicates issues that should be resolved and clearly documented.

Overall

Overall scoring is pulled down mainly by reliability and over-crediting risk signals rather than by a complete absence of controls: additionality is VVB-confirmed and permanence provisions include a 25% buffer with no reversals reported. Contradictions were addressed by privileging the more recent monitoring report (2022-06-01) over the older validation report (2016-08-02) for safeguards/FPIC/grievance/benefit-sharing, because it is later in time and should reflect implemented practices; however, the inconsistency itself reduces confidence and therefore lowers transparency and documentation. For leakage, the most recent monitoring report (2022-06-01) stating leakage is not addressed was privileged over the older monitoring report (2016-07-02) claiming negligible leakage, because it is more recent and more conservative; this contradiction reduces integrity and claim safety. For reversals, the monitoring report’s 'none reported' was used as the best available statement, but the existence of another record indicating reversals were 'not addressed' suggests incomplete reporting and slightly reduces integrity.

Audit Analysis

This IFM project shows some core integrity strengths (VVB-confirmed additionality, a 25% buffer contribution, and no reversals reported), but key risk areas are weakly evidenced. Leakage is recorded as a 0% deduction while the justification is inconsistent across monitoring reports, and a corrective action on forest stratification raises MRV reliability concerns.

Project Description

The Fujian Yong'an Improved Forest Management Project is a commercial forest located in Yong'an City, China. The project aims to improve the forest coverage rate and protect the local ecological environment. With over 7,000 hectares of commercial forest, the project is focused on the dominant tree species of Chinese Fir, Masson Pine and Broad-leaf trees. Prior to the implementation of the project, the forest was logged annually according to a timber logging and managing plan issued by the local forest authority.

Red Flags

  • Leakage is deducted at 0% while leakage justification is inconsistent across monitoring reports (negligible vs not addressed).
  • Corrective action (CAR01) indicates inconsistencies in forest stratification versus inventory evidence, increasing over-crediting risk.
  • Safeguards/FPIC/grievance/benefit-sharing are contradicted between the validation report and the later monitoring report, reducing confidence in social safeguard claims.
  • Leakage not addressed in project documentation

Credit Vintages

Issued Retired Available
2011
26,180 26,180 0
2012
52,222 52,222 0
2013
52,519 52,519 0
2014
52,814 10,000 42,814
2015
53,111 10,000 43,111
2016
55,041 21,940 33,101
2017
56,971 0 56,971
2018
57,294 0 57,294
2019
57,618 0 57,618
2020
57,941 44,342 13,599
2021
28,893 0 28,893
Total 550,604 217,203 333,401

Cosa migliorerebbe questo punteggio

  • Provide a clear, methodology-aligned leakage assessment and justification (or quantified deduction) consistent across monitoring reports, including activity-shifting/market leakage screening where applicable.
  • Close CAR01 with documented evidence showing corrected stratification consistent with forest inventory/second-class investigation data, and publish a transparent reconciliation of claimed vs verified ERs for the monitoring period.

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

25% buffer; no reversals reported

Leakage

0% deduction with weak/inconsistent justification

Baseline

Project-specific baseline; reassessment timing unclear

Safeguards

Safeguards/FPIC/grievance claims contradicted

Double-claim

Not CORSIA-eligible

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