Every methodology contains two parameter tables that look similar and behave completely differently. One lists values fixed at validation and never revisited. The other lists values measured again at every monitoring event. Treating a fixed parameter as monitored, or treating a monitored parameter as fixed, is one of the more avoidable ways to fail a verification.
The Two Tables
| Fixed ex ante | Monitored | |
|---|---|---|
| Set when | At validation | At each monitoring event |
| Examples | Carbon fraction, root:shoot ratio, default emission factors | Biomass stocks, area, activity data, fuel use |
| Can be updated? | Only through a methodology deviation | Expected to change |
| Risk if handled wrongly | Silent recalculation of earlier periods | Stale data presented as current |
The fixed parameters exist precisely so that the time series stays comparable. If the carbon fraction used in year one differs from year five, the reported change conflates growth with a definitional shift.
Why Fixed Parameters Get Changed Anyway
Usually with good intentions. A project discovers a better local wood density value, or a newer IPCC default is published, and updates it.
The result is that the current monitoring report is more accurate and no longer comparable to the last one. The carbon "gain" now includes the parameter change.
The correct handling is to apply the new value retrospectively across all periods, restate the earlier results, and document the restatement. That is more work than it sounds and it is the only approach that keeps the series honest.
Monitored Parameters Need Stated Precision
For each monitored parameter, the methodology typically expects: the measurement method, the frequency, the QA/QC applied, the uncertainty, and the archiving arrangement.
Uncertainty is the field most often left blank. A monitored parameter reported without an uncertainty estimate cannot enter the error propagation, which means either the propagation is incomplete or the parameter is being treated as exact. Neither is acceptable when the aggregate uncertainty drives the conservative deduction.
The Archiving Requirement Is Not Trivial
Most standards require monitoring data to be retained for a defined period after the last credit issuance, often two years beyond the crediting period, which for a thirty-year project means data retained for over three decades.
That is a records-management commitment, not a filing task. Spreadsheets on a departed employee's laptop do not satisfy it, and neither does a cloud folder nobody is responsible for. Projects that take this seriously assign it explicitly and test retrieval occasionally.
The Practical Check Before Each Verification
Take the methodology's parameter tables, and for each row confirm: is this fixed or monitored, what value are we using, where did it come from, and is it the same value we used last time. Fifteen rows, an afternoon.
Projects that run this check catch their own inconsistencies. Projects that do not have them caught for them, at a point when the fix is expensive.
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.



