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

Decision - Red Routes Update

Brighton and Hove Cabinet Decided 20 Mar 2025 · effective 29 Mar 2025 approved Key decision GET /api/coverage
Decision maker
Cabinet
Report author
Charles Field
Published
21 Mar 2025
Reference
7414

As published

the council's own words, unedited

This report outlines the results of a recent trial in London Road & Lewes Road and the way forward over the next financial year, including the proposed development of a strategic plan for red routes in the city.

1) Cabinet agrees to proceed with the red route in Queens Road, as set out in Appendix 3 2) Cabinet agrees to proceed with the design and implementation of a new red route along the Western Road corridor (from Holland Road to Montpelier Road). As set out in Appendix 3

Parsed from the document

gpt-5.6-luna-2026-07-09 · 1078/466 tokens · 4609ms · parsed 9 Sep 2026 15:34
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 report found that passenger injury incidents reported by Brighton and Hove Buses fell from 14 to 2 between April and October when comparing 2023 with 2024, an approximate reduction of 85.7%. It concludes that red routes have contributed to improved passenger safety and supports their continued and expanded use.

Recommendation
Extend red routes to other high-traffic areas, continue monitoring passenger injury incident data, and run public awareness campaigns about the benefits and rules of red routes.
Financial impact
none stated

Stakeholders named

parsed
PassengersBus usersDriversBrighton and Hove BusesThe public

Next steps

parsed
  • Extend red routes to other high-traffic areas.
  • Regularly analyse incident data to measure effectiveness and make necessary adjustments.
  • Educate the public on the benefits and rules of red routes.

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