Rimba Raya Biodiversity Reserve Project

Integrity

The project uses a project‑level baseline under VM0004 (methodology v1.0) as stated in the monitoring report, which is appropriate for avoided deforestation projects. However, additionality is inconsistently documented: an earlier monitoring report (2020-07-16) records additionality as verified by the VVB, while the monitoring report dated 2022-02-27 indicates additionality was not confirmed by the VVB. There is no evidence of a recent baseline reassessment in the extracted records, and although a buffer pool percentage is provided (10% in a 2020 validation report), an earlier validation report (2015) listed 13%, indicating historical inconsistency. Corrective Actions and Clarifications reported in the monitoring/validation materials further weaken confidence in integrity.

Transparency

Transparency is moderately good: the VVB is named (AENOR Internacional) and a clear monitoring period (2019-07-01 — 2021-06-30) is provided in the monitoring report (2022-02-27). The project has extensive supporting documents (90 documents, including PDD, validation and monitoring reports) and extraction confidence is high. Nonetheless, contradictory reporting of core figures — notably total emission reductions differing between validation reports (6,890,938 in 2020 vs 11,121,623 in 2019) — reduces confidence in the public record and MRV consistency.

Claim Safety

Risk of overstated claims is moderate. The project is reported as not CORSIA‑eligible, lowering one double‑claim pathway, but the CCP status is not stated. Leakage is described as quantified in a monitoring report (2019-12-20) but no leakage deduction percentage is present in the extracted record, and usage/monitoring rates are not provided, creating uncertainty. Contradictory ERR totals and the history of corrective actions imply some over‑crediting risk remains.

Documentation

Documentation breadth is strong: monitoring report (2022-02-27), validation reports, PDD and issuance records are listed and n_docs_used is 90 with high extraction confidence. The monitoring report is recent (2022) and contains specific monitoring period and VVB name. However, multiple Corrective Actions Requests and Clarifications were issued (noted in the monitoring report), and several contradictions exist across validation/monitoring documents (buffer pool, reversal reporting, FPIC, grievance mechanism), which lowers the quality score despite the volume of documentation.

Overall

I privileged the most recent, project monitoring documents when resolving contradictions because they reflect the latest assessments and corrections: for buffer pool percentage I privileged 10% from the validation report dated 2020-07-22 over 13% from 2015 because the 2020 entry is more recent and presumably reflects updates; for total emission reductions I privileged 6,890,938 from the validation report dated 2020-05-11 over 11,121,623 from 2019 for the same reason; for additionality verification I privileged the monitoring report (2022-02-27) statement that the VVB did not confirm additionality over an earlier 2020 record claiming verification because the later monitoring report likely records the outcome of subsequent checks; for reversal events I note the extracted reversal_events field is 'none_reported' in some documents but there is an explicit loss quantified as 278,886 tCO2e in the reversal_events_detail — I privilege the reported loss detail as evidence that a reversal occurred and was quantified. These contradictions — especially in ERR totals, additionality confirmation, and reversal reporting — materially lower confidence in the project’s reported performance and contribute to the moderate overall score of 5.5. Documentation score remains above the gate thresholds, so no automatic capping was applied.