Distressed property leads in Dallas, from live Code Compliance cases

The exact signal we pull here

Dallas's code-enforcement activity is published inside its 311 dataset — d7e7-envw ("311 Service Requests October 1, 2020 to Present") on dallasopendata.com. It is a very large file: 3,089,664 rows at the time we probed it.

We narrow it to exactly one thing: department = 'Code Compliance' and service_request_type = 'Code Concern - CCS' and status in ('New','In Progress'), dated by created_date. In plain terms — an open code-enforcement case at Dallas Code Compliance, filed through 311, that the city has not closed yet. Anything already resolved drops out.

Addresses come through as a single, complete field including city, state and ZIP — for example 9659 Forest Ln, Dallas, TX, 75243. No composition, no guessing.

We measured Dallas's freshness ourselves, on 6 August 2026

Every list vendor says its data is fresh. Dallas is the market where that claim is actually provable, so rather than assert it we measured it: we took 1,000 rows off the feed and compared each case's filing date against the moment the record was visible to us on the API.

The newest event in that sample carried a timestamp of 2026-08-06T02:58 — the same morning we ran the pull. Read that for what it is: one measurement, by us, on one date, on those thousand rows. It is not a service level the city offers us, and it is not one we offer you. It is what the feed did when we looked, and we will re-measure it and change the date on this page when we do.

What a test pull actually returns

Our documented Dallas test run: --city Dallas --days 30 --limit 60 → 60 raw rows in, 59 unique properties out, 0 junk addresses dropped. That is the cleanest raw-to-unique ratio of any of our six markets — Dallas duplicates far less than Chicago does.

We also spot-checked twelve Dallas addresses against the US Census geocoder (geocoding.geo.census.gov, Public_AR_Current): 12 out of 12 matched. Every output row starts with a street number.

Real rows from the 6 August 2026 pull

Unedited output. The addresses, dates and statuses are exactly what the city published.

Notice that the Issue column reads the same on every row. That is not laziness on our side — see the limits section below.

What an investor actually does with this file

Dallas's strength is timing. Because the feed carries a genuine filing date and refreshes same-day, a case that was opened on Tuesday can be on your Wednesday call sheet. That matters more here than category detail does.

1. Work newest-first, hard. A case filed in the last seven days is an owner who has just been told by the city that something is wrong. Two months later they have either fixed it or stopped caring. Sort descending on date and start at the top.
2. Cut to your ZIPs. The address field already carries the ZIP, so this is one filter. 75216, 75217, 75227, 75241 behave nothing like 75230 or 75204 — pick your lane before you dial.
3. Watch for status movement. "New" means it has not been inspected yet. "In Progress" means an inspector has engaged and there is a live obligation. If you deliver a file every week, the rows that persist across weeks are your escalating cases.
4. Ask, don't assume, on the call. Since Dallas does not publish the sub-reason, your opener has to find out what the case is about. "The city has an open code case at the property — what did they flag?" gets you the answer and starts a real conversation.
5. Sort by the absentee flag before you dial. Absentee is derived at skip-trace time by comparing the mailing address to the property address.

The honest limits in Dallas