Blog·

What a root-to-shoot ratio is and why registries apply it to AGB data

Close-up of bare birch tree trunks rising from the forest floor among green undergrowth.

Every AGB figure that comes off an allometric equation or a remote-sensing regression describes one thing: the biomass standing above the soil line. Trunks, branches, bark, foliage. None of it tells you what's happening underground, and underground is where a meaningful share of a forest's carbon sits.

That's the gap a root-to-shoot ratio closes. It's a simple multiplier, usually written as R, that relates below-ground biomass (BGB) to above-ground biomass:

R = BGB / AGB

Flip that around and you get the conversion a reviewer needs for sign-off: total biomass = AGB × (1 + R). Apply the standard carbon fraction (commonly 0.47 for most forest types, per IPCC guidance) to that total and you've moved from a canopy-structure measurement to a carbon stock figure, which is what gets reported.

Where the ratio comes from

Nobody is digging up root systems across a project boundary every reporting cycle. BGB is measured by destructive excavation, a slow and expensive process even on a handful of plots, so almost no project generates its own root-to-shoot data from scratch. Instead, most registries point project developers to the IPCC default values in Table 4.4 of the 2006 Guidelines for National Greenhouse Gas Inventories (and the 2019 Refinement), which break the ratio out by ecosystem type and, in several categories, by the AGB level of the stand itself.

A tropical rainforest with AGB above 125 t/ha, for example, uses a lower default ratio than a sparse dry forest with AGB below 20 t/ha. That's not an accident. Below a certain biomass threshold, root mass makes up a proportionally larger share of the total tree, so the ratio climbs as stand biomass drops. A reviewer checking a submission should expect to see the AGB threshold the project fell into at the time of the inventory, not just a single ratio pulled off the table without context.

Some projects use a locally derived ratio instead, usually sourced from a published study on the same forest type or region. That's acceptable to most registries, but it comes with a documentation burden: the source, the sample size behind it, and a justification for why it's a better fit than the IPCC default. If that paperwork isn't there, the registry falls back to the default, and a reviewer should check which ratio the project actually used in its final carbon accounting, separate from whichever one appears in the methodology narrative.

Why registries insist on it at all

A project could, in principle, report AGB alone and call it conservative, since leaving out below-ground carbon undercounts the stock rather than overcounts it. Several early methodologies did exactly that. But most current frameworks, including VCS/Verra methodologies and CDM afforestation/reforestation baselines, require the below-ground pool to be accounted for, even where it's addressed through a simple default multiplier rather than field sampling. A registry wants a full carbon stock estimate it can audit against a consistent, citable standard, rather than a partial number that happens to be easy to measure from imagery or plot data.

That's also why the ratio matters to anyone building or reviewing an AGB layer at landscape scale. A regression of canopy structure against biomass, run from wide-swath multispectral imagery, gives you the above-ground side of the equation at a resolution and cadence that field plots alone can't match. What it can't do is substitute for the root-to-shoot step. That conversion still has to happen downstream, with a documented ratio and a clear citation trail back to IPCC Table 4.4 or whatever regional study the project cites instead.

For a reviewer, the practical checklist is short: confirm the AGB figure in the submission is labeled as above-ground only, confirm which root-to-shoot value was applied and why, and confirm the resulting total biomass and carbon stock were recalculated consistently across every reporting cycle rather than carried forward from an earlier vintage. A project that refreshes its AGB layer annually has to reapply the ratio on every cycle, using the AGB value for that year rather than the baseline figure.

If your registry workflow needs an AGB layer that holds up to that kind of scrutiny year after year, the annual biomass layer we build from satellite imagery is a reasonable place to start.