# T035 — Lonoke Required Case Numbers vs Public Search Audit Lonoke Policy 10.16 says deputies shall place a related CAD call or incident-report number in the Search tool's Case Number field. The vendor portal's 104-row public audit shows that field blank in 100 rows. Because every visible user ID is masked and the export does not define whether each row belongs to a Lonoke deputy, a dispatcher, or a network-shared user, the evidence raises a configuration and compliance question without proving a policy violation. ## Statement A > "When using the 'Search' tool, deputies shall input the related CAD call number or incident report number in the 'Case Number' field." ([[Lonoke County ALPR Policy 10.16]], `738.FOIA...pdf`, p. 31). The next clause requires deputies to enter the most accurate applicable justification in the Search Reason field (same page). ## Statement B The portal's downloadable audit contains 104 unique rows from 2026-06-29 through 2026-07-27. The `caseNumber` field is blank in 100 and populated in four. All 104 `userId` values are `***`, and `networkCount` ranges from 1 to 6,257 (vendor primary/self-description, [Lonoke County AR SO Transparency Portal](../../web%20archive/2026-07-28/transparency.flocksafety.com/lonoke-county-ar-so.md), companion CSV). ## Why it matters If the rows are Lonoke deputies' Search-tool uses, the 100 blanks conflict with the local mandatory-field rule and may indicate that the platform does not technically enforce the policy. If the public export suppresses case numbers, includes other organizations' users, or represents a different search path, the apparent conflict narrows or disappears. The distinction also affects auditability: a reason string such as `investigation` is not the CAD/report cross-reference the policy requires. ## Resolution status `open` — resolve through the tenant's field configuration, a data dictionary for the public audit, unmasked agency/role attribution with personal identities redacted, and the policy-required random browsing-audit records. ## Discovery Surfaced on 2026-07-28 by comparing Policy 10.16, p. 31, to the live portal's downloadable public-search CSV. ## Notes The public CSV is vendor-hosted web evidence. The Sheriff's Office directed the requester to it, but it is not a Tier-1 agency-produced audit file.