Ancient trees, missing data, and the fight over Bristol Airport’s planned expansion

So far, most of the public alarm about this expansion has centred on Felton Common, the well-loved local nature reserve on the other side of the runway, where the airport wants to plant 8.5-metre approach lights and fencing across protected grassland. Campaigners under the Save Felton Common banner have campaigned hard against that ‘land grab’, and rightly so. But the fierce fight over the Common has largely overshadowed a second, quieter yet important threat next door — the loss of irreplaceable habitat at Cook’s Farm, which has drawn far less attention. That is what our objection is chiefly concerned with.

Bristol Airport wants to grow. Its planning application (ref. 26/P/0686/OU2) seeks permission to expand from 12 million passengers a year to 15 million. To do this, the airport needs more land — including Cook’s Farm, some 24 hectares of long-established agricultural countryside where hedgerows have stood since at least the 1840s and where some trees have been growing for centuries. The airport now proposes to compulsorily purchase the site so it can carry out its plans.

However, it first needs to persuade the planners that its proposal is acceptable. We say it’s not, and we’ve lodged a detailed objection. It is a technical document, full of hectares and habitat codes, but underneath the detail is a simple story: irreplaceable habitat is at risk, the evidence supporting the plans doesn’t add up, and the law says that should matter.

Here is what our objection says, in plain terms.

The heart of it: three veteran trees

The most emotive part of the case concerns three veteran trees growing in an ancient hedgerow on the boundary of Cook’s Farm — two Ash and one Sycamore. The airport doesn’t propose to simply cut them down. Instead, it plans to translocate them: lift them with a giant tree spade and replant them on the northern edge of the development.

That might sound like a reasonable compromise, but our objections explain why it’s not in careful detail.

A veteran tree isn’t just an old tree, especially those in long-established hedgerows. It’s a whole ecosystem — cavities, rot, deadwood and fungal growth that specialist insects, fungi and other wildlife depend on and cannot find anywhere else. These features take centuries to form. You cannot manufacture them, and you cannot move them.

Worse, veteran trees are extremely unlikely to survive being moved. Their biology works against them. Over centuries they’ve spent their reserves coping with drought, storms, disease and damage, leaving little in the tank to survive the shock of relocation. Their roots are extensive but fragile, they depend on specialised underground fungal networks built up over generations, and much of their internal wood is effectively dead but structurally essential — it can’t be repaired if damaged. Successful relocation needs around two full growing seasons of careful root preparation beforehand. Crucially, the airport’s plan makes no proposal to reduce the trees’ roots at all. As our objection bluntly puts it: if the trees are translocated without root reduction, they will die.

Our conclusion is that, for the purposes of a planning decision, these three veteran trees should be treated as lost. The airport itself seems to half-accept this: it promises a ‘compensation’ package of ten new future veteran trees and the artificial ‘veteranisation’ of ten existing trees. But you can’t conjure a veteran tree on demand. Even with the right conditions, it takes two or three decades for a ‘veteranised’ tree to start resembling the real thing — and it will still lack the fungal decay that gives a true veteran its ecological value.

The evidence doesn’t add up

Beyond the trees themselves, we found that the environmental evidence supporting the application is riddled with inconsistencies. This means that the application can’t properly be decided as it stands.

The airport is required to demonstrate that it will deliver ‘Biodiversity Net Gain’ — a calculation meant to prove development leaves nature in a measurably better state (at least 10%) than it was before development. But our objection shows the numbers in the official metric calculation simply don’t match the airport’s own ecological survey. The two documents use different habitat categories, different reference codes, and don’t cross-reference each other. Some habitats that appear in the survey are missing from the metric altogether. Habitat parcels aren’t sized, and their locations aren’t shown on the map. In short, it’s impossible to reconcile the airport’s own datasets.

The tree surveys are a particular problem. Three surveys tucked into the appendices fail to meet BS5837:2012, the British Standard for trees in planning. Between them they’re missing the surveyors’ names and qualifications, survey dates, crown-spread data, branch heights and directions, life-expectancy estimates, soil assessments, and even the number of trees in some groups. One key survey dates from June 2024 and is now out of date. And when we asked for the tree schedule in a usable spreadsheet format so we could check it, our request was refused — leaving them, in their words, to analyse the data ‘as best we can’.

Even working with that inadequate evidence, their interim analysis is striking. Of roughly 1,618 individual trees on the site, some 367 — more than a fifth — are set to be removed, along with a share of the site’s hedgerows, which the airport’s own figures and the survey record in wildly different numbers (10 hedgerow parcels in one document, 71 in another).

Why this is a matter of law, not just sentiment

This is where our objection turns from ecology to policy — and it’s the part that could decide the outcome.

National planning rules are clear about irreplaceable habitats. Paragraph 193(c) of the National Planning Policy Framework says development that causes the loss or deterioration of irreplaceable habitats — and it names ancient and veteran trees specifically — ‘should be refused, unless there are wholly exceptional reasons and a suitable compensation strategy exists’.

We make two arguments about this test:

  • First, it’s a two-part test that has to be met in sequence: you need both wholly exceptional reasons and a suitable compensation strategy. A compensation package — however good, and here they say it isn’t good — cannot on its own make the reasons ‘wholly exceptional’. The decision in Juden v London Borough of Tower Hamlets [2021] EWHC 1368 (Admin) backs this interpretation.
  • Second, we argue that this scheme doesn’t clear the ‘wholly exceptional’ bar at all. The Framework’s own example of exceptional reasons is nationally significant infrastructure — the kind of once-in-a-generation project decided by government. This application, we say, is simply about increasing the capacity of an existing airport. That’s not the sort of wholly exceptional circumstance the rules have in mind.

Our objection also points to local policy. North Somerset Council’s own adopted Core Strategy (Policy CS4) requires it to protect, connect and enhance important habitats, ‘particularly designated sites, ancient woodlands and veteran trees’. The same protection is included in the Council’s emerging 2041 Local Plan. Approving the loss of these veteran trees would go against the Council’s own rules.

What it comes down to

Strip away the appendices and the acronyms, and our case is straightforward. The airport wants to expand on to land that includes centuries-old, irreplaceable habitat. Its plan to ‘move’ three veteran trees is, on the evidence, a plan to kill them slowly. The paperwork meant to justify all this is inconsistent, incomplete and in places non-compliant with the relevant standards. National and local planning policy both say irreplaceable habitat like this should be protected, not traded away for extra passenger numbers.

Our central demand is modest but firm: these problems need to be resolved before the application can properly be decided. For anyone who cares about Cook’s Farm, its ancient hedgerows and the veteran trees growing in them, that’s the line worth holding.

Here is our full response to the application:

BTF Consolidated Comments – 06 May 2026

The small-sites rule change that could quietly cost your neighbourhood its trees

From 6 August 2026, a change to the planning rules takes effect that most people will never hear about — but it could reshape the trees on our streets, in our gardens and on the small plots being built on all over the country.

Here is the short version.

What is changing

When land is developed, the law has, since 2024, usually required a small boost to nature — a “Biodiversity Net Gain” of at least 10%. In plain terms, a development is meant to leave nature a little better off than it found it.

From 6 August, the smallest sites — those of 0.2 hectares or less (about 2,000 square metres, roughly a third of a football pitch, or a small cluster of houses and their gardens) — no longer have to do this at all.

For hard-pressed small builders, that is a welcome simplification. But there is a catch for trees.

Why trees are caught in the middle

Under the old rules, removing even a single tree was usually enough to bring a small project into the nature-boost system — because of the way a tree’s protected “footprint” is measured. In practice, that meant a developer could not quietly fell a tree on a small plot without having to make good the loss.

The new rule swaps that “what is the impact?” test for a much simpler “how big is the site?” test. If the site is 0.2 hectares or smaller, the nature rules simply do not apply — however many trees are cleared.

What that means on the ground

On a site right at the new limit, the equivalent of up to 48 small trees — or around a dozen mature ones — could be removed with no requirement to replace or compensate for them under this system. And the trees most exposed are exactly the ones we tend to notice most: established trees on small urban and infill plots.

What still protects trees

It is not a free-for-all. Tree Preservation Orders, conservation-area rules and the special protections for ancient and veteran trees all still apply — they sit entirely outside this change. Some councils also have their own local tree policies: Bristol’s Tree Replacement Standard, for example, still requires replacement planting whatever the new exemption says.

The snag is that these local protections only exist where a council has actually put them in place — and not every council has.

Why it matters

The change is a sensible piece of red-tape reduction for small builders. But it is also, almost by accident, a real step back for the everyday trees that give our neighbourhoods shade, character and wildlife. From August, whether the trees near you are protected will depend less on national nature rules and more on whether your council has its own policies — and on whether a particular tree happens to be covered by an order.

If you value the trees around you, it is worth asking your local council what protections are in place.


We have set out the full detail — the mechanics, the legal position, and what to watch next — in an accompanying briefing note.

Read the full briefing note here.

The Local Nature Recovery Strategy and Bristol: a reassessment

In January 2025 we argued that the West of England Local Nature Recovery Strategy (LNRS) would do little to improve biodiversity net gain (BNG) in proposed development sites in Bristol. Since then, three things have changed enough to warrant a second look:

A follow-up to our January 2025 post, The Local Nature Recovery Strategy fails to deliver for Bristol.


  1. The emerging Bristol Local Plan has moved to the final stages of the public examination and the timetable for the 2045 Local Plan has been published.
  2. The West of England Mayoral Combined Authority (WECA) has published detailed guidance for developers and ecologists.
  3. We have been able to measure how much of the city the LNRS focus areas cover.

    These three changes mean that the picture is now more nuanced than a simple ‘fails to deliver’, but the practical conclusion is broadly the same. This post sets out why.

    What the latest LNRS has now made explicit

    WECA’s guide for planners, ecologists and developers, together with a dedicated BNG strategic-significance map, now spells out how the 15% Strategic Significance Multiplier uplift is meant to work. To attract the uplift, a proposed intervention must be in a mapped focus area for nature recovery and deliver a measure recommended (mapped) for that location.

    Two points in that guidance are worth dwelling on, because they confirm the argument we made in 2025 — this time in WECA’s own words.

    First, on baseline habitats. Our January post relied on Defra’s position that the multiplier applies only to habitats created or enhanced after development, not to what’s already on site – the baseline habitat. WECA’s FAQ now states this directly: the multiplier ‘is never applied to baseline habitats in the BNG Metric’. That is significant: it means the strategy can never reward the retention of existing habitat on a development site; but only new or enhanced habitats, and then only where a matching measure is mapped.

    Second, on where the mechanism is aimed. The single worked example in WECA’s guide is a developer purchasing off-site BNG units in a focus area. That’s a fair reflection of how the uplift is designed to behave: it’s a tool for steering off-site compensation and habitat banking towards priority locations, not something that typically assists the onsite footprint of a development itself.

    How much of Bristol is a focus area?

    In January we said it was ‘hard to imagine’ the LNRS helping on most Bristol sites, but we did not put a number on the coverage. We have now done so, using WECA’s own published data.

    Taking the Combined Authority’s mapped focus-area layer and clipping it to the official Bristol City Council boundary, 24.2% of the city — roughly 2,640 hectares of its 109 km² — lies within a focus area for nature recovery. (We checked the figure in two independent ways: a regular sampling grid and a random sample of over 90,000 points; both give 24.2%, and the method reproduces the city’s official area to within half a percent.)

    This is not a trivial share; anyone tempted to say the LNRS ‘barely touches’ Bristol should note that nearly a quarter of the city sits inside a focus area. But coverage is the wrong thing to count. That 24.2% is a ceiling — the maximum extent over which the multiplier could ever apply — before two much tighter filters are applied: the habitat being created or enhanced must match a measure mapped for that spot, and none of it can be baseline habitat.

    Coverage is not opportunity

    The more telling question is what is mapped, and where. When we count the individual measures that fall within the Bristol boundary, the focus areas turn out to be almost entirely watercourses and existing public green space that’s unlikely ever to be developed.

    LNRS measures mapped within the Bristol City boundary. Management/enhancement of existing habitat and watercourses (teal) dominates; new-habitat creation measures a developer could deliver on a site (amber) are comparatively few.

    River and floodplain measures dominate, followed by public parks & green space management and hedgerow, scrub and woodland under management. These are overwhelmingly measures for the management, restoration or enhancement of habitat that already exists — mostly along the Avon and Frome corridors, in the city’s parks, and on railway and river margins. This is land that is unlikely ever to be developed and, under the BNG regime, cannot be used to offset on-site habitat losses; BNG offsets may only be provided by registered Biodiversity Gain Sites (BGS). There are six in the LNRS but, currently, none are in Bristol.

    By contrast, the measures a developer might be able to deliver as new habitat on a site — creating woodland, hedgerows, wildflower meadow or mosaic habitat — appear only in the low tens of features and are themselves largely tied to the same green and blue corridors. So, the headline coverage figure and the practical opportunity point in opposite directions: a quarter of the city is mapped, yet the fraction of developable land where a scheme could both sit in a focus area and deliver a matching biodiversity improvement remains very small.

    The planning picture

    The wider planning position has moved on since January 2025, though not in a way that resolves the problem we identified at the time.

    Bristol’s emerging Local Plan completed its examination hearings last year with the final consultation has just completed. We are expecting the inspectors’ final report in the autumn so the plan is not yet adopted and still may not be. In the meantime, the Council having just published the timetable for the 2045 Local Plan which, when it starts this September, will not be completed until April 2029 at the earliest.

    Despite this, the two things we flagged in January still stand. No commitment has yet been made to designate any of Bristol’s focus-area sites — its parks, river corridors and green margins as BGSs available for off-site habitat mitigation — one route by which the uplift could be applied. Central Government has still not issued guidance on the role of the LNRS in planning decisions even though the Levelling-up and Regeneration Act requires plans to ‘take account’ of it. Until that guidance arrives, the strategy’s weight in day-to-day planning remains as defined under the BNG regime.

    Conclusion

    The LNRS is better documented than it was a year ago, and WECA deserves credit for setting out the mechanics clearly. On the specific question we raised in January 2025, that guidance has, if anything, confirmed our reading at the time: the multiplier cannot reward existing habitat. It is built for off-site delivery in priority locations rather than for the sites where most Bristol development happens. As none of these locations in the city are BGS sites, it is practically impossible to apply the 15% uplift they provide.

    The new coverage figure sharpens rather than softens the point. Yes, a quarter of the city is mapped as a focus area — but that land is the Avon, the Frome, in parks or railway land, all of which are already managed and enhanced in place. For a developer weighing up a site in Bristol, the chance that the strategy changes their BNG arithmetic is still low and, where it does, it will usually be through habitat bought outside the city.

    If the LNRS is to deliver the benefits promised for nature in Bristol, the gap is not in the mapping but in the mechanism: making suitable focus-area land available for off-site mitigation, and — as we suggested in January — allowing the city’s own adopted strategies, from its ecological network to its tree and green-space plans, to carry strategic significance where the LNRS does not.

    We suspect that this analysis is also likely to apply to other urban areas across England.


    Our earlier explanation of how strategic significance is assessed is set out in Assessing habitat parcels: strategic significance explained. Coverage and measure figures in this post were derived from the West of England Combined Authority’s LNRS layers on its Open Data Portal, clipped to the Bristol City Council boundary (ONS code E06000023), July 2026.

    Analytical research, policy review and initial drafting were undertaken with the assistance of Claude (Anthropic, 2025). All technical conclusions and professional judgements are those of the author.

    Understanding Biodiversity Gain Plans

    Since BNG became mandatory in February 2024, qualifying developments in England must show how they will deliver at least a 10% gain, to be set out in a Biodiversity Gain Plan (BGP) submitted to the local planning authority. We’ve transcribed 160 BGPs from 21 LPAs into a single, comparable dataset.

    What the data shows so far:

    • Just over under 60% (95 of 160) deliver their gain entirely on site. Another 34 use a mix of on-site and off-site measures, while 17 rely wholly on off-site units and 14 did not state an approach. Two bought Statutory Credits.
    • Off-site reliance is a recurring theme. A number of plans record an on-site biodiversity loss offset by purchased habitat units — a legitimate route, but one that moves the gain away from the community where the development happens.
    • Net gain has to be met habitat type by habitat type (area, hedgerow, watercourse), not as a single blended figure. Several plans that pass overall are marginal — or fall short — on an individual module.

    Accessing this data was harder than it should be:

    • There is no central register of gain plans – why can’t Defra or Natural England include them in their BGS allocation dataset? These documents should be easily accessible.
    • Each council’s portal has to be searched separately, with no consistent way of identifying the relevant application. Only a few authorities (City of York, Bristol and Cotswold among them) have a dedicated application category for BNG discharges. Otherwise the BGPs sit inside generic “discharge of conditions” applications and are very difficult to find.
    • BGPs are produced in a variety of forms – as clean PDFs, fillable forms, bespoke versions or scanned images requiring OCR – which is challenging, especially if they are hand-written.
    • They are often internally inconsistent: off-site figures just copied from the on-site section, credits confused with habitat-bank units, or headline numbers that do not reconcile.
    • Off-site claims frequently differ from what the Biodiversity Gain Sites register records as allocated.
    • Many applications do not include the required BNG Metric calculation.
    • Some applications can’t be analysed because all that is produced (and approved) is the certificate of the off-site HU purchase – and sometimes not even that. As a result, we’ve been unable to include these in our analysis.

    The information exists, but we can only conclude that the planning approval process makes meaningful public scrutiny far harder than it needs to be. Using the available standard Defra form and creating a single searchable register of BGPs would be a straightforward improvement.

    The full dataset and analysis are here — comments, corrections and more data are welcome:

    BGP Full Data Extract

    NB. This analysis will grow as we add more data.

    #BiodiversityNetGain #BNG #BGS #Planning #Nature #Transparency

    Losing our Local Green Space designations

    Are councils protecting our local green spaces? Our research reveals a worrying picture.

    Parks, playing fields, village greens and community orchards are vital for our wellbeing — places where children play, neighbours meet, and nature finds a foothold in our towns and cities. Yet our research suggests that many local councils are failing to use the powers available to them to protect these spaces, leaving them vulnerable to development and neglect.

    How we did our research

    Using Freedom of Information laws, we contacted 62 Local Planning Authorities (LPAs) across England, asking whether their current local plan includes policies protecting Local Green Space (LGS) sites, as set out in the National Planning Policy Framework (NPPF). We also asked them whether any new local plan would do so.

    The LGS designation was introduced in the NPPF in 2012 to give communities the power to protect the green areas that matter most to them. It remains part of national planning policy, and councils are expected to consider it when drawing up local plans.

    Of the 62 requests sent, 55 councils have responded (88%). Eight told us they don’t hold this information. That left 47 substantive responses from councils with real power over local green space protection. Eight councils have yet to respond. The full collated responses are available online.

    What we found: current local plans

    Of the 47 councils that gave a substantive answer, 17 — 36% — confirmed that their current local plan includes LGS policies in line with the NPPF. Twenty-three said their current plan does not, mainly because it predates the NPPF (2012). Bromsgrove, Redditch and Stoke-on-Trent all have plans dating back to 2009/2011 and so that lack LGS provisions, though Stoke’s does contain general green space protections.

    A further six councils gave qualified answers. South Hams, Stoke-on-Trent, Torbay and West Devon noted that designation of specific LGS sites has largely been left to Neighbourhood Plans. Solihull had adopted both an LGS policy and seven Neighbourhood Plans had also adopted their own LGS policies. This is a permitted approach, but one that places the burden on local communities rather than the council.

    What we found: future local plans

    The picture for future plans is only marginally better. Of the 47 substantive respondents, only 12 — 28% — gave an unqualified yes to designating LGS in their new or emerging local plan: Cheltenham, East Devon, Tewkesbury, Cannock Chase, Cotswold, Gloucester City, Bath and North East Somerset, Cornwall, North Somerset, Stratford-on-Avon, Swindon and Wyre Forest. Cotswold confirmed its 2025–43 plan will contain new LGS sites; Bath and North East Somerset (BaNES) proposes retaining and expanding its LGS policy, subject to Cabinet approval, and Stoke-on-Trent’s emerging plan contains LGS designations, a positive step for a city whose current plan predates the 2012 NPPF.

    A further nine councils said they do not intend to designate LGS at all. Birmingham will continue using strategic, criteria-based policies rather than site-specific designations. Tamworth explicitly ruled out using LGS designations, citing limited space and preferring broader open space policies. Rugby says its emerging plan ‘defers to national planning policy’, and South Gloucestershire, despite having LGS policies in its current plan, will drop them from its new one. Broader open space policies offer some protection, but not the strong protection that LGS provides.

    The largest group — 23 councils — said it was too early to tell or that no decision had been made, reflecting how slowly local plan preparation moves. Bournemouth, Christchurch and Poole, for instance, won’t be scoping consultation until June 2026.

    Solihull is currently working on a new Local Plan, and will be reviewing the status of Local Green Space sites and whether there will be any amendments or additions to these.

    The Bristol case: a warning from the front line

    Bristol offers a stark illustration of what’s at stake. While our FOI research was under way, Bristol City Council, at the request of the examining inspectors, was removing all Local Green Space designations from its emerging local plan. Its current plan had included policy GI1, designating LGS sites identified through years of community consultation involving residents, community groups and the Bristol Parks Forum (BPF), with a matrix showing how each site met the NPPF criteria.

    During examination, the inspectors rejected all proposed LGS designations as ‘not considered to be justified or effective,’ so the Council removed the policy entirely. BPF objects, pointing out that 14 sites met all five NPPF criteria and a further 27 met four, yet the Inspector rejected all designations en masse without considering the individual merits of each proposed site. BPF describe this as ‘a real disservice to the people of Bristol.’

    The Council argues Bristol’s green spaces will still be protected through ‘Reserved Open Spaces’ (now call ‘Protected Open Space’ (POS)) status, but both we and BPF reject this as inadequate. POS does not carry the same weight or permanence as LGS. Other cited designations, such as Site of Nature Conservation Interest (SNCI) status, will offer weakened protection in the new proposed local plan. BPF cites Brislington Meadows as an example of a site that lost out despite its status as an SNCI. BPF says:

    The only robust long-term protection for our locally important green spaces against development is to give a site Local Green Space designation. For a city like Bristol to have none is unbelievable.

    Notably, Bristol’s FOI response makes no mention of this removal, instead stating that under the new system introduced by the new Levelling Up and Regeneration Act 2023 (LURA), it has ‘not yet decided’ whether its new local plan will designate LGS sites.

    Both we and BPF are calling for the LGS policy and the proposed designations to be reinstated until a future local plan can provide equivalent or better protection, warning that any gap between local plans will leave green spaces exposed to development with no adequate defence.

    LURA: a planning system in transition

    Under LURA, there’s a transition deadline: plans submitted under the old system must be published by 31 December 2026. Authorities that fail to do this must use LURA’s streamlined 30-month timetable instead ­­— roughly half the current time required.

    This is, in principle, an opportunity: many councils currently without LGS policies are operating under plans that predate the NPPF, and the obligation to produce a new plan forces the issue. But the compressed timetable, reduced consultation, and a shift of generic policies to national level all create conditions in which LGS designation could be marginalised or skipped. The Bristol example, where the Inspectors rejected all proposed LGS designations en masse, demonstrates this.

    The role of Neighbourhood Plans

    Local Green Space designation has often been left to Neighbourhood Plans rather than local plans. Bristol, Plymouth, Torridge, Torbay, Rugby, Solihull and Newcastle-under-Lyme all have made Neighbourhood Plans designating LGS, even where their local plan does not. These designations carry real weight, but Neighbourhood Plans require significant community time and resource. Relying on them risks a two-tier system where well-resourced communities can protect their green spaces but those with fewer resources cannot.

    Why these issues matter

    Bristol is a symptom of a wider problem. Access to good-quality green space improves mental and physical health, supports biodiversity, helps manage flood risk, and strengthens community cohesion. In cities like Bristol — which declared an Ecological Emergency in 2019 and is involved in nature recovery initiatives — densification without adequate green space protection directly contradicts those commitments. When councils fail to use the tools available, a community may find itself powerless to save a local green space, sometimes valued for generations, once a development application arrives.

    What needs to change

    Councils preparing new local plans should treat LGS designation as a core part of the process, not an optional extra, and should engage residents early on which spaces matter most. The Planning Inspectorate should also assess LGS proposals on their individual merits rather than rejecting them wholesale, as happened in Bristol. Councils currently reviewing plans that predate the NPPF have a clear opportunity to put this right.


    What you can do

    • Get involved in your local plan consultation and make the case for LGS designation — and if your council is proposing to remove or weaken protections, say so clearly.
    • Ask your councillors whether your local plan protects local green spaces and what they’re doing about it.
    • Explore Neighbourhood Planning, which gives communities the power to designate LGS directly and may, in some cases, come with government funding.
    • Engage with council open-space strategies and green infrastructure reviews to help build the evidence base for future designations.
    • Support your local parks forum: organisations like the Bristol Parks Forum hold councils to account and amplify community voices. If your area doesn’t have one, consider helping to start one.

    The places where we walk, play, breathe and connect with each other and with nature are worth fighting for — but only if we use the planning system’s tools, hold councils to account, and make sure that our communities are genuinely heard.


    Speaking up for Bristol

    The last opportunity for us to comment on Bristol’s proposed local plan has now passed, so all we can now do is hope that the Inspectors change their minds and reverse their decision to revoke all proposed LGS designations.

    In any event, the Council assures us that it will publish its timetable for a further new local plan, as required under the new LURCA regime, by the end of June. When it does, we must insist that it reinstates its original ambition to adopt an LGS policy and designate LGS sites.


    A copy of this article is available here: Losing our Local Green Space designation – 16 June 2026

    Here are Bristol Parks Forum’s representations: Bristol Parks Forum response to Bristol Local Plan EXA064: Schedule of main modifications 11 June 2026