What the City's record of a building is made of
The City of Chicago's record of a building is a body of public records — documents a government creates in the course of its own work and is then obliged to make available. It is made of two things, and only two things: approvals the City granted, and enforcement the City took. Permits are the first. Violations are the second. Between them there is a very large space that the record does not describe at all.
This matters because readers approach the record expecting something else. They expect a file on the building: what was built, when, by whom, and whether it was done properly. No such file exists. What exists is a trail left behind by two administrative processes that were designed to move applications and close cases, not to document a structure for a future buyer.
A permit is an authorization to do described work. An inspection record is a note that a City inspector attended and wrote something down. Neither is a statement about the condition of the building — the physical state of its structure, systems and finishes — and the City says so in its own documentation. The gap between what the record is and what readers take it for is the single largest source of error in reading Chicago building records, and almost all of it is structural rather than accidental.
Where the record lives, and what sits outside it
The published portion lives on the Chicago Data Portal as two datasets maintained by the Department of Buildings. Building Permits (ydr8-5enu) covered 851,077 rows when its row count was read directly from the City's own interface on October 22, 2026; its metadata field for time period says 2006 to present, and the one for update frequency says the data are updated daily. Building Violations (22u3-xenr) covered 2,033,347 rows on the same date, from January 1, 2006 to present, also updated daily.
Those two datasets are the public record for most practical purposes. A metadata field is simply a labelled property the City attaches to the dataset itself — who owns it, how far back it runs, how often it changes — and reading those fields first is the difference between knowing what a search covered and guessing.
Several records that readers assume are on the portal are not. Outstanding enforcement actions live in the Circuit Court of Cook County and at the Chicago Department of Administrative Hearings. Title evidence lives in the title commitment. The City names all three in the Building Violations dataset description itself, directing lenders and title companies — the firms that research and insure title at a sale — away from the portal and toward those records for transactional purposes. That instruction is published alongside the data, in the City's own words.
Source: Building Violations dataset metadata, City of Chicago.
What the record was built for
The permit dataset is structured around money and process, not around buildings. Its fields track the date the City began reviewing an application, the date the City determined a permit was ready to issue subject to payment of fees, the processing time between the two, and the fees themselves split three ways across building, zoning and other charges — paid, unpaid and waived. It records the ward at the time of issuance, which is useful for City administration and meaningless for a structure.
The violation dataset is structured around cases. Each row is a cited line item attached to an inspection number, with a status that describes where the file stands rather than where the building stands.
Read that way, the omissions stop looking like oversights. Nothing in the permit record marks work as finished, because finishing work was never what the permit system was tracking. The City's own description of the Building Permits dataset states that work under a permit may not begin until the applicable permit fee is paid, and defines the issue date as the date the City determined the permit was ready to issue, subject to that payment. The record is a record of administrative readiness. Whether anything was then built is a separate question the dataset does not answer.
Source: Building Permits dataset metadata, City of Chicago.
The structural reason the record shows less than readers expect
Here is the finding that organizes everything else: the City publishes no standalone Department of Buildings inspections dataset. A catalog search of the Data Portal for inspections run on October 22, 2026 returns food inspections from Public Health, environmental inspections from the Department of Environment, a targeted neighborhood program and a life safety evaluation set deprecated in 2015 — but no citywide buildings inspections dataset. Department of Buildings inspection data reaches the public portal only where an inspection produced a violation, carried as inspection number, inspection status and inspection category on the violation rows themselves.
The consequence is severe and is rarely stated plainly. A passed inspection generally produces no public record at all. The inspection system is visible to the public almost exclusively through its failures. A building with a clean violation history may have been inspected repeatedly and passed; it may equally never have been looked at. The published record cannot distinguish the two, and no amount of careful searching will make it do so.
Compounding this, the City does not initiate the inspection of permitted work. Section 14A-5-502.3 of the Municipal Code places the duty on the permit holder to notify the building official when work done under a permit is ready for inspection. The City's Office of Inspector General, auditing that process in 2022, found that the Department does not initiate an inspection unless it receives a request from a permit holder or a complaint. Compliance — in the sense of work actually meeting the code — is therefore confirmed only when someone outside the City asks for it to be confirmed.
Four kinds of silence, and they look identical
When an address returns nothing, four quite different things may have happened, and the record provides no way to tell them apart.
- The work was exempt. A considerable amount of lawful Chicago work requires no permit — interior finishes, limited drywall and masonry, low-voltage wiring, small sheds and fences, in-kind replacement of certain equipment in small residential buildings. Exempt work leaves no trace.
- The work was unpermitted. Work that should have been permitted and was not leaves exactly the same trace as exempt work: none.
- The work predates publication. Both principal datasets begin in 2006. For a city whose housing stock is largely older than 1940, the published record covers the last fraction of most buildings' lives.
- The permit was removed. The Building Permits dataset description states that it excludes permits voided or revoked after issuance. A revoked permit does not appear as revoked; it disappears. The public record cannot show a revocation at all.
This is why absence of a permit record is not evidence that no permit was issued, and why a thin permit history is not evidence that little was done. Silence in this record carries almost no information.
Who created the record decides what it weighs
The most useful habit when reading any Chicago building record is to ask who made it, because that determines its evidentiary weight more than its title does.
A record made by a City inspector who attended and passed the work is the strongest thing available, and it is also the rarest, for the reason set out above. A record made by a licensed design professional self-certifying an application reflects that professional's signature standing in place of a City plan examiner's review — a different thing entirely, and the public record does not always make the substitution obvious. A record made by an owner or their contractor, such as a permit application and its description of work, is a statement of intention by the party with an interest in it. A record that exists because somebody complained to 311 tells you about the complaint as much as about the building.
None of these is worthless and none is conclusive. But a reader who treats all four as equivalent City findings will overread the weak ones and miss the significance of the strong ones.
What to carry into any individual record
Three distinctions do most of the work. First, authorization is not execution: a permit shows the City allowed described work, and there is no field anywhere recording what was actually built. Second, a case status is not a condition: the City states expressly that its violation data does not necessarily reflect the current condition of a building or property, and that the dataset contains both liable and not-liable outcomes without distinguishing them. Third, an inspection is not implied by a permit, and the strongest evidence the system produces — a passed final inspection, or a certificate of occupancy, which is the document the City issues when a building may lawfully be occupied — exists for only a narrow class of buildings.
The Inspector General's 2022 audit measured that last point directly, finding the Department completed 98.9% of required inspections on permits that require a certificate of occupancy against 16.7% of new construction permits generally, where most buildings need no such certificate. The Inspector General's June 2024 follow-up concluded that the Department had not implemented corrective actions.
Nothing in that is a reason to distrust every record. It is a reason to read each one for exactly what it says and nothing further — which is what the rest of this reference is for.