Securing tree protection through conditions and bonds

A tree protection planning condition is only worth what it can be enforced against. Most of them are drafted to require a method statement that nobody reads again, discharged by a consultant's letter, and then breached by a groundworker who parks a dumper inside the fencing on a wet Tuesday. By the time the council's tree officer visits, the roots are compacted and no condition in the world will undo it.

Which is why councils increasingly ask for money as well as words. That request runs into a legal problem the council does not always acknowledge.

The conditions councils reach for

The standard set is familiar. A condition requiring development to proceed in accordance with an approved arboricultural method statement and tree protection plan prepared to BS 5837:2012. A condition requiring protective barriers to be erected before any equipment or materials are brought onto site and retained until completion. A condition restricting activities within the root protection areas. A condition requiring replacement planting where a tree is lost, usually within the next planting season.

Two of those carry most of the weight. The barrier condition works because compliance is visible from the road, and the method statement condition works because it fixes a document that contains the detail.

The root protection area is where the technical content sits. BS 5837 derives it from stem diameter, with the radius normally twelve times the diameter for a single-stemmed tree and the area capped for very large trees. Where construction has to occur inside that area, the method statement should say what technique is used, whether that is a no-dig surface, hand digging, air spade excavation or a cantilevered foundation, and who supervises it. A tree survey that stops at the schedule without the constraints plan leaves the condition with nothing to attach to.

Pre-commencement wording and the statutory constraint

Section 100ZA of the Town and Country Planning Act 1990 and the 2018 regulations made under it prevent a council imposing a pre-commencement condition without first giving the applicant written notice of the proposed condition and obtaining their agreement, subject to the prescribed procedure.

That changed the dynamic. Councils now send a schedule of proposed pre-commencement conditions before the decision, and applicants have a short window to respond. Read that schedule properly, because agreement given in silence is agreement.

The wording itself deserves attention. A condition saying no development shall begin until the method statement is approved catches every operation, including the site investigation and the demolition the method statement itself depends on. Better wording names the trigger precisely, so that site clearance, demolition or any works within the root protection areas are what is prevented, and allows the earlier enabling works that cause no arboricultural harm.

Ask for two more things. That the method statement condition refers to a document already submitted, so there is nothing left to approve. And that any required supervision regime names its frequency and its reporting, rather than leaving both to be argued later.

Whether a bond can lawfully be required

Here is the point that matters. A planning condition cannot require the payment of money. National guidance on the use of planning conditions is clear that conditions requiring a payment or other consideration are not lawful, and a condition purporting to require a tree bond falls foul of that.

So a bond has to be secured through a planning obligation under section 106 instead, and the obligation then has to satisfy the statutory tests in the Community Infrastructure Levy Regulations 2010: necessary to make the development acceptable in planning terms, directly related to the development, and fairly and reasonably related in scale and kind.

That is a real test, not a formality. A bond is defensible where the tree is of high amenity value, where the construction actually encroaches on the root protection area, and where replacement would be costly or impossible. It is much harder to justify on a scheme where the trees sit well clear of the works and ordinary protective fencing is adequate.

The practical consequence is that an applicant asked for a bond can ask which limb of the test it satisfies. Sometimes the answer is good. Often the request is a habit carried over from a previous scheme.

What a bond covers and how it is sized

Where a bond is agreed, it usually covers the cost of replacement planting, remedial works to a damaged tree, the monitoring the council carries out, and in some cases a valuation of the amenity lost.

Amenity valuation is where the figures get large. Councils commonly use one of the published tree valuation systems, which produce a capital value from stem size, life expectancy, condition and public visibility. A mature street-facing lime can value at a figure that surprises everybody, and the applicant's arboriculturist should check the inputs rather than the arithmetic, because the inputs are where the judgement sits.

Negotiate the release mechanism at the same time. A bond with no defined release date is an open-ended cost, so tie release to a stated period after practical completion, usually one or two growing seasons, with a defined inspection. Where long-term management is also required, long term tree management secured by planning agreement sets out how that obligation is normally structured.

Discharging the conditions with supervision records

The evidence a council wants at discharge is not a letter saying the trees are fine. It is a record.

That usually means dated photographs of the barriers in position before any plant arrives, a site supervision schedule listing each visit with what was inspected, records of any approved incursion into a root protection area with the method used, and a completion report confirming the condition of each retained tree against the pre-works baseline.

Appoint the arboriculturist to the supervision role at the start and write the visits into the construction programme. The alternative, which is a consultant called out after a problem, produces a report that documents damage rather than preventing it.

Where crown works are needed on retained trees during construction, the specification has to be right first time, and specifying crown works councils will accept covers the wording that avoids a second application.

Breach, enforcement and injunctions

If a tree protection condition is breached, the council has three routes. A breach of condition notice under section 187A of the 1990 Act, which carries no right of appeal and leads to prosecution in the magistrates' court. An enforcement notice, which does carry an appeal. Or an injunction under section 187B, which is the one that stops work the same week.

Councils use injunctions sparingly because of the cost and the undertaking in damages, but they do use them where a protected tree is about to be felled. Where the tree is also subject to a Tree Preservation Order, a separate offence arises under the tree preservation provisions, and the penalties for damaging a protected tree apply alongside the planning breach.

Damage that kills a tree slowly is the hard case. Root severance and compaction can take three or four years to show, by which time the development is complete and the condition has been discharged. A bond that has already been released cannot help, which is an argument for a longer release period rather than for a larger sum.

Negotiating wording before the decision

Do this while the application is live. Once the decision notice is issued the options are a section 73 application or an argument at discharge, both of which cost more than an email during determination.

Ask for four things. Precise triggers rather than a blanket commencement restriction. A method statement referenced to a submitted document. A supervision regime with a stated frequency. And a replacement planting requirement that names species, size and a defined establishment period rather than leaving it to a future scheme. Where planting is extensive, the Landscape Strategy should carry the detail so the condition can simply refer to it.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.

Enter your postcode on PlanScope to see which tree and landscape reports a site is likely to need.