The problem is visible before any legal argument begins. The Sheriff’s own Warrant Details report was printed July 15 under a named login. It carries a warrant issued in May 2026 on a probation-revocation petition as Active, Felony, and Violation—but the two charge lines are the original May 2022 traffic offenses. Both bond fields are blank. The issuing-agency field names the Lincolnshire Police Department.
A database record must describe the instrument it represents
The public correspondence asks the Sheriff to correct the disputed fields or explain each one in writing. That request does not ask the agency to disregard a court order. It asks whether the local record, and any replicated state or national entry, accurately describe the warrant that actually issued.
Why data quality is a liberty issue
Officers act on database fields in real time. Category, status, bond, charge description, issuing agency, pickup area, and service conditions affect how a person is stopped, held, transported, or released. An inaccurate field is not clerical trivia when the database is an arrest instruction.
The native audit trail can name every touch
The Event Log and Service Attempts tables, plus the LEADS/NCIC validation history, can identify who created, modified, printed, transmitted, or reviewed the record and when. The July 29 FOIA requests seek exactly those lifecycle records.