Spec vs Drawings Conflicts for Contractors: FAR/AIA Steps

If drawings and specifications contradict each other, preserve both versions, issue an RFI or contractual notice, and do not proceed on your own interpretation. Precedence depends on the contract, but the immediate response does not. Acting without written clarification shifts the financial risk onto you, a point both FAR 52.236-21 and standard AIA practice make explicit.

TL;DR:

• Federal contracts generally give specifications precedence, but private contracts may use different rules, so read the governing clause before deciding which document controls.
• Preserve dated copies, identify the exact sheet, detail, and specification paragraph, then send a written RFI with evidence, a proposed fix, and a response deadline.
• Stop affected work when a conflict creates a safety risk or major nonconformity; otherwise, document assumptions and track related costs separately pending written direction.
• During bidding, price requirements found in only one document as a risk allowance or list them as written exclusions, and confirm supplier quotes against specifications.
• A human reviewer must verify extracted text and interpret contract precedence, because automated tools can flag likely conflicts but cannot approve the project’s response.

Table of Contents

• What drawings cover versus what specifications cover
• Common conflict types to watch for during review
• Who decides: check the contract first
• Step-by-step resolution workflow
• Estimating and bidding implications
• Prevention: coordination habits that cut future conflicts
• How a structured bid-review tool and human oversight help
• Legal implications and risk management
• Case studies illustrating real-world conflicts and resolutions
• Role of technology and software tools in detecting conflicts
• Recurring root causes and one habit that saves time
• See how ArosBid catches these conflicts before bid day
• FAQ
• Sources

What drawings cover versus what specifications cover

Drawings show location, geometry, dimensions and quantities. Specifications cover products, quality, performance, workmanship and submittal requirements. Neither document stands alone, and a requirement that appears in only one of them is still binding on the project.

The Federal Highway Administration’s specification guidance treats drawings and specifications as complementary parts of a single set of instructions, with specifications carrying the performance and quality language that drawings cannot show visually. Reading one without the other leaves gaps that surface later as RFIs or rework.

• Drawings answer where, how big, and how many.
• Specifications answer what material, what standard, and how it gets installed and tested.
• A detail missing from the drawings but called out in the specs is still a contract requirement.

Common conflict types to watch for during review

Forensic reviewers who examine disputed projects after the fact see the same conflict patterns repeat across different trades and contract types, according to HKA’s forensic accounting overview. Knowing the categories in advance speeds up triage during document review.

1. Contradictory dimensions or quantities between a schedule and a drawing.
2. Different materials, performance ratings, or specified products than what a tag or legend shows.
3. Missing or mismatched schedule tags and drawing cross-references.
4. Obsolete revisions left in circulation alongside updated sheets or sections.
5. Inconsistent terminology for the same component across disciplines.
6. Cross-discipline interface assumptions, such as structural and mechanical drawings that each assume the other handles a penetration or support.

Who decides: check the contract first

Precedence language is project-specific and jurisdiction-specific, so the first move is always to open the contract documents rather than guess. Federal construction contracts commonly use FAR 52.236-21, which states that where drawings and specifications differ, specifications generally govern, and that contractors must promptly report the discrepancy for a written determination. Private work governed by AIA or FIDIC forms typically carries its own precedence clause, and that clause can differ from project to project.

• Find the precedence clause before assuming either document wins by default.
• Submit an RFI or contractual notice even when you believe you already know which document governs.
• Wait for a written determination before adjusting price, schedule, or means and methods.
• Proceeding on your own reading, even a reasonable one, puts the cost of being wrong on you.

Step-by-step resolution workflow

Once you spot a conflict, the sequence matters as much as the substance. This order keeps you administratively protected while the question gets answered.

1. Preserve the original versions. Keep dated extracts or photos of both the drawing and the spec section, and record the exact sheet number, detail number, specification paragraph, and revision date for each.
2. Quantify the impact. Note whether the conflict touches safety, schedule, procurement lead time, or cost, and draft a short impact note you can attach to the RFI.
3. Notify in writing. Issue an RFI or formal contractual notice with a specific question, the attached evidence, one or two recommended resolution options, and a requested response date.
4. Pause or proceed carefully. Stop affected work if safety or a major nonconformity is involved. Otherwise, document any assumptions you are working under and track the associated costs separately so they are recoverable if the determination goes against your assumption.
5. Close the loop. Once a written response arrives, update the master documents, revise affected estimates, submittals, and schedules, and circulate the corrected version through document control so the whole team is working from the same information.

A partner resource on RFI workflow mistakes covers common missteps subcontractors make at the notification stage, including vague questions and missing response deadlines, both of which slow resolution and weaken your position if a dispute follows.

Pro Tip: Attach a single recommended resolution to every RFI instead of just a question. A specific proposal gets answered faster than an open-ended one.

Estimating and bidding implications

A conflict discovered during bid preparation changes what you are actually pricing, not just what you are questioning. Before submitting a number, reconcile scope, quantities, product finish or performance class, submittal lead times, testing requirements, and any temporary works tied to the affected area.

• Log any requirement that appears in only one document and treat it as an open clarification, either priced as a risk allowance or carried as a written exclusion in your bid.
• Adjust contingency and schedule float to reflect unresolved items rather than assuming the most favorable reading will hold.
• Flag affected scopes for buyout and get supplier confirmation before locking in a price, since a vendor quote based on the wrong spec section creates the same exposure further down the chain.

A short checklist on logging spec conflicts walks through the five fields worth tracking for every flagged item so nothing gets lost between bid day and contract award.

Prevention: coordination habits that cut future conflicts

Most spec versus drawing conflicts trace back to drafting habits rather than complex technical disagreements. The FHWA’s specification guidance outlines five Cs for specification writing: clear, concise, complete, correct, and consistent. Applying them during document preparation prevents a large share of the RFIs that show up later.

• Maintain a cross-document matrix that tracks each element by tag, location, quantity, performance requirement, material, responsible trade, and revision date.
• Build in formal revision review cycles and give contractors real time to mark up drawings and specs before they are finalized, a practice AIA’s best-practice guidance links to fewer RFIs and change orders.
• Require a clear submittal procedure so product substitutions get checked against both the drawing tag and the written spec section, not just one of them.
• Standardize naming conventions and keep a short glossary so the same component is not called three different things across disciplines.

Pro Tip: Architects tend to think visually while spec writers think in text. A short glossary shared across both groups closes more semantic gaps than another review meeting.

How a structured bid-review tool and human oversight help

We use a structured bid-review tool to read the full bid document set, including front-end clauses, and flag likely mismatches between drawings and specifications for estimator review before submission. A single command center tracks RFIs, vendor quote leveling, and document approvals in one place, which cuts the number of conflicts that slip through during bid assembly.

Tooling surfaces probable discrepancies, but it does not decide contractual precedence. That judgment still sits with the estimator or project manager reviewing the flagged item, consistent with how AIA’s guidance frames the limits of automated review against human interpretation of contract language.

Legal implications and risk management

A spec versus drawing conflict is not just a coordination headache, it is a contract risk event the moment you notice it. Under forms like FAR 52.236-21, proceeding on your own interpretation without a written determination puts the cost of a wrong guess on the contractor, regardless of which reading seemed more reasonable at the time.

The risk runs in both directions. Builders who silently choose the cheaper interpretation expose themselves to rework costs if the owner’s written determination goes the other way. Owners and designers who leave uncoordinated documents in circulation expose themselves to delay claims and change order requests they could have avoided with clearer drafting.

Managing that risk starts with documentation discipline rather than legal maneuvering. Keep a dated record of when the conflict was identified, when the RFI was submitted, what was requested, and when (and how) the written response arrived. That record is what protects you if a dispute over cost or time ever reaches a claim or arbitration. Forensic reviewers who examine failed projects after the fact consistently point to early coordination and clear cross-referencing as the difference between a conflict that gets resolved quietly and one that becomes a claim driver, according to HKA’s forensic services overview.

The practical rule holds regardless of contract type: never let a live conflict resolve itself through silence. Silence reads later as acceptance of whichever interpretation was cheaper for you, and that reading rarely favors the contractor once a dispute reaches review.

Case studies illustrating real-world conflicts and resolutions

Patterns repeat often enough that the categories are more instructive than any single project’s details. A structural drawing calling for a beam size that does not match the load table in the specification is a common dimensional conflict; the fix is a written clarification confirming which value governs, followed by an update to both documents so the next trade working from them is not misled.

A finish schedule naming one flooring product while the specification section describes a different performance class is a typical materials conflict. Left unresolved, it surfaces at submittal review when the supplier’s data sheet does not match either the schedule tag or the spec, forcing a late substitution request that can push back procurement by weeks.

Interface conflicts between disciplines tend to be the hardest to catch early because each drawing set looks internally consistent on its own. A mechanical drawing assuming a structural opening that the structural drawings never show is a case in point. These conflicts rarely appear as contradictions, they appear as a gap, and gaps slip past single-document reviews because no individual sheet looks wrong by itself. The fix in each of these patterns is the same: identify the exact sheet, detail, and spec paragraph, submit the question in writing, and update the full document set once a determination is issued, rather than relying on verbal agreement at a site meeting.

Role of technology and software tools in detecting conflicts

Manual cross-checking a full bid package against hundreds of spec sections does not scale well once a project has more than a few dozen drawings. Software built specifically for document review can flag likely mismatches, such as a tag referenced on a drawing with no matching specification section, far faster than a manual read-through, and surface single-document-only requirements that are easy to miss under deadline pressure.

The caveat that matters is the one AIA’s best-practice guidance raises directly: specialist tools help surface mismatches, but human review remains essential to interpret contract precedence, validate any extracted text against the source document, and approve the actual RFI response. A tool that flags a hundred potential conflicts is only useful if someone with contract knowledge triages which ones matter.

For BIM-based projects, coordination at the model level catches a subset of these conflicts before documents are even issued for bid, which is a separate but complementary layer to document-level review during bidding. A partner article on BIM coordination covers how model clash detection reduces the interface-type conflicts that are hardest to catch in a flat document review. The right combination, for most bid teams, pairs automated document flagging with a human reviewer who has the authority and context to decide what gets escalated.

Recurring root causes and one habit that saves time

The conflicts we see most often trace back to late revisions issued without a corresponding update everywhere else, inconsistent terminology between disciplines, and submittals rushed through without a real markup cycle. One change helps more than most: require a one-page conflict register and a contractor markup pass before bid submission, plus a brief cross-discipline sign-off at pre-bid and pre-construction.

— arosbid team

See how ArosBid catches these conflicts before bid day

This platform automates the document checks described in this playbook and centralizes RFI tracking, vendor quote leveling, and approval workflows in one command center, so flagged conflicts do not get lost between intake and submission.

• See current plans, including One Desk, The Department, and The Whole Year, on our pricing page.
• Book a live demo to see how document review flags conflicts during an active bid.

FAQ

What is the difference between drawings and specifications?

Drawings show the location, geometry, dimensions, and quantities of a project’s components, while specifications define the materials, performance standards, workmanship, and submittal requirements for those same components. Both are part of the contract documents and must be read together, since a requirement stated in only one of them is still binding.

Do specs take precedence over drawings?

Precedence depends on the specific contract, so the governing clause in your contract documents is the first place to check. Federal contracts using FAR 52.236-21 generally have specifications govern over drawings, but you should still submit a written RFI or notice and wait for a determination rather than assume.

What are the five Cs of specification writing?

The five Cs are clear, concise, complete, correct, and consistent, a framework described in FHWA specification guidance for reducing ambiguity in written specifications. Following them during drafting cuts down on the RFIs and disputes that come from vague or contradictory language.

What should be done if there is a discrepancy between the drawings and the specifications?

Preserve both versions of the conflicting documents, record the exact sheet, detail, and spec paragraph involved, and submit a written RFI or contractual notice describing the conflict and a recommended resolution. Do not proceed on your own interpretation; wait for a written determination, since FAR 52.236-21 and standard contract practice place the risk of an unapproved adjustment on the party who acted without one.

Sources

• Attachment 4 - Development and Review of Specifications - Federal Highway Administration
• Best practices for enhancing drawings & specifications | AIA
• HKA forensic services overview

Recommended

• Construction Spec Conflicts: 5 Fields Every Estimator Must Log
• Spec says 350 tons. The drawing says 400.
• Contractors: Compliance First Construction RFP Response That Wins