From the Public Safety edition of September 22, 2026
Lebanon, MO publishes monthly ALPR audits and disables Genetec after EO 26-18
Lebanon Police Department (City of Lebanon, Missouri) · Local law enforcement / municipal transparency · Lebanon, Missouri, United States
- Publisher
- City of Lebanon, Missouri official website
- Original publication
- September 2026 (page current; Genetec update references Sept. 16, 2026 EO)
- Source retrieved
- 2026-09-23
- Event date
- 2026-09-16
What happened
Lebanon Police Department published a public ALPR Audit & Transparency page stating it has audited ALPR/camera systems monthly since February 2026 and is releasing the full February–August 2026 history. The published table shows August 2026 totals of 298 Flock searches, 9 Axon searches, and 763,078 Genetec camera reads (June peaked at 3,349,090 Genetec reads with 359 Flock and 108 Axon searches). The department explicitly distinguishes automatic camera reads from investigator-initiated searches. Citing Governor Kehoe’s Sept. 16, 2026 EO 26-18, Lebanon states it has disabled its Genetec camera system and that it is no longer accessible; future reports will omit Genetec reads until status changes. The page also links Flock and Axon public transparency portals and notes December 2025 council approval of Flock purchase (Ordinance 7204) as separate from a still-proposed use ordinance.
Why it matters
Concrete municipal policing example of ALPR multi-vendor inventory, quantitative monthly audit publication, and operational response to statewide AI/surveillance guardrails—core public-safety oversight, not emergency services.
Evidence and measured results
Primary municipal web publication with monthly numeric table and EO-linked Genetec disablement statement. Full per-officer/case-type reports are linked as available below the table; this inspection used the summary table and narrative. No independent re-audit of search legitimacy.
Limitations and uncertainty
Page does not publish misuse determinations or hotlist-hit outcomes in the summary table. “As of today” Genetec disablement lacks a precise timestamp beyond the EO date reference. City-authored transparency, not an independent inspector-general audit.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- After buying ALPR gear, the city must show residents monthly usage facts and respond when statewide EO rules change mid-deployment.
- Stakeholders
- Police chief
- City council
- City attorney
- Residents / transparency advocates
- Vendor account managers (Flock/Axon/Genetec)
- Discovery questions
- Do you publish monthly search counts by system?
- Can you disable a vendor stream within days of a state order?
- Was a use ordinance enacted before or after purchase?
- How do you explain camera reads versus investigator searches?
- Value hypothesis
- Bounded value is public auditability and EO-responsive operations—not crime-outcome proof from the published counts.
- Potential engagement
- 2–4 week ALPR transparency standup: unify multi-vendor metrics, draft public table, and document disablement procedures.
- Unsupported claims
- That low search counts prove no privacy risk
- Guaranteed EO compliance for all Missouri cities
- Effectiveness of Flock for clearance rates from this page
Pre-sales engineering
Role takeaway
- Fit
- Small-city multi-vendor ALPR with public monthly reporting and EO kill-switch needs.
- Architecture and integration
- Flock/Axon query logs + Genetec read counters → monthly ETL → public HTML table; access control to disable Genetec endpoints after EO.
- Prerequisites
- Vendor audit/API or portal exports
- Officer and category coding
- Change-control for system disablement
- Constraints
- Three vendor platforms
- Genetec reads unavailable before June 2026 in table
- Proposed use ordinance not yet passed
- Security
- Ensure disabled Genetec credentials revoked; restrict who can run searches; keep audit exports immutable.
- Proof of value
- August-style monthly table published on schedule
- Confirmed zero Genetec accessibility post-disable
- Public portals linked and reachable
Delivery
Role takeaway
- Work
- Monthly audit production, Genetec shutdown, ordinance completion, and resident communication distinguishing reads vs searches.
- Dependencies
- Vendor portal access
- Council ordinance process
- EO 26-18 interpretation
- Ownership
- Lebanon PD command with city communications support.
- Skills and adoption
- Train staff on which systems remain searchable and how to categorize searches for public reports.
- Governance checkpoints
- Month-end report posted
- Genetec disability verified
- Use-ordinance hearing scheduled
- Acceptance criteria
- Feb–Aug history public
- Genetec marked offline in future reports
- Ordinance status tracked separately from purchase
- Risks
- Transparency without misuse findings
- Residual Genetec access if credentials linger
- Policy lag behind hardware purchase
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?
Multi-vendor ALPR environments (Flock, Axon, Genetec) need unified audit reporting that separates passive reads from active searches and can take a vendor stream offline when statewide rules change.
Governance
Who approves, reviews and stays accountable for outcomes?
Publishing monthly search counts and disabling a system after a state EO shows transparency plus compliance action; remaining governance gap is the still-proposed local use ordinance after equipment purchase.
Security and privacy
What data, permissions and controls need testing?
High passive-read volumes (millions/month) underscore mass location capture even when active searches number only hundreds; disabling Genetec after EO reduces one capture path.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Publishing officer-level breakdowns (linked reports) requires records capacity and clear redaction rules; officers need training on search categorization used in public tables.
Procurement
What should contracts, pricing and exit terms secure?
Lebanon’s sequence—purchase approved Dec. 2025 before a finished use ordinance—shows procurement should couple camera buys with enforceable use rules and multi-vendor exit/disable clauses.
Operating model
Which teams own the service once it runs?
Monthly audit publication plus EO-triggered vendor disablement becomes part of routine ALPR operations, not a one-time project.
Publication history
- 2026-09-22Public Safety · Issue 164 resources
Stable resource ID: lebanon-mo-alpr-audit-transparency-202609