{"resourceId":"fairfax-county-police-lpr-947-arrests-100-percent-audit-vienna-ledger-20261107","versions":[{"version":"external-e18dc3eb79993896981071aa4ae4a506a4eb6f4197bc522255b7f21ee61a5d1c","resource":{"id":"fairfax-county-police-lpr-947-arrests-100-percent-audit-vienna-ledger-20261107","title":"Fairfax County police report 947 arrests from plate readers over four years, with every search logged to a case number and audited, while supervisors keep reviewing the Flock cameras","organization":"Fairfax County Police Department; reported by Vienna Ledger","sector":"Policing / automated license plate readers","geography":"Fairfax County, Virginia, United States","publishedAt":"Vienna Ledger, Nov. 7, 2026","publicationDate":"2026-11-07","eventDate":null,"sourceName":"Vienna Ledger","sourceLabel":"Fairfax police plate readers hit 947 arrests in four years","sourceUrl":"https://viennaledger.com/articles/fairfax-police-plate-readers-hit-947-arrests-in-four-years-mw5aw2r4","evidenceClass":"independent-reporting","outcomeClass":"mixed","topics":["governance-procurement","data-security"],"finding":"Vienna Ledger relays Fairfax County police figures on the department’s license plate reader program since November 2022: 1,670 criminal cases, 947 arrests, 578 stolen vehicles recovered worth over $9.4 million, 68 firearms and 60 missing persons located. The department says every search is tied to a case number and logged, an audit team reviews all searches, a separate AI tool flags patterns against preset criteria, a monthly report goes to a commander barred from searching, and violators must justify, are removed and retrained. Policy bars immigration enforcement use. The article also notes that on Sept. 15 supervisors voted unanimously to pause new stationary Flock cameras, and committee members questioned data storage, federal access and stalking risk; no votes were taken Oct. 20.","sledRelevance":"Shows a concrete control set (case-number requirement, full audit review, commander separation) that other agencies can compare with their own, alongside the reality that local boards still pause expansion despite reported results.","evidence":"Agency-reported outcome counts relayed by local news; no independent evaluation, no comparison group, and no audit findings published in the article.","architectureImplications":"Search logging tied to case numbers and automated pattern flagging over audit logs are the technical features described.","governanceImplications":"Separating the commander who receives reports from search access, requiring written justification and retraining, and a written ban on immigration use are the stated controls.","securityPrivacyImplications":"Board members raised data storage, possible federal immigration access and stalking misuse; the article does not show how those were resolved.","caveats":"Outputs are agency counts of cases the technology contributed to, not causal effects; single county; control descriptions come from the department, not an auditor.","streamIds":["public-safety"],"roles":{"sales":"Use this as a reference model for the conversation about what responsible plate reader use looks like: case numbers on every search, full audit review, and separation of the reporting commander from search access. Offer a bounded control gap review against that model rather than promising arrests or savings, since the results are agency reported. Expect elected boards to ask about storage and federal access before approving expansion.","engineering":"The technical pattern is search logging that forces a case number, immutable logs, and automated flagging of unusual search behavior. Verify what your platforms can log and export before proposing a design, including who can query across agencies and how long data is kept. Proof of value should be audit coverage and time to review flagged searches, not arrest counts, which the article cannot attribute to the technology.","delivery":"Plan an assessment that compares an agency’s current search logging, audit sampling, supervisory reporting and violation handling with the controls described here. Name an audit owner outside the search users, set a reporting cadence, and agree what happens when a violation is found. Keep legal questions on immigration and data sharing with agency counsel, and treat the open board review as a risk to schedule."},"roleDetails":{"sales":{"customerProblem":"Boards and residents question plate reader data storage, federal access and misuse, and agencies lack a clear control model to show them.","stakeholders":["Police chief","Board or council members","County attorney","Privacy officer","IT security lead"],"discoveryQuestions":["Is every search tied to a case number and logged?","Who reviews audit results and are they separate from users?","What happens to a user found violating policy?"],"valueHypothesis":"A documented control model can ease board review of expansion; arrest or cost outcomes are not claimed.","potentialEngagement":"Short plate reader control gap review with a one-page board briefing.","unsupportedClaims":["That the program caused the reported arrests","That the controls prevent misuse","That the Flock review will end favorably"]},"engineering":{"fit":"Audit logging and review workflow for plate reader searches; not a detection accuracy evaluation.","architectureIntegration":"Connect search logs, case management numbers and audit review into one reportable record.","prerequisites":["Search log export from each vendor","Case number field available at search time","Defined retention settings"],"constraints":["Multiple vendors with different logs","Agency-reported results only","Sharing network settings may differ by vendor"],"security":"Restrict search privileges, log all queries, and review sharing with outside agencies.","proofOfValue":["Share of searches with a valid case number","Time from flagged search to review decision"]},"delivery":{"work":"Assess logging, audit and reporting practice and produce a control checklist and board briefing.","dependencies":["Vendor log access","Agency counsel input","Audit staff availability"],"ownership":"Police administration with an audit owner outside the search users.","skillsAdoption":"Train users on case-number and justification requirements and reviewers on flagged-search triage.","governanceCheckpoints":["Monthly report to command","Board review before expansion","Annual policy review"],"acceptanceCriteria":["Every search carries a case number","Audit reviews all or a defined sample of searches","Violation handling is documented"],"risks":["Board pauses expansion","Controls exist on paper but are not exercised","Vendor logs incomplete"]}},"retrievedAt":"2026-11-10T03:49:02Z","enrichedAt":"2026-11-10T03:51:29Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Audit reviewers and supervisors carry the workload of checking every search; staffing for that review is not described in the article.","procurementImplications":"Contracts with several vendors (Axon, Flock, Motorola) need comparable logging, audit export and data-sharing terms; this is interpretation, as the article does not describe contract terms.","operatingModelImplications":"A named audit team and a commander separated from search access are the operating roles described; the department reports monthly to command.","sourceVerification":{"openedUrl":"https://viennaledger.com/articles/fairfax-police-plate-readers-hit-947-arrests-in-four-years-mw5aw2r4","referenceExcerpt":"every LPR search is tied to a case number and permanently logged. An audit team reviews 100 percent of searches","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}