Bikes for the Planet - Brazil
Score Breakdown
Integrity
verified Additionality confirmed by the VVB (validation/verification documented by Earthood in the verification report)
missing Leakage not addressed (monitoring report states leakage justification: not_addressed) and no buffer pool percentage provided
Transparency
verified Named verifier (Earthood) and a recent monitoring period reported (2021-01-27 — 2022-10-31) in the monitoring report (2024-02-28)
missing Large inconsistency in claimed vs verified emission reductions across documents (240 claimed in 2019 vs 2,519 in 2024), which undermines transparency
Claim Safety
verified Usage monitored via smart meters (monitoring report), which supports measurement quality
missing Project-specific baseline with no recent reassessment and contradictory ERR figures increases over-crediting risk
Documentation
verified Multiple source documents available (validation report, monitoring report, PDD, issuance) and 19 docs extracted; latest monitoring report dated 2024-02-28
inferred Unclear items remain (no buffer pool pct, baseline reassessment not stated); contradictions between documents indicate data reliability issues
Detailed Analysis
Integrity
Additionality is supported by a barrier test and confirmed by the VVB (verification report by Earthood). However, the baseline is project-specific and there is no record of a recent baseline reassessment. Leakage is explicitly marked as not addressed in the monitoring report and no leakage deduction percentage or buffer pool percentage is provided, increasing the risk of overstatement. The contradiction in emission reduction figures across documents (240 vs 2,519) further reduces confidence in the reliability of integrity-related data.
Transparency
The project names the verifier (Earthood) and provides a clear monitoring period (2021-01-27 — 2022-10-31) in the 2024 monitoring report. A substantial evidence set is present (19 documents). Nevertheless, the large inconsistency between historical claimed ERs (240 in 2019) and the more recent figure (2,519 in 2024) is a major transparency concern and suggests recordkeeping or reporting problems.
Claim Safety
Measurement quality is supported by smart meter usage monitoring which helps reduce measurement error. But the reliance on a project-specific baseline without a stated reassessment date, the absence of leakage treatment, and the contradictory ERR figures raise over-crediting and greenwashing risks. CORSIA/CCP status is not stated, leaving double-claim risk unresolved.
Documentation
Documentation coverage is reasonably good: multiple document types (validation report, monitoring report, PDD, issuance) were extracted and the latest monitoring report is dated 2024-02-28; extraction confidence is high. However, key fields are missing or not stated (buffer pool percentage, baseline reassessment date, leakage deduction), and contradictory statements across documents (notably ERR, FPIC, safeguards, benefit sharing) reduce the usefulness of the documentation.
Overall
I privileged the more recent documents when resolving contradictions because they are likelier to reflect updated monitoring and verification results. For the emission reduction contradiction, I privileged the 2,519 figure from the validation report dated 2024-02-28 over the 240 figure from 2019 because the later verification is more recent and appears in the validation/monitoring package; this large upward change nonetheless reduces score confidence. For FPIC, safeguards, and benefit sharing contradictions I privileged the 2024 monitoring report findings over earlier documents (2022 issuance/monitoring) because the 2024 report is the latest project disclosure; these changes (e.g., FPIC now reported as not conducted, benefit sharing now described as not present) lower scores for safeguards and stakeholder protections. Overall score was reduced to reflect these contradictions and the absence of leakage treatment and buffer details. Note: extraction confidence was high, so scores are based on available documents rather than OCR uncertainty.
Audit Analysis
The project shows some positive elements (VVB-verified additionality and named verifier, recent monitoring report) but has material weaknesses: leakage is not addressed, baseline is project-specific and not recently reassessed, and there are contradictory emission reporting figures. These issues reduce confidence in the reliability and integrity of credited emission reductions.
Project Description
Proponent: ZSCORE S. A. Protocol categories: Transport Protocols: AMS-III.BM Estimated annual GHG reductions: 167 tCO2e Region: Latin America Registration date: 2020-06-04
Red Flags
- Large contradiction in reported emission reductions (240 vs 2,519) across documents
- Leakage explicitly not addressed and no leakage deduction stated
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2018 | 2,549 | 2,228 | 321 | |
| 2021 | 1,504 | 0 | 1,504 | |
| 2022 | 1,015 | 0 | 1,015 | |
| Total | 5,068 | 2,228 | 2,840 |
Cosa migliorerebbe questo punteggio
- Provide a clear leakage assessment with an explicit deduction or a robust justification for negligible leakage, and state any buffer pool contribution.
- Resolve and publicly reconcile the contradictory emission reduction figures across reports (explain methodology/measurement changes) and document baseline reassessment timing.
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
buffer unclear
not addressed
project-specific
inconsistently documented
CORSIA/CCP status unknown
Where to buy
+ 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 →