How Pre-Suit Rules Create a Construction-Defect Data Trail

A homeowner finds cracked stucco and calls a lawyer. Long before that call, the public record has been quietly documenting the builder — permits pulled, inspections failed, complaints filed, lawsuits opened. In many states, a required pre-suit notice process sits at the front of defect claims. Around it sits years of public data, waiting to be read.

The pre-suit process and the record around it

Many states make a property owner send the builder a written notice before filing a construction-defect lawsuit. The notice describes the problems. The builder then gets to inspect the property and offer to repair, offer to pay, or dispute the claim. Each step runs on a set deadline.

That exchange stays private between the parties. The intelligence lives in the public record around it. Licensing and discipline files, building permits and inspections, corporate registrations, and court dockets all document how a builder operates over time. The records are public but scattered — spread across agencies, counties, and formats. No single file tells the story. Assembled across a builder's whole body of work, they reveal patterns no one case can show.

What the combined record shows

Before a notice goes out, it helps to know how the builder has handled similar disputes, where its complaint history clusters, and whether it tends to settle early or dig in and fight. A builder with a record of resolving claims quickly calls for a different approach than one with a pattern of stonewalling.

None of that requires confidential information. It requires the engineering to link and analyze scattered records at scale. That is the problem DAIS Analytics is built to solve, and the premise of Builder Intelligence: aggregate, anonymized context on builder behavior, drawn entirely from public and licensed data.

Two rules govern the reading. Read the rate, not the raw count — a big builder files more of everything, so the signal is complaints or failures relative to volume. And read the trend, not the snapshot. One year describes a moment. Several years describe the builder.

One complication: large builders often work through dozens of subsidiary companies, so the record arrives split across many legal names. How those pieces get resolved into one builder is covered in Tracking Builder Shell Entities.

Permits and complaints as conduct signals

A building permit looks like paperwork. Read across a builder's full portfolio, permits become a conduct archive. Each application states the work proposed; each inspection records what a licensed inspector found. A builder whose projects keep failing inspections in the same categories — framing, waterproofing, structural — is documenting how it operates. That pattern sits in the record, no interpretation required.

Complaint records add a second layer. Permits show what inspectors found; complaints show what owners and contractors reported. When complaints cluster in one area or product type, that concentration marks where the exposure is densest. And how past complaints resolved — quickly, or only after escalation — shows how the builder has historically responded to pressure.

Why the timeline matters

Construction defects surface late, typically three to seven years after completion. So a builder's current profile reflects work done years ago, and the snapshot can mislead. A builder that fixed its quality problems may still look troubled. One that started cutting corners recently may still look clean.

The direction of travel tells you more. Metrics that were high and are falling suggest a problem addressed, or one still working through the pipeline. Metrics that were low and are climbing suggest exposure that has not yet peaked. Neither reading decides an individual case. Both supply context a single file never could.