Vai al contenuto principale
VCS Construction United States Registry: Registered Documentazione completa General Methodology v2.0

Recycling Roadways for Carbon Emission Reductions - Midstate Reclamation and Trucking

VCS-3616 ↗

4.9 / 10
Integrity
5.4
Transparency
4.6
Claim Safety
4.8
Documentation
4.1

Score Breakdown

Integrity

verified Additionality was confirmed by the VVB, and the project used a combined additionality test under VM0039.

missing Leakage and reversal treatment are weakly evidenced: leakage is only described as deemed negligible, while reversal events are marked as not addressed.

Transparency

verified The monitoring period is clearly stated, and the verification report identifies SustainCert as the VVB.

missing Key MRV fields are not stated in available documents, including total ERs claimed versus verified, usage monitoring method, and any quantified leakage deduction.

Claim Safety

verified The project uses a project baseline under VM0039, which is at least methodologically specific.

missing No verified usage-rate, leakage deduction, or CORSIA/CCP status is available, which leaves over-crediting and claim-risk questions unresolved.

Documentation

verified The record includes a monitoring report dated 2025-10-23 and references 16 extracted documents, suggesting a reasonably broad evidence base.

missing Extraction confidence is only medium, and the monitoring report lists 3 Corrective Action Requests and 8 Clarification Requests.

Detailed Analysis

Integrity

The monitoring report confirms additionality was verified by SustainCert using a combined test, which supports the project’s core crediting logic. However, leakage is only described as deemed negligible, with no quantified deduction, and reversal handling is not addressed in the extracted record. No material findings were reported, but the presence of multiple corrective and clarification requests weakens confidence in the robustness of the integrity case.

Transparency

Transparency is limited by missing or unstated MRV details. The monitoring period is clearly identified and the VVB is named, but the extracted record does not provide total ERs claimed versus verified, the usage monitoring method, or any quantified leakage deduction. The absence of these figures makes it harder to independently assess issuance quality.

Claim Safety

Claim safety is middling because the project has a specific methodology and a project baseline, but several key over-crediting checks are unavailable. There is no verified usage-rate information, no leakage deduction, and no CORSIA or CCP status in the extracted record. That leaves residual uncertainty about whether the credited reductions are conservative enough for strong external claims.

Documentation

The documentation base is broader than a single file, with 16 documents used and a recent monitoring report dated 2025-10-23. Even so, extraction confidence is only medium, and the report records 3 Corrective Action Requests plus 8 Clarification Requests. The crediting period is long and current, but the missing buffer pool, reversal detail, and several MRV fields indicate incomplete documentation quality.

Overall

I privileged the 2025-10-23 monitoring report where it was more specific, but I also noted the contradiction on leakage treatment: one extracted value says leakage was deemed negligible, while another says it was not addressed. I also treated reversal risk conservatively because one record says reversal events were not addressed, while another older record says none were reported; the more recent and more cautionary wording was given priority. Because the file has a decent evidence base but important gaps and some reliability issues, the overall score stays in the mid range rather than high.

Audit Analysis

The project has some positive integrity signals, including VVB-confirmed additionality and no material findings reported, but key risk controls are weakly documented. Leakage and reversal treatment are not fully robust in the extracted record, and several important MRV fields are missing or not stated. Overall, this looks like a moderate-quality file with meaningful evidence gaps rather than a high-confidence, low-risk crediting case.

Project Description

Proponent: Global Emissionairy, LLC Protocol categories: Construction Protocols: VM0039 Estimated annual GHG reductions: 75767 tCO2e Region: North America Registration date: 2024-01-04

Red Flags

  • Leakage treatment is inconsistent across extracted records, with one version saying it was deemed negligible and another saying it was not addressed.
  • Reversal risk is not clearly resolved, and the extracted record does not show a buffer pool or detailed reversal handling.

Credit Vintages

Issued Retired Available
2021
28,915 28,915 0
2022
23,950 23,950 0
2023
36,769 36,769 0
2024
28,887 28,322 565
Total 118,521 117,956 565

Cosa migliorerebbe questo punteggio

  • Provide a quantified leakage assessment and a clear explanation of why leakage is negligible for this project type.
  • Disclose reversal risk treatment, including whether any buffer pool applies and how permanence is monitored over time.

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 combined test

Permanence

reversal handling unclear

Leakage

negligible claim without quantified deduction

Baseline

project baseline, reassessment not stated

Safeguards

grievance mechanism present, FPIC not found

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