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

Decision - General Fund Budget Planning and Resource Update 2025-26

Brighton and Hove Cabinet Decided 26 Sep 2024 approved GET /api/coverage
Decision maker
Cabinet
Report author
Nigel Manvell
Published
27 Sep 2024
Reference
7293

As published

the council's own words, unedited

This report presents the General Fund resource and cost estimates for 2025-26 and the 4-year MTFS period for noting. The report also seeks approval of the approach for setting the annual revenue and capital budget for 2025-26.

That Cabinet: 1) Note the planning assumption of a Council Tax increase of 2.99% over the 4-year Medium-Term Financial Plan period and an Adult Social Care Precept of 2.00% or the equivalent in grant funding in 2025/26. 2) Note the funding assumptions and net expenditure projections for 2025/26 including a projected budget shortfall of £36.730 million. 3) Note the Medium Term financial projections for 2025/26 to 2028/29 and the predicted budget gaps totalling over £105 million over the period. 4) Note the proposed budget development approach and that members will use this to develop 4-year medium-term service and financial plans and proposals for Budget Council consideration, including detailed budget proposals to set a legally balanced budget in 2025/26 and enable the Council Tax for the year to be set. 5) Note the planning assumption of recurrently funding transformation enabling resources of at least £1 million, as set out in paragraphs 7.5 to 7.6 , from the revenue budget rather than the previous practice of utilising capital receipts since 2016/17. 6) Note that projections for next year and the Medium Term Financial Plan (MTFP) will be updated following government funding announcements expected in Autumn 2024 and Spring 2025.

Parsed from the document

gpt-5.6-luna-2026-07-09 · 4576/504 tokens · 5806ms · parsed 9 Sep 2026 15:20
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 assesses financial risks affecting the council’s Medium Term Financial Plan, including inflation, pay awards, social care demand, homelessness, income shortfalls and uncertainty over future government funding. It sets out the potential financial impacts of these risks and the proposed monitoring, control and mitigation measures.

Financial impact
The report identifies potential financial sensitivities ranging from £0.193 million for a 0.1% change in the council tax base or collection rate to £5.2 million for a 1% increase in gross expenditure; these are risk estimates rather than confirmed expenditure.
Ward affected
city-wide

Stakeholders named

parsed
Council servicesCouncil taxpayersCouncil Tax Reduction Scheme claimantsBusinesses within the citySocial care providersPeople requiring social carePeople experiencing homelessnessGovernmentFurther education establishments

Next steps

parsed
  • Continue monitoring financial risks and the collection fund through budget monitoring.
  • Implement financial recovery action plans and additional spending controls where pressures arise.
  • Monitor demand-led budgets, income performance, pay awards, contract prices and savings delivery.
  • Lobby Government for additional funding where national policy or pay awards create pressures.
  • Review and update the Medium Term Financial Plan as economic conditions, funding settlements and risk levels change.

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