Code violation property leads begin with a public record, not a conclusion about the property or owner. A complaint, a citation, a resolved issue, and a lien are different records with different meanings. Your job is to source the record, match it to a parcel, verify current status, and decide whether the situation fits your outreach. USLeadList is a different prepared source: inheritance data matched from death records to property records, delivered in monthly county files, typically about five weeks after death.
If you want to inspect the inheritance-data layout, Get a Free Sample. The sample shows historical examples of inheritance-data fields and layout, not code records.
How to source code records
Start with the local custodian. For federal agency records, FOIA.gov explains that FOIA applies to federal agencies. City and county code requests follow the local public-records process, so ask the relevant custodian about available releasable records, fees, and restrictions. Do not assume a federal FOIA request covers a city or utility.
Ask what fields exist before you build a workflow. Common fields include case number, address, parcel number, violation type, opened date, closed date, status, and inspector notes if releasable. Some jurisdictions publish open data portals; others require a request. Record formats vary, so confirm whether you can receive a spreadsheet, CSV, or another export.
Types of records and what they mean
| Record type | Common meaning | What it does not prove | Practical next step |
|---|---|---|---|
| Complaint | Someone reported a possible issue; may be unverified | Not a citation, lien, or confirmed violation | Check case status and inspection notes |
| Citation | Enforcement notice issued for an alleged violation | Not proof of current damage, lien, motivation, discount, or authority to sell | Verify current status and any compliance dates |
| Resolved issue | Case closed or compliance recorded | Closure reason matters; closed does not always mean corrected | Read closure reason and current status |
| Lien | A recorded monetary claim, if one exists | Not automatically created by a citation; verify at recorder or title | Ask a title or legal professional |
A code record is not a structural inspection. It may describe an alleged violation, an inspection result, or an administrative status. Treat legal and title questions as questions for the appropriate professionals.
Parcel matching
Match the record to a parcel using the county assessor or GIS source. An address alone can be ambiguous. A parcel ID is a stronger match. Watch for common issues: new subdivisions, condominiums, unincorporated areas, and situs addresses that differ from mailing addresses. A match helps you organize research, but it does not prove ownership, title transfer, or authority to sell.
Due diligence checklist
- Identify the record source and the custodian that controls it.
- Capture the record type, case number, and dates exactly as published.
- Match the record to a parcel ID when possible.
- Verify current status, closure reason, and any later updates.
- Check for separate liens at the recorder or through a title professional.
- Research ownership through assessor or recorded documents, then verify occupancy separately with current sources.
- Refer legal, title, and compliance questions to the appropriate professionals.
- Decide whether the record fits your outreach criteria before you contact anyone.
Outreach with code records
Identify yourself accurately as an investor, and never imply you represent the city or code department. Verify the current case status before referencing it in outreach. Keep the message factual and low pressure: you noticed a public record and wanted to introduce yourself about the property. Respect contact preferences and opt-outs. Do not claim a citation proves motivation, distress, vacancy, equity, or a discount.
For related prospecting, see distressed property leads and using public records to find probate properties. You can also compare vacant property leads and review the inheritance property index to understand how a separate data layer fits your county plan.
Inheritance data as a separate layer
USLeadList matches death records with property records and delivers monthly county files. It does not depend on a probate filing, but every record is not guaranteed to precede probate. Distribution is capped at three USLeadList subscribers per lead, not market-wide exclusivity. It is not a court-file list: no executors, probate case numbers, filing dates, or court documents. Optional contact enrichment is separate from the base file and does not prove a relative can sell.
The buying benefit is prepared property matching that saves assembly work and recurring county delivery that supports planning. If you already work code records, inheritance data can be a second list for the same county. Keep the sources separate in your notes so you do not confuse a code record with an inheritance record.
FAQs
Does a code citation prove a lien?
No. A citation is an enforcement record. A lien is a separate recorded claim, if one exists. Verify at the recorder or with a title professional.
Does USLeadList provide code-violation data or matching software?
No. USLeadList supplies death and property matched inheritance data, not code records or code-matching software. You can independently compare lawful datasets using verified property identity.
Is a closed code case proof the issue was corrected?
Not necessarily. Read the closure reason and current status. A closed case may reflect compliance, an administrative closure, or another outcome.
If you work a county and want to add inheritance data as a separate layer, tell us the county or counties you cover. We will confirm current availability and pricing for that county before you order. Request a county quote.