top of page
Search
Cover: VM0047 census-based approach, every tree on the record, beside an illustration of a crew planting seedlings

VM0047 census-based approach: what to record for every tree

Writer: Nick
Nick
1 day ago
10 min read

The VM0047 census-based approach is the way Verra's afforestation, reforestation and revegetation (ARR) methodology credits dispersed tree planting by counting every tree, rather than by sampling plots and comparing them with control areas. Under VM0047 v1.1, it is open to projects that plant 50 or fewer trees per hectare on land that is not forest and whose land use does not change. Each "planting unit" (a tree, shrub or bamboo clump, as the project defines it) must be found again at every monitoring event, identified either by GPS points, with trees spaced at least as far apart as the GPS accuracy, or by a durable physical marker carrying a unique ID.


This guide is for project developers and field leads running agroforestry, shelterbelt or farm-boundary planting. It explains who can use the approach, how it differs from the area-based route, and what a field team has to capture for every tree so that a verifier can follow the count. For how this kind of project can look on the ground, see our smallholder agroforestry use case.


The VM0047 census-based approach in brief

VM0047 is Verra's consolidated ARR methodology. Verra's methodology page states that "As of May 14, 2025, VM0047 v1.1 is effective and may be used for all projects", replacing v1.0, which was active from 28 September 2023. The same page says both versions have been approved by the Integrity Council for the Voluntary Carbon Market (ICVCM), which lists VM0047 as CCP-Approved in its ARR category. Our post on CCP-approved ARR methodologies covers that list.


The methodology offers two ways to quantify removals. Verra's summary of the census-based one is short:


  • It is for projects that do not occur in forests and do not cause land-use change.

  • Additionality and the crediting baseline are set using a project method, not a performance benchmark.

  • Projects are exempt from the leakage deduction.

  • It suits dispersed planting, such as urban forestry, agroforestry and shelterbelts.


The v1.1 methodology document sets out the full applicability conditions in section 4.3. Among them: "The project activity only includes direct planting", and "The pre-project land use is maintained throughout the project lifetime".


In plain terms: trees scattered across farms, field edges, compounds or streets, where the land keeps its existing use, can be credited by keeping a complete, auditable count of the trees themselves.


Census-based vs area-based approach

The two approaches answer the same question, how much carbon the project has removed, with different evidence. Each project instance follows one of them.



Census-based approach

Area-based approach

Typical project

Dispersed planting: agroforestry, shelterbelts, urban trees

Projects that turn non-forest into forest, or add stock to existing forest

Planting density

50 or fewer planting units per hectare

Excluded where a project plants fewer than 50 per hectare and could use the census route; instances under 1 ha allowed in v1.1 above 50 per hectare

What is counted

Every planting unit, from a complete census

Vegetation change across the area, from remote sensing and sample plots

Additionality and baseline

Project method

Dynamic performance benchmark from a stocking index, compared with matched control plots

Leakage

Exempt from the deduction

Applied with the VMD0054 leakage module

Project boundary

A buffer around each recorded planting unit

The planted or restored area

Who does most of the field work

Crews who plant, tag and re-visit each tree

Plot teams and remote-sensing analysts


Sources: Verra's VM0047 v1.1 methodology page, revision notice of 14 May 2025 and the v1.1 document (sections 4.3, 4.4.1 and 5.2).

Diagram comparing the census-based and area-based approaches of VM0047: what is counted, density, baseline and leakage
The two quantification routes in VM0047 v1.1, summarised from Verra's methodology page and sections 4.3 and 4.4.1 of the document. Read the methodology itself before choosing.

The area-based approach is built on remote sensing: a stocking index tracks vegetation in project plots and in matched control plots, and the project is credited for doing better than the controls. That is a strong design for large, contiguous restoration. It is a poor fit for 30 trees spread along the edge of a smallholder's field, which is why the census route exists.


What changed for census-based projects in v1.1

Verra described v1.1 as a minor revision. Three changes matter for a field team:


  1. A density limit for every instance. In Verra's words, "The census-based approach is now limited to projects that plant 50 or fewer trees per hectare", "regardless of instance size". Section 4.3 of v1.1 scales the limit to the instance: a 0.5 ha instance may hold no more than 25 planting units, and on larger instances the planting must be spread so that the limit holds across the whole area. The v1.0 document set no density limit; its census condition said the project "must not produce continuous tree and/or shrub cover on any contiguous area exceeding one hectare."

  2. One of two ways to identify trees. v1.0 required each planting unit to be "given a physical marker onsite with a unique ID", with its "location recorded by GPS with a minimum accuracy of five meters". Section 4.3 of v1.1 says instead: "One of the following identification approaches must be used". Option (a) is GPS points, where "the spacing between individual planting units is greater than or equal to the positional accuracy" of the GPS units used; the document's example is 5 m spacing for 5 m accuracy. Option (b) reads: "Each planting unit must be marked with a durable, in-field physical identifier bearing a unique ID."

  3. Small dense plantings move to area-based. "The area-based approach can now be used on instances under one hectare if planting density exceeds 50 trees per hectare." Section 4.4.1 of v1.1 adds the reverse rule: the area-based approach is excluded where "The project is planting fewer than 50 planting units per hectare and could use the census-based approach."


The second change is the one that affects daily field work most. GPS points alone are now an option, but only where the trees stand at least as far apart as the GPS readings are accurate. Where trees are closer than that, the tag route is the one that fits.


What the field team records for every tree

The census is the backbone of the approach. The v1.1 document gives a field team these rules (section numbers are the document's; the methodology text is what counts):


  • A complete census at the start (4.3). "The establishment of a complete census of all planting units marks the start of the project and is t = 0." That census sets N, the total number of planting units.

  • Only the project's own trees (4.3). Only planting units planted by the project proponent go into the census. Existing vegetation stays out and does not count towards the density limit.

  • A clear definition of a unit (9.2, 9.3). "Planting units must be clearly defined (e.g., tree, shrub, bamboo clump) and identifiable in the field", and the monitoring plan must define the planting unit.

  • Four facts per tree (9.2). The parameter tables list a "Unique ID", a "Geo-referenced point of the location", the "Year planted" and the "Species" for each planting unit.

  • A buffer around each tree (5.2). "In the census-based approach, each planting unit has a 10-meter radius buffer." As EP Carbon summarises it, buffers within one instance may overlap, but they must not overlap with those of a separate instance.

  • Lost trees count as dead (4.3). Where a planting unit cannot be located during a monitoring event, "it is conservatively assumed that the planting unit has died".

  • Replanting has a ceiling (4.3). Dead "plantings may be replanted provided N does not exceed 50 live planting units per hectare".


Section 8.3.1.1 then ties the count to the carbon. It carries the note "Monitoring of the complete census of planting units is required." The project's woody carbon stock is estimated "by applying the number of planting units (N) as a scaling factor and adjusting for mortality", with the average stock per unit taken from the planting units sampled and measured in that year. Section 8.5.2 states that "Uncertainty in population size (N) is assumed to be zero", which rests on the census being complete. Which trees are sampled, and which measurements feed the allometric equations, is a design to agree with your validation and verification body (VVB) before the first census.

Five-step diagram of one tree in a census-based project, from planting to the mortality count
How one tree moves through a census-based project, summarised from VM0047 v1.1. The methodology text is what counts.

GPS or a physical marker

Section 4.3 asks the project to use one of the two identification approaches, and each has a cost in the field.


  • Option (a), GPS points. Quick to capture at planting, but the spacing condition applies: every pair of neighbouring trees has to stand at least as far apart as the positional accuracy of the GPS units used. Check the accuracy your devices actually achieve on site, under the canopy the trees will grow into, before you plan the planting pattern.

  • Option (b), physical markers. A durable in-field identifier with a unique ID makes re-visits unambiguous at any spacing, but tags fade, get eaten, or are removed with the prunings. A missing tag can turn a living tree into a "not located" one.


Whichever option the project names, the record for each tree still carries a geo-referenced point (9.2). A tag number captured with every GPS reading costs a few seconds and gives the verifier a second way to match a tree. Settle with your VVB which option the project description relies on.


Re-visits and the mortality count

The mortality count is where census projects are won or lost. Every tree a crew cannot find is treated as dead, so the re-visit route matters as much as the planting day. Three habits help: walk the same route each monitoring event, record "not located" as its own answer instead of skipping the tree, and photograph the tag and the tree together so the record shows what the monitor saw.


How a community survey can carry a census

Census-based projects ask for a lot of small, repetitive records, often from farmers or local crews spread across many sites. That is the kind of data a phone survey handles well. Here is how the CitizenClimate app could be set up for it, using features documented in the App Guide and the Data Integrity and Methodology Protocol.


The survey. Survey questions can be "multiple choice, text, numbers, dates, photos, videos, audio, species identification or GPS". A tree census survey could ask for the tag ID as a text or number question, the planting year as a date, the species by photo identification or from a project list, a photo of the tree and tag, and a status at re-visits (alive, dead, not located). Our field data collection app tour shows the survey builder.

Tree Planting and Survival survey question asking which species were planted, with a species list
Real app screen from the demo account: a tree planting and survival survey asking which species were planted. Form only, no project data.

Location. The Protocol says the app requests "the highest available GPS accuracy from the device (navigation-grade, typically < 5 metres)", and stores the GPS accuracy in metres with each reading "so VVBs can assess the precision of each reading". Surveys that require a location won't start without a GPS fix. Whether that precision is enough for your tree spacing is a question for your methodology reading and your VVB, not something the app decides.


Time. Offline records keep the time they were made. The Protocol says the original timestamp is preserved when the phone syncs, and the sync date is recorded separately. That matters for a census planted over weeks in places with no signal.


Species. Photo identification of plants uses Plant.id. Photos taken offline are saved and identified when the phone reconnects, and the platform does not treat AI output as ground truth, so the species list should still be checked.


The audit trail. "Submissions can never be deleted." A wrong record is archived with a reason from a fixed list, and photos stay attached. A VVB can be given a read-only role with direct access to every record, and the data can be exported as CSV or JSON raw records.


One limit to state plainly: the app does not print tags or keep a separate tree register. The unique ID is a question the project adds to its survey, and matching each re-visit to its tree is done on the tag ID in the exported records. Projects should plan that join as part of their monitoring plan.

Map of site boundary walkover submissions from the demo account, filtered by user
Demo account screen with simulated data: walkover submissions on a map, filtered by user. A fictional project, shown for illustration.

Our tree-planting survey set-up page shows how a set of tree-planting surveys can be configured for smallholders. It describes a survey set-up, not measured results.


CitizenClimate's data is structured to align with the monitoring requirements of Verra VCS, Gold Standard, Plan Vivo, Puro.earth and Carbon Standards International. CitizenClimate is not certified, accredited or endorsed by any standard body, and it does not issue credits. Our Verra alignment page lists VM0047 among the methodologies it covers and carries a disclaimer: CitizenClimate has no affiliation with Verra, and project proponents are responsible for compliance with VCS Program rules.


Questions to settle before the first census

A short list for the project team and the VVB, before anyone plants a tagged tree:


Question

Why it matters

Is every instance at 50 or fewer planting units per hectare, and will it stay there after replanting?

Above that, the census route is closed

GPS points or physical markers?

Sets the kit, the minimum spacing between trees and the re-visit routine

What counts as one planting unit (a tree, a shrub, a bamboo clump)?

The census counts units, so the definition must be fixed

How will trees planted by farmers outside the project be kept out?

Only the proponent's own planting units count

Who re-visits, how often, and on what route?

Every tree not found is counted as dead

How will records be matched across years?

The tag ID or location has to join each re-visit to its tree

Which growth measurements are taken, on which trees?

They drive the quantification, so agree them with the VVB


Frequently asked questions

Who can use the VM0047 census-based approach?

Projects that plant 50 or fewer trees per hectare, on land that is not forest, where the project does not change the land use. Verra names urban forestry, agroforestry and shelterbelts as typical cases. Since v1.1 the density limit applies "regardless of instance size", scaled to each instance. A project planting fewer than 50 units per hectare that could use the census route is excluded from the area-based approach.


Do census-based projects need GPS for every tree?

Each planting unit's record includes a geo-referenced point, but GPS is no longer the only way to identify trees. Section 4.3 of v1.1 asks for one of two approaches: GPS points, with trees spaced at least as far apart as the GPS accuracy, or a durable physical marker with a unique ID. Version 1.0 required both a marker and GPS with a minimum accuracy of five metres.


What happens if a tree cannot be found at a monitoring event?

Section 4.3 of the v1.1 document treats it conservatively: a planting unit that cannot be located is assumed to have died, and the monitoring parameters count a unit as dead where relocating it is not possible. That is why the re-visit route and the way trees are tagged deserve as much planning as the planting itself. A missing tag or a weak GPS fix can cost credits for a tree that is still alive.


Is the census-based approach the same as counting trees from satellite images?

No. The census route rests on a field count of each planting unit, starting with a complete census at the project's start. Remote sensing and a stocking index belong to the area-based approach, where project plots are compared with matched control plots. Satellite images can still help plan routes, but they do not replace the census.


Keep every tree on the record

The census-based approach makes dispersed planting creditable, as long as each tree can be found again at every monitoring event. Decide how trees will be identified and re-visited before the first seedling goes in, and read the methodology itself with your VVB. Download the free app to build a tree census survey, or read the App Guide to see how survey questions and exports work.

Comments


bottom of page