Tree protection monitoring reports and condition discharge

A tree monitoring report condition is the one developers discover they have breached at the end of the job, when the authority refuses to sign off the arboricultural condition because no reports were ever submitted. The condition itself is usually short, requires the development to proceed in accordance with an approved arboricultural method statement including its monitoring schedule, and requires reports to reach the authority within a stated period of each visit. Nobody reads it until the final discharge application, by which point the visits that did not happen cannot be retrofitted.

The fix costs almost nothing if it is set up in the first fortnight on site.

What the condition usually requires

Arboricultural conditions come in a predictable sequence and the monitoring obligation sits in the third one.

First, a condition requiring an arboricultural method statement and tree protection plan to be submitted and approved before any development starts. A condition of that kind now needs the applicant's written agreement under section 100ZA of the Town and Country Planning Act 1990, so the wording was seen and accepted at decision stage, which removes the usual argument that it was imposed without notice.

Second, a condition requiring the development to be carried out in accordance with the approved documents. This is the operative one, and it incorporates the monitoring schedule inside the method statement by reference, which is why the schedule's drafting matters as much as the condition's.

Third, a reporting requirement: monitoring reports to be submitted to the authority within a stated number of days of each visit, often seven or fourteen, with a final report on completion.

Read the method statement you submitted, not the condition alone. Many method statements are written by arboriculturists with a generous monitoring regime that the developer never priced. Where the regime is heavier than the site needs, vary it by submitting a revised method statement for approval early rather than quietly ignoring it.

Frequency and timing of the visits

A workable schedule ties visits to construction events rather than to the calendar, because events are what create risk.

1. Pre-start, to confirm the barrier is erected on the correct line and sign it off before plant arrives.
2. At the start of any phase involving work within or adjacent to a root protection area.
3. During hand excavation or air spade work near roots, in attendance rather than by inspection.
4. On installation or alteration of ground protection.
5. On erection, alteration or striking of scaffold near a canopy.
6. On completion of hard landscaping within a root protection area.
7. At practical completion, for the final condition assessment.

Then add a routine interval between those events, typically monthly on an active site and quarterly during quiet periods, so the record is continuous rather than a series of unconnected spot checks.

Seasonal constraints affect what a visit can tell you. A tree inspected in February gives no information about foliage density, crown dieback or early stress symptoms, and the limitations of that are set out in the note on winter inspection limits for a tree survey. Where a baseline or a final assessment falls in winter, say so in the report and programme a leaf-on check.

What the report should record

A monitoring report that an authority can discharge a condition on is short and factual. Two pages plus photographs is normal.

Record the date and time of the visit, the weather, who attended and in what capacity, and which construction activities were in progress. Record which trees were inspected, by their reference numbers from the approved tree protection plan, not by description. Record the condition of each barrier run against the approved line, and state explicitly whether it matched.

Then record findings. For each item, state what was observed, where, the tree references affected, whether it constitutes a departure from the approved documents, what instruction was given, to whom, and what the agreed remedy and timescale are. Close each item at a later visit and say in which report it was closed.

Finish with three statements: outstanding items carried forward, the date of the next scheduled visit, and a compliance statement saying whether, in the author's opinion, the works to date have been carried out in accordance with the approved method statement. That last sentence is what the tree officer reads first.

Photographic evidence and the fence line check

Photographs are the evidence; everything else is assertion. Set up fixed photo points at the first visit, mark them on the tree protection plan with a number and an arrow showing the direction of view, and take the same frames at every visit.

Include a scale object in shots of ground conditions, and photograph the barrier signage close enough to read it, because illegible signage is itself a departure from the standard specification.

The fence line check has a fixed list and it is worth working through it in the same order every time.

• Barrier on the approved line, with no section moved, removed or displaced.
• Barrier structurally sound and braced, and not being used as a leaning post for materials.
• Signage present, legible and attached at intervals.
• No materials, spoil, skips or plant stored inside the exclusion zone.
• No wheel tracks, rutting or standing water inside the zone.
• No excavation, trenching or service runs inside the zone other than as approved.
• Ground protection in place and intact where the method statement requires it.
• No fires, fuel storage, cement washout or chemical storage within or draining into the zone.

Scaffold and site access are the two recurring causes of departure, and the specification issues behind them are covered in the discussion of scaffolding and site access within a root protection area.

Reporting incursions and remedial action

An incursion is not a disaster provided it is reported and remedied. An unreported incursion discovered by the tree officer on a site visit is a different matter entirely, because it puts the whole monitoring record in doubt.

So report promptly, in writing, with photographs, and with a remedial proposal rather than an apology. Remedies that authorities accept include decompaction by air spade with incorporation of organic matter, mulching, irrigation through the following growing season, crown management to reduce stress loading, and in the worst cases a revised protection arrangement with a tighter monitoring interval.

Where a root has been severed, record the diameter, the position, the method of severance and the treatment, because that detail determines whether the tree is likely to survive and it is the first thing a later assessment will look for. Service trenching is the usual cause, and the approach set out for utility trenching close to trees on a development site prevents most of it.

Keep a running incursion log across the whole project, separate from the individual reports. When a bond release is negotiated, that log is the document that gets scrutinised.

Who the report is addressed to

Send it to the case officer named on the decision notice and copy the authority's tree officer, and upload it through the authority's planning portal against the application reference so it lands on the public file.

Email to an individual officer is not submission. Officers change roles, mailboxes are not part of the application record, and an authority asked to discharge a condition will search the file rather than their inbox. A report that exists only in a consultant's project folder has not been submitted, whatever the covering email says.

Keep a submission log with the date, the method, the reference and an acknowledgement. On a two-year build with monthly reports that log is 24 lines and it is the difference between a smooth discharge and a dispute.

Final compliance and sign off

The discharge application is made under the procedure for approval of details reserved by condition, with a fee per request set by the fees regulations. Those fees are indexed annually from 1 April, so check the current schedule rather than a figure from an old job. The determination period is eight weeks.

The final submission should contain a completion report rather than just the last monitoring report. It needs a list of every visit with dates, confirming the schedule was met, a summary of every departure and its remedy with cross-references to the report in which each was closed, a final condition assessment of each retained tree against the baseline, and photographs from the fixed points.

Where a tree bond or a financial guarantee secured by planning obligation is in place, the completion report is also the document that releases it, and the arrangements for that are set out in the look at tree bonds and financial guarantees secured by planning obligation. The baseline against which the final assessment is made comes from the original tree survey and arboricultural impact assessment, which is why that survey needs to be detailed enough to compare against.

What happens when visits are missed

The authority cannot discharge a condition that required reports it never received, and it has no power to pretend the visits happened.

Three consequences follow. The condition stays undischarged, which shows on a search and which a purchaser's solicitor will raise. The authority may serve a breach of condition notice under section 187A of the 1990 Act, against which there is no appeal. And any bond or guarantee stays in place, with the authority entitled to apply it to remedial works it considers necessary.

The practical route back is an honest retrospective submission: a report stating which visits took place and which did not, an assessment of current tree condition, an explanation of what cannot now be evidenced, and a proposal for an extended post-completion monitoring period to demonstrate the trees have survived. Authorities accept that more often than developers expect, because the alternative is enforcement over trees that are still standing.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. For specialist technical reports, qualified professional input may be required, and arboricultural monitoring must be carried out by a suitably qualified arboriculturist. You can enter the site postcode to see which reports a scheme is likely to need.