What happens to my Verified Carbon Units and my project when Verra opens a quality control review?

Verra puts the project on hold and tells the project proponent and the verifier. While the review runs, Verified Carbon Units (VCUs) the proponent holds are on hold, buffer contributions are on hold and issuance stops. The verifier has 90 days to answer Verra's findings.

What can start one

Section 6.1.1 of the Registration and Issuance Process gives four examples of how Verra learns of a possible breach of the rules, and says the list is not limited to them.

• The project proponent finds an issue itself.
• The verification body (VVB) finds one while validating or verifying.
• Verra finds one in its own work, for example when reviewing a request or a complaint under its Grievance Redress Policy.
• Verra learns of a legal order, government action or allegation of unlawful conduct that touches the project.

What freezes the day it opens

Our reading, not Verra's wording: the hold names units held by the proponent. The text does not say what happens to units already sitting in a buyer's account, so a buyer should ask the seller and check the project's status on the Verra Registry.

• The project is put on hold, and Verra tells the proponent and the VVB (6.2.2).
• Active VCUs issued to the project and held by the proponent are put on hold (6.2.3).
• Buffer contributions linked to the project are put on hold (6.2.3).
• New issuance to the project is suspended (6.2.3).
• Verra may also pause its review of other requests from the project (6.2.4).

The verifier's 90 days

Verra sends the VVB a review report with findings. The VVB shall respond within 90 days of receiving it (6.3.2). For each finding it checks what was done in the original audit. If that was enough, it gives evidence and reasons. If not, it coordinates more validation or verification with the proponent, has the project description or monitoring report corrected, and issues an updated or new report. It writes an answer to every finding and sends Verra tracked and clean versions of changed documents. Where findings are still open, Verra may raise another round (6.3.3).

How it ends

• Findings addressed and no VCUs issued in excess of the correct amount: Verra closes the review, reinstates the project and tells both parties (6.4.1).
• Findings not addressed properly, or no timely reply from the VVB and the proponent: the review is closed and the project is rejected (6.4.2).
• A VVB that does not address findings or reply on time may get a warning notice and a non-conformity report, and may be sanctioned (6.4.3).
• If too many VCUs were issued, a separate replacement process applies.

Example timeline

• Verra's report reaches the VVB on 1 March.
• 1 March + 90 days = 30 May, the last day for the VVB's written answer to every finding.
• Issuance stays suspended while the review is ongoing. If it closes cleanly Verra reinstates the project (6.4.1); if not, the project is rejected (6.4.2).

Dates are an example. The 90 days run from the VVB receiving the report.

What Senseible does here

Senseible reads fuel invoices and electricity bills into monthly records that you can keep with your project evidence. Its in-house check is not an accredited third-party verification, and Senseible is not part of Verra's process.

• Excess credits: how they are replaced
• What a negative verification opinion means
• How long to keep project records
• Carbon credits

Sources: Verra, VCS Registration and Issuance Process v5.0 (16 December 2025)

Last reviewed 2026-11-05. Check the current VCS Standard, Registration and Issuance Process and Program Guide on Verra's site before you rely on this; Verra updates them periodically.