# Lonoke County Sheriff's Office First Production The [[Lonoke County Sheriff's Office]] delivered one 16,214,648-byte PDF by email on 2026-07-28 at 13:48 CDT. Its 34 pages combine the response letter, [[Arkansas Department of Transportation|ARDOT]] Permit 1924 and the associated six-site engineering package, a customer-signed [[Flock Safety, Inc.|Flock]] order form, and Policy 10.16. The agency preserved the exact filename `738.FOIA Joshua P. Dunlap - 911 Communications camera, Flock, and access records..pdf`. SHA-256 is `f49b67be7c4352ddd543160e16435c6bd00eb7821eb4af8707c681355391ecba`. ## What's inside - [[Lonoke County Flock Contract ARDOT Permit and Camera Locations]] — pp. 3-28: Permit 1924, a six-location plan, and a $24,000 annual Flock order for three LPR-plus-fixed-video bundles and three standalone LPRs. - [[Lonoke County ALPR Policy 10.16]] — pp. 29-34: the local ALPR policy implemented 2025-07-08, including required case-number fields, alert verification, retention, browsing audits, and six-month reports. - Response letter — pp. 1-2: identifies the three supplied record categories, says other requested records are not created or stored by the agency, and directs the requester to the Flock transparency portal. ## Key takeaways 1. **Nine cameras at six exact sites.** The order form lists three `Solar Multi-Purpose LPR and Video Fixed` bundles and three standalone Flock LPRs (`738.FOIA...pdf`, p. 25). The plan's first three sites each show two `Picard` products and the final three show one, producing nine mapped device records at six exact coordinate strings (p. 9). 2. **Six LPRs and three fixed-video units.** The contract's product descriptions distinguish the bundled LPR and live-streamed fixed camera from the standalone LPR (pp. 25, 27). The live portal separately reports nine total cameras and six LPR cameras (vendor primary/self-description, [Lonoke County AR SO Transparency Portal](../../../../web%20archive/2026-07-28/transparency.flocksafety.com/lonoke-county-ar-so.md)). 3. **A $24,000 annual plan.** The customer order form has a 12-month initial term, 24-month renewals, 30-day retention, $24,000 annual recurring subtotal, and $24,000 contract total (p. 25). [[Doug Erwin]] signed the customer block on 2025-04-11; the produced Flock signature, title, and date fields are blank (p. 28). 4. **ARDOT Permit 1924.** ARDOT issued the permit on 2025-10-06 for "Installation of 6 ALPRs in Lonoke County, Arkansas" across Highways 31, 38, 70, 165, and 294 (p. 3). The applicant and ARDOT signature dates are 2025-10-07 (p. 4). 5. **Policy 10.16 requires operational controls.** Each Search-tool use must carry a related CAD call or incident-report number in the Case Number field (p. 31). The policy also requires frequent and routine random browsing audits and a six-month public-review report preserved for 18 months (p. 33). 6. **The public CSV creates a bounded case-number question.** The portal's 104-row public search audit has 100 blank visible `caseNumber` fields. Because user identifiers are masked and the CSV does not define whether every row is a Lonoke employee's search, [[T035 - Lonoke Required Case Numbers vs Public Search Audit]] remains open rather than concluding noncompliance. 7. **The response leaves a records-existence question.** The cover letter says, "The other records you are requesting are not records we create or store within our agency" (p. 2), while the produced policy says six-month reports "shall" be compiled and routine browsing audits "shall" be conducted (p. 33). [[T036 - Lonoke Required Reports and Audits vs No-Other-Records Disposition]] tracks the need for a narrow clarification. 8. **The portal documents a large configured sharing surface.** Its two labeled lists contain 741 organizations granted access to Lonoke data and 1,984 organizations sharing data with Lonoke. Those are vendor-hosted configuration entries, not proof of searches, camera-level permissions, or outcomes. ## Safety and integrity The PDF is valid, unencrypted PDF 1.7. No embedded file, JavaScript, launch action, rich media, XFA, submit action, document open action, additional action, or form widget was detected. Microsoft Defender reported no threat. All 34 pages were rendered and visually reviewed; pages 1-2 carried native text and pages 3-34 were extracted with OCR. Raw and extraction hashes were rechecked after staging. ## People and organizations - [[John Staley]] — Sheriff named on the response and Policy 10.16. - [[Michael Gebhardt]] — Chief Deputy on the 2026 response letterhead. - [[Danny Clem]] — Chief Deputy on the 2025 permit-support letter and Policy 10.16; the order form uses his agency address for accounts payable. - [[Doug Erwin]] — County Judge who signed the customer order form and permit-support letter. - [[Joseph D. Hawkins]] — ARDOT TSMO Division Head who signed Permit 1924. - [[Cody Boudreaux]] and [[Matt Triana]] — Flock permitting and project contacts on the engineering package. - [[Brittney Hall]] — main contact on the order-form cover. - [[Mark Smith (Flock Safety General Counsel)|Mark Smith]] — printed in the unsigned Flock execution block. - [[Sandra Dale]] — FOIA Coordinator who transmitted the attachment and portal link in Gmail. ## Open questions / follow-ups - Whether the agency compiled any six-month report required by Policy 10.16 § IX and Ark. Code Ann. § 12-12-1805; if none, whether the agency confirms that no report was compiled. - Whether any written finding, review record, or other retained artifact exists from the frequent and routine random browsing audits required by Policy 10.16 § VIII. - Whether the agency can export existing SharedNetworks, Network Audit/history, organization-access, role, or equivalent administrator records already available through its Flock account without creating a new compilation. - Whether the no-other-records statement covers the separate 911 Communications/PSAP operation or whether another county custodian holds those records. - Installation, inspection, acceptance, activation, relocation, removal, invoice, payment, and lifecycle records beyond the permit and customer order form.