From the Public Safety edition of November 3, 2026
Little Rock board fails to advance a police surveillance oversight ordinance with monthly misuse audits and retention limits, a month after three officers were relieved over plate-reader misuse
City of Little Rock Board of Directors / Little Rock Police Department · Policing / surveillance technology oversight · Little Rock, Arkansas, United States
- Publisher
- KATV
- Original publication
- KATV, Nov. 2, 2026 (updated 10:13 PM Central)
- Source retrieved
- 2026-11-04
- Event date
- 2026-11-02
What happened
KATV reported that the Little Rock Board of Directors did not reach agreement on Nov. 2, 2026 on the Police Surveillance Technology Reporting Ordinance and will revisit it later; the Arkansas Democrat-Gazette reported it failed to advance. The ordinance would require the Little Rock Police Department to run monthly audits for misuse of surveillance tools including Flock license plate readers and facial recognition, publish an annual report on use, arrests and policy violations, delete plate-reader data after 150 days and other surveillance data after 180 days, discuss purchases of $50,000 or more in public, and disclose trials before purchase. It followed an audit finding one officer searched the same plate 28 times in 10 days, after which three officers were relieved of duty with pay. A similar ordinance failed last December.
Why it matters
A concrete local control package (monthly audits, retention limits, purchase and trial disclosure) that stalled even after documented misuse, showing the politics of surveillance oversight.
Evidence and measured results
Opened and read the KATV article, including its post-meeting update. The Democrat-Gazette report was opened but is paywalled beyond its first paragraph; it confirms the measure failed to advance.
Limitations and uncertainty
Ordinance text was not opened; vote details and reasons for the stall are not reported; facts from local news.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Police surveillance tools face public distrust after misuse, and oversight rules may stall.
- Stakeholders
- Police chief
- Internal affairs
- City board members
- City auditor
- Discovery questions
- Can we export every query with officer and case number?
- What retention period do we use now?
- Who reviews audit findings?
- Value hypothesis
- Voluntary audits and reporting can protect tools and trust before rules are set.
- Potential engagement
- Audit and transparency program for plate readers and facial recognition.
- Unsupported claims
- That the ordinance is dead
- That audits stop misuse on their own
- Arrest counts attributed to the tools
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any agency using Flock or facial recognition.
- Architecture and integration
- Exports of vendor query logs to an audit tool with rules for unusual patterns and a reporting dashboard.
- Prerequisites
- Query logs with case reason
- Retention configuration access
- Audit reviewer
- Constraints
- Vendor log formats
- Staff time
- State records law
- Security
- Restrict access, log every search with a reason, and enforce deletion schedules.
- Proof of value
- Run pattern rules on three months of logs
- Verify deletion at 150 days
- Draft annual report
Delivery
Role takeaway
- Work
- Stand up monthly audits, an annual report and trial disclosure.
- Dependencies
- Vendor log access
- City auditor support
- Policy update
- Ownership
- Police chief with internal affairs and city auditor.
- Skills and adoption
- Supervisors need training to review audit flags and act on them.
- Governance checkpoints
- Audit policy approved
- First monthly audit completed
- Annual report published
- Acceptance criteria
- Monthly audits on schedule
- Retention verified
- Violations reported publicly
- Risks
- Vendor log limits
- Political conflict
- Audit fatigue
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?
Monthly misuse audits require query logs with officer identity and case reason that can be reviewed in bulk.
Governance
Who approves, reviews and stays accountable for outcomes?
The proposal ties surveillance tools to public reporting and pre-purchase disclosure; without it, oversight depends on internal audits.
Security and privacy
What data, permissions and controls need testing?
Retention limits of 150 and 180 days would cap exposure; repeated searches of one plate show insider misuse risk.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Audits and annual reports add work for police staff or the city auditor.
Procurement
What should contracts, pricing and exit terms secure?
Disclosure of trials and public discussion of purchases over $50,000 would bring free pilots into view.
Operating model
Which teams own the service once it runs?
Agencies can adopt monthly audit and annual reporting voluntarily while councils debate.
Publication history
- 2026-11-03Public Safety · Issue 585 resources
Stable resource ID: little-rock-board-stalls-police-surveillance-technology-ordinance-monthly-audits-after-flock-misuse-20261103