{"resourceId":"franklin-county-oh-sheriff-flock-audit-deputy-suspended-division-majors-oversee-alpr-access-20261030","versions":[{"version":"external-752d9c558e1d60c3b10444a7a293f39cf83808fc395b491e1667105afb178039","resource":{"id":"franklin-county-oh-sheriff-flock-audit-deputy-suspended-division-majors-oversee-alpr-access-20261030","title":"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","organization":"Franklin County Sheriff’s Office (Ohio)","sector":"Policing / automated license plate readers","geography":"Franklin County (Columbus), Ohio, United States","publishedAt":"Franklin County Sheriff’s Office news release, Oct. 30, 2026","publicationDate":"2026-10-30","eventDate":null,"sourceName":"Franklin County Sheriff’s Office","sourceLabel":"Conclusion of Flock Camera System Investigation & Disciplinary Action","sourceUrl":"https://sheriff.franklincountyohio.gov/About-Us/Public-Affairs-Media-Relations/2026/Conclusion-of-Flock-Camera-System-Investigation-and-Disciplinary-Action","evidenceClass":"government-audit","outcomeClass":"mixed","topics":["data-security","governance-procurement","operating-model"],"finding":"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.","sledRelevance":"Shows an agency audit catching insider misuse and producing a named oversight structure, a template others can copy and measure.","evidence":"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.","architectureImplications":"Division-level oversight needs search logs with user, time and stated reason that a major can review without vendor help.","governanceImplications":"Accountability assigned to a named rank in each division, plus regular audits; discipline included loss of system access.","securityPrivacyImplications":"Insider misuse is the documented risk here; access should be role-based and revoked on reassignment or discipline.","caveats":"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.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Franklin County ran a plate-reader audit before any scandal reached it, found one deputy’s improper use and set up division-level oversight. The buyer problem is proving that insider use is checked, not just promised. A bounded engagement could define audit frequency, sampling and reporting so the new oversight role produces evidence. Do not claim the audit found all misuse; the release gives no scope or search counts.","engineering":"Engineering framing: the new oversight depends on search logs that majors can read. Pre-sales should confirm the platform exports each search with user, plate, time and reason, and supports role-based access that is removed on reassignment. A proof of value would pull a month of logs, flag searches lacking a case number, and show access revocation in the admin console. Constraints: vendor-held logs and free-text reason fields that are hard to audit.","delivery":"Delivery framing: the work is turning “regular audits” into a repeatable procedure. Ownership sits with each division major, reporting to the sheriff’s professional standards unit. Acceptance criteria are proposals: a written audit schedule, a sampling rule, a monthly summary of flagged searches and outcomes, and access lists reviewed quarterly. Main risks: audits that lapse after attention fades and reviewers without training to spot misuse."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"A defined audit procedure turns a one-time finding into continuing evidence of control.","potentialEngagement":"Design an ALPR audit procedure, sampling plan and reporting template for division oversight.","unsupportedClaims":["That the audit found all misuse","That one deputy’s case reflects the full risk","Any deterrent effect of the suspension"]},"engineering":{"fit":"Relevant to any agency running Flock or similar plate-reader networks.","architectureIntegration":"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.","proofOfValue":["Month of logs exported and reviewed","Searches without case numbers flagged","Access revocation demonstrated"]},"delivery":{"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.","skillsAdoption":"Majors need training on reading logs and recognising misuse patterns; deputies need clear rules on permitted searches.","governanceCheckpoints":["Audit procedure approved","First quarterly audit reviewed","Access list reconciled"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-11-02T14:37:44Z","enrichedAt":"2026-11-02T14:41:23Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Majors take on audit duties; they will need training on reading search logs and spotting misuse patterns.","procurementImplications":"Contracts should guarantee agency-owned, exportable audit logs and user-level access controls.","operatingModelImplications":"Moves from ad hoc review to a standing audit role per division; frequency and metrics still need to be defined.","sourceVerification":{"openedUrl":"https://sheriff.franklincountyohio.gov/About-Us/Public-Affairs-Media-Relations/2026/Conclusion-of-Flock-Camera-System-Investigation-and-Disciplinary-Action","referenceExcerpt":"the Sheriff has instructed each Division designate a major to oversee access to the ALPR data systems","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}