Contractor Management
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.
Photographs are the most common form of tree-related evidence councils collect. They are also among the most inconsistently captured. A photo with no identifying context is hard to use later. A photo without GPS or timestamp is hard to defend. A photo attached only to a job, not to the tree, disappears when the job is archived.
A short, opinionated standard is more useful than a long policy. The goal is to make sure every photo can answer three questions later: which tree, when, and what was happening.
What to capture
A workable minimum for most operations:
- Wide shot showing the whole tree and its immediate surroundings
- Defect or condition shot focused on the specific issue
- Before and after shots when work is performed
- A reference shot that shows the tree in its streetscape context (helpful for later identification)
- For high-target-zone trees, a shot that shows what is beneath and around it
Quantity is not the point. Five well-composed photos that answer the three questions are more useful than thirty hurried ones.
How to identify the tree in the photo
The most common failure point is later not being able to tell which tree is in the photo. A few practical patterns:
- Include the asset ID in the photo where possible (printed tag, marked stake, written on a worksheet held in frame)
- If no asset ID exists, capture a wide shot that shows the surrounding house numbers, signage or landmarks
- Always retain the EXIF metadata, especially GPS and timestamp
- Where the device supports it, use a capture tool that embeds the asset ID into the file name
Without identification, a photo is supporting evidence for an asset only as long as someone remembers which job it came from. That is usually short.
When to capture
Photo discipline tends to be uneven across the work cycle. The pattern that helps:
- During inspection: defect-focused photos and a wide context shot
- Before work begins: wide and detailed shots of the existing condition
- During work: only where conditions warrant (unexpected findings, hazards, safety incidents)
- After work: wide and detailed shots matching the before set
- For storm and emergency response: as much as is safe to capture, even at lower composition
The before-and-after pair is the most useful for closeout. Make it the default expectation.
How to attach to the record
Photos that live only in the contractor's phone are private. Photos that live only in the job folder are tied to the job and disappear when the job is archived. Photos attached to the tree record are retrievable as long as the asset exists.
The discipline is to attach evidence to the tree first and the job second, or to both. Where the systems only support attaching to one, attach to the tree.
Resolution and storage
Modern phone cameras produce photos that are higher resolution than needed for tree records and that consume storage quickly. A reasonable compromise is to retain full-resolution photos for a defined retention period (often 2-5 years), and compressed versions afterwards. Both should retain the EXIF data — that is what makes the photo legally and operationally useful, not the pixel count.
A standard that holds up
The test for a photo evidence standard is whether someone reviewing the record three years later can answer the three questions: which tree, when, what was happening. If yes, the standard is doing its job. If no — and the most common reason is the first question — the standard needs to tighten on identification rather than on photo quality.