Code-Violation Records for Investor Property Research (2026)
Start with the local code-enforcement agency's public portal. Where it offers an export, filter to the area, date and issue you want to research, then keep the case IDs and source labels with the results. Review which cases belong to the same property before calling it a property list.
Begin with the official city record
Find the city or county code-enforcement source, preserve its case number and published address, and note the date and status the agency displays. Some jurisdictions publish rich case data; others publish only a category or address, and some publish nothing usable for a particular purpose. Source quality is part of the answer.
Get a focused list: a tested Chicago workflow
For a property manager reviewing window-maintenance cases, Chicago's Building Violations dataset offers a practical starting point.
- Open the official dataset and select Data.
- Open the VIOLATION DESCRIPTION column menu and select its filter tab. Keep Filtering Operator → Contains and enter
MAINTAIN WINDOWin Filter Value. Close the menu and wait for the table to finish loading. - Open the VIOLATION DATE column menu. Keep Equals and enter
2026-10-09. This selects the cited date; choose a date relevant to your own research. - Read the results before exporting. Keep the case ID, description, published status and date; review the address/property grouping separately.
- Open Export → Download file. Check the CSV format and the Modified data scope. Wait until that count matches your filtered table; the dialog can briefly show zero while calculating. Avoid All data, which selects the entire dataset, then use Download for the scope you actually chose.
Checked October 12, 2026: the filters returned three records and the export dialog resolved to Modified data (3 rows). A download request for that scope produced the portal's Export initiated message, but a completed file was not captured or audited. No whole-dataset export was requested. Official source.
Use one result without overstating it
Case 7555547 was among those results. It displayed CN104035, MAINTAIN WINDOW, OPEN, and a cited date of October 9, 2026. The same filtered query also returned cases 7555432 and 7555402. Property addresses, inspector comments and personal/contact details are omitted here. Check the source cases.
For a property manager, the next useful step is to match the relevant case to a property in its portfolio and check the agency's current record. For an investor, it is one input to property research. A record does not establish an owner's willingness to sell. Three case rows are not necessarily three properties.
Chicago says multiple violations can belong to one inspection. Its PROPERTY GROUP key links address variants for one property; it is not a respondent name or a guaranteed parcel match. Keep every case ID while reviewing that grouping:
| Original address/reference | Case IDs | Source property-group key | Status checked on | Match result |
|---|---|---|---|---|
| Confirmed / Different / Unresolved |
The publisher describes this dataset as historical and informational, so verify current agency status before acting on a case. Retain the original addresses and leave ambiguous property matches unresolved. Chicago's source description and field definitions.
Browse ViolationNet's Chicago records or check an address as a convenience alongside the official source. Supported fields and publication timing vary by source.
Use published labels as labels
An agency may use terms such as unsafe structure, property maintenance, vacant building, or unpermitted work. These labels can help prioritize which records to research further. They do not establish repair cost, a deadline, a person’s financial circumstances, or a transaction opportunity. Agency definitions vary, so verify both the category and current status at the source.
Resolve the property carefully
Addresses are often incomplete, formatted differently, or missing a unit. Treat a match as only as complete as the city-published record. When ownership or mailing data is relevant, obtain and verify it from the appropriate public authority; not every city record carries it, and no record should be treated as contact permission.
Add the evidence a decision actually needs
For an individual property, useful independent checks may include the local assessor, title and tax records, permits, inspections, and a current agency lookup. Keep the source URL or case ID, query date, and the limitations of the match. That creates a reviewable research file instead of an unverifiable list.
Where ViolationNet helps
ViolationNet collects publicly available municipal code-enforcement records for supported cities and helps monitor properties you select. When a newly collected public record matches a selected property, it can appear in your monitoring workflow according to the source’s publication timing and your alert settings. Review the city source and agency record before acting; coverage and field availability vary.
Check an address or city · See coverage and pricing
Frequently asked questions
What are code-violation leads?
The phrase usually refers to address-level research built from municipal code-enforcement records. The record itself is public data, not evidence that an owner is motivated to sell or open to contact.
How can I verify a code violation?
Use the city-published address and case reference to check the issuing agency’s record. Confirm its current status and preserve the source link and review date.
Are city violation records available everywhere?
No. Availability, fields, publication timing, and address quality vary by jurisdiction. Check the specific city source before building a workflow around it.
Does a violation record include an owner or phone number?
Not necessarily. Some public sources contain property or mailing context; many do not. A public record should never be treated as permission to contact a person.