Vai al contenuto principale
VCS avoidance Peru Vintage 2018, 2019, 2020 Registry: Registered Documentazione completa General Methodology v2.0

REDD+ PROJECT IN NUT CONCESSIONS IN MADRE DE DIOS, PERU

VCS-868 ↗

5.7 / 10
Integrity
6.2
Transparency
5.5
Claim Safety
4.8
Documentation
6.5

Score Breakdown

Integrity

verified baseline reassessed in 2021 and uses a project-specific baseline (monitoring report, 2024)

missing contradiction over whether additionality was confirmed by the verifier (monitoring report, 2024 shows both true and false in extracted records), which reduces confidence

Transparency

verified monitoring period and full verified issuance figure are present in the recent monitoring report (2021–2023; monitoring report, 2024)

missing VVB name listed as TBD and several core fields (CORSIA/CCP eligibility, usage monitoring) not stated in available documents, limiting traceability

Claim Safety

verified leakage was quantified and a leakage deduction of 0% is documented with justification (monitoring report, 2024)

missing unresolved contradictions in reported ERR totals and buffer pool percentage raise over‑crediting risk (validation report 2022 vs monitoring report 2024)

Documentation

verified broad evidence set: PDD, validation report, monitoring report, issuance, with 58 documents referenced and high extraction confidence

missing core administrative details (VVB name) unresolved and multiple contradictions between documents (ERR, buffer %, crediting period), reducing documentation reliability

Detailed Analysis

Integrity

The project uses a project-specific baseline and was last reassessed in 2021, which supports baseline validity (monitoring report, 2024). A 10% buffer pool is recorded in the monitoring report but validation records show 13% in an earlier document, creating uncertainty about permanence treatment (monitoring report 2024; validation report 2020). Leakage is claimed to be quantified with a 0% deduction and justification provided (monitoring report, 2024), and no material findings or corrective actions are listed in the verification record. However, the contradiction over whether the VVB confirmed additionality (extraction shows both confirmed and not confirmed in monitoring/validation records) lowers confidence in the additionality claim.

Transparency

The monitoring report provides a clear monitoring period (2021–01–01 to 2023–12–31) and a reported total verified ERR figure in the recent report (monitoring report, 2024). The registry is VCS and evidence includes PDD, validation and monitoring reports and issuance, with 58 documents used and high extraction confidence. Key transparency gaps remain: the VVB is not named (listed as TBD), CORSIA/CCP eligibility status is not stated, and usage monitoring methods and grid emission factors are not provided in the extracted records, limiting independent verification.

Claim Safety

Leakage has been treated and justified with a 0% deduction (monitoring report, 2024), which reduces one avenue of over‑claiming risk. However, conflicting ERR totals (2,623,309 vs 2,206,081 from validation records) and inconsistent buffer percentages across documents increase the risk of over-crediting. Absence of stated CORSIA or CCP status in the extracted record leaves double-claim risk unresolved.

Documentation

Documentation is relatively complete and recent: monitoring report dated 2024-10-23, validation report(s) 2022/2020, PDD and issuance included; n_docs_used is 58 and min extraction confidence is high. Nonetheless important administrative details are unresolved (VVB name TBD) and multiple contradictions exist across core fields (ERR totals, buffer %, crediting period), which undermines the perceived completeness and consistency of the file.

Overall

I privileged the most recent monitoring report (monitoring report, 2024-10-23) for current operational facts (e.g., monitoring period, reported ERR and reversal status) and relied on validation reports (2022, 2020) for historical verification context. Contradictions to address: (1) total ERR — extraction shows both 2,623,309 and 2,206,081 reported in validation records; I treat the monitoring report's 2,623,309 as the current claimed total but flag the discrepancy, lowering confidence; (2) buffer pool — 10% in the monitoring report (2022) vs 13% in earlier validation (2020); I treated the monitoring report as more recent but reduced permanence score for inconsistency; (3) reversal events — earlier monitoring record did not address reversals while the 2024 report states none reported, so I accept the latest report but note the gap; (4) additionality verification — conflicting extraction in the monitoring record (both confirmed and not confirmed) is a serious reliability issue, and I did not assume additionality was confirmed. These contradictions reduce the integrity and claim-safety scores and are reflected in the moderate overall score of 5.7.

Audit Analysis

The project shows several positive integrity elements (project-specific baseline, recent reassessment in 2021, buffer pool) but key verification items are contradictory or unspecified (VVB name and whether additionality was confirmed). Documentation base is large and recent, but contradictory ERR and buffer values and unclear VVB independence raise moderate concerns about data reliability and over-crediting risk.

Project Description

Name: REDD+ Brazil Nut Concessions Location: Madre de Dios, Perú Developer: Bosques Amazónicos S.A.

Red Flags

  • Contradictory statements about whether additionality was verified by the VVB in the monitoring records
  • Conflicting total emission reduction/ERR figures (2,623,309 vs 2,206,081) and inconsistent buffer percentage (10% vs 13%) across documents

Credit Vintages

Issued Retired Available
2010
4,936,277 4,832,848 103,429
2013
2,149,576 1,113,855 1,035,721
2015
3,166,622 1,272,624 1,893,998
2017
2,366,747 617,201 1,749,546
2018
2,317,178 143,603 2,173,575
2019
2,239,195 256,429 1,982,766
2020
1,883,326 32,800 1,850,526
Total 19,058,921 8,269,360 10,789,561

Cosa migliorerebbe questo punteggio

  • Clarify and publicly name the VVB and provide the definitive verification statement confirming whether additionality was verified.
  • Resolve and document the discrepancies in total ERR, buffer pool percentage, and crediting period across validation and monitoring reports, with an explicit correction or reconciliation statement in the registry.

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

test present; VVB confirmation unclear

Permanence

buffer present but inconsistent

Leakage

quantified with justification

Baseline

project baseline; recent reassessment

Safeguards

FPIC and grievance present

Double-claim

eligibility/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-23 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