Distressed Property Leads in Dallas

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.

3,751

open Code Concern cases filed in the trailing 30 days (probed 6 Aug 2026)

same-day

cadence — max(created_date) was 6 Aug 2026 at probe time

59 / 60

unique properties from a 60-row test pull, zero junk addresses

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.

dealsignal_dallas_20260806.csv

Signal	Date filed	Address	Issue	Status	Owner	Phone
VIOLATION	2026-08-06	9659 Forest Ln, Dallas, TX, 75243	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████
VIOLATION	2026-08-06	5925 Royal Crest Dr, Dallas, TX, 75230	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████
VIOLATION	2026-08-06	10955 Middle Knoll Dr, Dallas, TX, 75238	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████
VIOLATION	2026-08-05	828 Peavy Rd, Dallas, TX, 75218	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████
VIOLATION	2026-08-05	820 S Carroll Ave, Dallas, TX, 75223	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████
VIOLATION	2026-08-05	4632 Sycamore St, Dallas, TX, 75204	Code Compliance / Code Concern - CCS	New	████████ ███████	(███) ███-████

Source: Dallas Open Data, dataset d7e7-envw, filtered to department='Code Compliance', service_request_type='Code Concern - CCS', status in ('New','In Progress').
Owner and phone are blanked on purpose. Those two columns are the skip-trace step we add before delivery; we redact them in a public sample rather than publish a named person's phone number on the open web. Your delivered file has them filled in.

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.

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.
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.
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.
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.
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

We cannot tell you the violation type in Dallas, and we will not pretend to. "Code Concern - CCS" is the city's single catch-all 311 request type for code enforcement, and the public feed does not publish the sub-reason — weeds, junk and inoperable vehicles, and substandard structures all arrive with the same label. So every Dallas row's issue field reads Code Compliance / Code Concern - CCS and nothing more. Any vendor telling you they can filter Dallas by violation category from open data is either using a different source or overselling.

Dallas's dedicated code-violation datasets are dead history. We probed all three on 6 August 2026 before choosing this feed: x9pz-kdq9 stops at 31 July 2018 (712,998 rows), xrzj-c8ez stops in 2015, hqes-3ct4 stops in 2014. They look authoritative and they are frozen. We rejected them for that reason.

311 catches complaints, not everything. This feed is complaint-driven and proactive-inspection-driven; it is not a full register of every violation in the city.

The city does not publish the owner. Name, phone and mailing address come from a licensed skip-trace provider; matching is probabilistic and some rows come back without a phone.

Public records are not consent to call. You own TCPA and Do Not Call compliance before you dial — see our Terms of Service, §2.3.

Want 25 of these for your Dallas ZIPs?

Send us the ZIP codes you buy in and we'll pull 25 open Code Compliance records for them, skip-trace them, and email you the file. No card, no call required.

Get 25 free Dallas leads → See pricing & the $99 Pilot →

Starter locks one Dallas ZIP to you exclusively at $149/mo. The $99 Pilot gets you 100 skip-traced records with no subscription attached.