Topic cluster · Contractor management
Contractor activity is where the record either stays honest or quietly drifts
Vegetation contractors do most of the physical work that touches public trees. The standard for proof, photos and closeout is what determines whether that activity informs the register or disappears into job folders.
What this cluster covers
Councils outsource most of their physical tree work to vegetation contractors. That is not a problem in itself — councils that try to run all of it in-house rarely have the flexibility to absorb storms, peak pruning and reactive work. The problem is that the standard for what comes back from a job is often weaker than the standard for what was sent out.
This cluster pulls together the writing on what to expect at closeout — proof of work, structured activity records, photo evidence — and how each piece should attach to the tree record, not just the job record.
The pattern this cluster pushes back on
The most common failure mode is contractor evidence that lives on the job rather than on the tree. The job folder closes when the invoice is paid. Two years later, when a resident asks what happened to the tree out the front, the photos are in an archived folder somewhere, and the tree record looks unchanged.
Pushing evidence onto the tree record at closeout is one of the most high-leverage operational changes a council can make. It costs little, takes modest discipline to enforce, and dramatically improves register quality over a year or two.
Primary articles
Start here
Two articles covering the foundational expectations: proof of work, and the photo evidence standard that supports it.
Proof of Work for Vegetation Contractors
What proof-of-work councils should expect from vegetation contractors so that completed work updates the record and supports payment, audit and risk review.
25 March 2026
Photo Evidence Standards for Council Tree Work
Photos are the most common form of council tree evidence, and the most inconsistently captured. A short, opinionated standard is more useful than a long policy.
17 May 2026
Related reading
Registers, risk and system linkages
Articles from neighbouring topics that shape how contractor evidence reaches the register — and what happens when it does not.
Why Council Tree Registers Fail in the Field
Most council tree registers are built once and left to drift. Here are the patterns that quietly erode register quality, and what to do about each.
15 April 2026
Storm Response and the Tree Record
Storm response is the moment a tree program is most visible to residents and most at risk of operating blind. A small amount of preparation makes the record useful when the storm arrives.
6 May 2026
Tree Risk Records and Public Liability
Defensible tree risk records are not a paperwork exercise. They are the difference between a manageable claim and an unmanageable one.
11 March 2026
Closing the Loop Between Resident Requests and the Tree Record
Resident tree requests are a primary source of operational information about public trees. Most councils do not connect them to the asset record. Here is how to close that loop.
11 April 2026
Linking GIS, Asset Systems and Tree Records
GIS, the asset management system and the operational tree record each do something different. The trouble starts when councils ask one of them to do all three jobs.
13 May 2026
Core topic page
Read the core topic: Vegetation contractor management
The core contractor topic covers the full workflow: scope and allocation, field activity, evidence capture, council review and closeout against the tree record.
A closeout standard contractors can actually meet
Forestrees publishes practical resources on contractor closeout, photo evidence, work order discipline and the council practices that keep the register honest.