From the Public Safety edition of November 6, 2026
Avon and Somerset Police announce Live Facial Recognition with first Bath deployment planned for 25 November, with South Wales support and PCC scrutiny
Avon and Somerset Police / Office of the Police and Crime Commissioner · Policing / live facial recognition deployment · Bath / Avon and Somerset, United Kingdom (transferable)
- Publisher
- Avon and Somerset Police
- Original publication
- Avon and Somerset Police, Nov. 5, 2026
- Source retrieved
- 2026-11-07
- Event date
- 2026-11-05
What happened
On Nov. 5, 2026 Avon and Somerset Police said it will introduce Live Facial Recognition in coming weeks, with the first deployment planned in Bath on Wednesday 25 November subject to final operational authorisation. South Wales Police will support an initial deployment using its equipment and expertise. LFR compares live CCTV faces on a closed network to a pre-authorised watchlist; officers review alerts before action; non-matches are automatically and permanently deleted; watchlists are deleted after each deployment. Deployments are to be overt with marked vehicles, signage outside the Zone of Recognition and officers available to the public. Senior officer authorisation and equality/data-protection assessments are required for each use. The PCC’s office led community, academic and resident engagement to shape scrutiny. No measured hit rates, false-positive rates or demographic performance figures are published in the announcement.
Why it matters
A transferable UK force-level LFR rollout with human review, deletion defaults and PCC scrutiny—useful contrast for U.S. SLED agencies debating watchlist FR under civil-rights constraints.
Evidence and measured results
Opened the official Avon and Somerset Police news page via HTTPS curl (User-Agent SLED-research-bot/1.0) and converted HTML to text; read in full.
Limitations and uncertainty
UK legal context differs from U.S.; announcement is prospective (subject to authorisation); no published accuracy or bias metrics; vendor stack not fully specified.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agency wants FR capability with public legitimacy and oversight.
- Stakeholders
- Chief constable/police chief
- PCC/oversight board
- Civil liberties groups
- Discovery questions
- Who authorises each deployment?
- What is deleted and when?
- What metrics will we publish?
- Value hypothesis
- Overt, time-bounded deployments with scrutiny can reduce legitimacy risk.
- Potential engagement
- LFR control framework and metrics plan.
- Unsupported claims
- UK accuracy transfers to U.S.
- That human review eliminates bias
- Crime-prevention guarantees
Pre-sales engineering
Role takeaway
- Fit
- Relevant to agencies considering watchlist LFR in public spaces.
- Architecture and integration
- Closed CCTV network, watchlist service, alert queue, deletion jobs, audit log.
- Prerequisites
- Legal basis
- Watchlist policy
- Trained reviewers
- Constraints
- Demographics performance
- Public notice
- Cross-force equipment
- Security
- Minimise retention; delete non-matches; restrict watchlist authorship.
- Proof of value
- Alert precision
- Time-to-locate metrics
- Published bias tests
Delivery
Role takeaway
- Work
- Authorise Bath deployment; staff overt posts; report to PCC; decide on permanent capability.
- Dependencies
- South Wales Police
- PCC office
- Legal
- Ownership
- Operational lead with PCC scrutiny.
- Skills and adoption
- Officers must review alerts and engage the public.
- Governance checkpoints
- Pre-deployment notice
- Post-deployment deletion check
- PCC review
- Acceptance criteria
- Authorisation on file
- Non-matches deleted
- Outcomes published
- Risks
- False matches
- Mission creep
- Legal challenge
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Closed-network CCTV, per-deployment watchlists and automatic deletion of non-matches are core controls.
Governance
Who approves, reviews and stays accountable for outcomes?
Pair every LFR deployment with published authorisation, PCC/community scrutiny and advance notice of place/time.
Security and privacy
What data, permissions and controls need testing?
Overt signage and human review reduce surprise surveillance claims but do not by themselves prove demographic fairness.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Public-facing officers must explain the tactic during deployments; training and FAQs matter.
Procurement
What should contracts, pricing and exit terms secure?
Forces may borrow experienced-force equipment first; buyers should demand outcome metrics before owning a permanent stack.
Operating model
Which teams own the service once it runs?
LFR is framed as locating wanted or high-harm people, not continuous citywide identification.
Publication history
- 2026-11-06Public Safety · Issue 615 resources
Stable resource ID: avon-somerset-police-live-facial-recognition-bath-deployment-20261105