Verification procedures differ across standards, methodologies and bodies. Underneath the procedural variation, assessors are trying to answer the same five questions, and every document request traces back to one of them. Preparing against the five is more efficient than preparing against a checklist.
The Five
| # | Question | What satisfies it |
|---|---|---|
| 1 | Is the project what it says it is? | Boundary, tenure, activities implemented at claimed scale |
| 2 | Would it have happened anyway? | Additionality evidence, at validation and on review |
| 3 | Where did these numbers come from? | Provenance from report to field record |
| 4 | How wrong could they be? | Quantified uncertainty and the resulting deduction |
| 5 | What did you not tell us? | Completeness — pools, sources, leakage, reversals |
Question 3 Consumes the Most Time
Most of a verification's hours go into tracing numbers. The assessor samples figures from the report and follows each back through the calculation chain to field records.
The cost driver is entirely on the project's side. A traceable chain makes this fast; a reconstructed one makes it slow and generates findings even where the numbers turn out correct, because "we believe this is right" is not the same evidence as "here is the record".
Question 4 Is the One Projects Answer Badly
Uncertainty is frequently reported as a single percentage with no derivation, or omitted with the observation that the methodology allows a default.
What an assessor wants: which components contributed, how they were combined, and what deduction resulted. Errors propagate in quadrature, so the largest term dominates and being able to name that term demonstrates the project understands its own numbers rather than having run a formula.
A project that says "our uncertainty is dominated by the allometric model, not the sampling, which is why we invested in equation selection" has answered question 4 convincingly. One that reports 15% with no breakdown has not.
Question 5 Is Asked Indirectly
Nobody says "what are you hiding". The question arrives as a series of specific probes: why is this pool excluded, what happened in this area that appears different in the imagery, why does this monitoring period differ from the last.
The way to pass is to raise these yourself. A monitoring report that identifies its own weak points, such as a stratum with fewer plots than planned, a disturbance event, or a parameter that had to be changed, and explains them reads as competent. The same facts discovered by the assessor read as concealment, even when there was none.
What Preparation Actually Means
Not assembling documents on request. Running the five questions internally before the verifier arrives, and fixing what does not hold up.
The most useful exercise is adversarial: have someone who did not produce the numbers try to break them. They will find the same things the assessor would, at a point where fixing them is cheap and does not appear on a findings list.
The Pattern Across Failed Verifications
Projects rarely fail because the carbon was not there. They fail because the evidence that it was there could not be assembled, as a result of records lost, protocols undocumented, calculations irreproducible, or a chain broken at one step that nobody noticed for three years.
That is a records problem masquerading as a carbon problem, and it is almost entirely preventable at the design stage for a fraction of what it costs to remediate.
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.
