{"resourceId":"little-rock-board-stalls-police-surveillance-technology-ordinance-monthly-audits-after-flock-misuse-20261103","versions":[{"version":"external-66d819ce5d5508754ad0a9179f9f9d054983947337de2577c80474a530836da6","resource":{"id":"little-rock-board-stalls-police-surveillance-technology-ordinance-monthly-audits-after-flock-misuse-20261103","title":"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","organization":"City of Little Rock Board of Directors / Little Rock Police Department","sector":"Policing / surveillance technology oversight","geography":"Little Rock, Arkansas, United States","publishedAt":"KATV, Nov. 2, 2026 (updated 10:13 PM Central)","publicationDate":"2026-11-02","eventDate":"2026-11-02","sourceName":"KATV","sourceLabel":"Little Rock board to vote on ordinance boosting oversight of police surveillance tech","sourceUrl":"https://katv.com/news/local/little-rock-board-to-vote-on-ordinance-boosting-oversight-of-police-surveillance-tech-facial-recognition-license-plate-reader-technology-monthly-audits-","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","data-security","operating-model"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Monthly misuse audits require query logs with officer identity and case reason that can be reviewed in bulk.","governanceImplications":"The proposal ties surveillance tools to public reporting and pre-purchase disclosure; without it, oversight depends on internal audits.","securityPrivacyImplications":"Retention limits of 150 and 180 days would cap exposure; repeated searches of one plate show insider misuse risk.","caveats":"Ordinance text was not opened; vote details and reasons for the stall are not reported; facts from local news.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Little Rock shows that misuse findings do not guarantee new oversight rules pass. The buyer problem for police leaders is keeping public trust in plate readers and facial recognition while councils argue. A bounded engagement could set up monthly misuse audits and an annual public report the department runs on its own. Do not claim the ordinance was defeated permanently; the board plans to revisit it.","engineering":"Engineering framing: monthly misuse audits need searchable logs of every plate-reader and facial recognition query, tied to officer and case number. Pre-sales should ask whether current vendor logs can be exported, whether retention can be set to 150 days, and how repeated searches are flagged. A proof of value would run an automated rule, such as many searches of one plate in a short period, against three months of logs.","delivery":"Delivery framing: the work is building an audit and reporting routine for surveillance tools. Ownership sits with the police chief and internal affairs, with the city auditor reviewing. Acceptance criteria are proposals: monthly audit reports, a published annual summary of use and violations, retention settings verified, and trials disclosed. Main risks are vendor log limits, staff time, and political conflict if audits reveal more misuse."},"roleDetails":{"sales":{"customerProblem":"Police surveillance tools face public distrust after misuse, and oversight rules may stall.","stakeholders":["Police chief","Internal affairs","City board members","City auditor"],"discoveryQuestions":["Can we export every query with officer and case number?","What retention period do we use now?","Who reviews audit findings?"],"valueHypothesis":"Voluntary audits and reporting can protect tools and trust before rules are set.","potentialEngagement":"Audit and transparency program for plate readers and facial recognition.","unsupportedClaims":["That the ordinance is dead","That audits stop misuse on their own","Arrest counts attributed to the tools"]},"engineering":{"fit":"Relevant to any agency using Flock or facial recognition.","architectureIntegration":"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.","proofOfValue":["Run pattern rules on three months of logs","Verify deletion at 150 days","Draft annual report"]},"delivery":{"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.","skillsAdoption":"Supervisors need training to review audit flags and act on them.","governanceCheckpoints":["Audit policy approved","First monthly audit completed","Annual report published"],"acceptanceCriteria":["Monthly audits on schedule","Retention verified","Violations reported publicly"],"risks":["Vendor log limits","Political conflict","Audit fatigue"]}},"retrievedAt":"2026-11-04T03:49:23Z","enrichedAt":"2026-11-04T03:52:08Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Audits and annual reports add work for police staff or the city auditor.","procurementImplications":"Disclosure of trials and public discussion of purchases over $50,000 would bring free pilots into view.","operatingModelImplications":"Agencies can adopt monthly audit and annual reporting voluntarily while councils debate.","sourceVerification":{"openedUrl":"https://katv.com/news/local/little-rock-board-to-vote-on-ordinance-boosting-oversight-of-police-surveillance-tech-facial-recognition-license-plate-reader-technology-monthly-audits-","referenceExcerpt":"An audit found that one officer searched the same license plate through the Flock camera system 28 times over a 10-day period.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}