Carbon methodologies count carbon. They say little about what lives on the land that holds it. The Biodiversity section of the Climate, Community and Biodiversity (CCB) Standards fills that gap. It asks a plain question: is the project area, and the wider landscape it affects, better for wildlife and habitat with the project than without it?
The wording that matters is "net positive". Avoiding harm is not enough. The project has to show a gain against a documented alternative.
The Same Logic as the Other Two Sections
Like the Climate and Community sections, Biodiversity is built on a without-project scenario. The developer describes the biodiversity conditions in the project zone as they stand, and what would probably happen to them if the project did not exist. The project scenario is then compared against that.
This has a practical consequence. A project that plants on land already supporting rich native vegetation cannot claim a biodiversity gain just because there are more stems per hectare afterwards. The comparison runs against what was there, and what was likely to become of it.
| Element | What the project has to show |
|---|---|
| Baseline conditions | The state of species, habitats and ecosystems in the project zone before activity starts |
| Without-project scenario | The likely trajectory of that biodiversity if the project did not go ahead |
| Net positive impact | The project scenario improves on that trajectory |
| Offsite effects | Activities displaced outside the zone do not cancel the gain |
| Monitoring | Biodiversity is tracked over time, not described once |
Conservation Value Comes First
Before a project can say anything about gain, it has to say what is at stake. The standard expects the developer to identify areas of particular conservation value in and around the project zone. These are places that hold rare or threatened species, significant concentrations of endemic species, or important habitat for them.
Most teams do this through a high conservation value assessment. If the assessment shows that a site holds something sensitive, the project design has to protect it and maintain or enhance it. A plan that quietly converts a high-value area because the carbon arithmetic favours it will not clear this section.
Species Choices Are Part of the Test
For planting projects, the choice of species is a biodiversity question as well as a carbon one. A fast-growing single species often maximises early carbon. It is also the design a biodiversity reviewer will question hardest. The standard's approach is to expect native or otherwise appropriate species and to ask for an assessment of any risk the project species pose to the surroundings, including the risk of spreading beyond the planted area.
That does not mean every project must plant a complex mix. It means the reasoning has to be written down. If a project uses a small number of species, the document should say why, and what protects the surrounding habitat.
Monitoring Has to Be Designed, Not Improvised
The weakest biodiversity sections in project documents are the ones that promise monitoring and specify nothing. A credible plan names what will be measured (for instance, indicator species or habitat condition), how often, by whom, and how the results feed back into management. Inventory methods used for carbon plots can sometimes be extended to record vegetation composition, which keeps the cost down. Wildlife surveys usually need separate expertise.
The monitoring also has to be reported. Results go into the monitoring report and are checked at verification, like any other claim.
What Teams Get Wrong
Three patterns come up repeatedly.
First, treating a species list as a baseline. A list says what was seen on one visit. A baseline describes condition and trend.
Second, ignoring the landscape. The section looks beyond the fence, so a project that pushes pressure onto neighbouring habitat has not delivered a net gain.
Third, leaving it to the end. Biodiversity baseline work done after the design is fixed can only describe the damage. Done early, it can steer where and what to plant.
The Practical Takeaway
Treat the Biodiversity section as a design input rather than a reporting chore. The teams that handle it well do the conservation value screening first, let it shape the planting plan, and set up a monitoring routine that survives staff turnover. Those that do not usually find out at validation, when the cheapest fixes are already gone.
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.



