For Lambeth Council
One clear report in, one reply out to everyone
SafeWatch.Lambeth is a free, independent residents' service. Here is what the council would receive, what we ask, and how we'd measure it — honestly.
1. Summary and aim
SafeWatch.Lambeth already lets residents raise local problems safely. Its newest part, Shared issues, lets neighbours who face the same problem flag it together. When enough of them have flagged it, our team sends the council one combined report (no names, addresses or emails) through its official route, then sends the council's one reply to everyone who flagged it — and asks them whether it got fixed.
Proposal: run it for six months in two wards chosen with the council, at no cost to the council, and publish an honest review at the end.
The aim: fewer duplicate contacts for officers, clear replies for residents, and a visible record of what happened.
2. What residents and the council are facing
- In 2024/25, 22.0% of Lambeth council tenants were satisfied with complaint handling and 44.0% said the landlord listens and acts (Lambeth, Oct 2025 (opens in a new tab)). Lambeth's own 2025 survey shows satisfaction rising by 7 points (Love Lambeth, Feb 2026 (opens in a new tab)) — this is about helping that continue.
- Stage 2 housing complaints rose from 508 to 1,342 in a year; the root causes named were delays, communication and call-backs that didn't come (Lambeth complaints report 2024/25 (opens in a new tab)).
- 3,862 councillor enquiries about housing in 2024/25 — nearly as many as formal complaints (same report).
- Nationally, what residents most want is to know which issues are being considered (47%) (Community and Engagement Survey, Aug 2026 (opens in a new tab)).
- Over 250,000 Londoners are offline (Good Things Foundation, Feb 2025 (opens in a new tab)) and about 355,000 speak little or no English (GLA, Census 2021 (opens in a new tab)).
Existing tools route individual reports well. None we found counts how many residents share one problem, with their consent, and returns one reply to all of them.
3. What it does — live now
- Shared issues: one flag per resident, with consent; staff check every issue before it goes public; one combined report at the threshold.
- Hazard fast lane: residents with damp, mould, heating, electrics, fire risk or pests are sent straight to their landlord's repairs line — they never wait for a threshold.
- Reply list: the date each combined report was sent and the date a reply came back. The council's reply is emailed word for word to the residents who flagged the issue, and published on the site only once the council agrees. No grades or "missed" labels unless the council agrees a timescale first. "No, and here's why" is a valid reply.
- "Is it fixed?": the residents who flagged it confirm. If most say it isn't, we send one follow-up to the council.
- Ward briefings: a monthly snapshot per ward, identical for every councillor of every party, paused during elections.
- The route finder: our sister site Civic.Lambeth (opens in a new tab) points residents to the council's own services, in 9 languages including Romanian, and helps them track their own reports.
4. What the council receives — and what it never receives
Receives
- One combined report per problem, through the route the council chooses
- How many residents, since when, and how many reported it themselves
- Council reference numbers — only where residents ticked to share them
- How it affects people (small numbers hidden)
- For hazards: a request to inspect the block or street — not notice about any individual home
Never receives
- Names, addresses, emails or notes
- For shared issues: photos or free text written by residents
- Anything sent automatically
- Real-time heatmaps or crime maps
- Sentiment scores or AI analysis of residents' words
Community observations are separate: our team may pass a de-identified observation, with a street-level location, to the Met's Safer Neighbourhood Team or the council (Privacy Notice).
Why no heatmaps: live counts can reveal who reported, maps can stigmatise streets, and report maps show who complains rather than where problems are. Monthly ward tables with small numbers hidden give the same insight safely.
5. Privacy, security and law
- Run by DanceOnVibes Limited (company no. 17423769), registered with the Information Commission (the ICO), no. ZC249791. Privacy Notice covers Shared issues.
- Residents consent on every flag and can withdraw it. Public numbers are rounded; exact flag times are never shown.
- Every staff action is logged. Flags are deleted 12 months after an issue closes.
- Encrypted connections (HTTPS) throughout. A data-protection impact assessment and an Online Safety Act risk assessment are in progress.
- Open legal question we'd like the council's view on: whether a combined report (no names, addresses or emails) counts as the landlord being "made aware" under Awaab's Law or the Complaint Handling Code. We treat hazard reports as if it might, and always send residents to report their own home directly.
6. Six months in two wards (proposal)
- Before starting: agree a named contact, a reply timescale, publishing replies in full, and the legal view above. Choose two contrasting wards together — one that reports a lot, one that's usually quieter — avoiding any ward with an election due.
- Months 1–2: launch through tenants' associations, community groups, libraries and WhatsApp group admins in those wards. Paper flag cards for residents who are offline.
- Months 3–5: combined reports, replies, "is it fixed?" checks and monthly ward briefings.
- Month 6: a public review against the measures below, shared with the council before publication.
7. How we'll measure it — honestly
- Working days from "enough flags" to the combined report being sent (our own reliability first)
- Council replies within the agreed time, and median days to reply
- Dated commitments kept on time
- Residents' "is it fixed?" answers, and disputed issues
- How many flaggers also hold an official council reference (we add to official channels, not compete)
- Replies delivered to everyone who flagged, within 3 working days
- Whether quieter wards are being heard (flags per 1,000 residents alongside deprivation)
- Safety: removed posts about people, data-protection complaints, near-misses
Live now: 0 shared issues published · 0 combined reports sent · 0 council replies (0 by the date we asked) · 0 of 0 commitments kept.
We won't claim changes to borough-wide satisfaction or Ombudsman figures — two wards can't move those, and they follow their own methods.
8. What we ask of the council
- One named contact in existing staff (complaints or resident services) to receive combined reports.
- A reply timescale — we suggest 20 working days, in line with the complaint codes' Stage 2.
- Permission to publish the council's replies in full, with officers' personal details removed.
- A legal view on the "made aware" question.
- Agreement on two wards.
We don't ask for money, a contract or a new post. Libraries and community hubs could optionally stock paper flag cards.
Working together: we'd welcome ideas and feedback from council teams, councillors and the local police team, whether on a small pilot, the wording of a page or getting residents to the right service first time. We have more ideas ready to discuss that could save officers time. Anything that connects to council or police systems would only happen with written agreement, and on your terms.
Contact: support@safewatchhq.com. Our sister site's page for the council: Civic.Lambeth — For Lambeth Council (opens in a new tab).
SafeWatch.Lambeth is independent and isn't part of Lambeth Council. It treats every party and councillor the same.