From the Public Safety edition of October 13, 2026
Richmond, Va., ends its Flock ALPR deal but keeps other plate-reader vendors on the table, citing lost regional integration
City of Richmond and Richmond Police Department (reported by VPM) · Policing / automated license plate readers · Richmond, Virginia, United States
- Publisher
- VPM
- Original publication
- Oct. 13, 2026
- Source retrieved
- 2026-10-14
- Event date
- 2026-10-13
What happened
Richmond will not renew its Flock ALPR contract, which runs to June 30, 2027 and cost $285,000 in fiscal 2027, after Henrico County decided to end its own Flock contract a month early. Mayor Danny Avula said the city may still pick another ALPR vendor and that utility falls when the system cannot join a regional network. RPD runs 99 fixed ALPRs and a separate Flock gunshot-detection contract. The chief wants use tailored to murder cases and missing people and will keep publishing misuse cases.
Why it matters
Richmond shows that dropping one ALPR vendor is not dropping ALPR: the decision turns on regional data-sharing, narrowed use cases and state law, which is the requirements set a replacement procurement would face.
Evidence and measured results
Opened original source from VPM and drew findings from its text. Report of officials' statements at a crime briefing; no crime-solving data, misuse counts or replacement plan are given. Statewide legislation is pending in the 2027 session.
Limitations and uncertainty
No replacement decision or outcome data; depends on 2027 Virginia legislation.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-14; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Richmond is losing its Flock ALPR network and regional integration but wants to keep some plate-reader capability with community support.
- Stakeholders
- Mayor Danny Avula
- Police Chief Rick Edwards
- Richmond City Council
- Henrico County and regional partners
- Residents on both sides
- Virginia legislators
- Discovery questions
- Which use cases would the city permit in a successor system?
- Would a regional or state-managed network be acceptable?
- What happens to stored Flock data at contract end?
- How will 2027 legislation change requirements?
- Value hypothesis
- Clear use limits and regional data rules could give officials a basis to decide on any successor; no crime outcome is assumed.
- Potential engagement
- Vendor-neutral ALPR requirements and regional data-sharing options study before any new procurement.
- Unsupported claims
- ALPR reduces violent crime in Richmond
- Community consensus on surveillance
- A state network will exist
Pre-sales engineering
Role takeaway
- Fit
- Cities replacing or re-scoping ALPR networks where regional partners are leaving the same vendor.
- Architecture and integration
- Design plate-data sharing across jurisdictions with agency-owned data and auditable queries, separate from gunshot-detection systems.
- Prerequisites
- Inventory of 99 fixed sites
- Data-sharing agreements
- Draft use policy
- Legislative outcome
- Constraints
- Flock contract ends June 30, 2027
- Pending 2027 Virginia legislation
- Neighboring agencies' vendor choices
- Security
- Restrict queries by purpose, log every search, and block sharing with outside agencies not covered by policy.
- Proof of value
- Audit log review of current searches by purpose
- Regional sharing test under agency-owned rules
- Data deletion certificate at Flock exit
Delivery
Role takeaway
- Work
- Run community listening, align with 2027 legislation, define use limits, then decide on and procure any successor while winding down Flock.
- Dependencies
- Council direction
- Regional partner decisions
- General Assembly outcome
- Vendor exit terms
- Ownership
- Richmond Police Department with the Mayor's office
- Skills and adoption
- Investigators need procedures for tailored uses and for the gap period if no successor is in place by June 2027.
- Governance checkpoints
- Community input summary
- Post-session legal review
- Successor decision
- Flock data exit verification
- Acceptance criteria
- Proposed: written permitted-use policy before any new contract
- Proposed: published misuse reports continued
- Proposed: verified Flock data handling at contract end
- Risks
- Loss of investigative capability
- Misuse in a successor system
- Regional fragmentation
- Legal change mid-procurement
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?
Design plate-data sharing across jurisdictions with agency-owned data and auditable queries, separate from gunshot-detection systems.
Governance
Who approves, reviews and stays accountable for outcomes?
Run community listening, align with 2027 legislation, define use limits, then decide on and procure any successor while winding down Flock.
Security and privacy
What data, permissions and controls need testing?
Restrict queries by purpose, log every search, and block sharing with outside agencies not covered by policy.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Investigators need procedures for tailored uses and for the gap period if no successor is in place by June 2027.
Procurement
What should contracts, pricing and exit terms secure?
Vendor-neutral ALPR requirements and regional data-sharing options study before any new procurement.
Operating model
Which teams own the service once it runs?
Operational owner: Richmond Police Department with the Mayor's office.
Publication history
- 2026-10-13Public Safety · Issue 366 resources
Stable resource ID: richmond-va-flock-nonrenewal-other-alpr-vendors-open-20261013