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

Decision - Life Events and Charges Review for Registration Services

Brighton and Hove Policy & Resources Committee Decided 19 Jan 2023 for determination GET /api/coverage
Decision maker
Policy & Resources Committee
Report author
Michelle Jenkins
Published
19 Jan 2023
Reference
6851

As published

the council's own words, unedited

to present registration and land charges fees & charges proposals for approval 23/24

RESOLVED : That the Committee approved the fees and charges set out at Appendix 1 of the report (as amended).

Parsed from the document

gpt-5.6-luna-2026-07-09 · 1746/379 tokens · 4611ms · parsed 9 Sep 2026 11:58
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 sets out proposed Registration Services fees for 2025/26. It includes revised charges for ceremonies, approved venues, licences and other life-events services, with most increases ranging from 7% to 16% while some fees remain unchanged.

Recommendation
Approve the proposed Registration Services fees for 2025/26.
Financial impact
None stated
Ward affected
city-wide
Decision maker
Policy & Resources Committee

Stakeholders named

parsed
people using Registration Servicesapproved venuesapproved premises

Next steps

parsed
  • Implement the proposed 2025/26 Registration Services fees if approved.

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