Warranty

Definition — what it is

A warranty is a contractual promise that construction work and the materials and equipment incorporated into it are free from defects and will be corrected at no cost to the owner for a defined period after completion. Construction warranties come in layers: the contractor's general one-year warranty of workmanship common in standard contracts, manufacturers' product warranties of varying lengths passed through to the owner, and extended or special warranties on specific systems such as roofing or waterproofing. A warranty is distinct from the correction-of-work obligation during construction and from latent-defect liability, which can extend for years beyond any express warranty under statutes of repose. A warranty is not a maintenance agreement and does not cover damage from misuse, normal wear, or lack of maintenance — it covers defects in the work as delivered, and confusing warranty obligations with owner maintenance responsibilities is one of the most common sources of post-completion disputes.

Also known as: Guarantee, Contractor's Warranty, Manufacturer's Warranty, Warranty Obligation

Why it matters — what it protects

Warranties define a real, bounded financial obligation that lives after the project's revenue is recognized. The contractor must reserve for warranty work, respond to claims, and manage subcontractor and manufacturer warranties for years after final payment, and a poorly scoped or poorly documented warranty program turns closed jobs into open-ended cost. The warranty period is when a project's true build quality shows up on the contractor's own books.

They allocate responsibility across a chain of parties, and the allocation only holds if the paper trail does. A defect that surfaces after completion may be the contractor's workmanship, a subcontractor's installation, or a manufacturer's product, and each carries a different warranty of different length. Without flowed-down subcontractor warranties and properly registered manufacturer warranties assembled at closeout, the general contractor absorbs claims it should have been able to pass through.

The warranty clock and its start date are frequently disputed, which makes them consequential. Whether the period runs from substantial completion, final completion, or beneficial occupancy, and whether repaired work restarts the clock, determines whether a given claim is inside or outside the window. A start date that is ambiguous in the contract becomes an argument at exactly the moment a defect appears.

Warranties sit at the boundary between defect correction and latent-defect liability, and the boundary is often misunderstood. An express one-year warranty does not cap the contractor's liability for defects that manifest later; statutes of repose and limitations set the true outer limit, which can be many years. Treating the express warranty period as the end of all responsibility is a costly misreading of how post-completion liability actually works.

Lifecycle — how it moves

1. Warranty terms set in the contract

   The prime contract sets the contractor's general warranty duration and scope, the start-date trigger, and any special warranties required on specific systems. These terms flow down into subcontracts and purchase specifications.

2. Flow-down and specification

   Subcontracts obligate trades to warranties matching or exceeding the prime, and specifications require specific manufacturer warranties (for example a 20-year roofing warranty). Gaps here leave the GC holding obligations it cannot pass through.

3. Warranty documentation assembly

   During closeout, the contractor collects and assembles all warranties — contractor, subcontractor, and manufacturer — into the closeout package, registering manufacturer warranties where registration is required for them to be valid.

4. Warranty period commencement

   The clock starts at the contractually defined trigger — substantial completion, final completion, or occupancy. Recording the exact start date for each warranty layer is essential and often neglected.

5. Claim intake

   The owner reports a defect during the warranty period. The claim must be triaged to determine whether it is a covered defect, an excluded maintenance or wear issue, and which party's warranty applies.

6. Responsibility determination and dispatch

   The claim is routed to the responsible party — the contractor's own crew, the responsible subcontractor, or the manufacturer under its product warranty. Misrouting or absorbing a sub's claim is where warranty cost leaks.

7. Correction and verification

   The defect is corrected and the repair verified. In many contracts the corrected work carries its own renewed warranty period, restarting the clock on that element.

8. Warranty expiration and walk-through

   Toward the end of the general warranty period, an eleven-month or end-of-warranty walk-through is commonly conducted so remaining defects are caught and corrected before the express warranty lapses. Latent-defect liability continues past this point under statute.

Anatomy — the data it carries

Warranty type and layer

Contractor general workmanship, subcontractor trade, or manufacturer product warranty. Each layer has different scope, duration, and responsible party.

Duration

The length of the period, from a standard one-year contractor warranty to multi-decade roofing warranties. Determines how long the obligation and reserve persist.

Start-date trigger

Whether the clock runs from substantial completion, final completion, or occupancy. The most-disputed element when a claim's timeliness is contested.

Scope of coverage

What defects are covered — workmanship, materials, specific systems — and what is expressly excluded. The line between defect and maintenance lives here.

Exclusions

Damage from misuse, normal wear, lack of maintenance, owner modifications, or acts of God. What the warranty does not cover, and a frequent dispute point.

Responsible party

Which party bears the correction obligation for a given defect. Determines routing and whether the GC can pass a claim through.

Manufacturer registration

Whether a product warranty required registration to be valid, and whether it was done. Unregistered warranties are a common closeout failure that voids coverage.

Transferability

Whether the warranty runs to the owner and to subsequent owners. Matters for developer-built and for-sale projects where ownership changes.

Renewal on repair

Whether corrected work restarts the warranty clock for that element. Affects how long a repeatedly repaired component stays covered.

Special/extended warranties

Enhanced warranties on specific systems, often with their own conditions such as certified installers or maintenance requirements to remain valid.

Claim procedure and notice

How the owner must report a defect and within what time. Failure to follow the procedure can jeopardize an otherwise covered claim.

Warranty bond or reserve

Any bond securing warranty obligations, or the contractor's internal reserve. The financial backing behind the promise.

Failure modes — how it breaks

Subcontractor warranties not flowed down

The prime requires warranties the subcontracts never match, so when a trade defect surfaces the GC has no back-to-back obligation to pass the claim to the responsible sub. The GC corrects it at its own cost.

Manufacturer warranty never registered

A product warranty required registration within a window to be valid, and closeout never completed it. When the product fails, the owner discovers the multi-year warranty everyone assumed was in place was voided at the start.

Ambiguous or unrecorded start date

The contract's warranty trigger is unclear or the actual start date was never recorded per warranty layer. When a claim arrives near the boundary, the parties argue over whether it is inside the window, with no clean record to settle it.

Maintenance issue treated as a warranty defect

The owner reports normal wear, filter changes, or damage from deferred maintenance as a warranty claim, and the contractor absorbs work it never owed. The line between warranty and owner maintenance was never made clear to the owner.

Claims misrouted or absorbed by the GC

A warranty claim that belongs to a subcontractor or manufacturer is handled by the GC's own forces because responsibility was not determined and the warranties were not accessible. The cost that should have been passed through lands on the GC.

Warranty expiring without an end-of-period walk-through

The general warranty period lapses with no eleven-month walk-through, so defects that could have been corrected under warranty are missed. After expiration the owner must pursue them under latent-defect law, which is slower and harder.

Express warranty mistaken for the outer limit of liability

The contractor treats the end of the one-year express warranty as the end of all responsibility and does not reserve for later claims. Latent defects that surface within the statute of repose still create liability the contractor failed to anticipate.

Metrics — how it is measured

Warranty documentation completeness

Share of required contractor, subcontractor, and manufacturer warranties assembled and registered at closeout. The foundation of a defensible warranty program.

Flow-down warranty coverage

Share of subcontracts carrying back-to-back warranties matching or exceeding the prime. Measures how much warranty risk the GC can actually pass through.

Claim response time

Time from an owner's warranty claim to acknowledgment and to correction. A direct driver of owner satisfaction and repeat work.

Pass-through rate

Share of covered claims routed to the responsible subcontractor or manufacturer rather than absorbed by the GC. Measures cost leakage.

Warranty claim rate by trade/system

Frequency of claims by trade and system. Reveals recurring quality problems and informs prequalification and design decisions.

Warranty cost against reserve

Actual warranty spend versus the reserve set at completion. Calibrates future reserves and flags underestimated obligations.

End-of-warranty walk-through completion

Share of projects with an eleven-month walk-through completed before expiration. Catches defects while they are still recoverable under the express warranty.

The AI shift — what actually changes

Conversational

You can interrogate the warranty record: which warranties on a given project are still active and when each expires, whether a reported defect falls within the covered scope or is an excluded maintenance issue, which party's warranty applies to a specific system, and which manufacturer warranties were never registered — with the specific warranty document and start date cited.

Generative

Warranty claim triage and end-of-period materials are drafted rather than composed: given a defect report, a model classifies it as covered or excluded, identifies the responsible warranty layer and party, and drafts the dispatch to that party or the denial explanation to the owner, and assembles the eleven-month walk-through checklist from the project's warranty inventory.

Orchestrated

Warranties are tied to the closeout package, the subcontracts, and the completion milestones: each warranty layer linked to its responsible party and start date, flow-down coverage checked against the prime, manufacturer registration status tracked, and claim intake routed to the right party with the governing warranty and its expiration surfaced automatically.

Autonomous

The warranty perimeter runs within guardrails: active warranties and their expirations tracked per project, incoming claims triaged as covered or excluded and routed to the responsible party, manufacturer-registration and flow-down gaps flagged at closeout, and end-of-warranty walk-throughs scheduled before expiration — while a human decides contested coverage, approves any claim the contractor will absorb, and resolves responsibility disputes.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — An owner reports a defect and you need to know if and how it is covered.

An owner has reported that the membrane roof on our completed project is leaking at several seams eighteen months after substantial completion. Using this project's warranty documentation, tell me which warranties are still active and their expiration dates, whether seam failure at this age falls within the covered scope or an exclusion, which party's warranty applies — our general workmanship warranty, the roofing subcontractor's warranty, or the manufacturer's system warranty — and whether that manufacturer warranty was properly registered at closeout. Note the claim procedure the owner must follow and whether this claim is inside the applicable warranty window. Flag any place the start date or coverage is ambiguous rather than resolving it in anyone's favor.

What good output looks like: A coverage determination identifying the active warranties, the responsible party, the registration status, and whether the claim is timely, with ambiguities flagged rather than resolved.

Follow-ups:

• Draft the dispatch to whichever party is responsible for this claim.
• If the manufacturer warranty was never registered, what is our exposure?
• Does correcting the seams restart any warranty clock on the roof?

Generative — Approaching the end of the one-year warranty and you need a walk-through plan.

Prepare an eleven-month end-of-warranty walk-through package for our project whose general warranty expires in a month. From the project's warranty inventory, build a room-by-room and system-by-system inspection checklist that targets the elements most likely to show warrantable defects before the express warranty lapses, and note for each system which warranty layer and responsible party would handle a defect. Draft the notice to the owner scheduling the walk-through and explaining its purpose, and draft a tracking log for any items identified so they can be corrected before expiration. Distinguish clearly between items that would be covered defects and items that are owner-maintenance responsibilities, so the walk-through does not generate claims we do not owe.

What good output looks like: A system-by-system walk-through checklist tied to warranty layers, an owner notice, and a tracking log, with covered defects distinguished from owner-maintenance items.

Follow-ups:

• Which manufacturer warranties extend past the general warranty and should we remind the owner about?
• Draft the correction dispatches for a sample set of likely findings.
• How should we document that the owner declined any recommended maintenance?

Orchestrated — Confirming warranty coverage is complete and flowed down at closeout.

Audit warranty coverage for this project at closeout. Compare the warranties required by the prime contract and specifications against what we have actually collected and assembled, and identify every missing contractor, subcontractor, or manufacturer warranty. For each subcontractor, confirm its warranty is back-to-back with the prime in duration and scope, and flag any that fall short of what we owe the owner. Verify that every manufacturer warranty requiring registration has been registered within its window, and flag any not yet registered. Record the start-date trigger and computed expiration for each warranty layer. Return one warranty-coverage report tying each gap to the prime requirement, subcontract, or product it concerns.

What good output looks like: A closeout warranty-coverage audit identifying missing warranties, flow-down shortfalls, unregistered manufacturer warranties, and computed expirations, each tied to its source requirement.

Follow-ups:

• Which unregistered manufacturer warranties must be registered before closeout?
• Where are we exposed because a sub's warranty is shorter than the prime's?
• Build the warranty summary sheet for the owner's closeout package.

Autonomous — Standing policy for running the warranty program after completion.

Operate our post-completion warranty program under these rules. Maintain a warranty inventory for each completed project with every layer, its responsible party, start date, and expiration. When an owner submits a claim, triage it as a covered defect or an excluded maintenance or wear issue, identify the responsible warranty layer and party, and draft the dispatch or the coverage explanation, but do not send anything that denies a claim or commits us to absorb work. Flag any manufacturer warranty not registered and any subcontractor warranty that falls short of the prime. Schedule the eleven-month walk-through before each project's general warranty expires. Never deny a warranty claim, never commit us to absorb a claim that belongs to another party, never determine a contested coverage or start-date question, and never approve warranty spend — route all of those to the project manager with your analysis.

What good output looks like: A running warranty inventory with triaged claims, expiration and registration alerts, and scheduled walk-throughs, where humans decide contested coverage, denials, and any absorbed cost, backed by a full audit trail.

Follow-ups:

• Show me every active warranty expiring in the next 60 days.
• Which incoming claims are triaged as excluded and awaiting my confirmation?
• List all unregistered manufacturer warranties across completed projects.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Reactive

   Warranties are a pile of documents in the closeout binder, claims are handled ad hoc, and the GC often absorbs work that belonged to subs or manufacturers.

1. Level 1 — Cataloged

   Warranties are inventoried with durations and expirations, but claim triage, flow-down verification, and registration tracking are manual and inconsistent.

2. Level 2 — Linked

   Warranties are tied to the closeout package, subcontracts, and responsible parties, so coverage gaps, flow-down shortfalls, and registration status are visible.

3. Level 3 — Assisted

   Claims are triaged and routed with drafts generated, walk-through packages are assembled, and coverage and registration gaps are surfaced for review.

4. Level 4 — Operated

   Warranty inventory, claim triage, expiration and registration tracking, and walk-through scheduling run unattended, while humans decide coverage, denials, and absorbed cost.

Common questions

How is a construction warranty different from the correction-of-work obligation and from latent-defect liability?

The correction-of-work obligation applies during construction and requires the contractor to fix nonconforming work as it is discovered before completion. The express warranty is a post-completion promise, typically one year for the contractor's workmanship, to correct defects that appear after the work is delivered. Latent-defect liability is broader still: it can extend for years beyond any express warranty under statutes of limitations and repose for defects that were not reasonably discoverable earlier. Treating the one-year express warranty as the end of all responsibility is a common and costly misreading, because latent-defect exposure continues well past it.

When does the warranty period actually start?

It depends on the contract's start-date trigger, which is commonly substantial completion but can be final completion or beneficial occupancy, and the choice matters because it determines whether a claim near the boundary is inside or outside the window. Ambiguity in the trigger, or a failure to record the actual start date for each warranty layer, is one of the most common warranty disputes, since manufacturer and special warranties may start on different dates than the contractor's general warranty. The defensible practice is to confirm the trigger in the contract and record the exact start and computed expiration for every warranty layer at closeout.

Why do manufacturer warranties so often fail exactly when they are needed?

Because many product and system warranties require registration within a defined window after installation to be valid, and that registration is frequently missed during a rushed closeout. The owner and contractor assume a long manufacturer warranty is in place, but it was never activated, so when the product fails years later the coverage everyone counted on does not exist. Extended and special warranties can also carry conditions such as certified-installer requirements or ongoing maintenance that, if unmet, void the coverage, which is why assembling and validating manufacturer warranties, not just filing them, is a core closeout responsibility.