← All civic notes

Covington Civic Field Notes

What I heard at Covington's August 18 caucus

Meeting snapshot

Status
Advanced from caucus
Meeting
Board of Commissioners Caucus · Aug 17, 2026
Location
Covington City Hall, 20 W. Pike St., Covington, Kentucky
Attendance
Attended in part
Recording
Partial — I arrived after the meeting began. Official video not yet published; see Sources and recording below.
Next action
Aug 24, 2026
Last updated
Aug 17, 2026
  • public-safety technology
  • ALPR
  • artificial intelligence
  • city vehicles
  • storm response

What I heard

I attended part of the Covington Board of Commissioners caucus on August 18, 2026. I arrived after the meeting had begun, so my recording and notes cover only the later portion. To make the account more reliable, I compared what I heard with the City’s official agenda packet and the Police Department’s written license-plate-reader policy.

Roughly, my recording covers:

Approximate time Subject
00:00–02:43 Public Works and Code Enforcement vehicle purchases; the public purchasing process
02:44–04:20 Fiscal-year 2027 Southbank Partners contribution
04:22–06:29 Introduction to the proposed Axon technology package
06:30–07:13 Competition, integration, vendor lock-in, and data migration
07:14–09:32 Flock comparison, Axon vehicle-mounted ALPR, access, sharing, retention, and Kentucky law
09:40–14:30 Storm response, interagency work, city employees, and residents helping neighbors
~14:31 Formal adjournment

I was interested in the explanation of why purchases that are already budgeted still come back to a public agenda. The budget establishes authority, but the public meeting gives commissioners and residents another chance to see what’s being bought and ask why it’s needed.

The storm discussion gave the meeting a more human ending. Commissioners described city employees, partner agencies, and residents clearing hazards, redirecting traffic, delivering food, and checking on affected households. What stayed with me was the shift from immediate emergency work to helping people whose groceries had spoiled during outages — a practical picture of public service that doesn’t stop when the road reopens.

What the documents show

Vehicle purchases. The official packet lists:

Department Purchase Vendor Cost
Public Works Two 2027 Ford F-550 XL Super Cab 4x4 trucks Paul Miller Ford $143,938.32
Public Works Five 2027 Ford F-350 XL Crew Cab 4x4 trucks Paul Miller Ford $260,406.00
Public Works One 2027 Ford F-350 XL Regular Cab 4x4 truck Paul Miller Ford $51,085.40
Code Enforcement Two 2027 Chevrolet Equinox EVs Bachman Commercial $51,282.00
Total $506,711.72

The eight Public Works trucks total $455,429.72. The packet says the purchases use state-bid pricing.

Southbank Partners. A fiscal-year 2027 membership contribution under an interlocal partnership: $82,750, described as a one-time annual membership fee. Meeting speakers described Southbank as a partnership among Northern Kentucky river cities and mentioned examples including digital kiosks, regional riverfront or grant work, and a Latonia-focused assessment — I’m treating those project descriptions as meeting statements until I can verify their exact names independently.

The Axon proposal. Axon Enterprise Inc. proposed a 10-year agreement, expected to run from October 1, 2026 through September 2036, at a total value of $6,025,083.04. It would replace a five-year Axon agreement expiring September 30, 2026. The packet’s payment schedule shows $590,779.06 in September 2026, $117,292.80 in October 2026, and $590,779.02 each September from 2027 through 2035. The item advanced from caucus toward a legislative meeting — the paperwork points to August 25, 2026 — and was not finally approved on August 18.

Components identified in the packet include 117 body-worn-camera bundles, 117 TASER 10 plans, four Axon Fleet 3 systems, four vehicle-mounted ALPR licenses, interview-room equipment, Evidence.com storage, auto-tagging and redaction tools, transcription, the Axon AI Assistant, Draft One AI-assisted report writing, and an Axon Air/Skydio drone-as-first-responder component.

Commissioners asked whether other vendors could supply the same integrated system, whether using multiple vendors would create incompatible systems, how difficult and expensive it would be to leave Axon, how the proposed readers differ from Flock, who can search or receive ALPR data, and how long ALPR data is retained. Staff said separating from Axon and migrating City-owned data would take substantial time and additional funding — I’m attributing that as a statement made at the meeting, not an independently calculated cost.

Flock vs. Axon. Covington did not choose Flock at this meeting. A commissioner raised Flock as a comparison because it had been in the news. The proposal on the table was a 10-year Axon package containing four vehicle-mounted Axon ALPR systems. The chief described the proposed Axon readers as cruiser-mounted equipment that reads plates while officers travel, not a new network of fixed cameras. But Covington’s written policy says the Police Department uses both fixed-location and vehicle-mounted ALPR systems — the fixed equipment is operated through a partnership with the Housing Authority of Covington. So I’m not generalizing the chief’s comment into “Covington has no fixed ALPR cameras” — the accurate statement is that the four systems in this Axon proposal are vehicle-mounted.

ALPR safeguards. Covington Police General Order 40.01, revised July 29, 2026, says ALPR use is limited to trained operators for official law-enforcement purposes; anyone browsing detections has to document the reason and, when available, a case or incident number; access requires individual login credentials; officers must verify an alert matches the observed plate and validate it before taking enforcement action; an unvalidated alert can’t by itself justify restricting someone’s freedom; default retention is no more than 90 days, with stated exceptions; detection-browsing inquiries are audited every 90 days, with the auditor randomly examining at least 10 inquiries per ALPR system and reporting findings to the police chief; and the department prohibits selling ALPR images, limiting sharing to what Kentucky law allows. The policy names comparison databases including NCIC, the Law Information Network of Kentucky, law-enforcement hot lists, provider/private-entity hot lists, and hot lists maintained by Covington’s Community Liaison and Intelligence Unit. Kentucky law has specific sharing exceptions — including to law enforcement, contracted third parties, the National Insurance Crime Bureau, insurers, financial institutions, and in response to subpoenas — so I’m not stating that no one outside Covington can ever receive the data; the exceptions are real and worth naming honestly.

Storm response. Officials said the City had received 178 service calls and responded to 133 by that point in the meeting. Public Works crews cleared streets into the evening and continued street sweeping the next morning. Residents improvised barriers and helped redirect traffic around debris and downed power lines. The response expanded to food assistance after power outages spoiled groceries, with food arriving from Frankfort, and fire, Code Enforcement, and other personnel went door to door in affected areas. I’m attributing these figures and observations to comments made at the caucus unless a later City report confirms them independently.

What stood out to me

What stood out to me was how much can sit behind a short agenda description. The proposed Axon item was labeled as police equipment, software, and licensing, but the packet describes a 10-year, $6.025 million package involving body cameras, fleet cameras, TASER plans, evidence storage, mobile license-plate readers, AI-assisted report writing, and a drone component. That’s not necessarily an argument for or against the agreement — it’s a reason the public discussion should match the full scope of the decision.

My view

I was encouraged that commissioners asked about privacy and vendor lock-in. An integrated platform may save time and reduce compatibility problems, but a system becomes harder to leave the more cameras, evidence, weapons, reports, and daily workflows depend on it. My view is that capability and accountability should grow together. If Covington enters a 10-year agreement, residents should get clear performance information, meaningful audit summaries, understandable data-sharing rules, and an exit plan that protects City-owned records. I’m not treating this technology as automatically good or automatically harmful — I understand why an integrated system can reduce administrative work and make evidence easier to manage. AI-assisted reports and drone deployment, especially, deserve direct public discussion on their own terms, not just inclusion inside a larger bundle.

Questions I’m following

Axon and ALPR — Did the Board approve, amend, delay, or reject the agreement? What’s the final executed contract value? How many fixed and vehicle-mounted ALPR systems are actually active? Which external networks and hot lists are enabled? Can outside agencies search Covington data directly? How often is data retained beyond 90 days, and under which exception? Will the City publish non-sensitive summaries of its 90-day audits? How many alerts are false or need correction?

AI-assisted reports — Must officers verify every generated sentence against recordings and notes? Is AI assistance disclosed in the case record? Are prompts, drafts, and edits retained? What training and supervisory review are required?

Drone program — Which calls justify a launch, and who authorizes each flight? What geographic, warrant, and privacy rules apply? How long is footage retained? Will the City publish a flight log and aggregate statistics?

Vehicles and Southbank — Which older vehicles are being replaced, and what happens to them? What savings or service improvements result? What Covington-specific projects, grants, or outcomes has the Southbank membership actually produced?

Storm response — What final service-call and response totals did the City report? What did the after-action review identify for improvement?

What happens next

The Axon item was advanced from caucus, but it was not finally approved that evening. I’m keeping the status as “advanced from caucus” and will update this entry after the Board takes formal action — the paperwork points to a legislative meeting on August 25, 2026. I’ll also keep following the City’s ALPR audits and the rules that end up governing AI-assisted reports and drone deployment.

Sources and recording

Update history

  • August 18, 2026 — Initial entry published, based on partial attendance and my own recording, cross-checked against the official agenda and packet.