Report · Landlord-tenant records · 2003 to 2025
Which complaints turned into a notice of violation?
The City's open data portal does not say which complaint a notice came from. So we read all 9,961 notices and looked for the complaint behind each one. 62.6% of them tell you, in their own words.
What we found
Most notices say what the complaint said.
A notice of violation usually repeats the words of the complaint it came from. So we looked for a complaint at the same address that says the same thing. 6,168 notices matched word for word. 41 more matched with small differences in wording, and 31 matched where the address was written differently.
Out of 40,540 landlord-tenant complaints, 5,323 (13.1%) led to at least one notice. Most of those led to just one: 4,572 complaints. 751 led to two or more.
How fast a notice followed
When a notice came, it came quickly.
Days from complaint to notice, for the 6,240 matched notices
Count and percent of matched notices
- Within 30 days5,16782.8%
- 31 to 90 days81713.1%
- 91 days to a year2343.8%
- More than a year180.3%
By the category the City gave them
Emergency notices find their complaint. Most others take more digging.
Notices, by the category on the notice
| Category on the notice | Notices | Matched | Percent matched |
|---|---|---|---|
| Landlord/Tenant | 500 | 242 | 48.4% |
| Emergency | 947 | 918 | 96.9% |
| No category on record | 8,514 | 5,080 | 59.7% |
| All | 9,961 | 6,240 | 62.6% |
Complaints, and whether a notice followed
| Category on the complaint | Complaints | Led to a notice | Percent of complaints |
|---|---|---|---|
| Landlord/Tenant | 19,756 | 636 | 3.2% |
| Emergency | 1,048 | 588 | 56.1% |
| No category on record | 19,736 | 4,099 | 20.8% |
| All | 40,540 | 5,323 | 13.1% |
Last inspection date, on complaints that led to a notice and ones that did not
Notices by year
Then 2020 to 2022 happened.
Notices of violation opened each year, matched and set aside
Dashed line: where 2020 to 2022 begins
The notices we set aside
3,721 notices we could not match.
We did not delete or change anything. These notices sit in their own file with the record number, address, date, description and a link to the City page.
Why a notice was set aside
| Reason | Notices |
|---|---|
| The notice has no description, so there is nothing to match on | 1,901 |
| The notice has a description, but no complaint at that address says the same thing | 1,820 |
A few set aside
A few that matched
What we know and what we don't
The limits, plainly.
We know that each matched notice repeats the words of a complaint at the same address, and that the complaint was opened first in all but 4 cases. We did not change the original records.
We don't know whether a set-aside notice came from a complaint we could not find, or from a different kind of case altogether. 108 matched notices fit more than one complaint at the address, for example repeat complaints with the same words. For those we used the closest complaint opened on or before the notice.
This covers only notices in the landlord-tenant records. A property can hold other notices, such as land use or construction, that are outside this count. Unfit buildings are their own group, handled with citations, and are not part of this match.
About the data
Where these numbers come from.
- Records and coverage. 56,258 landlord-tenant records, opened 2003 through December 31, 2025: 40,540 complaints and 9,961 notices of violation. 6,240 notices matched to 5,323 complaints. 3,721 notices were set aside.
- Source and processing. City of Seattle open data portal, Code Complaints and Violations. We matched each notice to a complaint at the same address that says the same thing. Two files go with this report: the list of the 6,240 matched notices and the list of the 3,721 set-aside notices, each with a link to the City record.
- Limits. A blank inspection date does not mean no one inspected. Until July 2025 the portal's last inspection date column held map coordinates, not dates.
- Verification. Matched list (SHA-256): f2bd12f99a6e09d174f971b9fd5ffabf72451917ec52a37ac8c79c0f27107578
Set-aside list (SHA-256): be5d8c2853808e630504dd6158a6239732f68b48942297caf399a49a6158cd64