When Specs and Drawings Don't Match: Who Wins?
Specification conflicts with construction drawings create ambiguity that leads to disputes, change orders, and claims. Understanding precedence, catching conflicts early, and knowing which documents govern the work prevents expensive litigation.
The Spec vs. Drawing Problem in Construction
A contractor is building out a commercial tenant space. The architectural drawings show a wall lined with glass blocks at 6" spacing. The specification section on glass block says "glass blocks shall be installed at 4" spacing to maximize light transmission." Which one governs the work?
The glass block supplier quotes based on 4" spacing. The installer reads the drawing and sets up for 6" spacing. When the first course is complete, the architect walks the site and says "This isn't right—specs say 4-inch." The work is torn out and re-done. The contractor demands a change order for extra labor. The owner says "Your bid was for what the drawings show." The dispute escalates.
This scenario plays out on hundreds of projects because the contract documents—the combination of specifications and drawings—contain conflicts that nobody caught during preconstruction review. When ambiguity exists, the contract often determines which document controls. But disputes about precedence consume time, money, and goodwill.
What We're Covering
- Types of spec-drawing conflicts and how they arise
- Contract precedence clauses and what they actually mean
- How ambiguity creates liability and claims
- Identifying conflicts during preconstruction review
- Resolving conflicts before they cost money
Common Spec vs. Drawing Conflicts
Material Specifications Don't Match Drawing Details
The specification for roofing material says "single-ply TPO membrane, 60 mil, with compression pads at all penetrations." The drawing shows a 45 mil membrane with regular fasteners. The spec is more stringent—it's actually a better roof. But the design team's intent might have been different when they created the drawing. The installer reads the drawing and buys 45 mil. The contractor who bid based on the spec suddenly faces material cost overruns or is forced to change what was quoted.
In this case, the spec likely governs (it's the more stringent requirement), but the conflict should have been resolved before bidding, not discovered during construction.
Quantity Mismatches
The spec calls for a specific finish to be applied to all exposed surfaces. The drawing shows the finish applied only to surfaces facing the occupied space. A section of ductwork in a plenum is exposed but not visible—does it get finished? The spec says yes. The drawing shows no finish. The MEP contractor didn't budget for finishing concealed surfaces. Once discovered, it becomes a change order or a dispute about what "exposed" means.
Performance Standards vs. Prescriptive Requirements
The specification for paint says "finish must achieve a gloss rating of 85 on the 60-degree meter." The drawing shows a high-gloss enamel with specific manufacturer and product number. The product shown in the drawing achieves 78 gloss. Is the manufacturer/product specification binding, or is the performance standard binding? If the contractor uses a different product to meet the 85 gloss requirement, is that acceptable, or have they deviated from the specified product?
Installation Methods and Standards
The spec for ceiling tile installation references the Ceiling Tile Manufacturers Council guidelines, which require certain clearances and support patterns. The drawing shows a slightly different grid pattern. The ceiling installer follows the drawing and runs into inspection issues because the installation doesn't meet the standard referenced in the spec.
Tolerances and Dimensional Conflicts
The spec for stonework says "all joints shall be 3/8 inch plus or minus 1/8 inch." The detail on the drawing shows 3/8 inch joints "as shown"—with no tolerance. A mason joints at 1/2 inch on one section, then tightens to 5/16 inch on another, both within the spec tolerance. But the drawing's "as shown" suggests exact dimensions. Does the spec tolerance apply, or must the work match the drawing exactly?
How Contract Documents Define Precedence
Most construction contracts—AIA A101, ConsensusDocs, state-specific forms—include a "Intent of the Contract Documents" section that attempts to define which documents take precedence when conflicts exist. Understanding these clauses is critical during preconstruction review.
The Typical Hierarchy
AIA documents typically establish this order:
- The Contract Agreement (purchase order, letter of intent)
- Conditions of the Contract (General and Supplementary Conditions)
- Specifications
- Drawings
This suggests that specs govern over drawings. But the contract also typically says that the contract documents work together and any conflict should be reported to the architect for clarification. In practice, the hierarchy is muddied by specific language: "Drawings and Specifications shall be considered as mutually explanatory" or "Work shown on drawings and described in specifications shall be performed by the contractor whether or not specifically mentioned."
The Problem: Ambiguous Precedence Language
Many contracts say "More restrictive requirement governs" or "Most stringent requirement applies." This sounds clear, but it creates its own disputes: Is 60 mil TPO more restrictive than 45 mil? Technically yes—it costs more, offers better durability. But if the design team's intent was 45 mil and the spec writer mistakenly called for 60 mil, is the specification really "more restrictive" in the intent sense?
Custom contracts may define precedence differently or omit precedence clauses entirely, leaving ambiguity about which document controls in case of conflict.
How Conflicts Lead to Claims
The Contractor's Argument
A contractor bids based on one interpretation of the contract documents, then the owner (or architect) claims the documents require something different. The contractor argues: "I bid based on the drawings as I understood them. If there was an intent to include [additional work/more expensive material/additional specification], that should have been clear. I'm entitled to a change order for the additional cost."
This argument is often successful. Ambiguity in contract documents is typically interpreted against the drafter (usually the architect or owner). If the spec and drawing conflict and the contractor bid to one interpretation, courts and arbitrators often award the contractor a change order for the delta between what was bid and what was actually required.
The Owner's Exposure
If the specification calls for better-quality materials than the drawing shows, and the conflict isn't caught, the contractor bids to the drawing (cheaper). The work is constructed per the drawing. But when it's complete, the owner (or inspector) insists on the spec requirement. The contractor demands a change order. The owner disputes the cost or denies the change order. Litigation follows.
Alternatively, the owner may absorb the cost to avoid delay and disputes, but that cost was preventable with upfront conflict resolution.
Catching Spec-Drawing Conflicts During Preconstruction Review
The preconstruction phase is when to systematically compare specifications against drawings and resolve conflicts. This requires discipline and coordination among the team.
Step 1: Read Both Documents for Each Trade/System
During drawing review, don't review specifications and drawings separately. For each major building system (roofing, MEP, finishes, structural), read the relevant spec section alongside the corresponding drawings. Look for:
- Material specifications that differ from what's shown on drawings
- Performance standards that might be interpreted differently from the drawing details
- Installation or quality standards that aren't reflected in the drawing
- Quantities or scope shown on drawing that don't match spec descriptions
Step 2: Create a Conflict Log
Document every discrepancy found, no matter how minor. For each conflict, record:
- Location (which drawing sheets, which spec sections)
- Description of the conflict
- What the drawing shows
- What the spec says
- Potential impact (cost, schedule, quality, interpretation uncertainty)
Step 3: Request Clarification from the Design Team
Present the conflict log to the architect and engineer. For each conflict, ask for a clear resolution: "Are we following the drawing or the spec on this item? If drawing, please revise spec. If spec, please revise drawing. If both are correct and precedence applies, please clarify which document governs and provide a written confirmation."
This conversation prevents misunderstandings and sets expectations. The design team has an opportunity to correct errors while changes are inexpensive. The contractor has a clear understanding of what's required, reducing the risk of change orders later.
Step 4: Document Resolutions
When conflicts are resolved, document the resolution. If the architect issues a clarification letter or revised drawing, attach it to the conflict log. If the resolution is that the spec governs and the drawing is outdated, note that in writing. This documentation protects everyone if disputes arise later: "We resolved this ambiguity before construction with this written clarification."
Using Specifications Effectively in Review
Reading and understanding specifications is a skill that many project teams skip. Specifications are dense, reference industry standards, and use technical language. But they contain critical performance and quality requirements that don't appear on drawings.
During preconstruction review, assign someone to read specifications for each major trade. That person should note:
- Product brands and models specified (sometimes more restrictive than drawings suggest)
- Quality standards and testing requirements
- Installation standards referenced (ACI, TCA, manufacturer guidelines, etc.)
- Tolerances and acceptance criteria
- Anything that isn't reflected in the drawings
The Business Case for Conflict Resolution
The cost of resolving a conflict during preconstruction is a project manager's time and a designer's hour or two. The cost of discovering the same conflict during construction is rework, change orders, schedule delays, and potential claims. Most conflicts cost tens of thousands to resolve once construction has started.
Investing in comprehensive preconstruction review—reading both specs and drawings, identifying conflicts, and documenting resolutions—is one of the highest-ROI activities a project team can do. It prevents disputes and protects all parties from the ambiguity that leads to expensive claims.
Related Resources
How to Read Specifications
Understanding spec sections and technical requirements
How to Review Construction Drawings
Systematic review strategies for drawings and details
Drawing QA/QC Checklist
Comprehensive review process for catching errors
How to Write an RFI
Documenting conflicts and ambiguities during construction
Preconstruction ROI
Value of thorough planning and conflict resolution upfront
Construction Litigation Prevention
Strategies for avoiding disputes and claims