Can the same VVB validate and keep verifying our Verra project every year?

No. Under VCS Standard v5.0 one VVB may do the initial validation and the first verification, but the next verification must go to a different VVB. No VVB may verify more than six consecutive years of a project's results, and it can return only after another VVB has verified at least three years.

The rule, section 4.1.27

• Initial validation and first verification: may be the same VVB.
• The verification after that: must be a different VVB.
• A cap per VVB: no more than six consecutive years of the project's reductions or removals.
• Coming back: a VVB that hit six years can verify the project again only after at least three years have been verified by a different VVB.

Combined or separate validation changes nothing

Verra spells it out. If validation and first verification happen together, the next verification needs a new VVB. If validation came first on its own, the same VVB may still do the first verification, and the one after that goes to someone else. Either way, plan for a second auditor at your second verification.

Budget for a new auditor learning your project

• Keep the project description, validation report, monitoring report and the data behind it in one place. These are what Verra requires you to give the VVB at verification.
• A new VVB decides on a site visit by its own risk assessment where the rules do not already require one, so expect questions the first VVB stopped asking.
• Check the new VVB is eligible under the VCS Program Guide and accredited for your sector before you sign.
• Ask each VVB how many years of your results it has verified so far, so the six-year cap does not surprise you mid-contract.

Example: a project validated in 2027

• Validation plus first verification, covering 2027 and 2028 results: VVB A
• Next verification: VVB B, required by the rotation rule
• VVB B verifies results for 2029 to 2034: six consecutive years, its limit
• Results for 2035 onward: any eligible VVB other than B, including A
• VVB B may return once another VVB has verified at least three years, for example 2035 to 2037

Years and auditor labels are an example.

What Senseible does here

For carbon removal projects, Senseible's verifier evidence pack is built from the same field records whichever VVB you hire, so a change of auditor does not mean rebuilding the file. Senseible prepares and checks the record; the accredited VVB verifies it.

• What a VVB is and how to choose one
• Can an FPO run its own project?
• What goes in a verifier pack
• Carbon credits

Sources: Verra, VCS Standard v5.0 (16 December 2025): Sections 3.24.3, 4.1.4, 4.1.11 to 4.1.12 and 4.1.27

Last reviewed 2026-11-03. Rotation rules sit in the current VCS Standard; recheck section 4.1.27 when Verra issues a new version.