From the Public Safety edition of October 15, 2026
Chandler, Arizona, discontinues 40 Flock ALPR cameras after an unexplained audit anomaly and pauses renewal
City of Chandler · Policing / ALPR oversight and discontinuation · Chandler, Arizona, United States
- Publisher
- City of Chandler
- Original publication
- Aug. 7, 2026
- Source retrieved
- 2026-10-29
- Event date
- 2026-08-07
What happened
In an Aug. 7, 2026 news release, Chandler announced it will discontinue 40 fixed Flock ALPR cameras and will not renew the vendor service agreement. Officials said a routine audit—for the first time in three years—found an anomaly in Flock system use that could not be explained through standard police action, triggering investigation of possible inappropriate use and discipline. The city will strengthen future ALPR safeguards through policy revision, additional audit procedures and reporting, and may issue an RFP only after a council-approved protection package. Flock retains ownership of cameras and poles and will remove them. The program began as a March 2024 pilot (14 cameras) and expanded to 40 in May 2025. Newly relevant now because Scottsdale's Oct. 6, 2026 non-renewal path and other Arizona exits make Chandler's audit-triggered stop a peer template.
Why it matters
Primary-source example of a city ending ALPR after internal audit failure detection, with an explicit condition that stronger controls precede any re-procurement.
Evidence and measured results
Opened the City of Chandler news-center release. Official statement; does not disclose the anomaly details, volume of misuse, or investigation outcome.
Limitations and uncertainty
Anomaly not described; investigation pending in the release. August date included for why-now linkage to October Arizona exits.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- An unexplained ALPR audit anomaly forced Chandler to discontinue Flock and withhold renewal pending stronger controls.
- Stakeholders
- City council
- Police leadership
- Internal affairs/professional standards
- City attorney
- Residents
- Discovery questions
- What exactly did the anomaly show?
- Which users and partners had access?
- What audit frequency failed to catch it sooner?
- What controls would council require before RFP?
- Value hypothesis
- A published control package and completed inquiry could support a later transparent RFP; it does not restore the discontinued cameras.
- Potential engagement
- ALPR audit-anomaly after-action and pre-RFP control package for council.
- Unsupported claims
- The anomaly was criminal misuse
- Removing cameras increased crime
- Any new vendor prevents anomalies
Pre-sales engineering
Role takeaway
- Fit
- Agencies whose ALPR audit logs just surfaced unexplained use and who are pausing the platform.
- Architecture and integration
- Preserve immutable copies of query logs; decommission vendor hardware; specify required audit APIs in any future RFP.
- Prerequisites
- Forensic log export
- User access roster
- Council protection-package criteria
- Constraints
- Cameras owned by vendor
- Investigation not concluded in the release
- Arizona peer exits changing market options
- Security
- Lock accounts tied to the anomaly, retain logs beyond vendor retention and bar shared credentials.
- Proof of value
- Complete anomaly chronology
- List of access paths involved
- Draft audit procedure that would have flagged it sooner
Delivery
Role takeaway
- Work
- Investigate, revise policy, add audit/reporting and prepare council materials for any future ALPR decision.
- Dependencies
- Internal investigation
- Council calendar
- Vendor removal schedule
- Ownership
- Chandler Police Department with city management
- Skills and adoption
- Auditors need recurring ALPR log-review skills, not one-time checks.
- Governance checkpoints
- Investigation outcome briefing
- Policy revision approval
- Public protection-package vote before RFP
- Acceptance criteria
- Cameras removed per release
- Written policy and audit procedure updates
- No renewal without council-approved package
- Risks
- Incomplete public explanation erodes trust
- Neighbor sharing continues to expose Chandler plates
- Rushed RFP without controls
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?
Immediate loss of fixed ALPR coverage; any future vendor must support enhanced audit logging and city data-protection requirements before go-live.
Governance
Who approves, reviews and stays accountable for outcomes?
Treat unexplained audit anomalies as stop-ship events that pause renewal until policy and audit upgrades are council-approved.
Security and privacy
What data, permissions and controls need testing?
City seeks to protect Chandler data within ALPR systems and add reporting requirements after an unexplained use anomaly.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Investigators and auditors need clear escalation paths when logs show non-standard police action.
Procurement
What should contracts, pricing and exit terms secure?
No renewal now; possible future RFP only after public protection package approval.
Operating model
Which teams own the service once it runs?
Operational owner: Chandler police leadership with city council oversight of any future ALPR return.
Publication history
- 2026-10-15Public Safety · Issue 516 resources
Stable resource ID: chandler-discontinues-flock-alpr-after-audit-20260807