Buying a newly constructed home in California comes with a reasonable expectation: the home should be built correctly. When that expectation is not met — when roofs leak, foundations crack, or plumbing fails within the first few years of ownership — homebuyers find themselves in a dispute with a developer who may be reluctant to acknowledge responsibility. California law provides substantial protections for homebuyers in these situations, but navigating the process requires an understanding of the legal framework, the developer's obligations, and the practical steps necessary to protect a claim.
The Developer's Legal Obligations
In California, residential developers owe homebuyers a duty to construct homes that meet applicable building codes and performance standards. This obligation arises from multiple sources of law:
SB 800 (Civil Code Sections 895-945.5) establishes specific building performance standards for homes sold on or after January 1, 2003. For more, see Understanding California's SB 800 Right to Repair Act. These standards define what constitutes a defect for each major building component — structural systems, building envelope, plumbing, electrical, soil and drainage, and more. A home that fails to meet these standards is defective under the statute regardless of whether the builder intended to cut corners.
Implied warranty of habitability requires that a new home be suitable for its intended use as a residence. This common-law doctrine applies independently of SB 800 and can cover defects that fall outside the statute's specific standards.
Express warranties are written warranties provided by the developer at the time of sale. Many developers offer limited warranty programs through third-party administrators. These warranties vary in scope and duration, and their terms should be reviewed carefully — they sometimes contain provisions that attempt to limit the buyer's rights.
Common Developer Defenses
When confronted with a construction defect claim, developers employ several common defenses. Homebuyers should anticipate these arguments:
"It's a maintenance issue, not a defect." Developers frequently argue that the problems are the result of the homeowner's failure to maintain the property rather than defective construction. While homeowners do have maintenance obligations, this defense fails when the underlying cause is a construction error. A roof that leaks because of improper flashing installation is not a maintenance failure — it is a construction defect.
"The warranty has expired." Developers point to the expiration of express warranty periods to argue that claims are untimely. However, the statutory rights under SB 800 and the statutes of limitations under the Code of Civil Procedure operate independently of the developer's warranty program. A claim may be timely under the law even if the express warranty has expired. For more, see Construction Defect Statute of Limitations in California.
"The homeowner caused the damage." Developers may claim that the homeowner's modifications, landscaping changes, or other actions caused the defective conditions. This defense requires the developer to prove specific causation, which is often difficult when the defect is in the original construction.
The Prelitigation Process
For homes subject to SB 800, California law requires homebuyers to follow a mandatory prelitigation process before filing a lawsuit. This process begins with a written notice to the developer describing the claimed defects. The developer then has the right to inspect the property and offer repairs.
The prelitigation process is designed to encourage resolution without litigation, but it also serves an important function for the homeowner: it creates a documented record of the claimed defects and the developer's response. If the developer fails to respond, offers inadequate repairs, or performs repairs that do not resolve the problems, that record becomes evidence in any subsequent litigation.
Homebuyers should approach the prelitigation process seriously. Notices should be detailed and specific. Inspections should be documented. And any repair offers should be evaluated carefully — accepting a partial repair may not resolve the underlying defect and could complicate future claims.
Key Steps for Homebuyers
Do not delay. Construction defect claims are subject to statutes of limitations that begin running at the close of escrow. Different defects carry different time limits under SB 800, ranging from one year to ten years depending on the component involved. Waiting too long to investigate suspected defects can result in the permanent loss of legal rights.
Document defects thoroughly. Photograph all visible defects, note when they first appeared, and keep records of all communications with the developer's warranty department. If the developer sends a representative to inspect, document what was inspected and what was said.
Do not allow the developer to control the investigation. Homebuyers have the right to retain their own forensic experts to evaluate the property. A developer's inspection is conducted with the developer's interests in mind. An independent investigation provides an objective assessment of conditions and identifies defects that the developer's inspector may overlook or minimize.
Understand what you signed. Purchase agreements for new construction often contain arbitration clauses, limitation-of-liability provisions, and other terms that affect the homebuyer's rights. These provisions are not always enforceable, but understanding them early allows for better strategic planning.
The Bigger Picture
Developer defect disputes in California are governed by a legal framework that, on balance, favors the homeowner. SB 800 establishes clear standards, defines a structured process, and provides meaningful remedies. But these protections are only useful to homeowners who act promptly, document their claims, and understand the process. A newly built home should not require major repairs within the first few years of ownership, and when it does, California law places the responsibility where it belongs — on the developer who built it.