{"resourceId":"lebanon-mo-alpr-audit-transparency-202609","versions":[{"version":"external-a0dfc7cb8c3893f4cdd19beb93d3fe9ffa3899c004e4da38afe78060ecd90a2b","resource":{"id":"lebanon-mo-alpr-audit-transparency-202609","title":"Lebanon, MO publishes monthly ALPR audits and disables Genetec after EO 26-18","organization":"Lebanon Police Department (City of Lebanon, Missouri)","sector":"Local law enforcement / municipal transparency","geography":"Lebanon, Missouri, United States","publishedAt":"September 2026 (page current; Genetec update references Sept. 16, 2026 EO)","publicationDate":"2026-09-16","eventDate":"2026-09-16","sourceName":"City of Lebanon, Missouri official website","sourceLabel":"Lebanon PD ALPR Audit & Transparency portal","sourceUrl":"https://lebanonmissouri.org/1081/ALPR-Audit-Transparency","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model","accessibility-workforce"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"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.","caveats":"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.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Lebanon’s portal is a compliance-and-transparency proof point for ALPR programs under new state floors—not a sales case for more cameras. Help cities publish monthly search-vs-read metrics, map multi-vendor inventories, and plan orderly vendor disablement when EO/statute changes hit. Stakeholders are chiefs, council (who bought Flock before finishing a use ordinance), and residents using transparency portals. Bound value to auditable reporting; do not claim clearance-rate benefits from these counts alone.","engineering":"Engineering framing: instrument ALPR stacks so monthly exports distinguish Flock/Axon searches from Genetec-style camera reads, support public portals, and allow rapid vendor cutover when statewide rules change. Prerequisites include search logs by officer/category and a kill-switch for noncompliant streams. Constraints include three parallel vendor systems and EO-driven sudden offline status. Proof of value is reproducible monthly tables plus verified zero access to disabled streams after credential revocation.","delivery":"Delivery framing: operationalize monthly audit publication, finish the local use ordinance that still lags the December 2025 purchase, and document Genetec disablement for auditors. Dependencies include vendor transparency portals, council ordinance drafting, and state EO interpretation. Ownership sits with LPD command with city IT supporting portals. Acceptance means published month-end reports and confirmed Genetec inaccessibility. Risks include purchase-before-policy sequencing and public confusion between reads and searches."},"roleDetails":{"sales":{"customerProblem":"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)"],"discoveryQuestions":["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?"],"valueHypothesis":"Bounded value is public auditability and EO-responsive operations—not crime-outcome proof from the published counts.","potentialEngagement":"2–4 week ALPR transparency standup: unify multi-vendor metrics, draft public table, and document disablement procedures.","unsupportedClaims":["That low search counts prove no privacy risk","Guaranteed EO compliance for all Missouri cities","Effectiveness of Flock for clearance rates from this page"]},"engineering":{"fit":"Small-city multi-vendor ALPR with public monthly reporting and EO kill-switch needs.","architectureIntegration":"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.","proofOfValue":["August-style monthly table published on schedule","Confirmed zero Genetec accessibility post-disable","Public portals linked and reachable"]},"delivery":{"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.","skillsAdoption":"Train staff on which systems remain searchable and how to categorize searches for public reports.","governanceCheckpoints":["Month-end report posted","Genetec disability verified","Use-ordinance hearing scheduled"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-09-23T03:16:45Z","enrichedAt":"2026-09-23T03:16:45Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Publishing officer-level breakdowns (linked reports) requires records capacity and clear redaction rules; officers need training on search categorization used in public tables.","procurementImplications":"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.","operatingModelImplications":"Monthly audit publication plus EO-triggered vendor disablement becomes part of routine ALPR operations, not a one-time project.","sourceVerification":{"openedUrl":"https://lebanonmissouri.org/1081/ALPR-Audit-Transparency","referenceExcerpt":"the Lebanon Police Department has disabled its Genetec camera system and it is no longer accessible.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}