What a VVB Actually Checks: Validation and Verification, Explained
No credit is issued until an accredited Validation and Verification Body signs off. Here's what a VVB examines, how validation differs from verification, what audits typically find, and how Indian FPOs and developers should prepare.
On this page
Between a farmer changing practice and a company paying for a credit sits an auditor. The Validation and Verification Body is the market's check on whether a carbon claim is real, and its sign-off is the gate every credit passes through. For Indian FPOs and developers, understanding what a VVB examines is the difference between a project that issues credits and one that stalls indefinitely.
Quick answer
What does a VVB do?
A VVB is an independent, accredited body that audits carbon projects. Registries approve which VVBs may operate under their programmes, and no credits are issued until an approved VVB signs off. Validation (before registration) checks that the project design, baseline and additionality argument are sound. Verification (after a monitoring period) checks that the claimed reductions actually occurred. The developer engages and pays the VVB, and that cost is normally recovered from credit revenue.
Validation versus verification
| Validation | Verification | |
|---|---|---|
| When | Before registration | After each monitoring period |
| Core question | Is this project designed correctly? | Did the claimed outcome actually happen? |
| Main evidence | Project design document, baseline, methodology application | Monitoring data, field records, sampling results |
| Failure looks like | Project not registered | Credits not issued for that period |
| Farmer impact | Enrolment may proceed but nothing is bankable | Practice change happened, payment does not |
The gap between these two is where farmers most often get hurt. A project can be registered — a milestone developers announce enthusiastically — and still never issue a credit, because registration reflects validation of the design, not verification that anything was delivered. When an agent tells you a project is "registered", the correct follow-up is: and has it been verified, and can I see that report?
What a validation audit examines
Baseline and additionality. The most scrutinised area. Is the documented pre-project management credible, evidenced and captured before practice change? Is the argument that this would not have happened anyway defensible? As covered in soil sampling and baselines, a retrospectively assembled baseline is the classic weakness.
Methodology application. Is the right methodology chosen for these activities, and applied as written — eligibility conditions, quantification approach, required parameters?
Project boundary and land eligibility. Which parcels are in, are they properly identified, and do they meet eligibility criteria?
Land tenure and carbon rights. Who owns the land, who holds the right to the carbon, and is that documented? On Indian smallholdings, with tenancy, shared holdings and informal arrangements common, this is frequently the hardest evidence to assemble.
Monitoring plan. Not merely whether it exists, but whether the organisation can realistically execute it with the staff and systems it actually has.
Safeguards and consent. Evidence that farmers understood what they signed and consented freely.
What a verification audit examines
Monitoring data completeness. Does data exist for every required parameter, for every period, across the claimed parcels?
Sampling execution. Did the project sample where the design said, at the stated depth, with documented chain of custody? Departures from the stated design are a common finding.
Field verification. Site visits and interviews on a sample of parcels. Auditors talk to farmers directly — and ask what they were told, what they agreed to, and what they were paid.
Calculation review. Recomputing claimed reductions from raw data, checking model application and parameters.
Consistency with the registered design. Is the project doing what it said it would?
Auditors interview farmers directly
This deserves emphasis for anyone running a programme. Verification includes talking to participants. If farmers cannot describe what they enrolled in, do not know which practices they committed to, or believe they were promised a guaranteed annual payment that does not exist in the agreement, the audit will surface that.
Overselling at enrolment is not merely an ethical problem. It is a verification risk that can delay or block issuance for the whole project. The transparency our benefit-sharing and scam-spotting guidance recommends is also, straightforwardly, good audit preparation.
Common findings in agricultural projects
The pattern worth internalising: most findings are not "the carbon isn't there". They are "you cannot prove it to an auditor's standard". Recurring ones:
- Baseline documentation weak or assembled after practice change
- Gaps in farmer-level activity records across seasons
- Sampling deviating from the documented design
- Missing chain of custody for soil samples
- Land tenure and carbon rights inadequately evidenced
- Consent records thin or generic
- Monitoring plan written but not actually followed in the field
Each is preventable at design stage and expensive to fix retrospectively.
How long it takes, and what it costs
Verification commonly runs to several months from engagement to completed report — document review, sampling and site visits, findings raised, project responses, final report. Where findings need substantive resolution, longer.
Add the monitoring period itself, and this is a principal reason first issuance typically arrives one to two years after enrolment. Any programme promising farmers payment within a season has not accounted for the audit that must happen first.
The developer engages and pays the VVB, choosing from registry-approved bodies. That the audited party pays the auditor is a genuine structural tension, managed through accreditation rules, independence requirements, registry oversight and the VVB's own reputational exposure. The cost is real, is normally recovered from credit revenue before farmer distributions, and should be disclosed to participants — a point covered in how much farmers actually earn.
Preparing properly
- Engage the VVB early. Treating verification as a year-two problem is how projects accumulate unfixable findings.
- Build the evidence chain from day one — baseline before practice change, records continuously, chain of custody documented.
- Write a monitoring plan you can actually run, matched to real field staff and connectivity.
- Get tenure and carbon rights documented at enrolment, when farmers are engaged and it is cheap to collect.
- Do not oversell. Auditors will ask farmers what they were promised.
Our Validation & Verification service covers audit preparation, VVB engagement and managing findings to closure.
Facing a first verification, or unsure whether your evidence would hold up? Request a free assessment and we'll tell you where the gaps are while they are still fixable.
Current as of August 2026. Requirements vary by registry and methodology and are revised periodically. General information only, not financial, legal or agronomic advice.
Frequently asked questions
What is a VVB?
A VVB is a Validation and Verification Body — an independent, accredited organisation that audits carbon projects on behalf of the market. It is not part of the project and is not the registry. Registries such as Verra and Gold Standard approve which VVBs may work under their programmes, and no credits are issued for a project until an approved VVB has signed off on it.
What is the difference between validation and verification?
Validation happens before the project is registered and asks whether the design is sound — is the baseline defensible, is the additionality argument credible, is the methodology applied correctly, is the monitoring plan workable. Verification happens after a monitoring period and asks whether the claimed reductions or removals actually occurred, based on real data from real fields. Projects must pass validation to be registered and verification to be issued credits.
Who chooses and pays for the VVB?
The project developer engages and pays the VVB, selecting from those approved by the chosen registry. This sounds like a conflict of interest, and the market manages it through accreditation requirements, registry oversight, independence rules and the VVB's own reputational exposure. The cost is real and is normally recovered from credit revenue before farmer distributions — which is why it should be disclosed to participants up front.
How long does verification take?
Commonly several months from engagement to a completed verification report, and longer where findings need resolving. Time is consumed by document review, sampling and site visits, raising findings, the project responding with corrections and evidence, and final report preparation. Combined with the monitoring period itself, this is a major reason first credit issuance typically comes one to two years after enrolment rather than within a season.
What do VVBs most commonly find wrong in agricultural projects?
Recurring findings include weak or retrospectively assembled baseline documentation, gaps in farmer-level activity records, sampling that departs from the stated design, missing chain of custody for soil samples, unclear evidence of farmer consent and carbon rights, and monitoring plans that the project has not actually followed in the field. Most are documentation failures rather than the carbon being absent.
Can a project fail verification?
Yes. A VVB can issue findings the project cannot close, and the claimed reductions are then not verified and not issued. More commonly the project must resolve findings before sign-off, which delays issuance and revenue. This is a central reason farmers enrolled in real projects sometimes receive nothing for years — the practice change happened, but the evidence did not survive audit.
Related reading
Permanence, Buffer Pools and Reversal Risk: Why You Don't Get Paid for Every Tonne
Soil carbon and trees can release their carbon again. Registries manage that with buffer pools that withhold a share of every project's credits. Here's what permanence means for Indian farmers, FPOs and the tonnes you actually get paid for.
Digital MRV and Remote Sensing: What Satellites Can and Can't Measure
Digital MRV is the only affordable way to monitor thousands of fragmented Indian smallholdings. But satellites cannot see below the soil surface. Here's what remote sensing genuinely delivers, and where the overselling starts.
What Is MRV? The Part of Agri-Carbon Projects That Decides Whether You Get Paid
MRV — Measurement, Reporting and Verification — is where Indian agri-carbon projects succeed or quietly fail. Here's what each step involves, who pays for it, and why a project without credible MRV never issues a single credit.
Rohan Mehta
Carbon Markets & Policy Lead
Rohan advises on methodology selection, registries, pricing and compliance — including how India’s Carbon Credit Trading Scheme (CCTS) and the EU CBAM affect agri-carbon programmes.
- Carbon markets & VVB management
- CCTS & CBAM advisory
- Offtake & price strategy