A tree inventory is the foundation of any serious urban forest program. Without one, municipalities are guessing at canopy cover, species diversity, and risk — and they usually only find out about a hazard tree after it fails. A well-run inventory answers three questions at once: what do we own, what shape is it in, and what needs attention first?
This guide walks through how to plan and execute a municipal tree inventory from scratch, what data to collect, how to choose tree inventory software, and how to keep the inventory alive after the first pass is finished.
Why municipalities invest in a tree inventory
- Risk management. Documented condition and inspection dates are the single strongest defense against tort claims.
- Grant eligibility. USDA Forest Service, state urban and community forestry grants, and the Inflation Reduction Act allocations all require inventory data to score competitively.
- Budget defense. A per-tree pruning cycle backed by data is far easier to fund than a vague "trim more trees" line item.
- Ecosystem service valuation. i-Tree Eco and i-Tree Streets translate inventory rows into dollars of stormwater, air quality, and carbon benefit — the numbers councils actually respond to.
Step 1 — Define the scope
Before anyone puts boots on a curb, decide exactly what "the inventory" covers. The three common scopes are:
- Street trees only. Fastest and cheapest. Covers the right-of-way between curb and sidewalk. Most first inventories start here.
- Street + park trees. Adds every tree inside developed park boundaries. Roughly doubles the data collection effort.
- Full urban forest sample. A statistical sample of the entire canopy, including private property. Used by i-Tree Eco projects; different methodology from a 100% street tree inventory.
Also decide up front: do you count stumps, vacant planting sites, and recently removed trees? Programs that skip these lose their planting pipeline within two years.
Step 2 — Choose the data model
Every inventory needs a shared schema so field techs record the same thing the same way. A defensible baseline for a municipal street tree inventory:
- Location (lat/lng, address, side of street, distance from curb)
- Species (common + scientific name; controlled list, not free text)
- DBH (diameter at 4.5 ft, in inches)
- Height class and canopy spread
- Condition (Good / Fair / Poor / Dead — ISA-aligned)
- Structural defects and target rating (basic Level 1 risk)
- Recommended maintenance (prune, remove, plant, monitor)
- Priority (routine / elevated / immediate)
- Photo(s) — front elevation minimum
- Inspector, date, and inspection method
If you plan to feed i-Tree Eco later, match your species codes to the i-Tree species list from day one. Retrofitting a controlled vocabulary onto 20,000 rows of free-text species is a special kind of misery.
Step 3 — Pick your tree inventory software
There is no shortage of options. The honest evaluation criteria that actually matter after year one:
- Offline field capture. Municipal inventories happen in neighborhoods with spotty cell coverage. If the app requires connectivity to save a record, your crews will lose data.
- GIS interoperability. Export to Shapefile, GeoJSON, and ArcGIS Online / Enterprise. The Public Works GIS team will want a live feed, not a quarterly CSV.
- Photo storage tied to the record. Not a shared drive. Not a separate SharePoint. Photos live on the tree.
- An event / history model. Each inspection, prune, and removal should append to the tree, not overwrite it. A "last inspected" date with no history is not an inventory — it is a spreadsheet.
- Multi-user roles. Field techs, supervisors, contractors, and the public portal need different permissions.
- Exportability. Your data should never be locked in. Ask for a live SQL export or full JSON dump before you sign anything.
Leading options include TreeKeeper, PlanIT Geo's TreePlotter, Davey's TreeWorks, the free i-Tree Streets, and LAM-OS, which treats every tree as a permanent digital passport with a full event timeline built in. Whichever you choose, run a real field pilot on 200 trees before committing to a citywide contract.
Step 4 — Plan the field work
A one-person crew with a rugged tablet can inventory 150–300 street trees per day depending on tree density and traffic. Budget:
- ~$4–$8 per tree for a basic street tree inventory done in-house.
- ~$10–$18 per tree for a contracted inventory with Level 1 risk assessment.
- Add 20% for training, QA/QC, and re-inspection of ambiguous records.
Split the city into inspection zones aligned with your existing maintenance zones — not census tracts. Field techs move faster when zones match how work is already scheduled.
Step 5 — Quality control
Have a certified arborist re-inspect a random 5% of every crew's work in the first two weeks, then 2% thereafter. Track disagreement rates by field and by inspector. Species ID and condition rating are the two fields that drift most.
Step 6 — Publish and use the data
The inventory only pays for itself when other people read it. At a minimum:
- A public tree map so residents can see what's in front of their house.
- A work order feed to your maintenance contractor.
- An annual State of the Urban Forest report to council with canopy, diversity, and risk metrics year over year.
The 10-20-30 rule (no more than 10% of any species, 20% of any genus, 30% of any family) is the standard diversity benchmark. Report against it every year.
Step 7 — Keep it alive
A tree inventory is not a project — it is a program. Every completed work order, every new planting, every removal, and every re-inspection has to write back to the same record. That is the difference between an inventory that still means something in year five and a $200,000 snapshot gathering dust.
Common mistakes to avoid
- Collecting more fields than crews can actually maintain.
- Free-text species names instead of a controlled list.
- Storing photos anywhere other than on the tree record.
- Treating "last inspection date" as the entire history.
- No plan for how work orders update the inventory.
Where LAM-OS fits
LAM-OS was built around one idea: every living asset owns a permanent digital passport, and history is appended, never overwritten. It is offline-first, multi-tenant from day one, and designed to extend beyond trees to any living asset a municipality manages — shrubs, wetlands, green roofs, and more. If you're evaluating tree inventory software for a municipal or contractor program, create a workspace and load your first zone. First 100 trees are on us.