# University of South Florida — 2026-09-02T00:00:00.000 (Pursuant to the Illinois Freedom of Information Act, I request copies of the records described below. For any data maintained electronically, I request production in machine-readable format (CSV, or the same $-delimited text layout used in prior

**Score:** 76/100

| Field | Value |
|---|---|
| Organization | University of South Florida |
| Filing Date | 2026-09-10 |
| Jurisdiction | IL |
| Locality | Pursuant to the Illinois Freedom of Information Act, I request copies of the records described below. For any data maintained electronically, I request production in machine-readable format (CSV, or the same $-delimited text layout used in prior productions, with a header row) per Section 6(a). This request asks for a single consolidated production that combines the layouts DOF has already released to me, plus several additional fields identified below. No field requested is a license plate number, a vehicle owner's name, or an owner's street address, and I am not requesting any field withheld under Sections 7(1)(b) or 7(1)(c) in prior responses. Complete ticket-level records, January 1, 2018 through the date of production. For all parking, standing, compliance, red light camera, and automated speed camera violations, one record per ticket containing the following fields. Fields a through w have each been produced by DOF in at least one prior response: a. Ticket Number, b. Notice Number, c. Issue Date/Time d. Violation location: Street Number, Street Direction, Street Name, e. Plate State and Plate Type, f. Vehicle Make, g. Ticket Type, h. Plate Expiration Month and Plate Expiration Year, i. Ward, j. Camera ID, Officer, Reporting District, Meter, k. Violation Code and Violation Description, l. Fine Level 1 and Fine Level 2, m. Current Amount Due, n. Total Payments, Collection Fee, Other Fees, o. Ticket Queue and Ticket Queue Date, p. Notice Level and Notice Date, q. Contest Queue, r. Hearing Disposition, Hearing Disposition Reason, Hearing Disposition Date, s. Owner Zip Code, Owner City, Owner State, t. Boot Flag, u. Bankruptcy Flag, v. Payment Date, Payment Amount, and Payment Origin for each payment on the ticket, produced as supplemental rows following the ticket row in the same manner as the prior productions. The August 26, 2026 response letter states that "if a payment exists, you will see supplemental rows following the core data which provide the payment information," but the files produced with that response contained no such rows. w. Violation Notice Date, Determination Notice Date, Final Determination Notice Date, Collection Fee Date, and Seizure Notice Date, as produced on August 26, 2026. The following fields are requested to the extent DOF's citation administration system maintains them. If any is not maintained, please state so; if any is denied, please deny it severably, cite the specific exemption, and produce the remainder of Item 1: x. A persistent anonymized vehicle or owner identifier for each ticket, produced in any of the following forms, whichever DOF maintains or can produce with the least burden: (i) the license plate number in one-way hashed or otherwise anonymized form; (ii) any internal vehicle or owner account identifier maintained in the citation administration system; or (iii) any other identifier that allows tickets issued to the same vehicle or owner to be associated with one another without disclosing the plate number or the owner's identity. Note that Section 2(c-5), quoted in DOF's August 26, 2026 response, defines license plate numbers as private information "except as otherwise provided by law or when compiled without possibility of attribution to any person"; an anonymized identifier compiled without possibility of attribution falls outside that definition. DOF has also previously produced license plate data in response to a 2018 FOIA request that was subsequently published in anonymized form. I requested a hashed or anonymized repeat-offender identifier previously (item 62 of F120781-112525); DOF's December 10, 2025 response suggested using notice numbers for that purpose rather than citing an exemption. I have since determined by comparing DOF productions from 2018, 2021, and 2026 that notice numbers are reassigned over time when new notices issue, so they cannot serve as a persistent owner identifier. y. Any indicator identifying tickets issued to fleet or commercial accounts, including: any fleet program enrollment flag or fleet account number associated with the ticket or vehicle; and any designation equivalent to the "Fleet" status that appears in Hearing Disposition Reason values in prior productions. If maintained at the account rather than ticket level, production of the account-level list with its identifier is acceptable. z. Refund transactions associated with each ticket: refund date, refund amount, and refund reason or type, produced as supplemental rows in the same manner as payment rows. Prior productions contain no negative or refund transactions. aa. Payment plan records associated with each ticket or its owner account, to the extent maintained: plan identifier; plan type (for example early, standard, or hardship); enrollment or initiation date; ticket status at the time of enrollment; the number of the account's prior defaulted plans as of enrollment, if derivable; balance due at enrollment; down payment amount and date; plan term in months; number of tickets covered by the plan; per-payment records for each plan installment (date, amount, origin); most recent payment date; current plan status; default or termination date; and any default fee or collection cost assessed on default. bb. The components of Current Amount Due for each ticket: original fine, late payment penalty, collection costs or fees, and any interest, as separate fields. cc. Contest or hearing request date, and scheduled hearing date, for contested tickets (in addition to the Hearing Disposition Date already produced; the Contest Queue field already conveys hearing type). dd. Administrative void, non-suit, or dismissal reason codes applied outside the hearing process.Every record must include Ticket Number so it can be matched to prior productions. |
| Classification | 2026-09-02T00:00:00.000 |
| Reported Metric | Christpher Reddish |
| Dataset Source | Chicago Data Portal (7avf-ek45) |

## Why this score
- Official Chicago Data Portal commercial filing (7avf-ek45)
- Verified organizational registry record
- Recent filing window (2026-09-10)
- Jurisdiction: IL

Source: Chicago Data Portal — FOIA Request Log (7avf-ek45) (https://data.cityofchicago.org/d/7avf-ek45). Last refreshed: 2026-11-04T06:11:35.432Z.
Source: Chicago Data Portal (data.cityofchicago.org, dataset 7avf-ek45). Public registry publication is a routine administrative record and is not a finding of fault, violation, or noncompliance. Individual and sole-proprietor records are excluded; verify directly with the issuing agency before taking action.