Asset Class for Trees: How to Treat Them in Asset Management Plans

Asset management plans usually started life as a way to manage roads, drainage, footpaths, buildings and parks infrastructure. Trees were added later, often by attaching them to the parks asset class or treating them as a soft asset alongside furniture and signage. The fit is rarely good.

The asset management framework assumes assets that depreciate predictably, can be valued by replacement cost, and can be inspected on a schedule. Trees do not depreciate predictably, are awkward to value, and the inspection regime for them is qualitatively different from a culvert.

The result is that trees end up either understated in the plan or treated as something that does not really belong there. Both miss the point.

Why trees should be a distinct asset class

Trees behave differently enough from civil infrastructure that they warrant their own class. Specifically:

• Their value is not just replacement cost — a mature street tree is not replaceable on a project timeline
• Their condition does not depreciate linearly — it changes through events as much as age
• Their inspection regime is qualitatively different — it depends on risk band, not standard cycle
• Their maintenance is cyclical and species-dependent, not failure-driven
• Their liability profile is sharper and different from most infrastructure

When trees share an asset class with park furniture or generic vegetation, these differences get smoothed away. The asset management plan loses the ability to talk meaningfully about the tree program.

Valuation logic

Tree valuation in asset management plans usually defaults to one of two approaches. The first is replacement cost at planting size, which dramatically understates the value of mature trees. The second is amenity valuation (Burnley, Helliwell or CAVAT-derived methods), which captures the public-benefit value but is sensitive to assumption and harder to reconcile with financial reporting.

A workable approach for many councils is to maintain both: a replacement-cost figure for accounting purposes and an amenity-value figure for strategic and public-communication purposes. The two answer different questions, and the plan should make that distinction visible.

Condition framework

Condition in an asset management plan usually maps to a 1-5 scale (excellent through to failed). Tree condition does not map cleanly to this. A tree rated structurally poor may still be ecologically valuable and worth retaining. A tree in good condition may be the wrong species in the wrong location.

The fix is to record condition as a separate field from structural risk and from desirability of retention. These three dimensions, recorded distinctly, give the asset management plan something usable. Collapsing them into a single condition rating produces decisions that are hard to defend later.

Lifecycle accounting

Tree lifecycle in an asset management plan is sometimes treated as an indefinite life with no depreciation. That is mathematically clean but operationally wrong — tree cohorts have characteristic lifespans, and a renewal program needs to plan against those.

A more honest approach is to assign typical lifespans by species and class, recognise depreciation against those lifespans, and treat planting and replacement as part of the renewal program rather than as new asset acquisition. This produces a plan that can answer questions about when replacement waves will be needed.

Reporting

Tree-specific reporting that belongs in the asset management plan, but rarely appears, includes:

• Asset count by precinct and species
• Condition distribution by precinct and risk band
• Inspection coverage and currency
• Planting cohort survival by year
• Removal counts with reason
• Risk-rated trees with current action timeframes

These are operational reports. They become asset-management reports when they appear in the plan alongside the equivalent reports for roads and buildings.

A reasonable destination

A reasonable destination for most councils is an asset management plan that treats trees as a distinct asset class, with their own condition framework, valuation logic and renewal program, and with operational reporting that connects to the same tree record the parks team uses. That sounds heavier than it is. The work is mostly clarifying language and structure, not building new systems.