Storm Response and the Tree Record

A serious storm changes a tree program for a week or more. Calls flood in. Crews are stretched. Limbs are down across the LGA. The pressure to do, rather than record, becomes overwhelming. That is the moment the tree record is most likely to fall behind, and the moment the council most needs it to be accurate.

A small amount of preparation in calm periods makes the record useful when the storm arrives.

What the record needs to absorb during a storm

Storm response generates a specific kind of operational data the regular workflow does not handle well:

• Many simultaneous reports of damage
• Reports from sources other than residents (police, SES, public works)
• Work performed under emergency protocols rather than scheduled work orders
• Activity by contractors who do not usually work on your trees
• Decisions made on the day that need to stand up under review later

A register designed for routine inspection cycles can struggle with all of these. The fix is not a separate system. It is a small storm-mode pattern layered onto the existing record.

Triage first, structured records second

In the first 24 to 48 hours, the priority is making safe what is dangerous. Detailed records can wait, but not for long. The minimum that should be captured at the moment of response is:

• What was done (tree removed, limb removed, made safe and left)
• Where (asset ID where available, otherwise GPS + photo)
• By whom and when
• Whether the tree still exists or has been removed entirely
• Whether further action is required

Even a one-line note per tree, with a timestamped photo, is enough to support full closeout later.

The 72-hour closeout window

After the immediate response, there is usually a window of a few days where the field memory is fresh and the team is still mobilised. That is the moment to convert quick notes into proper record updates: structured activity, before/after photos where available, contractor identity, and an updated latest known condition.

If the closeout slips past that window, accuracy drops sharply. People remember roughly what happened but not which tree it happened to.

What to record while it is fresh

A useful storm closeout updates several fields at once:

• Latest known condition (often "removed" or significantly altered)
• Defect notes capturing the cause of failure where visible
• Work performed, with date and contractor
• Whether replacement is planned, and on what timeframe
• Whether the surrounding cohort needs additional inspection (was this a wind-throw of a row of similar trees?)

The last point is sometimes the most valuable. A storm that takes down one tree of a particular species, age and position is a signal about the others nearby.

Defensibility under storm conditions

Storm response is also a defensibility moment. Property is damaged. Sometimes people are injured. The records made during and after a storm will be reviewed later. A tree record that shows the council did not know the tree existed, or had not inspected it for many years, is harder to defend than one that shows recent inspection, a known condition rating and a planned action that had not yet been actioned.

That is not about creating perfect records during a storm. It is about having a routine record-keeping practice that the storm does not destroy.

A small preparation before the next storm

The most useful preparation councils can do, in calm weather, is to walk through the storm response process once with the team — depot, parks, customer service, contractors — and confirm where the record updates happen. If no one can answer that question, the record will not survive the next storm.