Developers usually approach VVB selection as a procurement exercise and compare quotes. The binding constraint is almost never price — it is whether the body is accredited for your sector under your standard, and whether it has anyone available in the window you need.
Accreditation Is Sector-Specific
A VVB accredited for energy efficiency projects cannot validate a forestry project, regardless of competence. Accreditation is granted by scope, and forestry and land use is a distinct scope with its own requirements.
| Check | Why |
|---|---|
| Accredited for AFOLU / forestry scope | A general accreditation does not cover it |
| Accredited under your specific standard | Standards maintain their own approved lists |
| Currently active, not suspended | Accreditations lapse and are occasionally suspended |
| Has capacity in your window | The real constraint most of the time |
The standard body publishes the list. Checking it takes minutes and eliminates most of the candidates a general web search returns.
Independence Rules Constrain the Relationship
VVBs cannot verify work they helped create. A body that advised on methodology selection, designed the sampling, or wrote parts of the project document is conflicted out.
This catches developers who engage a consultancy for design help and then discover the same firm's verification arm is now ineligible. The two functions have to be procured separately from the outset.
Some standards additionally require rotation — a different body after a set number of consecutive verifications — which means the relationship has a built-in end date and the project should not become dependent on one body's institutional memory.
Capacity Is the Actual Bottleneck
The number of accredited AFOLU verifiers working in Southeast Asia is small relative to project demand, and it has not grown at the rate project registration has.
Practical consequences: lead times of months rather than weeks, verification windows that must be booked well in advance, and projects whose credit issuance slips because no verifier was available when the monitoring period closed.
Developers modelling cash flow on the assumption that verification happens promptly after monitoring are usually modelling optimistically. Book early, and build the lead time into the revenue schedule rather than discovering it.
What Makes a Verification Go Well
The VVB's job is to check that reported numbers trace to evidence. Projects that make that tracing easy finish faster and cheaper, because verification is charged on effort.
The things that reduce effort: a documented chain from field sheet to reported figure, parameter tables filled in completely, prior findings closed with evidence, and a single named person who can answer questions without escalation.
The things that increase it: reconstructed records, unexplained changes between monitoring periods, and a project team that has to go find out.
On Price
Price differences between accredited bodies are real but modest relative to the cost of a delayed or failed verification. Selecting on price alone, from a shortlist that was not filtered for scope and availability first, is how projects end up with a body that cannot start for six months.
Move beyond estimates
Verifiers test sampling design, uncertainty and whether a number traces back to the field. TREEO dMRV captures that evidence in real time, in one auditable chain.



