Permits tell you what work was planned. Code enforcement records tell you what went wrong, or what was done without a plan at all.
Most buyers and their agents spend the due diligence period focused on permit history, and for good reason. Permits document the work that was submitted, reviewed, and ideally inspected by the city. They're the paper trail for major systems like roofs, HVAC, electrical panels, and plumbing.
But permits only capture one side of the story. They show what a homeowner or contractor chose to document. Code enforcement records show what the city found on its own, or what a neighbor, inspector, or code officer flagged after the fact.
If you're representing a buyer on an Austin home, both records matter. Here's why.
What Are Code Enforcement Records?
Code enforcement records are complaints, cases, and outcomes filed through the City of Austin's code compliance process. They can be triggered by a neighbor complaint, a city inspection, or a routine code sweep of a neighborhood.
Common issues that generate code enforcement cases in Austin include:
- Work done without a permit. A homeowner hires a contractor to convert a garage, add a bathroom, or build a deck, and nobody pulls a permit. If the city finds out, it becomes a code enforcement case.
- Property maintenance issues. Overgrown lots, unsecured structures, accumulated debris, or unsafe conditions visible from the street.
- Occupancy or zoning concerns. Unpermitted short-term rentals, commercial activity in a residential zone, or occupancy beyond what the structure is approved for.
- Building code concerns. Structural modifications, drainage changes, or electrical work that doesn't meet current code, often discovered when a separate permitted project triggers a broader review.
These records are public. They're available through the City of Austin's code compliance system, and they document the complaint, the investigation, and the resolution, or lack of one.
Why Permits Alone Don't Tell the Full Story
Permit history is valuable because it documents planned, approved work. But it has a structural blind spot: it only captures work that someone chose to permit.
A homeowner who replaces an electrical panel without a permit won't show up in the permit record at all. But if a code officer, a neighbor, or a future inspection flags it, that shows up in the code enforcement record.
Here's a practical example. Say a property's permit history shows no electrical work in the last 20 years. That could mean the panel is original, or it could mean the panel was replaced without a permit. The permit record can't tell you which. But if there's a code enforcement case for unpermitted electrical work at that address, the picture gets a lot clearer.
This is the gap that code enforcement records fill. They surface work and conditions that never entered the permit system, the projects that skipped the process entirely.
What a Clean Record Actually Means
Not every property has code enforcement history, and that's a good thing. A clean record means no complaints were filed, no cases were opened, and no unresolved issues are tied to the address.
That's worth saying out loud to your buyer. A clean code enforcement record is a selling point, it means the property hasn't drawn attention from the city for unpermitted work, maintenance issues, or building code concerns. But it only becomes a selling point if the agent actually surfaces it and communicates what it means.
Too often, agents skip this section because there's nothing flagged. But "nothing here" is information. It means the property has stayed off the city's radar, and for a buyer weighing two comparable homes, that distinction can matter.
Why Nearby Records Matter Too
Code enforcement records aren't just about the subject property. The pattern of cases in the surrounding neighborhood tells its own story.
If five properties within a half mile have code enforcement cases for work done without a permit, that's worth knowing, even if the property your buyer is looking at has a clean record. It may suggest a pattern of contractors in the area cutting corners, or a neighborhood where unpermitted work is more common than average.
That context doesn't change the subject property's record. But it gives a buyer's agent a more complete picture of the area, and it might inform the kinds of questions worth asking during the inspection or option period.
For example, if nearby properties have multiple cases for unpermitted structural work, it's reasonable to ask the seller whether any work has been done on the home that isn't reflected in the permit history. That's not an accusation, it's due diligence informed by public data.
Open vs. Closed Cases
Not all code enforcement records carry the same weight. The distinction between open and closed cases matters.
Closed cases mean the issue was identified, addressed, and resolved to the city's satisfaction. A closed case for unpermitted work, for example, might mean the homeowner went back, pulled the proper permit, had the work inspected, and brought everything into compliance. That's actually a positive signal, it means the issue was caught and fixed.
Open cases are different. An open code enforcement case means the issue is still unresolved. For a buyer, that's a timeline flag. Open cases should be resolved before closing, because an unresolved code enforcement case can complicate title transfer, affect insurance, or surface during the lender's review.
If your buyer is looking at a property with open code enforcement cases, the question isn't whether to walk away. The question is whether the seller can resolve the open cases before closing, and what the timeline and cost look like to do that.
How This Shows Up in a Landset Property Briefing
The code enforcement history section of a Landset Property Briefing pulls the enforcement record for the subject property and the surrounding area. It shows:
- Any code complaints or cases filed at the address
- Whether those cases are open or closed
- What types of issues were flagged, such as work without permit, property maintenance, or zoning
- The pattern of code enforcement cases on nearby properties
When a property has no code enforcement history, the briefing says so, because a clean record is information worth communicating. When nearby properties have patterns worth noting, those show up too, with enough context to understand what they mean without overstating what they imply.
The goal isn't to alarm anyone. It's to surface public records that are already available but rarely reviewed during a typical transaction, and to give the buyer's agent something concrete to discuss with their client before the option period starts.
First report is $24.99.
Get Report →What to Do With This Information
If you're a buyer's agent reviewing code enforcement records for the first time, here's how to think about what you find:
Clean record on the property, clean nearby: Communicate it. Tell your buyer the property has no code enforcement history and the surrounding area doesn't show unusual patterns. That's a straightforward positive.
Clean record on the property, patterns nearby: Note the patterns and consider whether they're relevant to your buyer's situation. Nearby cases for work without a permit might prompt a conversation about whether any undocumented work has been done on the subject property. It's a question worth asking, not a reason to panic.
Open cases on the property: Flag them early. Understand what the cases involve, whether they can be resolved before closing, and what the seller's plan is to address them. Your lender and title company will want to know.
Closed cases on the property: Read the details. A closed case often means the issue was resolved, which can actually be reassuring. The work was flagged, corrected, and signed off by the city. That's a better outcome than work that was never reviewed at all.
The Bottom Line
Permit history and code enforcement records are two lenses on the same property. Permits show what was planned and approved. Code enforcement records show what the city found outside of that process, the work that was skipped, the conditions that were flagged, the issues that were resolved or left open.
Neither one replaces a home inspection. But together, they give a buyer's agent a more complete foundation for the questions they ask, the conversations they have with their client, and the priorities they set for the option period.
The information is already public. The question is whether you surface it first, or wait for someone else to find it later in the deal.