Every methodology a project uses will eventually be revised or retired. This is not a risk to be avoided — it is a certainty to be planned for, and the projects that handle it badly are usually the ones that assumed it would not happen to them.
How Transitions Are Structured
| Stage | What it means for a project |
|---|---|
| New version published | Projects may adopt it; existing ones usually continue |
| Transition period opens | A defined window to migrate, with both versions valid |
| Registration deadline | After this, new projects must use the new version |
| Old version retired | Existing projects must have migrated or face restrictions |
The dates are the operational risk. They are published, they move occasionally, and secondary summaries go stale quickly — which is why applicability should be confirmed from the standard's own documentation at the time of planning.
What Grandfathering Does and Does Not Cover
Grandfathering typically lets an already-registered project continue under the version it validated against, for a defined period.
It does not usually survive a crediting period renewal, and it does not extend indefinitely. A project relying on grandfathering is operating on a clock, and the clock is the standard's, not the project's.
The Splicing Trap
The most damaging error is combining results calculated under different methodology versions without recalculation.
If the old version and the new one treat a pool differently, apply different deduction rules, or set the baseline differently, then subtracting one period's result from another's produces a difference that reflects the method change rather than anything that happened in the forest.
Verifiers find this quickly. The remedy — recalculating earlier periods under the new method — is laborious but bounded. Discovering it at verification, after credits have been sold against the spliced figure, is neither.
What to Do Now
Record which methodology version governs each monitoring period, in the monitoring record rather than in someone's memory.
Track revisions to the methodologies you depend on as a standing task, the way you would track a regulatory change.
And keep the underlying field data in a form that can be recalculated under a different method. A project that stored results rather than inputs cannot migrate without re-measuring — which is the expensive version of this problem.
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.



