VM0048 AND VMD0055 FREQUENTLY ASKED QUESTIONS
This page answers some of the most frequently asked questions about VM0048 and VMD0055 and projects’ transition of REDD projects them. It will be updated from time to time.
Once activity data are available for a jurisdiction, all projects in this jurisdiction (new, listed, or registered) can adopt the new REDD methodology. After a six-month grace period following the activity data release, the new methodology becomes mandatory, as set out below.
- I’m developing a new project: I must use the VM0048 if I request pipeline listing (with either the “under development” or the “under validation” status) after the end of the six-month grace period.
- My project is listed with the status “under development”: I must use the VM0048 if I request a status change to “under validation” after the end of the six-month grace period.
- My project is listed with the status “under validation”
- I may proceed with validation using any active AUDD methodology (VM0006, VM0007, or VM0015) if:
- My project was listed “under validation” before the end of the six-month grace period and
- My project completes validation within one year of the start of the public comment period.
- If the two conditions above are met, and I can complete verification before 1 January 2025, I can verify using the registered baseline.
- In cases other than those outlined in a and b above, I must use the VM0048 to proceed with validation.
- I may proceed with validation using any active AUDD methodology (VM0006, VM0007, or VM0015) if:
- My project is registered, and my project baseline is still valid
- I may proceed with verification using my registered valid baseline if I can demonstrate that verification was initiated before the end of the six-month grace period. Such a demonstration requires proof of VVB contracting and a complete draft monitoring report.
- In all other cases, I must adopt the VM0048 to verify.
- My project is registered, but my project baseline is no longer valid, and I need to reassess the baseline to be able to verify
- I may proceed with baseline reassessment and verification if I can demonstrate that verification and baseline reassessment were initiated before the end of the six-month grace period.
- Such a demonstration requires proof of VVB contracting and a complete draft monitoring report that includes baseline reassessment.
- The reassessed baseline will only be valid for the verification report for which verification has been initiated before the end of the six-month grace period. After that, the project must adopt the VM0048.
- In all other cases, I must adopt the VM0048 to verify using the baseline allocated to my project.
- I may proceed with baseline reassessment and verification if I can demonstrate that verification and baseline reassessment were initiated before the end of the six-month grace period.
A list of jurisdictions that Verra has prioritized for activity data collection, risk mapping, and activity data allocation is available on the Activity Data Availability webpage.
Verra will produce activity data (data that describe the rate of deforestation) for a jurisdiction. It will use that and other relevant data to build a risk map showing the risk of deforestation across the jurisdiction. The jurisdictional activity data and risk map will be used to allocate activity data to each project within the jurisdiction. Stakeholders are invited to submit data for potential inclusion in activity data or risk mapping – see “Opportunities to Contribute” on the Activity Data Availability webpage.
Project proponents can use data allocated to them, together with locally estimated emission factors, to calculate the annual baseline emissions from carbon stock changes in their project area and estimate the net emissions under the baseline scenario.
Anyone, including project proponents and governments, can provide relevant inputs (e.g., sample plot observations representative of the jurisdiction, including those developed for the national forest reference emissions level, ancillary data layers, alternative deforestation risk models, etc.) for calculating the jurisdictional activity data and constructing the jurisdictional deforestation risk map to the data service provider that Verra selects for the jurisdiction. Verra will then compare, in statistical terms, the ability of various alternative risk maps to predict deforestation across the jurisdiction; the best able risk map will be formally adopted by Verra as the risk map for that individual jurisdiction. Verra will utilize the jurisdictional activity data and deforestation risk map to allocate activity data to each project in the jurisdiction.
See “Opportunities to Contribute” on the Activity Data Availability webpage for more information.
Verra will inform all projects listed or registered on the Verra Registry when we begin to develop data for the jurisdiction in which they are located. At that point, they will be able to contribute to establishing activity data and risk maps for the jurisdiction and submit a formal request for allocation of activity data using a template provided by Verra. Once Verra has received a formal request, Verra will provide allocated data to the respective project proponent.
The initial version of the consolidated REDD methodology will be based on the modules that were consulted on in April-May 2022. Therefore, it will cover only the Avoiding Unplanned Deforestation component of REDD. Modules establishing similar requirements for forest degradation and planned deforestation are under development. The module for Avoiding Planned Deforestation is expected to be released in 2024. Wetlands components will be addressed by the forthcoming update to VM0033 Methodology for Tidal Wetland and Seagrass Restoration or the methodology for tropical peatlands.
Verra’s goal is to ensure that any activity addressed under VM0006, VM0007, VM0009, VM0015, or VM0037 is covered by the consolidated REDD methodology or another VCS methodology.
Such cases will be considered on a project-by-project basis. If your question relates to a project listed on the Verra Registry, please contact secretariat@verra.org providing the project’s identification number in your email. For all other questions, contact forestcarbon@verra.org
The VMD0055 sets out requirements for activity data. If a government-produced forest reference emission level (FREL) or forest reference level (FRL) uses activity data that meets VCS requirements, we encourage stakeholders to submit the activity data to Verra.
Projects that use VM0048 and VMD0055 are not necessarily considered nested projects. As in JNR, the allocation approach is used in VMD0055 to maintain the integrity of greenhouse gas accounting within a jurisdiction. However, no jurisdictional program or government involvement is required.
View information on Jurisdictional and Nested REDD+ framework.
When a version of the VM0048 has been published that accounts for all Avoiding Planned and Unplanned Deforestation and Degradation activities, Verra will inactivate the existing AUDD and APDD methodologies. Elements of existing REDD methodologies not covered by the consolidated REDD methodology may be covered in other VCS methodologies.
If your question is not covered here and relates to a project listed on the Verra Registry, please contact secretariat@verra.org providing the project’s identification number in your email. For media inquiries, contact media@verra.org. For all other questions, contact forestcarbon@verra.org.