akar.earthMethodology Deviations and Revisions in Carbon Projects
Methodology deviation at Verra explained: deviations vs project description deviations vs methodology revisions, and how to handle each one.
A methodology deviation is a project-specific departure from a methodology’s procedures or monitoring requirements, allowed under Verra’s VCS rules only when it keeps the accounting conservative and does not change the methodology’s core logic. A methodology revision, by contrast, changes the methodology itself for every user and needs Verra’s approval.
Real projects rarely go exactly to plan. Equipment changes, a data source disappears, a plot gets flooded. Knowing which change mechanism to use avoids failed verifications and long delays.
The change mechanisms
| Mechanism | What changes | Who decides | Typical example |
|---|---|---|---|
| Methodology deviation | How one project applies the methodology’s procedures or monitoring | VVB assesses; registry reviews | Using a different but equivalent measurement instrument |
| Project description deviation | The registered project design or monitoring plan, without touching the methodology | VVB assesses; some need approval | Changing monitoring frequency within methodology limits |
| Methodology revision | The methodology itself, for all users | Verra, through its methodology approval process | Adding a new data source or applicability condition |
| New methodology | An entirely new method | Verra, through full development and assessment | New activity type |
The exact rules, including which changes need prior approval, are in the VCS Standard and VCS Methodology Requirements. Verra issued v5.0 of both on 16 December 2025. v4.7 of the Standard and v4.4 of the Methodology Requirements remain active until 1 July 2027. Check which version applies to your project.
When a deviation is acceptable
In general, a methodology deviation is acceptable only if:
- it does not change applicability conditions, additionality or baseline scenario identification;
- it does not reduce the conservativeness of the quantification;
- it is limited to the project in question;
- it is fully described and justified in the project description or monitoring report.
If a change fails any of these tests, a revision or a different methodology is needed.
How to handle a deviation step by step
- Identify the problem early. Spot the gap between the methodology and what the project can do.
- Classify it. Is it a methodology deviation, a project description deviation or a revision?
- Assess impact. Quantify the effect on results. Show conservativeness with a sensitivity test.
- Document. Describe the deviation, the reason, the alternative approach and the impact in the relevant document.
- Discuss with the VVB. Agree in advance that the approach is acceptable.
- Seek approval if needed. Some changes must be approved before verification.
- Apply consistently. Use the same approach in later monitoring periods unless changed again.
Methodology revisions and versions
Verra regularly updates methodologies. Recent examples from our research:
- VM0047 v1.1 became effective for all projects on 14 May 2025, with corrections and clarifications to v1.0 released the same day. v1.0 projects had to request pipeline listing by 31 December 2025 and request registration by 31 December 2026.
- VM0042 has had corrections and clarifications, with a major revision to v3.0 consulted on from 11 February to 31 March 2026.
Corrections and clarifications can be mandatory for all users of a version. Monitor the methodology page and Verra announcements. Read VM0047 and VM0042.
Indonesia and Southeast Asia examples
Common situations in Indonesian forest and land projects:
- Allometric equations. A project registers with a pantropical equation, then a species-specific Indonesian equation becomes available. Switching may count as a deviation and must be shown to be conservative. Read allometric equations.
- Remote sensing source. A satellite product used at validation is discontinued. Replacing it needs justification of equivalence. Read remote sensing for biomass.
- Plot loss. Plots destroyed by fire, flood or encroachment. Replacement plots need a documented approach.
- Monitoring frequency. Field access is limited in the wet season, so timing shifts.
- National rules. New requirements under Permenhut 6/2026 or SRUK registration can change monitoring or reporting needs.
Keeping a change log
Keep a project change log from day one. Record each change, the date, the reason, the type of change, its estimated effect on results and where it is documented. Share it with the VVB before each audit. A clear log turns a potential finding into a quick check.
Pitfalls verifiers flag
- Deviations applied without being declared.
- Deviations that change baseline or additionality logic.
- No sensitivity analysis showing conservativeness.
- Using a newer methodology version partly, mixing versions.
- Approval not obtained where required.
Our validation and verification support helps classify and document changes before audits. See also project design documents, monitoring reports and the standards hub.
Frequently asked questions
What is a methodology deviation under Verra?
A methodology deviation is a project-specific departure from the criteria, procedures or monitoring requirements of a methodology. It is allowed only within limits set by the VCS rules, must remain conservative, and is assessed by the VVB.
How is a deviation different from a methodology revision?
A deviation applies to one project and cannot change the core of the methodology. A revision changes the methodology itself for all users and goes through Verra's approval process.
What is a project description deviation?
A change to the registered project design, such as monitoring plan details, that does not involve changing the methodology. Depending on its effect, it may be handled at verification or need prior approval.
Can a deviation increase credits?
A deviation must not undermine the conservativeness of the quantification. In practice, deviations that raise credits draw close scrutiny and may be rejected.