Construction Defect · Public Records

What public records can — and can't — tell you about a home builder.

Before you buy a home or hire a builder, a surprising amount is already on the public record. Read those sources for what they actually measure and you learn a lot. Read them carelessly and you draw confident conclusions the records don't support.

The record is more open than people think

Home construction leaves a paper trail across several public systems. None of it is secret, and much of it is searchable. The point of this piece is not that any one record is a verdict on a builder — it is that, read together and read carefully, these sources let a buyer or owner ask better questions. Here is what each source shows, and just as important, what it does not.

Building permits and inspection records

Local building departments issue permits and record inspections for most residential construction. Permit records can show what was built, when, under which contractor or qualifier, and how the inspection history ran — including failed inspections, re-inspections, stop-work orders, and the certificate dates that close a project out.

What they can reveal: whether work was permitted at all, who pulled the permit, how the inspection sequence went, and the certificate-of-occupancy or completion dates. Those dates matter for more than curiosity — they are also the trigger for construction-defect deadlines (see our companion pieces on repose versus limitations).

What they can't: a permit record does not tell you a home is defect-free, and a clean inspection history is not a warranty. Inspections are limited in scope and timing; many defects — a missing water-resistive barrier behind stucco, for instance — are not visible at the moments an inspector looks. A failed inspection is also not proof of a bad builder; corrections during construction are normal.

Court dockets and litigation history

Civil court records are public. A search of docket systems can surface lawsuits involving a builder or developer — construction-defect suits, lien and payment disputes, warranty claims, and the like.

What they can reveal: whether an entity has been sued repeatedly, the general nature of those disputes, and sometimes the outcomes. A pattern of similar suits across many projects is a genuine signal worth understanding.

What they can't: a lawsuit is an allegation, not a finding. Being named as a defendant proves nothing about fault, and many suits settle for reasons unrelated to the merits. Big builders also generate more litigation simply because they build more homes — raw case counts have to be read against volume, not in isolation. And corporate structure muddies the water: builders often operate through many entities, so litigation tied to one name may not surface under another. Reading dockets well means reading them skeptically.

Regulatory and licensing records

Contractors and the individuals who qualify them are typically licensed and regulated, and those records are public. Depending on the jurisdiction, you may find license status, the qualifying agent, and any disciplinary history or regulatory actions.

What they can reveal: whether a license is active and in good standing, who stands behind it, and whether a regulator has taken formal action.

What they can't: a clean license record is not a promise of quality, and the absence of discipline may mean nothing more than that no one filed a complaint. Regulatory records also lag — recent conduct may not appear yet.

Corporate and property records

Business-entity filings and property records round out the picture. Entity filings show corporate structure, registered agents, and related companies; property records show ownership, transfers, and sometimes construction financing.

What they can reveal: the web of entities a builder uses, which is often the key to connecting projects, permits, and lawsuits that otherwise look unrelated.

What they can't: structure is not misconduct. Builders use multiple entities for ordinary, legitimate reasons. The entity map is a tool for connecting records, not evidence of wrongdoing by itself.

The discipline that makes this useful: any single record is weak evidence and easy to over-read. The value is in the pattern — consistent signals across permits, dockets, regulatory files, and entity records, read against how much a builder actually builds. A responsible read connects sources and stays honest about what each one does and does not prove. Careful analysis of public permit, docket, and regulatory records — including machine-assisted analysis at scale — is a real tool, but it surfaces questions to investigate, not conclusions to publish.

How to use this as a buyer or owner

Concerned about a builder or a home that wasn't built right?

Tell us who you are and we will set up a free case review. Please do not include confidential details yet — we will confirm we have no conflict of interest first.

Request a Free Case Review

Related: How to check a builder's record before you buy — or before you sue  ·  A Chapter 558 notice does not stop the repose clock  ·  What "closed without payment" means in claims data  ·  Construction-defect practice