Yes, you can sometimes build within a root protection area — but only using an engineered, root-friendly method (no-dig surfacing, cantilevered or pile-and-beam foundations) that a qualified arboriculturist justifies and the local planning authority approves. There is no absolute prohibition, but there is no free pass either.
If you don't yet know what an RPA is or how it's worked out, read what is a root protection area? and how to calculate a root protection area first. This guide is about what you can actually do when the design and the RPA overlap.
The default rule, and why it bends
Inside an RPA the default is: no excavation, no compaction, no level change, no material storage, no contamination. That's because the fine feeding roots a tree depends on sit in the top 600mm or so of soil — and are killed by exactly those activities, often invisibly, with the tree declining and dying back years later once the crown outgrows the surviving root system.
But BS 5837:2012 is deliberately design-led, not a blanket ban. It is a British Standard containing recommendations, not law; its whole purpose is to let trees and development coexist. So where an incursion is unavoidable, the standard expects a method that protects the roots rather than an assumption that nothing can happen. The test the tree officer applies is simple: after the works, does the tree retain enough undisturbed, viable rooting area to survive and stay healthy?
The RPA you are working against is a circle with radius 12 × the stem diameter measured at 1.5m, capped at 707m² (a 15m radius) for very large trees — or 15 × stem diameter for a veteran tree. That gives you the size of the zone you must protect or engineer around.
The engineered solutions
Three techniques do most of the work. Each avoids the two things that kill roots — cutting them and compacting the soil around them.
No-dig construction (for surfaces)
The most common solution for driveways, paths and parking within an RPA. Instead of digging out and laying a conventional sub-base, the surface is built up on top of the existing ground: a geotextile separation layer, then a cellular confinement system or geogrid filled with sharp, angular granular material that spreads vehicle and surface loads without compacting the soil beneath. Roots keep their air and water; the surface sits over them. No-dig is the go-to answer whenever the conflict is hard landscaping rather than a building. Kerb edges are usually pinned rather than dug, and finished levels rise slightly — something to design in early, because a no-dig driveway sits proud of the surrounding ground.
Cantilevered foundations
Where a structure needs to sit near a tree, a cantilevered (or transfer) foundation places the load-bearing footings outside the sensitive rooting zone and projects the structure over the RPA, so no excavation happens within it. The building oversails the roots rather than digging into them. This suits a rear extension or outbuilding that clips the edge of an RPA on one side.
Pile-and-beam foundations
Instead of continuous strip or trench foundations that would sever a wide band of roots, narrow piles are installed at intervals — minimising the ground disturbed — and a ground beam spans between them to carry the walls. Careful pile positioning, often hand-located and arboriculturist-supervised, threads the foundation between major roots. Where excavation near roots is genuinely necessary, hand-digging and precise supervised techniques replace machine trenching, with any roots over ~25mm retained and cut cleanly only as a last resort.
| Conflict | Usual method | Why it works |
|---|---|---|
| Driveway / patio / parking over RPA | No-dig cellular confinement | Builds up, no excavation or compaction |
| Extension edge clips RPA | Cantilever / transfer foundation | Loads land outside the rooting zone |
| Wall / footing crosses roots | Pile-and-beam, hand-dug piles | Threads between major roots |
| Services (drains, utilities) in RPA | Hand-dig or trenchless / thrust bore | Avoids open machine trenching |
A worked example
Take a rear extension planned near a neighbour's mature oak with a 600mm stem diameter. RPA radius = 12 × 0.6 = 7.2m (≈163m²), and part of that circle falls across the boundary onto the extension footprint. The design can't simply dig strip foundations there. The arboriculturist reshapes the RPA as a polygon (same area) where rooting is provably constrained by the existing house, specifies a pile-and-beam foundation with hand-dug piles on the RPA side, and adds ground protection and exclusion fencing for the rest. Because the oak sits over the boundary, its protection is assessed even though the applicant doesn't own it — and if it carries a TPO, works within its RPA need the tree's own council's consent as well as planning approval.
It has to be justified and approved
None of this is self-certifying. Every incursion has to be:
- Assessed in an arboricultural impact assessment that shows the effect on each affected tree; and
- Detailed in an arboricultural method statement specifying exactly how the works will be carried out, protected and supervised; and
- Shown on a tree protection plan with fencing and exclusion zones.
The method statement is frequently imposed as a pre-commencement planning condition — meaning it must be submitted to and approved in writing by the authority before any site works start, even if you already hold full planning permission. Starting before that condition is discharged can render the development unlawful. See our full guide to discharging an arboricultural condition. Construction is then usually monitored by the arboriculturist on site.
What won't fly
- Unjustified incursion. Building or hard-surfacing across an RPA with no engineered method and no justification is one of the most common reasons tree-related applications are refused or invalidated.
- Method chosen after the design is fixed. If the layout drives foundations and services straight through RPAs and only then looks for a fix, the "solution" is often a costly redesign. Work out RPAs before the layout — see the tree survey for planning.
- Ignoring protected status. If the tree also carries a Tree Preservation Order or sits in a conservation area, that's a separate consent regime on top of the planning method — planning permission alone does not authorise works to a protected tree, and unauthorised root damage to one is a criminal offence.
Local rules decide how far you can push it
There is no single national rulebook for how much RPA incursion an authority will accept, or what the tree officer expects to see in your method statement. It is set locally: each council adopts BS5837 through its own validation checklist, and each tree officer applies their own judgement on which incursions are acceptable and how much justification a given tree deserves. A no-dig detail waved through in one borough can be sent back for more detail in the next.
So before you commit to a design, check your authority's requirements. PlanWatch tracks live tree-related planning activity per council, so you can see how applications near trees are actually being handled in your area — compare, for example, Leeds, Manchester and Bristol, or find your own council from the tree-surveys hub. Note too that this guidance is England-centric: Scotland, Wales and Northern Ireland run parallel-but-distinct planning and tree-protection regimes, so verify the framework that applies where you're building.
Bottom line
Building in an RPA is a question of how, not simply whether. With no-dig, cantilever or pile-and-beam methods, justified by a suitably qualified arboriculturist and approved by the authority, sensitive schemes get built next to retained trees every day. The failures are almost always the ones that skipped the method and hoped. To scope your own site, start with a BS5837 tree survey or find a tree surveyor.