Does this page claim the warrant was fabricated?

No. It documents the fields printed in the Sheriff’s own July 15 report and asks whether those fields accurately describe the underlying 2026 revocation warrant.

Why does a blank bond field matter?

Bond and custody fields govern how officers and detention personnel handle an encounter. A blank field on an Active Felony record leaves the handling instruction undefined at the moment it is most consequential.

Why is a village police department listed as the issuing agency on a county probation warrant?

That is one of the disputed fields. The July 29 correspondence asks the Sheriff to correct it or explain it in writing.

The Sheriff’s Database Carried a 2026 Revocation Warrant as an Active Felony on 2022 Traffic Tickets.

The Sheriff’s own July 15 Warrant Details print shows Active, Felony, blank bond fields and two 2022 traffic charge lines — on a warrant issued in May 2026 on a probation petition.

warrant 314270warrant data accuracyLake County SheriffLEADS

What the Record Establishes

The Sheriff’s own report describes a 2026 probation-revocation warrant using 2022 traffic charge lines.
The category field reads Felony against charge rows marked Traffic.
Both bond fields are blank on a record officers act on in real time.

What They Have Not Produced

The Event Log and Service Attempts tables: who created, modified, printed, and transmitted this record, and when.
The LEADS/NCIC validation history and whether the same fields replicated to the state and national systems.
A written explanation for each disputed field — requested on July 29, still outstanding.

You do not need a legal theory to see this one. You need to read the report. The Sheriff’s Warrant Details record was printed on July 15, 2026 at 14:17 under a named login. It carries a warrant issued in May 2026 on a probation-revocation petition. The category field says Felony. The type field says Violation. The two charge lines underneath are the original May 23, 2022 traffic offenses, both flagged Traffic. Both bond fields are empty. The issuing-agency field names a village police department.

A database entry is an arrest instruction

This is the part that gets waved away as clerical. It is not clerical. When an officer runs a name at 2 a.m., what comes back is these fields — category, status, bond, charge description, issuing agency, pickup area, service conditions. Those fields decide whether a person is stopped and released, held, transported across county lines, or booked into custody on a felony hold. An inaccurate field in a warrant system is not a typo. It is an instruction to armed officers about a human being.

What was asked, and what it was not

The July 29 correspondence to the Sheriff asks the office to correct the disputed fields or explain each one in writing. It does not ask any agency to disregard a court order. It asks a narrower question that a records custodian is required to be able to answer: does this database record accurately describe the instrument that actually issued, and does the replicated state and national entry match?

The audit trail can name every hand that touched it

Warrant systems log everything. The Event Log and Service Attempts tables identify every creation, modification, print, transmission, and review, with a user and a timestamp. The July 29 FOIA requests seek precisely those lifecycle records, alongside the Illinois State Police data-quality request covering the LEADS side. Read the pocket-warrant visibility gap for how this warrant behaved before it was public.

Open the dossier for the Sheriff whose office owns the record.