Blog·

What is a notifiable tree, and why does it matter for rail clearance?

A railway track running through bare, overhanging trees in a damp autumn forest.

Every vegetation team doing boundary work along a rail corridor runs into this sooner or later: a tree that's clearly encroaching, clearly needs cutting back, and yet can't just be felled on the next scheduled visit. It's "notifiable." That one word adds weeks to the job.

A notifiable tree is one that's protected in a way that requires someone to tell the local planning authority before work starts, usually with a set notice period, before a chainsaw goes anywhere near it. The two situations that come up most on the lineside are a Tree Preservation Order (TPO) and a tree sitting inside a conservation area. A TPO attaches to a specific tree or group and usually means a formal application to the council before felling, topping, or lopping. A conservation area tree doesn't need an order to be protected. Under Section 211 of the Town and Country Planning Act, the council normally gets six weeks' notice before any work, even routine pruning, so they can decide whether to slap a TPO on it before the chainsaws start.

There's a third category worth knowing: dead, dying, or dangerous trees are usually exempt from the notice requirement even if they're under a TPO or in a conservation area. That exemption is exactly where disputes start, because "dangerous" is a judgment call, and a landowner or local authority can push back hard if they think a healthy tree got felled under that excuse.

Why this matters for signal sighting and track clearance

None of this changes the engineering problem. A tree inside sighting distance of a signal is still a tree inside sighting distance of a signal, whether it's protected or not. What changes is the timeline and the paperwork. If your vegetation-management contractor turns up expecting to clear a stretch of boundary and finds a TPO tree in the middle of it, that tree comes off the work order until someone's filed the application and the council has responded. For a signal with a known sighting problem, that delay matters in a way it doesn't for general lineside tidying.

A lot of near-miss compliance issues start exactly here: the tree causing a sighting problem turns out to be notifiable, and the felling gets stuck behind a six-week council process nobody budgeted for. Flagging the sighting issue early, before the growing season closes in again, gives whoever is managing the contractor time to check protected status and get the paperwork moving instead of discovering it in week two of a tight clearance window.

What a notifiable status check doesn't replace

Knowing a tree might be notifiable doesn't tell you it actually is. That still means checking the local authority's TPO register and confirming whether the location falls inside a conservation area boundary, work a vegetation-management contractor or the asset owner has to do directly with the council. A survey of the corridor won't return that status on its own. What it can do is tell you exactly where the encroachment sits and which signal it affects, so the person doing that council check knows precisely which trees to look up instead of walking the whole boundary first.

An annual read of encroachment and sighting distance across the corridor closes that gap: a location, the encroachment type, distance to track, and a flag on any signal with reduced sighting, handed over as a table a contractor can work from. That table tells you exactly where to send someone to check protected status, well before the sighting problem turns into a compliance conversation.

If you're planning this year's clearance round and want to see what that table looks like for your corridor, get in touch.

Start a project

← Back to the blog