Tree preservation orders, and the survey behind them

The mature canopy threading through Edinburgh's residential streets and grounds is one of the things that makes the city's estates pleasant to live on. It is also a source of legal duty that a property manager can walk past for years without noticing, right up until a contractor takes a chainsaw to a protected tree and the council opens a file. A tree protected by a preservation order is not landscaping. It is a constraint on what you can do, when, and with whose permission, and the only reliable way to know which of your trees carry that constraint is to survey for it before you need to act, not after.

The pattern is familiar from the air. A site is bought or taken over, the buildings get the attention, and the trees are treated as a backdrop until one is dead, dangerous or in the way. By then the question is no longer "shall we prune this", it is "are we allowed to, and can we prove we asked". A tree preservation order, or a tree in a conservation area, turns a routine grounds task into a regulated one.

What a TPO actually does

A tree preservation order, made by a local planning authority, protects specific trees, groups or woodlands. Where one applies, you generally cannot cut down, top, lop, uproot or wilfully damage the tree without the authority's consent, and doing so without permission can be an offence. Trees within a conservation area carry their own notification requirements even where no individual order exists. The precise mechanism and the way orders are administered vary between England, Scotland and Wales, so a manager on an Edinburgh site should confirm the position with the City of Edinburgh Council and under Scottish planning rules rather than assume the English process applies. The principle is constant across the UK: some of your trees are legally protected, and you have to know which.

The duty cuts both ways, which is what makes it awkward. You are constrained from harming a protected tree, but you also retain a duty of care for safety. A protected tree that becomes genuinely dangerous still has to be dealt with, usually through a defined exemption or by giving the authority the required notice. Getting that balance right depends entirely on knowing the tree's status in advance and being able to evidence the decision.

The survey is the thing that finds the duty

You cannot manage what you have not identified. A tree survey, typically following the British Standard approach to trees in relation to design, demolition and construction, is what turns a vague sense of "there are some big trees" into an inventory: species, location, condition, and crucially whether any protection applies. It is the document that converts an unknown liability into a managed one.

A useful tree record for a managed site captures, for each tree or group:

• Location tied to the site boundary, so it can actually be found again.
• Species and approximate age or size class.
• Condition and any defects, with the date assessed.
• Protection status: TPO, conservation area, or none, with the reference where one exists.
• The recommended management action and its timing.
• Who carried out the survey and when it should be revisited.

That inventory is not a one-off. Trees grow, decline and fail. A survey from five years ago tells you what was true five years ago. The duty is ongoing, so the record has to be revisited on a sensible cycle and after significant events such as storms.

Where the record usually breaks

The common failure is not the absence of a survey. It is a survey that exists, somewhere, in a consultant's PDF that the current manager has never seen. The protection status of a tree is exactly the kind of fact that needs to live with the site, attached to its location, and visible to whoever is about to instruct grounds work, not buried in an inbox from two managing agents ago.

This is the same problem we keep meeting across land management: a duty that is known to someone, once, but not held anywhere durable. The fix is the same too. The tree inventory belongs as a layer on the site boundary, alongside the drainage, the retaining structures and the rest of the ground risk, so that the question "is this tree protected" has an answer before the contractor arrives, not after. We have argued the broader version of this in managing the land a building sits on.

A simple cadence

Tree management rewards a light, regular rhythm far more than an occasional crisis response. A workable pattern for most residential and mixed-use sites:

• Commission a full survey on taking over a site, or when none exists.
• Hold the inventory on the site record with protection status flagged.
• Carry out a visual condition check annually, and after major storms.
• Revisit the full survey on the cycle the surveyor recommends, often every few years.
• Before any grounds works, check status and seek consent where a tree is protected, keeping the application and decision on file.

The last point is the one that saves a manager from the worst outcome. The difference between "we removed a tree we did not realise was protected" and "we applied, here is the consent, dated" is the difference between an offence and a routine task done properly.

Keep the evidence with the tree

A protected tree is a small thing that carries a disproportionate amount of legal risk, and the risk is almost entirely manageable with a survey and a record. Identify what you have, know what is protected, check it on a cadence, and keep the consents with the site so the next person inherits the duty rather than the surprise. In SAMRISK, a tree inventory and its protection status can sit on the site record as a layer on the boundary, so the answer to "can we touch this tree" lives where the work gets planned.