Choosing tree inventory software is one of those decisions that looks like a feature checklist and turns out to be about workflows. Every tool in this space can store a species and a diameter. What separates them after twelve months is how they handle spotty cell coverage, how much of the asset's history is preserved instead of overwritten, and whether the GIS team can still get to the data.
This is a practitioner-oriented comparison of the five options municipal and contractor programs actually shortlist in 2026: TreePlotter, TreeKeeper, ArborNote, i-Tree, and LAM-OS. If you haven't scoped your inventory yet, start with the municipal tree inventory how-to first — the tool you pick depends on the scope.
What actually matters
- Offline-first field capture. Not "offline mode." A real local queue that survives an app crash and a battery swap.
- Event history, not overwrites. Every inspection, prune, and removal should append to the tree. "Last inspected" is not history.
- Photos live on the record. Tied to the tree, not a shared drive.
- GIS interoperability. ArcGIS + Shapefile + GeoJSON out. Live feed preferred over quarterly CSV.
- Data exportability. If you can't get a full SQL or JSON dump on demand, you don't own your data.
- Multi-user roles. Field, supervisor, contractor, public. Different scopes.
- Pricing model. Per-user, per-tree, and per-org models each hide different traps at scale.
The shortlist
TreePlotter INVENTORY
PlanIT Geo
Strengths
- Deep Esri / ArcGIS integration — the fastest onboarding if the city already runs on ArcGIS Online.
- Configurable public-facing tree map is bundled.
- Strong Level 1 risk workflow.
Watch-outs
- Offline capture on the mobile app is functional but has historically been the weakest link — pilot in low-signal neighborhoods first.
- License model scales with users; contractor access adds up fast.
Best for — Mid-to-large cities already standardized on Esri.
TreeKeeper
Davey Resource Group
Strengths
- Long track record with municipal urban forestry departments.
- Work-order and pruning-cycle modules are mature.
- Bundled i-Tree Eco reporting.
Watch-outs
- UI is dated compared with newer entrants.
- Customization typically routes through Davey's services team rather than self-serve config.
Best for — Cities that want a bundled software + consulting relationship.
ArborNote
ArborNote
Strengths
- Popular with commercial tree-care contractors, not just municipalities.
- Solid proposal-to-invoice workflow for service providers.
Watch-outs
- Less focused on municipal inventory reporting and canopy analytics.
- GIS export is available but less first-class than TreePlotter.
Best for — Commercial arborist firms managing customer trees, not city-owned inventories.
i-Tree Streets / Eco
USDA Forest Service (free)
Strengths
- Free, open, and the reference implementation for ecosystem-service valuation.
- Peer-reviewed methodology — grant reviewers know it.
Watch-outs
- Not a day-to-day operations tool. There is no field-friendly capture app, no work orders, and no role-based multi-user model.
- Best used alongside an operational inventory tool, not instead of one.
Best for — Reporting canopy value once you already have inventory data.
LAM-OS — Living Asset Manager OS
LAM-OS
Strengths
- Offline-first by design — every field capture goes into a local queue and syncs when connectivity returns.
- Every tree owns a permanent Digital Passport with an append-only event timeline; work orders, inspections, and photos never overwrite history.
- Multi-tenant from day one — a single operator can manage trees for many municipalities or customers.
- Extends beyond trees to any living asset: shrubs, wetlands, green roofs, habitats.
Watch-outs
- Newer entrant. Fewer canned reports out of the box than TreeKeeper, though data exports are unrestricted.
Best for — Municipal + contractor programs that need real offline capture and full audit history, not just a database.
How to run a real evaluation
Vendor demos will always look great. The three things that separate a good pilot from theatre:
- Load your own data. Not the vendor's demo dataset. Import at least one full zone.
- Kill connectivity. Put a tablet in airplane mode, capture twenty trees with photos, force-quit the app, reboot, then re-open. Every record should still be there and should sync cleanly.
- Export everything. Ask for a full CSV + Shapefile + JSON export on day one. If it takes a support ticket, that is the answer.
Where LAM-OS fits
LAM-OS was built specifically for the two workflows the incumbents underserve: offline field capture that never loses a record, and an append-only Digital Passport that keeps every inspection, work order, and photo tied to the asset forever. It's multi-tenant from day one and designed to extend to any living asset — not just trees.
If those are the two workflows that keep you up at night, create a workspace and pilot a zone. First 100 trees are on us.