The Spearin Doctrine: Why Owners Implicitly Warrant Their Own Design
In 1918, the US Supreme Court decided United States v. Spearin, establishing what's now known as the Spearin doctrine. The case held that when an owner furnishes a contractor with plans and specifications, the owner implicitly warrants that those plans and specifications are adequate for the intended purpose. If the contractor builds per the plans and the result fails because the plans were defective, the contractor is not liable — the owner bears the cost.
The doctrine has been followed by federal courts, nearly every state supreme court, and most construction arbitration tribunals. It's one of the central protections contractors have on traditional design-bid-build projects where the owner (or the owner's architect) provides the design. Understanding its scope, limits, and how modern contracts modify it is essential for contractors bidding design-bid-build work.
The Spearin case involved a contractor building a drydock per government-provided specifications. The specs called for connection to an existing sewer that had to be relocated. After relocation, a heavy rainstorm broke the sewer, flooding the drydock under construction. The contractor rebuilt the damaged work; the government refused to pay extra, arguing the contractor should have foreseen the sewer problem.
The Supreme Court disagreed. Chief Justice Brandeis wrote that when the government (or any owner) provides specifications, it impliedly warrants that building according to them will produce a satisfactory result. The contractor's obligation is to build as directed; the risk that the specs won't work belongs to the party that wrote them.
Spearin applies broadly to plans, specifications, and other design information the owner provides. Specifically:
Documents typically covered by Spearin
- Architectural drawings showing dimensions, layouts, and details
- Structural engineering calculations and drawings
- Mechanical, electrical, and plumbing design documents
- Product or system specifications prescribing specific materials or installations
- Subsurface and geotechnical information the owner provides
- Performance requirements where the owner specifies the means to achieve them (design specifications)
The key distinction is between "design specifications" (owner dictates the means) and "performance specifications" (owner dictates the end result, contractor chooses means). Spearin applies strongly to design specifications. For performance specifications, the contractor bears more design responsibility, and Spearin is less protective.
The contrast matters because many modern specifications mix both types. Consider two ways to specify a roof system:
Design specification example
- Install 4-ply built-up asphalt roof
- Use specific manufacturer and product model
- Follow installation details in drawings A5.1 through A5.4
- Use specific flashing details at penetrations
Performance specification example
- Roof system must achieve 20-year warranty against leaks
- Must withstand wind loads per local code
- Must meet energy code for insulation R-value
- Contractor selects specific materials and installation methodology
Under Spearin, if the design spec version fails because the specified assembly doesn't work, the owner is liable. Under the performance spec version, if the contractor's selected system fails, the contractor is liable — the owner specified the result, not the means, so the contractor's design choices own the risk.
Spearin isn't absolute. Several limits can defeat or narrow it:
Limits and defenses to Spearin claims
- Obvious defects — if a defect in the plans was so obvious the contractor should have seen it at bid time, the contractor may be barred from claiming reliance
- Contractor's independent obligations — some contracts require the contractor to review plans and report conflicts, which if breached can shift risk
- Contract disclaimers — some contracts explicitly disclaim the Spearin warranty, making it a negotiated allocation; enforceability varies
- Industry knowledge — if the problem was something any competent contractor would know about (not peculiar to the plans), the Spearin warranty may not extend to it
- Deviation from plans — if the contractor deviated and the deviation caused the failure, no Spearin recovery
- Contributory negligence — contractor negligence in executing the plans can reduce or eliminate recovery
In practice, these limits are fact-specific. The contractor's best protection is to identify and report any plan issues during bidding and promptly after award — both because it's good practice and because it preserves the Spearin argument by demonstrating the contractor wasn't ignoring obvious problems.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Spearin protects a contractor who builds per plans. It doesn't protect a contractor who saw a problem, didn't say anything, built it anyway, and then wants the owner to pay for the resulting failure. Raising issues in writing via RFI preserves the doctrine.
Design-build contracts change the Spearin analysis because the contractor is responsible for the design. When the design-build contractor produces drawings and then builds from them, the contractor can't assert Spearin against itself — they're both the designer and the builder.
But the owner's pre-design-build documentation — program requirements, criteria documents, preliminary drawings — can still trigger a narrowed Spearin argument if the contractor had to rely on those documents. For example, if the owner provided incorrect subsurface information that the design-build contractor relied on in developing their design, and the design fails because of the incorrect information, the contractor may have Spearin-type protection even in a design-build context.
Modern construction contracts often include provisions that test or limit Spearin. Some common ones:
Contract provisions that intersect with Spearin
- Plan review obligations — contract requires contractor to review plans and report problems pre-bid; failure to do so may waive Spearin
- Subsurface disclaimer clauses — contract disclaims all subsurface information provided by owner; this has been tested in courts with mixed results
- Flow-down of warranties — owner's warranty flows down to subs on specific items, potentially shifting Spearin risk
- Gap filling clauses — contract says contractor must provide all items needed even if not shown, which can shift minor design omissions to contractor
Courts generally have been willing to enforce reasonable contract language that allocates design risk, but not willing to let contracts effectively nullify Spearin in egregious cases. A contract clause that tries to shift all design risk to the contractor on a traditional design-bid-build project may be struck down as unconscionable or not applied to the specific facts.
When a contractor encounters a design failure and believes Spearin applies, the claim process typically involves:
Steps to prepare a Spearin claim
- Document the specific plans or specs that failed
- Document the contractor's construction per those plans
- Document the failure and the cost to correct
- Demonstrate the failure was caused by the design, not contractor workmanship
- Provide evidence that the design problem wasn't obvious to the contractor at bid time (no duty to discover)
- Provide notice per the contract — a Spearin claim is a change-order claim in substance, so the contractor's notice obligations apply
The Spearin doctrine is a core protection for contractors on design-bid-build projects. When the owner provides the design, the owner implicitly warrants it's adequate, and the contractor who builds per the design isn't liable if the design fails. The doctrine has limits — obvious defects, contractor obligations to review, contract disclaimers — but its core protection remains intact in most US jurisdictions. Contractors who understand Spearin, document their reliance on owner-provided plans, and raise issues via RFI preserve the protection. Contractors who silently build questionable designs and hope to recover later often find that Spearin's obvious-defect and duty-to-report limits take away the protection they were counting on.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts