What a building violation record proves
A Chicago building violation record proves that on one date an inspector from the Department of Buildings wrote down a condition they considered out of compliance with the building code — the body of law setting minimum standards for construction and maintenance — and that a file was opened. It is a snapshot of a finding. It is not a statement about the building's condition now, and it is not a determination that anybody was at fault.
That distinction is not a technicality invented by this site. The City draws it itself, in the dataset's own description, and draws it specifically for the people most likely to read the record with money at stake.
Everything else on this page follows from a single structural fact: a violation is the opening move in an enforcement process whose outcome is decided somewhere the public dataset does not reach.
The City tells lenders not to rely on this data
The most important sentence written about Chicago building violations was written by the City, and it sits in the description of the Building Violations dataset itself:
Lenders and title companies, please note: These data are historical in nature and should not be relied upon for real estate transactions. For transactional purposes such as closings, please consult the title commitment for outstanding enforcement actions in the Circuit Court of Cook County or the Chicago Department of Administrative Hearings.
The same description adds that the information is informational only and does not necessarily reflect the current condition of the building or property, and that the dataset contains cases where a respondent has been found to be liable as well as cases where the respondent has been found to be not liable.
Read what that instruction concedes. The City publishes a violations dataset, updates it daily, and then tells anyone with a transaction in front of them to look somewhere else — naming three places, none of which is on the data portal. A clean address search before closing is not clearance, and the City has said so in the record itself. The text is in the dataset's published metadata.
The three statuses, read carefully
The City's own definition of the status field is short, and each of the three values means something narrower than it appears to.
Complied is defined as violations having been addressed. That is a case-management state — a description of where the file is, not a finding about the building. Set beside the City's statement that the data does not necessarily reflect current condition, a complied status records that the matter was closed out. It is not an inspector's certificate that the building is sound, and it is not evidence that the specific defect was repaired well or at all.
Open means the file is not closed. It does not establish that the condition persists. An owner may have corrected the problem years ago and never had it reinspected, and the file stays open because closing it requires someone to return.
No Entry is neither of the above, and it is the one readers mishandle most. The City defines it as the inspector having been unable to gain access to the premises. A string of no-entry rows is a record of the City being unable to look — information of a completely different kind, which is routinely counted into a building's violation history as though each row were a defect.
Counting rows is not counting problems
The City states that violations are always associated to an inspection, and that there can be multiple violation records to one inspection record.
The consequence is arithmetic and it defeats most informal analysis of this data. A single visit that identified six deficiencies produces six rows. A building with forty violations in the dataset may have been inspected four times. Any count taken per address is a count of cited line items, and describing it as a number of violations, inspections or problems misstates what was counted.
The same effect runs in the other direction. One serious structural citation is one row, exactly like one citation for a missing address number. The dataset carries a violation code, a description and an ordinance reference on each row, and nothing in the row count distinguishes severity. A long list is not necessarily a worse building than a short one; it may be a building that was inspected more thoroughly, or more often, or by an inspector who itemized.
Each row also carries free-text inspector comments. That field is the only narrative in the entire record, it is written by the individual inspector, and it is not standardized — which makes it the most informative and least comparable part of the dataset at the same time.
Why the record exists at all, and what that selects for
The dataset carries an inspection category field that answers the question of who caused the record to exist. The City documents two values: complaint, where the inspection resulted from a 311 complaint, and periodic, where it resulted from a recurring inspection. The published field description is truncated, so the full list of categories is unverified and these should not be assumed to be the only two.
That field matters more than its obscurity suggests. A complaint-driven violation exists because a person picked up a telephone. A periodic one exists because the building falls into a class the City inspects on a cycle. Neither mechanism reaches buildings that nobody complained about and that fall in no cycle — which is most buildings in Chicago.
So the violations data is a record of where the City looked, shaped by complaints and by program thresholds, and not a survey of the building stock. An address with no violations may be a well-maintained building, or a building nobody has ever reported and no program has ever scheduled. The two are indistinguishable in the published record.
One further structural trap sits in the geography. The dataset carries a property group field because, in the City's words, properties in Chicago can typically have multiple point addresses, range addresses and buildings — corner lots and large lots being the examples it gives. A search on one street address can miss violations recorded against a sibling address on the same lot, and corner buildings are the routine case rather than the exotic one.
The one thing a violation record proves well
Against all of that, there is something a violation record establishes better than any other public Chicago building record: it is durable evidence that a City inspector attended this building on this date and wrote something down.
That matters because of what the City does not publish. There is no standalone Department of Buildings inspections dataset. A passed inspection generally produces no public record at all. Inspection fields — the inspection number, status, category and whether it was waived — reach the open data only as attributes of a violation row. Chicago's building inspection history is visible almost exclusively through its failures.
For a reader trying to establish whether a City inspector has ever examined a building, the violation record is therefore often the only trace available, and an inspection that produced citations is better evidence of attention than silence is of compliance. The Department's own inspections page describes enforcement follow-up inspections as follow-ups on cases before the Department of Administrative Hearings or the Circuit Court of Cook County, which is where the question of liability is actually decided.
The honest summary is this. A violation record proves the City looked and cited. It does not prove the condition existed as cited, because that is decided in an adjudication the dataset does not record; it does not prove the condition was fixed, because complied is a file status; and it does not describe the building today, because the City says so itself. Read as a history of municipal attention, it is reliable. Read as a condition report, it is the wrong document.