Two ways a benefit can disappear
A forest carbon project aims to keep more carbon out of the atmosphere than would have happened without it. That could mean protecting a forest that was likely to be cleared, or growing new trees on land that had few. Two problems can undermine the result even when the project is run in good faith: permanence and leakage.
Permanence: will the carbon stay put?
Carbon stored in trees is not locked away for good. It stays only while the trees and soil stay in place. Permanence is the question of how long that storage lasts. A release, called a reversal, can come from:
- Fire. A wildfire can release years of accumulated carbon in days. Forest fires are a natural part of many landscapes, and a changing climate can make severe fire more likely in some regions.
- Pests and disease. Outbreaks of forest insect pests can kill large numbers of trees.
- Drought and storms. Prolonged drought stress can weaken or kill trees, and storms can cause windthrow across a stand.
- Human decisions. A landowner may harvest the trees, a government may change land policy, or a project may simply end and the protection lapse.
- Slow decay. Dead wood and disturbed soil release carbon over time.
Because the atmosphere does not distinguish between carbon released now and carbon released in fifty years, the length of storage matters. Releasing it later still delays the effect, but the benefit shrinks if it returns to the air.
How projects try to handle permanence
No method removes the risk entirely, but several are commonly used:
- Long commitments. Projects may agree to maintain the forest for many decades, sometimes backed by legal agreements on the land.
- Buffer pools. A share of the credits a project earns is set aside as insurance. If a reversal happens, the buffer is used to cover part of the loss. How large the buffer should be depends on the assessed risk, and the approach varies among programs.
- Monitoring. Satellite data and field plots can show whether the forest is intact. Methods overlap with forest monitoring more generally.
- Risk assessment. Projects in fire-prone or politically unstable areas typically face more scrutiny.
- Diversified portfolios. Spreading projects across regions reduces the chance that one event wipes out all of them.
These tools reduce risk without eliminating it, and people disagree about how well they work in practice.
Leakage: did the emissions just move?
Leakage occurs when protecting one forest shifts the harmful activity somewhere else. Suppose a project stops logging on one tract. If the demand for timber stays the same, the loggers may cut trees on neighboring land instead. The project area looks healthy, but the overall result is smaller than reported, or even zero.
A simple hypothetical shows the arithmetic. Imagine a project prevents the loss of 100 units of carbon on its land, but because of that, activity displaced to other land causes 30 units of loss that would not otherwise have happened. The net benefit is 100 minus 30, which is 70 units, not 100. If displaced losses were 100 or more, the net would be zero or negative. The numbers here are invented for illustration only.
Leakage may be:
- Local, as when farmers displaced from a protected area clear land nearby.
- Market-based, where reduced supply of a product raises prices and encourages production elsewhere. This is harder to observe.
- Activity shifting, where a company stops one practice in a project area but continues it on other holdings.
Reducing leakage
Common approaches include:
- Looking at the drivers of clearing, such as demand for timber or farmland, and addressing them instead of only fencing off a forest.
- Providing alternative livelihoods to people who depended on the land.
- Measuring changes in a surrounding area and deducting estimated leakage from the credits.
- Working at larger scales, such as a whole region or country, where displacement inside the boundary is counted. Rules for this appear in carbon accounting frameworks.
Related issue: additionality
Permanence and leakage are often discussed with additionality, which asks whether the carbon benefit would have happened anyway. If a forest was never going to be cut, protecting it avoids little. Judging this requires a baseline, which is a reasoned estimate of what would have occurred without the project, and baselines can be debated.
What this means for readers
When reading about any forest carbon project, useful questions are:
- How long is the forest meant to be protected, and what legally secures that?
- What happens if there is a fire or other loss?
- How were leakage and baselines estimated, and by whom were they checked?
Good answers do not make a project risk free, but vague answers are a reason for caution. Forest carbon projects can contribute to climate goals, yet their results depend on honest accounting of what could go wrong.