From the Public Safety edition of November 1, 2026
Franklin County, Ohio, sheriff’s proactive Flock audit finds a deputy’s unauthorized use, and assigns a major in each division to oversee plate-reader access with regular audits
Franklin County Sheriff’s Office (Ohio) · Policing / automated license plate readers · Franklin County (Columbus), Ohio, United States
- Publisher
- Franklin County Sheriff’s Office
- Original publication
- Franklin County Sheriff’s Office news release, Oct. 30, 2026
- Source retrieved
- 2026-11-02
What happened
The Franklin County, Ohio, Sheriff’s Office said on Oct. 30, 2026 that it had concluded an audit of its Flock camera system, which Sheriff Dallas Baldwin started after hearing of misuse at other agencies. The audit found Deputy Robert Tischler accessed the system in a manner inconsistent with his authorized duties. He was suspended without pay for 30 days, moved from patrol to the Corrections Division and removed from Flock access. Since the investigation began, the sheriff has had each division designate a major to oversee who is authorized to use the plate-reader data systems and when, including regular audits. The release does not say how many searches were reviewed, what the deputy looked up, or how often audits will run.
Why it matters
Shows an agency audit catching insider misuse and producing a named oversight structure, a template others can copy and measure.
Evidence and measured results
Opened and read the full sheriff’s office release. Also opened WSYX ABC6 coverage, which matches the release. Audit scope, search counts and audit frequency are not disclosed.
Limitations and uncertainty
Agency self-report; audit method, number of searches reviewed and the nature of the misuse are not disclosed; the release is not an independent audit.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies need to show that insider use of plate-reader data is checked, not only promised.
- Stakeholders
- Sheriff or police chief
- Professional standards or internal affairs
- Division commanders
- County counsel
- Discovery questions
- How often will each division audit searches, and how are they sampled?
- Do search logs require a case number or reason?
- Who outside the agency sees audit results?
- Value hypothesis
- A defined audit procedure turns a one-time finding into continuing evidence of control.
- Potential engagement
- Design an ALPR audit procedure, sampling plan and reporting template for division oversight.
- Unsupported claims
- That the audit found all misuse
- That one deputy’s case reflects the full risk
- Any deterrent effect of the suspension
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any agency running Flock or similar plate-reader networks.
- Architecture and integration
- Vendor plate-reader platform with search logs and user administration; exports feed an audit workbook or dashboard.
- Prerequisites
- Exportable search logs
- Required reason or case-number field
- Role-based user list
- Constraints
- Vendor-held logs
- Free-text reasons
- Shared or generic accounts
- Security
- Role-based access, prompt revocation on reassignment, and immutable search logs.
- Proof of value
- Month of logs exported and reviewed
- Searches without case numbers flagged
- Access revocation demonstrated
Delivery
Role takeaway
- Work
- Write the audit schedule and sampling rule, train majors, and publish summary results.
- Dependencies
- Vendor log export
- Professional standards unit
- Union and discipline policy
- Ownership
- Division majors, reporting to professional standards and the sheriff.
- Skills and adoption
- Majors need training on reading logs and recognising misuse patterns; deputies need clear rules on permitted searches.
- Governance checkpoints
- Audit procedure approved
- First quarterly audit reviewed
- Access list reconciled
- Acceptance criteria
- Audit run on schedule each period
- Flagged searches resolved with documented outcome
- Summary shared with county oversight
- Risks
- Audits lapse over time
- Reviewers lack training
- Logs incomplete or vendor-controlled
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?
Division-level oversight needs search logs with user, time and stated reason that a major can review without vendor help.
Governance
Who approves, reviews and stays accountable for outcomes?
Accountability assigned to a named rank in each division, plus regular audits; discipline included loss of system access.
Security and privacy
What data, permissions and controls need testing?
Insider misuse is the documented risk here; access should be role-based and revoked on reassignment or discipline.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Majors take on audit duties; they will need training on reading search logs and spotting misuse patterns.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should guarantee agency-owned, exportable audit logs and user-level access controls.
Operating model
Which teams own the service once it runs?
Moves from ad hoc review to a standing audit role per division; frequency and metrics still need to be defined.
Publication history
- 2026-11-01Public Safety · Issue 565 resources
Stable resource ID: franklin-county-oh-sheriff-flock-audit-deputy-suspended-division-majors-oversee-alpr-access-20261030