A door schedule on the drawings calls for one hardware set. Division 08 of the spec calls for another. Neither document is wrong on its own — they just don't agree with each other, and now someone in the field has to decide which one to build. Spec vs. drawing conflicts are one of the most common sources of RFIs on a commercial set, and the honest answer to "which one wins" depends entirely on which contract is governing the job — a fact that surprises a lot of owners and contractors who assume there's one universal rule.
There is no universal rule — it depends on the contract
The most common misconception is that specifications automatically override drawings, full stop, on every project. That belief is real, it's just misapplied. It comes from federal construction contracting, where FAR 52.236-21 ("Specifications and Drawings for Construction") explicitly states that in case of a difference between drawings and specifications, the specifications govern — along with related rules that large-scale drawings govern over small-scale drawings, and that a schedule shown on any drawing takes precedence over conflicting information elsewhere on that or any other drawing.
That's a real rule — on a federal job. It is not the rule on most private commercial work, which runs on AIA contract documents instead. AIA A201 (the General Conditions most commercial owner-architect and owner-contractor agreements incorporate) treats the drawings and specifications as complementary, not ranked. If something appears in either the drawings or the specs, it's part of the contract requirement — a contractor can't point to the drawings to skip a spec requirement, or vice versa. AIA deliberately left out a precedence clause, on the theory that an artificial hierarchy would substitute for the architect's actual judgment when a real conflict shows up.
ConsensusDocs contracts split the difference. The ConsensusDocs 200 agreement's standard order of precedence puts change orders and contract amendments first, then the owner-contractor agreement itself, then drawings and specifications together in the same tier — but within that tier, the specifications are given priority over the drawings when the two genuinely conflict.
"Specs always win" is a federal contracting rule that gets carried, incorrectly, into private AIA-based jobs where no such default exists. Checking which contract framework actually governs your project — not assuming — is the first step before anyone argues about which document controls.
What actually happens on an AIA job when the two disagree
On a standard AIA-governed private project, there's no shortcut. When a contractor finds a place where the drawings and specifications genuinely contradict each other — not just where one is silent and the other fills in detail, but where they actively conflict — the contract process is:
- The contractor identifies the discrepancy and submits it as a Request for Information (RFI) rather than picking whichever document is cheaper or faster to build.
- The architect reviews both documents, along with the design intent behind them, and issues an interpretation — sometimes as a straightforward RFI answer, sometimes as a formal clarification or a full Architect's Supplemental Instruction (ASI) if the fix changes scope.
- If the architect's answer changes the cost or schedule of the work, that interpretation becomes the basis for a change order.
None of that is fast. Even a same-week RFI turnaround means the crew working that section either stops, works around it, or proceeds at risk — and if the eventual answer changes the scope, that becomes a change order layered on top of whatever schedule impact the wait already caused. This is the same mechanism covered in more detail in the hidden cost of coordination conflicts: RFI count itself isn't the real problem, but a spec-drawing contradiction sitting in an active work area is exactly the kind of RFI that carries real cost, because it stops production rather than just clarifying a detail.
Why these conflicts happen in the first place
Drawings and specifications are produced by different people, on different timelines, often revised independently as a project moves from design development through construction documents. A door hardware set gets value-engineered in the spec section during a late-stage cost review, but the drawing's door schedule — a separate file, on a separate discipline's sheet set — doesn't get the corresponding update. A structural note calls out a fire rating that the architectural spec section states differently for the same assembly. None of this is anyone acting in bad faith; it's what happens when two document types, maintained by two different workflows, both have to describe the exact same piece of building.
That's also why these conflicts cluster where coordination complexity is highest — multi-discipline interfaces, assemblies that get referenced from more than one spec division, anything that got revised late in design. The same pattern shows up in where coordination-error costs actually come from: the projects most exposed to this kind of conflict are the ones where several disciplines' documents have to agree with each other on the same detail, not the ones with the biggest overall document count.
Catching it before bid, instead of resolving it by RFI
The RFI process above is how a spec-drawing conflict gets resolved once it's discovered in the field — but "discovered in the field" is the expensive version. The cheaper version is finding the same contradiction during a document review pass before the set goes out to bid, when the fix is a one-line correction in the issued set instead of a stopped crew and a change order.
That's the difference between a spec-vs-drawing conflict as a live field problem and the same conflict as a line item in a findings report: sheet-located, priced, and fixed before anyone breaks ground. Anatomy of a findings report covers what that actually looks like — every conflict tied to a specific sheet and spec section, with the dollar exposure and schedule impact attached, rather than a general note that "coordination should be checked." A drawing set that's actually ready for bid is one where these cross-document contradictions have already been run down, not one where they're waiting to surface as the first round of RFIs after the crew shows up.
Key takeaways
- There's no universal rule for who wins a spec vs. drawing conflict — it depends entirely on the governing contract.
- AIA A201, the framework behind most private commercial work, treats drawings and specs as complementary with no built-in precedence — the architect interprets, and the contractor RFIs.
- ConsensusDocs 200 gives specifications priority over drawings within their shared precedence tier; federal contracts under FAR 52.236-21 give specifications priority outright.
- "Specs always win" is a federal contracting rule that gets misapplied to private AIA jobs, where it doesn't exist by default.
- These conflicts are cheaper to catch in a pre-bid document review than to resolve through an RFI once a crew is standing in front of the contradiction.
Knowing who wins on paper doesn't make the conflict disappear — it just tells you who has to make the call once it's already in front of a crew. The better outcome is not needing that call at all: a set where drawings and specs were checked against each other before bid, so the only decision left in the field is which trade shows up next.
Frequently Asked Questions
Do specifications or drawings take precedence in a construction contract?
It depends on the governing contract, not a universal rule. Federal contracts under FAR 52.236-21 explicitly state that specifications govern over drawings. ConsensusDocs 200 gives specifications priority over drawings within their shared precedence tier. Most private commercial work runs on AIA A201, which treats drawings and specifications as complementary with no built-in winner — conflicts go to the architect for interpretation instead.
What happens when the specs and drawings disagree on an AIA-governed project?
The contractor identifies the discrepancy and submits it as an RFI rather than choosing whichever document is more convenient to build. The architect reviews both documents against the design intent and issues an interpretation, which can become a formal clarification, an Architect's Supplemental Instruction, or the basis for a change order if it affects cost or schedule.
Is it true that specifications always take precedence over drawings?
No — that's a common misconception carried over from federal contracting rules like FAR 52.236-21, where specifications do govern by default. On most private commercial projects using AIA contract documents, there is no default precedence; the architect's interpretation controls when the two genuinely conflict.
Why do spec vs. drawing conflicts happen in the first place?
Drawings and specifications are produced by different people on different timelines, and both have to describe the same building detail independently. A late-stage change to a spec section, like a value-engineered hardware set, doesn't always get mirrored on the corresponding drawing, and vice versa. These gaps cluster around high-coordination details that multiple disciplines' documents both have to describe consistently.
How can spec vs. drawing conflicts be caught before they become an RFI in the field?
A cross-discipline document review before bid checks the drawings and specifications against each other directly, catching contradictions while they're still a one-line correction in the issued set rather than a stopped crew and a change order. That review produces a sheet-located, priced findings report instead of leaving the contradiction to surface as the first round of field RFIs.