Vai al contenuto principale
VCS avoidance India Registry: Late to verify Documentazione completa General Methodology v2.0

Shree Nakoda Ispat Ltd 12MW Biomass Power Generation Project

VCS-876 ↗

6.3 / 10
Integrity
6.2
Transparency
6.6
Claim Safety
5.6
Documentation
7.4

Score Breakdown

Integrity

verified The verification/monitoring documentation reports an investment additionality test confirmed by the VVB (monitoring report, 2011).

missing Baseline is project-specific and the timing of any baseline reassessment is not stated in available documents (monitoring report, 2011).

Transparency

verified Claimed and verified emission reductions match (68,566 tCO₂e) for the stated monitoring period (monitoring report, 2011).

missing Key MRV/context fields are missing in the extracted record (e.g., grid EF year and usage monitoring method), limiting reproducibility (monitoring report, 2011).

Claim Safety

missing Leakage is treated as 0% with “deemed negligible” justification in monitoring, but described as quantified in validation, creating over-crediting/greenwashing risk (monitoring report, 2011; validation report, 2011).

inferred CORSIA and CCP status are not stated in available documents, so downstream claim eligibility and double-claim risk cannot be screened (registry record extracted set).

Documentation

verified Multiple core documents are present (monitoring report, validation report, and PDD) and extraction confidence is high.

missing Contradictions on core descriptors (crediting period, safeguards mention, leakage framing) reduce confidence in document consistency.

Detailed Analysis

Integrity

The monitoring documentation indicates additionality was assessed via an investment test and confirmed by the VVB DNV Climate Change Services AS (monitoring report, 2011). The baseline is described as project-specific rather than standardized, and the timing of any baseline reassessment is not stated in available documents (monitoring report, 2011). Leakage is applied as a 0% deduction with a “deemed negligible” rationale in monitoring, but the validation record indicates leakage was quantified, which weakens confidence in conservative accounting (monitoring report, 2011; validation report, 2011).

Transparency

For the monitoring period 2009-01-27 to 2010-10-21, the project’s claimed ERs equal the verified ERs (68,566 tCO₂e), which supports MRV clarity for that issuance slice (monitoring report, 2011). The VVB is identified (DNV), and key parameters like the grid emission factor are provided (0.7959), but the grid EF vintage year is not stated in available documents, limiting traceability (monitoring report, 2011). The extracted record also lacks details on usage monitoring methods, which reduces transparency on operational data controls (monitoring report, 2011).

Claim Safety

Over-crediting risk is moderate because leakage is taken as 0% and justified as negligible in monitoring, while the validation report characterizes leakage as quantified; this inconsistency makes it unclear whether leakage was conservatively handled (monitoring report, 2011; validation report, 2011). The baseline is project-specific, which generally carries higher discretion than standardized baselines and can increase claim risk if assumptions are not periodically reassessed (monitoring report, 2011). CORSIA eligibility and CCP status are not stated in available documents, so buyers cannot easily assess eligibility-related reputational risk from the extracted record alone.

Documentation

The extracted record includes a monitoring report, validation report, and PDD, with seven documents used and high extraction confidence, supporting a relatively strong documentation score. No material findings or corrective actions are reported in the monitoring documentation, which suggests no major non-conformities were recorded for that period (monitoring report, 2011). However, internal inconsistencies across documents on leakage framing, safeguards mention, and crediting period dates reduce confidence in the coherence of the document set (monitoring report, 2011; validation report, 2010/2011).

Overall

Overall performance is moderate: additionality is VVB-confirmed and ER accounting is consistent for the monitored period, but contradictions and missing eligibility/safeguards details elevate risk. For leakage justification, the monitoring report (2011-11-28) is privileged for the applied accounting outcome because it reflects the implemented deduction (0%), but the validation report’s “quantified” description is treated as a reliability concern because it conflicts with the monitoring narrative. For safeguards, the monitoring report indicates safeguards were not mentioned, while the earlier validation report (2010-06-02) says they were; this is scored conservatively as weak safeguards disclosure because the later monitoring record does not evidence implementation. For the crediting period, the monitoring report’s 2010-10-22 to 2020-10-21 is treated as the crediting period, while the validation report’s 2009-01-27 to 2010-10-21 is interpreted as the monitoring period; the fact that it appears under “crediting period” is a documentation quality issue and reduces confidence.

Audit Analysis

This VCS biomass grid-connected power project shows moderate integrity: additionality is supported by an investment test confirmed by the VVB, and the verified ERs match the claimed ERs for the monitoring period. However, baseline and leakage treatment rely on project-specific assumptions with an internal inconsistency on whether leakage was quantified or merely deemed negligible, and safeguards are weakly evidenced in the extracted record.

Project Description

This project involves installing and operating a 12MW biomass-based power plant in Chattisgarh, India, which will generate electricity from rice husk and be connected to the grid. The project will replace grid power and be used for captive power consumption at SNIL, with surplus power exported to the grid. The plant and machinery consist of a high-pressure steam turbine configuration.

Red Flags

  • Leakage treatment is inconsistent across documents (quantified in the validation report vs deemed negligible with 0% deduction in the monitoring report), increasing over-crediting risk.
  • Safeguards and stakeholder protections appear weak (no FPIC and no grievance mechanism found in the extracted record), with a contradiction on whether safeguards were mentioned at all.
  • Crediting period dates conflict between documents, indicating basic data reliability issues.

Credit Vintages

Issued Retired Available
2009
32,164 32,164 0
2010
36,402 30,196 6,206
Total 68,566 62,360 6,206

Cosa migliorerebbe questo punteggio

  • Provide a clear, consistent leakage assessment across validation and monitoring, including whether leakage was quantified and the evidence supporting a 0% deduction.
  • Publish/append safeguards evidence (stakeholder consultation outcomes, FPIC where relevant, and a functioning grievance mechanism) and ensure consistent reporting across documents.
  • Clarify and correct the crediting period vs monitoring period dates in the public documentation and registry metadata, and disclose the grid emission factor vintage year and calculation references.

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 reversal risk evidenced

Leakage

0% deduction with inconsistent justification

Baseline

Project-specific baseline; reassessment timing unclear

Safeguards

No FPIC/grievance evidenced; inconsistent disclosure

Double-claim

CORSIA/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