Spreadsheets vs Tree Management Systems

Spreadsheets remain one of the most common tools for council tree records. They are familiar, fast to set up and easy to share. They are also where many tree registers quietly stop reflecting reality.

The question is not whether spreadsheets are bad. It is whether they fit the operational demands placed on a tree register over time.

Where spreadsheets work well

Spreadsheets are reasonable when:

• the dataset is small and stable
• a single person owns it
• updates happen during scheduled review cycles, not continuously
• there is no field activity feeding back into the record
• evidence is not required to be attached to records
• reporting needs are modest

Many councils start here, and for a long time it works.

Where spreadsheets break down

Once tree records have to absorb routine inspection updates, contractor closeouts, resident requests, photo evidence and risk follow-up, spreadsheets begin to show predictable cracks:

• field updates are slow and require returning to the office
• there is no audit trail for who changed what and when
• photos and documents live elsewhere
• multiple people cannot safely edit at the same time
• risk follow-up depends on someone remembering
• reporting requires manual reshaping each time
• the file inevitably forks into multiple copies

None of these is fatal on its own. Together, they erode register quality enough that the spreadsheet stops being a reliable answer to "what is the latest known state of this tree."

What a tree management system changes

A dedicated tree management system is not magic. It is a system designed for the specific operational loop tree records require:

• field capture from a phone or tablet, including offline
• structured inspection forms that update the asset
• work orders that close out against the tree, not only the job
• contractor evidence attached to the tree record
• risk follow-up lists that age and persist until closeout
• a clear audit trail of who did what and when
• standard reports without manual reshaping

The advantage is not just features. It is the assumption that the record will be updated continuously by the people doing the work, rather than periodically by someone in the office.

A practical decision framework

For most councils, the decision is not "should we move off spreadsheets in general" but "for which parts of the tree record do spreadsheets still fit." Reasonable patterns:

• keep spreadsheets for planning, modelling and ad-hoc analysis
• move the live operational record — condition, risk, inspections, works, evidence — into a system designed to be updated continuously
• treat the spreadsheet as a downstream view, not the source of truth

Councils that take that route tend to find their reporting gets easier rather than harder, because the underlying record finally matches what is happening in the field.