Civic Signal GUEST
ROWS
API PATHS
Docs Sign in
Browsing as a guest. A free key raises the rate limit.

Decision - Hanover & Tarner Liveable Neighbourhood

Brighton and Hove Transport & Sustainability Committee Decided 3 Oct 2023 approved GET /api/coverage
Decision maker
Transport & Sustainability Committee
Report author
Andrew Renaut
Published
17 Oct 2023
Reference
7053

As published

the council's own words, unedited

Update on project following consultation and engagement

1) That Committee agrees to note the outcomes of the consultation that has been undertaken for the preferred option for the pilot Hanover & Tarner Liveable Neighbourhood area, which indicate that the proposals do not have the full support of local residents. 2) That Committee agrees to cease work on a pilot Liveable Neighbourhood project in the Hanover & Tarner area. 3) That Committee requests that previously agreed priorities to improve pedestrian crossing facilities in Elm Grove at Hampden Road/de Montfort Road and Bonchurch Road are developed and delivered at the earliest opportunity, subject to the approval of recommendation 2.6. 4) That Committee requests that officers undertake the development and delivery of designs to upgrade the Elm Grove/Queen's Park Road junction as part of the council's programme for upgrading the city's traffic signals, at the earliest opportunity, subject to the approval of recommendation 2.6. 5) That Committee requests that officers assess the existing crossing point at the Queen's Park Road/Egremont Place/West Drive junction, and the possible introduction of vehicle activated speed signs in Queen's Park Road as part of the council's Safer, Better Streets prioritisation framework, at the earliest opportunity. 6) That Committee requests that officers seek the necessary approvals from the Strategy, Finance and City Regeneration Committee to reallocate £400,000 from the £1.0 million budget allocation previously made to the Hanover & Tarner Liveable Neighbourhood pilot project from the Carbon Neutral Fund, to the Local Transport Plan capital programme to enable the work referred to in recommendations 2.3 and 2.4 of this report to be commenced.

Parsed from the document

gpt-5.6-luna-2026-07-09 · 2829/829 tokens · 7147ms · parsed 9 Sep 2026 12:09
Everything below was read out of a PDF by a model It is useful and it is not authoritative. The document it came from is linked in the rail, and where the two disagree the document is right.

The February 2023 engagement gathered residents’ views on proposed changes to Elm Grove, Queen’s Park Road and Egremont Place. Feedback focused on reducing traffic speeds, improving crossings and cycling facilities, protecting or managing parking, adding greenery, improving accessibility and addressing concerns about displaced traffic.

Recommendation
No formal recommendation is stated; the feedback proposes considering traffic-calming, safer crossings, cycle infrastructure, parking and enforcement measures, greening, improved accessibility, bus-routing changes and traffic reduction targets.
Financial impact
none stated
Ward affected
Hanover & Tarner

Stakeholders named

parsed
local residentspedestrianscyclistspeople with disabilitiesbus usersmotoristsschool userslocal businessesemergency services

Next steps

parsed
  • Consider the engagement feedback when developing the Hanover & Tarner Liveable Neighbourhood scheme.
  • Assess proposals for traffic calming, safer crossings, cycling, parking, greening, accessibility and traffic reduction.
  • Consider further investigation of bus routing, pollution monitoring, enforcement and displaced traffic.

Precedents

not built
"Decided elsewhere" is not built Finding the same decision in other councils needs semantic matching over decision text, which is part of the search rewrite. Until then, the council's own decisions list is the way through.
Documents
Who voted
Not extracted
Recorded votes are published in the minutes but we do not yet parse them into a direction per councillor. This page will not guess at one.
Watch this
Not built
Following a decision would ask you for a channel — email or webhook — at the point of following, with no default. Neither channel exists yet.
GET /api/coverage