If someone told you that construction specifications always override drawings when there’s a conflict, you’d probably believe them. Most people do. It’s one of the most widespread beliefs in the industry, and it’s repeated so often that even experienced architects accept it as fact. But what do the contracts actually say? The answer might surprise you.
This podcast is also available on YouTube, Spotify, and Apple Podcasts
Surprise: Pop Quiz!
Let’s start with something I hear all the time from ARE candidates and even experienced architects. See if you can answer this question correctly:
Here’s your question:
If there is a discrepancy between the drawings and specifications in a set of construction documents, which of the following takes precedence?
A) Drawings
B) Specifications
C) Whichever has the more stringent requirement
D) Neither – the architect must provide an interpretation
After years of coaching ARE candidates and moderating the ARE Facebook group, I’ve seen countless people select option B, convinced that specifications always win.
But the correct answer is D.
This isn’t just a trivial exam question. Understanding this relationship correctly is crucial both for passing your ARE and for your daily practice as an architect.
What AIA A201 Says About Construction Specifications and Drawings
Let’s start with the facts. What do the AIA A201 General Conditions actually say about which document takes priority?
AIA A201, the General Conditions of the Contract for Construction, contains specific language about this in Section 1.2.1.
It states:
“The Contract Documents are complementary, and what is required by one shall be as binding as if required by all.”
Let that sink in for a moment.
If something appears in either the drawings OR the construction specifications, it’s required. You can’t ignore one document in favor of the other.
This language has been consistent across multiple editions of A201 because it reflects how construction documents actually function together.
When conflicts do occur, A201 doesn’t establish a rigid pecking order. The architect is responsible for interpreting any inconsistencies between documents.
The AIA could have easily included language establishing specs over drawings if that was the intent, but they didn’t.
Now here’s where the myth comes from. Some construction contracts, like government contracts under FAR 52.236-21, do specify that “specifications govern over drawings.” This is exactly where the “specs always win” belief originates. Someone works on a federal project, learns the FAR rule, and then incorrectly applies it to every project they touch, including private AIA contracts where that rule doesn’t exist.
The fact that government contracts need to add a specific clause proves there’s no universal rule. If specs always governed by default, the clause would be unnecessary.
If you want to go deeper on how AIA contracts structure these relationships, our AIA Contracts 101 course breaks down B101, A201, and C401 in detail.
The Practical Reality
Now let’s talk about why this matters in the real world.
Imagine if specs always took precedence. Picture this scenario:
- Your drawings show an expensive custom lighting fixture
- Your specs only mention standard fixtures
- What would happen?
Contractors would deliberately bid based on the cheaper spec, knowing they could argue against the more expensive drawn detail later.
They’d use your own documents against you:
“Sorry, we don’t have to provide those fancy fixtures because they’re not in the specs, which take precedence.”
This creates a perverse incentive to find and exploit discrepancies rather than seeking clarification.
It gets worse when we think about payment applications.
- As the architect, you review and approve contractor payment applications
- If a contractor followed one document but ignored the other claiming “precedence,” you’d be in a real bind
- You’d have to either approve payment for incomplete work or deny payment for work that technically followed half of your documents
Can you see how this puts architects in an impossible position and undermines our authority?
The complementary documents approach properly allocates risk and responsibility:
- Contractors must flag discrepancies
- Architects must resolve them
This encourages communication and problem-solving rather than playing gotcha with contract loopholes.
How Construction Specifications and Drawings Work Together
So how do drawings and specs work together in practice?
Think of them as having different strengths but serving the same goal.
Drawings excel at showing:
- Spatial relationships
- Dimensions
- Quantities
- Visual details
Construction specifications excel at describing:
- Quality standards
- Performance requirements
- Technical criteria
- Installation methods
Specifications are typically organized in the project manual (sometimes called the spec book) and arranged by CSI MasterFormat divisions, while drawings are organized by discipline: architectural, structural, mechanical, electrical, and so on.
Together they create a complete picture of what’s to be built.
A Real-World Example
I once reviewed a project where the structural drawings didn’t show any reinforcing in a masonry wall.
But the masonry specification clearly required rebar at specific spacing.
Under the complementary principle, the contractor had to provide the rebar because it was in the specs, even though it wasn’t shown on the drawings.
This is a perfect example of why an “either/or” approach doesn’t work.
- If specs always governed, the rebar would still be required
- But if drawings governed, it wouldn’t be, showing the flaw in any universal precedence rule
In well-coordinated documents, information is distributed logically: dimensions on drawings, material properties in specs.
But sometimes overlap is inevitable, which is why coordination between drawings and specifications is so important.
Neither document should be read in isolation. They’re two halves of a whole.
This is why exam questions often include both drawings and specs. They’re testing your ability to synthesize information from multiple sources, just like in real practice.
Resolving Conflicts Between Drawings and Specifications
So what happens when there is a conflict between drawings and specifications?
AIA A201 Section 3.2.2 is clear about what contractors must do:
Contractors must carefully study both drawings and specifications before starting work.
When they find conflicts, they must promptly report them to the architect, often using RFIs (Requests for Information).
This isn’t just a best practice. It’s a contractual obligation.
Proceeding without clarification puts contractors at risk.
As the architect, you have the authority to interpret the documents and decide which requirement applies. The goal is to preserve design intent while being fair to all parties.
Remember, you’re not bound by a universal “specs win” rule unless your specific contract establishes one.
Common Myths About Document Precedence
Let’s clear up some of the most common myths about how drawings and specs relate to each other:
Myth #1: “Specifications always take precedence over drawings.”
Reality: This is only true if your specific contract establishes that hierarchy. Standard AIA A201 treats drawings and specifications as complementary documents with equal weight. Unless you’re working under federal FAR regulations or a heavily modified contract, standard AIA documents treat them as equals.
And here’s something to watch for in practice: owners’ legal counsel frequently amends A201 to add a strict order of precedence. Always read the specific contract for your project, not just the standard template.
A typical order of precedence clause might look something like this:
- The Agreement (A101)
- Addenda
- Supplementary Conditions
- General Conditions (A201)
- Specifications
- Drawings
When you see a clause like this in a modified contract, that contract has established specs over drawings. But that’s a project-specific amendment, not a universal rule.
Myth #2: “If it conflicts, follow the more stringent requirement.”
Reality: While this is often a reasonable guideline (and AIA A201 leans this way), the architect has the final say in determining which requirement applies.
Myth #3: “Only the spec book matters in the end.”
Reality: Drawings contain crucial information that specifications often don’t, and courts have held contractors to things shown only on drawings.
Myth #4: “If it’s not shown on the drawings, it’s not included.”
Reality: If it’s in the specs, it’s required, whether or not it appears on the drawings (and vice versa). This is the entire point of the complementary documents principle.
Best Practices for Working with Construction Documents
For architects and project teams, here are some best practices to keep drawings and specs coordinated:
Establish clear division of content:
- Put dimensional information on drawings
- Put quality and performance requirements in specifications
- Don’t duplicate information unnecessarily
Use consistent terminology:
- Use the same terms in both drawings and specs
- If a material is “Type A” in the specs, don’t call it “Type 1” on the drawings
Cross-reference between documents:
- Add drawing annotations like “See Spec Section 07920 for sealant requirements”
- Keep references current if sheet numbers or spec sections change
Review documents together before issuing:
- Compare drawings and specs through quality assurance and quality control processes before finalization
- Verify that products in specifications appear on drawings and vice versa
- Use checklists to compare schedules, finishes, and material callouts
Keep your team in sync:
- Ensure drawing teams and specification writers communicate throughout the project
- When changes are made to one document, update the other. This is where change orders and contract modifications become critical during construction
Pay special attention to Division 01:
- Ensure general requirements are consistently represented in both documents
- Clarify which document governs specific requirements when necessary
What This Means for ARE Candidates
If you’re preparing for the Architect Registration Exam, here’s how to approach this on the exam.
This topic shows up specifically in PjM (where document coordination and contract interpretation are tested), PDD (where construction document production and specifications are tested), and CE (where construction administration and resolving field conflicts are tested).
When you see a question involving both drawings and specifications:
- Don’t automatically assume one document takes priority over the other
- Look for contextual clues about which is more specific to the situation
- Remember the complementary documents principle: both documents form the contract
- The exam is testing your understanding of coordination and interpretation, not a memorized hierarchy
This knowledge applies directly to your future practice:
- Keep specifications and drawings coordinated to avoid conflicts in the first place
- Respond promptly to RFIs about discrepancies
- Understand how risk is allocated between parties when conflicts arise
- This skill directly translates to being a more effective architect
Our ARE 101 Membership covers exactly how to handle these types of document coordination questions on the exam, with plenty of practice scenarios to build your confidence. You can also dive deeper into specific divisions with PjM 101, PDD 101, and CE 101.
And if you want structured coaching, accountability, and a clear roadmap through the entire licensing process, ARE Boot Camp is designed to get you from where you are now to fully licensed.
Frequently Asked Questions
What are construction specifications?
Construction specifications are the written portion of the contract documents that describe materials, workmanship, quality standards, and performance requirements for a project. While drawings show what goes where, specifications explain what materials to use and how to install them. Together, they create the complete picture of what’s required to build the project.
Do construction specifications take precedence over drawings?
No, not automatically. Under standard AIA contracts, specifically A201 Section 1.2.1, drawings and specifications are complementary documents. What’s required by one is as binding as if required by all. Neither document automatically overrides the other. The architect is responsible for interpreting any conflicts that arise.
What is the difference between drawings and specifications in construction?
Drawings communicate spatial information: dimensions, locations, quantities, and visual details. Specifications communicate quality information: materials, performance requirements, standards, and installation methods. Both carry equal legal weight as contract documents under standard AIA contracts.
What happens when drawings and specifications conflict?
The contractor must report the conflict to the architect through an RFI (Request for Information). The architect then provides an interpretation. Contractors are not permitted to proceed without clarification and cannot simply choose whichever document favors their bid.
What is a spec book in construction?
A spec book (also called the project manual) is the bound volume containing the written specifications for a construction project. It includes bidding documents, contract conditions, Division 01 general requirements, and the technical specifications organized by CSI MasterFormat divisions.
Construction Specifications are NOT Always The Winner
Construction specifications and drawings are complementary documents. The claim that “specs always take precedence” is a misunderstanding of how construction contracts actually work.
Understanding this relationship will help you both on the ARE and throughout your career in construction administration.
This is what Young Architect is all about: teaching you the concepts and understanding of how things work in the real world of architecture.
When you truly understand the “why” behind these concepts, it’s so much easier than trying to blindly memorize things for the exam.
And remember, this isn’t just about passing a test. This is about becoming a skilled architect who can navigate conflicts confidently in practice.
