A jurisdictional REDD+ programme under ART TREES does not get credits just by registering. Each year (or reporting period) the participant files a TREES Monitoring Report. It is the document that turns monitoring data into a number of credits. This post walks through its 16 sections, using the template and one verified report as the source.
What the report is for
The template describes the report as an outline of the ongoing performance of the participant. It summarises the activities carried out and the data collected and quantified for emission reductions and removals over the reporting period.
- It is completed on a form and submitted through the participant's registry account. - Attachments can be uploaded to the same account. - Grey fields mark where the participant must write something. Instructions in italics can be deleted before submission. - The final calculation workbook must go in with the report.
The report sits between two other documents. The Registration Document sets the rules for the crediting period. The verification report is written by an independent body after it reads the monitoring report. For the difference between the verification report and the verification opinion, see our post on the two documents.
The 16 sections at a glance
| No. | Section | What it asks |
|---|---|---|
| 1 | Participant information | Entity, contact, legal authority to represent the jurisdiction |
| 2 | Program partners | Agencies, NGOs and consultants who helped prepare the report |
| 3 | Crediting period and reporting period | Both date ranges, start and end |
| 4 | Accounting area | National or subnational, hectares of forest, share of national forest, GIS file |
| 5 | Eligibility criteria | Whether anything in the Registration Document has changed |
| 6 | Ownership rights | Rights to the reductions or removals |
| 7 | Safeguards | Evidence against the safeguard indicators |
| 8 | Participation in other programs | Any other REDD+ payment or credit on the same area |
| 9 | Double counting | Plan and procedures used to avoid it |
| 10 | Monitoring plan implementation and emissions | How the plan was run, and the emissions results |
| 11 | Reversals | Buffer contribution and whether a reversal occurred |
| 12 | Leakage | Leakage deduction from the assessment tool |
| 13 | Variances | Any approved departures from TREES |
| 14 | Emission reductions and removals | The quantified claim for the period |
| 15 | REDD+ implementation plan | Activities done in the period and their contribution to development goals |
| 16 | Changes | Major changes since the last TREES document |
The sections that carry the numbers
Sections 1 to 9 are largely carried over from the Registration Document. Section 5 is a good example: instead of describing how the programme meets each eligibility criterion again, the participant only says whether anything changed.
Section 10 is the working core. The instruction asks the participant to describe how the monitoring plan was implemented, noting any changes in:
- methodologies, - stratification, - quantification, - data collection or storage,
with a justification for each change. It also asks for the emissions from deforestation and degradation (and removals, if applicable) for the period, and for a description of how data were interpolated and prorated by calendar year.
In the verified example, section 10 was short on narrative and long on tables:
- A statement that the plan was implemented as described and methods stayed constant. - A single undifferentiated carbon stratum, because field data showed no significant difference in stocks between forests, so no stratification map was used. - Data storage and sharing procedures, written down as standard operating procedures. - Deforestation emission factors per activity in tCO2e per hectare with a 90 percent confidence interval. - Logging factors, such as per cubic metre harvested and per kilometre of skid trail. - Activity data per driver (hectares, cubic metres, kilometres) for the year. - Emissions per driver, summed to total deforestation and degradation emissions.
A footnote explained that a Monte Carlo simulation was used to combine and propagate errors, while the tables in the report show deterministic numbers for readability. That detail matters: the credit calculation uses stochastic inputs, so the printed emissions table alone will not reproduce the final credit figure.
Reversals, leakage and the final claim
Section 11 asks for the buffer contribution, using the buffer assessment tool, with evidence for any mitigating factors claimed. It also asks the participant to state plainly whether a reversal occurred in the period. Section 12 asks for the leakage deduction from the leakage tool. In the example, the accounting area covered 100 percent of national forest, so the report stated that there was no leakage deduction.
Section 14 is the claim itself. The example presented a small table with one row per year: emission reductions, buffer, leakage, uncertainty deduction and the final TREES emission reductions. Each deduction is taken off the gross reductions, and the full calculation sits in the annexed workbook. For a worked reading of such a table, see our post on buffer and uncertainty deductions.
Practical points for a programme team
- Keep the report consistent with the Registration Document. Section 5 and section 16 exist so changes are visible. - Record any change in method, even a small one, in section 10 with its reason. - State the negative explicitly: no reversal, no variance, no other programme. A blank is not an answer. - Expect the report to be revised. The example notes that it was updated to address verification findings. - Treat the workbook as part of the report. Reviewers will check the tables against it.
If your team is planning a jurisdictional programme and wants to see how monitoring data maps onto these sections, TREEO can walk through a template with you.
Move beyond estimates
Verifiers test sampling design, uncertainty and whether a number traces back to the field. TREEO dMRV captures that evidence in real time, in one auditable chain.



