Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Public Safety edition of November 2, 2026

Independent reportingEmergingNew this fortnight

London’s Metropolitan Police opens market engagement for AI video analytics to cut manual CCTV review, targeting a three-year contract from March 2027

Metropolitan Police Service (London) · Policing / AI video evidence analytics · London, England, United Kingdom

Publisher
PublicTechnology
Original publication
PublicTechnology, Nov. 2, 2026
Source retrieved
2026-11-03
Read original source

What happened

PublicTechnology reported on Nov. 2, 2026 that the Metropolitan Police published a planning notice for market engagement on AI-enabled CCTV video analytics, to reduce manual review time and turn video into usable intelligence. Requirements quoted include evidential integrity, interoperability, scalability, lawful and ethical AI use, video ingestion, evidential workflows and integration with future digital evidence management. Suppliers had until Nov. 3 to register and must respond to a request for information by Nov. 16. The Met has not committed to procurement but expects an initial three-year contract from March 2027 with a possible two-year extension to 2032; no value is estimated. The article cites an estimate of about 940,000 CCTV cameras in London.

Why it matters

A large force defining AI video analytics requirements around evidential integrity before buying, a template other agencies can compare against.

Evidence and measured results

Opened and read the full PublicTechnology article quoting the notice. The notice itself was not opened.

Limitations and uncertainty

Planning stage only; no performance data; secondary report of a notice; UK context.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-03; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Investigators cannot review the volume of CCTV footage collected for cases.
Stakeholders
  • Investigations or digital forensics lead
  • Procurement lead
  • Data protection officer
  • Prosecutors
Discovery questions
  • How will evidential integrity be tested when AI processes footage?
  • What review time is spent today per case?
  • Which evidence system must this integrate with?
Value hypothesis
Shorter video review if analytics are validated on local case footage.
Potential engagement
Requirements and evaluation design for AI video analytics procurement.
Unsupported claims
  • Time savings
  • Improved investigative outcomes
  • Supplier capability

Pre-sales engineering

Role takeaway
Fit
Relevant to agencies with large CCTV evidence volumes.
Architecture and integration
Video ingestion and analytics feeding evidential workflows and a digital evidence management system.
Prerequisites
  • Original-file preservation
  • Format conversion
  • Audit logging
Constraints
  • Private camera format variety
  • Storage scale
  • Disclosure rules
Security
Preserve originals, log every AI query and result, and restrict access by case.
Proof of value
  • Recall test on known-event footage
  • Review-time comparison
  • Chain-of-custody check

Delivery

Role takeaway
Work
Set evaluation criteria, run market engagement, and pilot on closed cases.
Dependencies
  • Evidence management system roadmap
  • Storage capacity
  • Legal review
Ownership
Digital forensics or investigations lead.
Skills and adoption
Analysts need training to review AI-surfaced segments and record their checks.
Governance checkpoints
  • Evaluation criteria approved
  • Data protection assessment
  • Legal sign-off before evidential use
Acceptance criteria
  • Chain of custody preserved in pilot
  • Recall measured on test footage
  • Review-time change documented
Risks
  • Unvalidated analytics used as evidence
  • Integration delays
  • Cost overrun

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?

Ingestion of mixed public and private CCTV, analytics, and evidential workflows that must integrate with a future digital evidence management system.

Governance

Who approves, reviews and stays accountable for outcomes?

Lawful and ethical AI use and evidential integrity are stated requirements; how they will be tested is not described.

Security and privacy

What data, permissions and controls need testing?

Large volumes of footage of the public; data protection and compliant use are required but not detailed.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Aims to reduce officer and analyst time spent trawling footage.

Procurement

What should contracts, pricing and exit terms secure?

Market engagement before commitment, with cost drivers and affordability explicitly explored.

Operating model

Which teams own the service once it runs?

Video review shifts from manual trawl to analyst review of AI-surfaced segments, if delivered.

Publication history

  1. 2026-11-02Public Safety · Issue 575 resources
Read preserved resource versions (JSON)

Stable resource ID: met-police-market-engagement-ai-cctv-video-analytics-contract-march-2027-20261102