Specifying a tree inventory and urban forestry management system

Reference article · 5 min read

A tree inventory is a public asset register that happens to be alive. Every record changes: the tree grows, its condition shifts, a limb fails, a stump is ground out and the site becomes a planting vacancy. Bought as a one-time deliverable, an inventory ages out of usefulness and the agency pays again for a fresh count. Maintained as a system of record, the same data supports pruning cycles, storm response, claims defense, and canopy planning.

This checklist covers what to specify when you fund an inventory, replace an aging tree database, or fold urban forestry into a broader asset platform. Decide what you must know about each tree and site, then how work is recorded against it, and only then evaluate software.

The core record: trees, sites, and vacancies

Specify the data model before the interface. Each record should carry:

A persistent unique identifier that never changes and is never reused, independent of any vendor's internal row numbers. Site identifiers should outlive the trees in them.
Location as coordinates in a stated coordinate system, plus address or block segment, side of street, and the jurisdiction responsible for maintenance.
Species as botanical name with cultivar where known, from a controlled list rather than free text. Common names belong in a display field.
DBH, diameter at breast height, measured at a stated standard height, with a field noting how multi-stem trees were measured.
Site attributes: street, park, median, or facility grounds; growing space dimensions, utility conflict, hardscape conflict, irrigation.
Planting vacancies as first class records. A vacant site with recommended species and constraints turns a planting program into a work plan.
Removed trees retained, not deleted. Mortality patterns and claims history depend on records of trees that no longer stand.

Condition, risk, and defensible records

Condition and risk are different assessments and belong in separate fields. Condition describes health and structure. Risk describes the likelihood of failure combined with what a failure would strike and how severe the consequence would be. Industry practice, reflected in ANSI A300 tree care standards and International Society of Arboriculture guidance, separates the two and expects the assessor, assessment level, and date to be recorded with the rating. Confirm current editions before citing them.

When a tree failure becomes a claim, the question is usually what the agency knew and when it acted, so ratings without attribution or timestamps are weak evidence. Require versioned edits rather than overwrites, and confirm retention rules with your records officer and counsel.

Work history, pruning cycles, and contractors

The inventory earns its cost when it drives work. Specify that:

Every work order links to a tree or site record, and completion writes back as history with crew, date, and work type.
Grid, cycle, and reactive work are distinguishable, so you can report how much pruning happens on cycle versus on complaint.
Contractor crews can receive work and record completion in the field, while the agency keeps the authoritative record and verifies completed units.
Resident requests, including those from 311 or a CRM, attach to an existing tree instead of creating duplicates.
Storm work can be logged rapidly and offline, with hazard and debris work categorized separately for reimbursement documentation. Disaster assistance rules change, so verify them with your emergency management agency.

Collection methods and refresh cycles

Full field inventory by qualified arborists produces the most complete record and costs the most. Sampling supports population estimates but not site level work. Aerial imagery supports canopy analysis but is not ground truth for species and condition. Most agencies combine methods, then plan for continuous update rather than a repeat census. Require mobile field editing that works offline, captures photos, supports GPS correction, and lets crews update condition during routine work. Set a review target by zone so no area goes unvisited indefinitely.

Canopy goals and analysis integration

If your jurisdiction has a canopy goal, the system should support the analysis behind it. The i-Tree suite from the USDA Forest Service and its partners is publicly available and widely used for canopy estimates and for modeling benefits from inventory data. Its tools expect particular fields, so check current requirements on the official i-Tree site and build them into your collection protocol rather than finding the gap after fieldwork ends. Ask how the system exports to your GIS, since canopy analysis by neighborhood usually happens there.

What to put in the RFP so the data outlives the vendor

Data ownership and export. The agency owns all data. Full export in a documented, non-proprietary format, including photos and attachments, on demand and at no added charge, during the term and at termination.
Documented schema. A published data dictionary and a documented API. Ask for sample export files during evaluation, not after award.
Migration in and out. A plan for loading existing records, and the format you receive when you leave.
Configuration without change orders. Which fields, pick lists, and workflows staff can change themselves.
Integration. GIS, work order or ERP, CRM or 311, and permitting, stating which are standard and which are custom.
Accessibility. If a public tree map is in scope, require conformance with the accessibility standard your jurisdiction follows.
Sustainment cost. Renewal pricing, cost drivers, and what happens as record counts grow.

Start by inventorying your current state: which records exist, in which systems, with which fields, and who maintains them. Then draft requirements with an arborist and a GIS or IT staff member together, because these systems fail on either arboricultural detail or data plumbing, and each group sees only one of those.

HQT works with state and local agencies on systems engineering, data integration, and software for asset and field operations, including requirements definition for inventory systems.

Frequently asked questions

What fields should a municipal tree inventory include at minimum?

At minimum, each record needs a persistent unique identifier, location coordinates and street address context, botanical species name from a controlled list, diameter at breast height, condition, a risk rating with assessor and date, site type and growing space constraints, and work history. Planting vacancies should be stored as records in the same system so planting and maintenance planning use one dataset. Removed trees should be retained rather than deleted, since mortality analysis and claims defense both depend on them.

How often should a city update or re-inventory its street trees?

Rather than budgeting for a full re-inventory on a fixed cycle, most agencies keep the data current through field edits made during routine pruning, removal, and inspection work. Setting a review target by management zone, so that every area is revisited within a defined period, keeps coverage even without a new census. A full recount is usually only warranted when the existing data is too incomplete or too poorly attributed to correct incrementally.

Should we buy dedicated urban forestry software or use our existing asset management system?

Either can work, and the deciding factor is usually whether the general asset system can hold arboricultural detail such as species taxonomy, condition and risk fields, and planting vacancies without heavy customization. Dedicated forestry products tend to handle that detail well but may integrate less cleanly with enterprise work orders and finance. Whichever direction you choose, require that the tree records link to work orders and that both sides of the integration are described in the contract as standard or custom work.

How do we make sure we keep our tree data if we change vendors?

Write data ownership and export terms into the contract rather than relying on a vendor's general policy. Require full export in a documented, non-proprietary format, including photographs and attachments, available on demand and at termination with no additional charge, along with a published data dictionary. Ask for a sample export file during evaluation so you can confirm the format is usable before award.

Does a tree inventory help defend against tree failure claims?

It can help, because claims often turn on what the agency knew about a tree and what it did in response. Inspection and risk ratings that record the assessor, the date, the assessment level, and the recommended mitigation are far more useful as evidence than ratings without attribution. Retention and litigation hold requirements vary by jurisdiction, so confirm your obligations with your records officer and counsel.