A monitoring plan describes what the project intends to measure. A monitoring report demonstrates what it actually measured. Most verification findings live in the gap between the two and the gap is almost always created in the field, years after the plan was written by someone who is no longer on the project.
What the Plan Has to Fix in Advance
The plan is not a statement of intent; it is a specification that constrains later choices. It should pin down:
| Element | Why it must be fixed early |
|---|---|
| Plot locations and marking method | Relocation is the basis of permanent-plot precision |
| Measurement protocol and thresholds | A changed DBH threshold breaks the time series |
| Allometric equations and their source | Swapping equations mid-project changes results independently of growth |
| Monitoring frequency | Irregular intervals complicate growth attribution |
| QA/QC procedures | Remeasurement checks are unconvincing if designed after the fact |
A plan that leaves any of these open has not eliminated the decision, but rather it has deferred it to a moment when the project knows which answer it prefers.
The Three Failures That Recur
Plots that cannot be relocated. Paint fades, tags are removed, GPS coordinates recorded at 10 m accuracy are not enough in dense canopy. The result is that "permanent" plots become de facto temporary ones, and the precision advantage evaporates.
Undocumented protocol drift. A new field team measures at a slightly different height, or includes stems the previous team excluded. Nothing was done dishonestly and the time series is still broken.
Missing chain of custody. Field sheet to spreadsheet to model to report, with a step that cannot be reconstructed. The assessor's core task is tracing a reported number back to a field measurement. A break anywhere in that chain is a finding regardless of whether the number is right.
QA/QC That Actually Convinces
The standard expectation is independent remeasurement of a sample of plots, typically a small percentage, by a team that did not take the original measurements, with a stated tolerance and a documented response when the tolerance is exceeded.
Two details separate credible QA/QC from decorative QA/QC. First, the remeasurement sample must be selected before anyone knows which plots they are, not after the data is in. Second, the response to exceedances must be defined in advance: what happens when a plot fails, and who decides.
QA/QC that has never rejected anything is not evidence of quality. It is evidence that the threshold is too loose.
Frequency and Its Consequences
More frequent monitoring produces a better growth curve and costs more. Less frequent monitoring costs less and leaves longer periods to be interpolated.
The choice is genuinely a budget decision, but it has an accounting consequence, given that credits cannot be issued for periods that have not been verified, so monitoring interval sets the cadence of revenue. Projects with tight cash flow sometimes monitor more often than statistically necessary for exactly this reason, and that is a legitimate basis for the decision, as long as it is stated rather than dressed up as a technical one.
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.



