Nashville’s public property standards log listed 210 distinct requests with receipt dates in September 1–7, 2026, in an extract collected by Heartland Civic Review on September 9. The city links to the records through its Codes public-records page and official viewer.
The log describes requests and the city’s recorded workflow. It does not establish a total of confirmed violations, unique properties or conditions that remain unresolved. Some records originated with inspectors or audits, so the 210 entries should not all be described as resident complaints.
Housing requests lead the selected categories
The city labeled 119 entries “Codes Housing Request,” followed by 43 in “Codes High Grass and Weeds” and 40 in “PS Audit.” The remaining eight requests fall into four other categories.
| Source category | Requests |
|---|---|
| Codes Housing Request | 119 |
| Codes High Grass and Weeds | 43 |
| PS Audit | 40 |
| Short Term Rental Property | 4 |
| Codes Sign Request | 2 |
| Home Occupation PS Complaint | 1 |
| Codes Right of Way Request | 1 |
| Total | 210 |
These are exported category names. The retained city dictionary does not define the newer category field, so this analysis does not expand the abbreviation “PS Audit” or treat the categories as legal findings.
The separate reporting-source field labels 80 requests as inspector-reported and 40 as audit-originated. That distinction matters when interpreting how a request entered the system.
A completed action is not always a resolved condition
For 202 requests, the latest recorded activity is “Abate Notice Generated - PS,” with the result “Action Completed.” The completed action is the notice-generation step. Those labels alone do not establish that the underlying condition was repaired.
Three requests have a latest inspection result explicitly recording that violations were found, and one records a violation resolved. Two latest actions concern the warrant process, while two records lack a latest action and result. These are the latest exported steps, not complete case histories or a count of every finding.
The separate request-status field contains 209 OPEN labels and one DONE label. We retain those workflow labels as supplied. They cannot be translated into 209 unresolved violations and one repaired property. The extract does not supply a status-change date.
What the dates cover
The receipt dates present in the selected extract are September 1 (47 requests), September 2 (91), September 3 (38) and September 4 (34). No matching September 5–7 receipt dates appeared in this snapshot. That absence does not prove that no complaints, inspections or enforcement activity occurred on those dates.
A request’s receipt date is separate from its latest recorded action date. Neither should be silently substituted for the date an inspector confirmed a violation or a condition was resolved.
How we checked the records
We selected receipt dates from September 1 inclusive to September 8 exclusive in America/Chicago, requesting 11 fields for identifiers, categories, reported problems and workflow details. We did not request property addresses, owner names, parcel numbers or coordinates.
Two complete reads returned the same 210 records, with 210 distinct request numbers and no duplicate request numbers. Counts, field definitions and dataset metadata matched before and after collection. The source reports its last data edit on September 8 at 10:45 UTC; this is not a current-status check of each request.
Original responses and query details are preserved. Reported problems remain separate from the notes field and from dated activity results. Nonempty notes alone do not establish a dated inspection. This article uses aggregates and identifies no individual request or property.
Primary sources: the city’s public-records page, official viewer, published data layer and field dictionary. The snapshot was collected September 9 at 10:27 UTC. A later extract may differ.
The records operation behind this publication also supports commercial property research. These records do not establish sale intent or financial distress. For a documented correction, contact the editorial inbox.