Can we mark our Verra baseline and additionality as confidential?
No. VCS Standard v5.0 presumes all project document information is public. You can protect genuinely commercially sensitive information, and the verifier checks the claim, but five items must stay in the public versions: the baseline, the additionality case, the reduction quantification, the monitoring and the non-permanence risk score.
The default is public
All information in project documents is presumed to be public. Where you show that something is commercially sensitive, it may be protected as set out in Verra's Registration and Issuance Process. The validation and verification body (VVB) confirms whether what you marked meets Verra's definition.
Five things that must be in the public versions
- Determination of the baseline scenario.
- Demonstration of additionality.
- Quantification of the estimated and actual reductions and removals.
- Monitoring of reductions and removals.
- Calculation of the non-permanence risk score (a land project item, so not relevant to a furnace or boiler).
What this means for a factory
The case that your project is additional and the way you worked out the reductions are public. Customer names and contract prices are not among the five. Where the line falls for a particular number, such as annual production, is for your VVB and Verra to say, so ask early.
What Senseible does here
Senseible keeps your invoices and bills private to your account. Which parts of a project document stay confidential is decided under Verra's rules and your verifier's review, not by Senseible.
Sources: Verra, VCS Standard v5.0 (16 December 2025), Sections 3.4.7 to 3.4.9
Last reviewed 2026-11-04. Section numbers are from VCS Standard v5.0 (16 December 2025); re-check them when Verra publishes a new version.