In all cases, guidance provided in the Isometric Standard, Protocols and Modules is authoritative.
A new version of my protocol has been certified. Do I have to upgrade?
You are not required to adopt a new minor or major version until you renew your crediting period. Adoption before then is voluntary, but projects may choose to update to take advantage of improved Protocol specifications, or newer modules. Protocol versioning is the authoritative source on this, and covers what happens if you have not been validated yet, what to do if you cannot meet every requirement of the new version, and whether upgrading also changes your module and Standard versions.Do I need another site visit if I upgrade?
In most cases, no new site visit is needed. An upgrade does not require a full revalidation, and a new site visit is only required if your project processes have changed significantly. The VVB concentrates its assessment on the parts of your project that the new version changes. See Site visits.How do I upgrade to a newer protocol version?
You can upgrade straight to any more recent certified version. You do not have to adopt the intermediate versions one by one.1
Identify what has changed
Open the Protocols page, find the new version of your protocol, and select the Changelog tab to compare the two versions. The Isometric MCP server can also help you to run a comparison.
2
Confirm your project can comply
If you are unsure whether you can meet the new requirements, ask your Registry Operations Manager (ROM).
3
Request the upgrade
Ask your ROM to upgrade the project for you in Certify.
4
Document your compliance
Some requirements need a change to your project, which you then document. Others are already satisfied by your existing processes, so you only document how your project meets them. Record changes in the Project Changes section of your GHG statement report. The VVB assesses these project changes as part of your next Verification.