What the list in front of you is
A Chicago permit history is a list of authorizations, not a list of work. Each row says the City allowed somebody to do described work at this address on a given date. It does not say the work started, finished, matched the description, or was ever looked at by an inspector.
The list is drawn from the Building Permits dataset the Department of Buildings owns on the Chicago Data Portal — 851,077 rows covering 2006 to the present when the count was read on October 22, 2026, updated daily according to the City's own metadata. Every address search you run, whether through the portal directly or through one of the commercial services that resell it, resolves to that same underlying table.
Understanding what one row carries, and what the spaces between rows carry, is most of what a reader needs. The short version: the rows are weaker evidence than they look, and the gaps are far weaker evidence than they look.
What a single row establishes
Taken on its own, one row establishes a small, specific set of facts, all of them administrative.
- That an application was reviewed and authorized. By somebody — the review type field records which process was used, which is where a self-certified application is distinguishable from one examined by City staff.
- What was authorized. The work description field is the City's record of the scope that was approved.
- The dates on the file. The application start date is when the City began reviewing. The issue date is defined by the City as the date it determined the permit was ready to issue, subject to payment of permit fees.
- What was charged. Fees appear split three ways across building, zoning and other charges: paid, unpaid and waived.
Two of those deserve more attention than they usually get. The issue date is not a start-of-work date; the City states that work under a permit may not begin until the applicable permit fee is paid, so a permit carrying an unpaid balance is a permit under which work was not lawfully begun, and that is visible in the record. And the reported cost field, which readers routinely treat as a valuation signal, is defined by the City as the estimated cost of work provided by the applicant. It is a number the applicant wrote down.
Source: Building Permits dataset metadata, City of Chicago.
What no row establishes
The permit record contains no inspection outcome. There is no field in the dataset recording whether a final inspection occurred, or passed. That absence is not a quirk of the public version — inspection results for permitted work are not published on the Data Portal at all except where an inspection produced a violation.
Nor does a row establish who did the work. The Department's own homeowner guidance states that owners of buildings with up to six dwelling units and up to three stories may act as their own general contractor, so a permit does not imply that a licensed contractor was involved.
Four of the dataset's fields are expressly flagged by the City as not available for all permit types, including permit status, permit milestone and work type. A blank in any of them means the field was not populated for that permit class. It does not mean no.
Why permit status is not a completion signal
Readers lean heavily on whether a permit reads open or closed. The City's own auditor examined that and found the status unreliable in both directions.
The Office of Inspector General's 2022 audit of permit inspections reported that 82.6% of permits remained open as of December 2020, that 72.5% of permits had no associated inspection requests at all, and that 65.6% of permits with required inspections did not appear to have received complete inspections. On the data itself, the audit found that the Department does not consistently close permits after required inspections are completed, that different divisions use the closed status differently, that electrical permits for maintenance work requiring no inspection are generally not closed or deleted and cannot be distinguished by the system from construction electrical permits, and that the Department's system cannot identify all uncompleted required inspections.
So an open permit does not establish that work is unfinished, and a closed permit does not establish that anything was inspected. The status field describes the state of a case file in a system its own auditor found inconsistent.
What a gap in the list means
Almost nothing, and this is the hardest thing to accept about the record. Four different histories produce an identical blank.
- Exempt work. A great deal of lawful work in Chicago requires no permit at all — interior finishes, limited drywall and masonry, low-voltage wiring, small sheds, fences and gazebos, in-kind replacement of certain fixtures and equipment in small residential buildings. None of it appears.
- Unpermitted work. Work that required a permit and never got one looks exactly the same as exempt work: like nothing.
- Work before 2006. The dataset starts there. In a city whose housing stock is largely pre-1940, most of each building's life sits outside the published window.
- Permits that were removed. The City's description states the dataset excludes permits voided or revoked after issuance. A revoked permit does not appear flagged as revoked — it is simply gone.
That fourth point has a consequence worth stating twice: the public record cannot show you a revocation. And because of it, the absence of a permit is not proof that none was issued.
Why the list is not a construction history
The permit record describes authorizations. There is no field anywhere recording what was actually built. The only mechanism in the system that connects the two is an inspection — and inspections of permitted work happen when the permit holder notifies the building official that the work is ready, under section 14A-5-502.3 of the Municipal Code. If nobody notifies, the record stops, and the permit row looks the same as it would have if everything had gone perfectly.
This is why a permit at an address is not evidence about the work visible at that address. The scope in the work description field and the structure standing on the lot are two separate facts with nothing in the public record tying them together. The most widely discussed Chicago example involved a building whose most recent permit covered mechanical equipment while the element that later failed was never within that permit's scope; that case is documented in secondary accounts rather than in a City source, so it is cited here only as illustration of a structural point the City's own fields establish independently.
Reading the dates, and one documented gap
Two date features repay attention. First, for permits in the 2019 to 2020 window, the code that governed a project depended on when the application started rather than when the permit issued, because the Chicago Construction Codes became mandatory for most applications started on or after August 1, 2020 and were optional before that. Some work descriptions from that period literally contain the strings 2019 BUILDING CODE or 2019 REHAB CODE, marking which code the project was reviewed under — an unusually direct piece of evidence sitting in plain text.
Second, the City has published a change notice for the Building Permits dataset dated September 13, 2024 describing a temporary pause in updates. The pause is therefore documented rather than inferred. Its length and exact dates could not be verified — the notice text is rendered in a way that did not yield to retrieval — so a thin stretch of records around that period should be treated as possibly an artifact of the pause, and nothing more definite should be claimed about it.