Every TREES verification cycle produces two documents with almost the same name, filed at the same time, by the same verification body. People new to the registry assume one is a draft of the other. They are not. The report is the evidence; the opinion is the conclusion. Confusing them is the fastest way to misread what a verification body actually attested to.
Two Documents, Two Jobs
The verification report is long because its job is long: it walks through the monitoring report's claims line by line, documents the sampling and evidence the verification team checked, records any findings raised during the cycle and how the program responded, and explains the basis for every material judgment the team made. It is written for someone who wants to check the work, not just trust the conclusion — a technical reviewer, a buyer's due-diligence team, a later auditor reconciling a dispute.
The verification opinion is short because its job is narrow: it states, in a page or two, whether the verification body's overall conclusion is that the reported emission reductions or removals are fairly stated, free of material misstatement, in accordance with the applicable standard. It is the signed deliverable a registry actually keys issuance decisions to. A buyer skimming a project record is usually reading the opinion, not the report.
| Verification Report | Verification Opinion | |
|---|---|---|
| Length | Long — tens of pages | Short — one to a few pages |
| Content | Evidence, sampling, findings, responses | Overall conclusion and scope statement |
| Audience | Technical reviewers, auditors, disputants | Registry, buyers, public record |
| What it drives | Nothing directly — it's the trail | The issuance decision |
Why Both Exist Rather Than One
Publishing only the opinion would make verification unauditable — no one could check how the verification body reached its conclusion, which defeats the purpose of third-party assurance. Publishing only the report without a clear opinion would bury the actual finding inside volume a casual reader has no reason to wade through. ISO 14064-3, the underlying assurance standard most carbon verification practice traces back to, separates these for the same reason financial audits separate a detailed working file from a short audit opinion: the conclusion has to be legible on its own, and the evidence has to be available to whoever wants to test the conclusion.
A publicly filed TREES verification cycle — Costa Rica's, for example — shows this pairing clearly: a verification report covering the full monitoring period's evidence base, filed alongside a verification opinion stating the headline conclusion for that same period. The two are dated together and cover the same monitoring period, but they are not interchangeable, and a program cannot satisfy the filing requirement with only one of them.
What to Actually Read
If the question is "did this program pass verification," the opinion answers it directly — look for qualified versus unqualified language, and for any scope limitations the verification body noted. If the question is "how confident should I be in the specific numbers," the report is where that confidence has to come from: what sample sizes were checked, what discrepancies were found and corrected before the opinion was finalized, and whether any findings were closed with a workaround rather than a genuine fix.
A verification opinion that reads as unqualified does not mean the underlying report contained no findings — most verification cycles raise at least minor findings that get resolved before the opinion is issued. It means the verification body judged that, after those findings were addressed, the reported numbers were fairly stated. Reading only the opinion and assuming a spotless process skips a step a careful buyer or reviewer should not skip.
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.



