A common myth on jobsites is "the spec always wins" (or "the drawing always wins"). Neither is reliably true. Whether the specifications or the drawings control when they disagree depends entirely on the order-of-precedence clause in your contract — and many widely used contracts don't crown a winner at all.
The two common contract philosophies
1. Documents are "complementary" (the AIA approach)
Under the AIA A201 General Conditions and similar forms, the contract documents are treated as complementary — what's required by one is as binding as if required by all. There's no automatic ranking of spec over drawing. Instead, when the contractor spots a conflict, the obligation is to ask — submit an RFI and let the architect/engineer clarify in writing before proceeding. Guessing and building it wrong is on you.
2. An explicit order-of-precedence clause
Many owner contracts, ConsensusDocs forms, and federal/public contracts do spell out a hierarchy. A typical ranking, highest to lowest:
- Modifications & change orders (latest in time)
- Addenda (later addenda over earlier)
- The Agreement
- Supplementary Conditions, then General Conditions
- Specifications
- Drawings
Under a clause like this, a later change order beats everything, and the specifications may outrank the drawings — but only if your specific contract says so. Some contracts flip parts of this (e.g., figured dimensions on a drawing govern over scaled dimensions; large-scale details govern over small-scale).
The rule that's always true: don't let the field silently pick
Whatever your contract says, the failure mode is the same — a foreman, faced with a spec and a drawing that disagree, just picks one to keep moving. If that pick is wrong, you've bought rework, a possible back-charge, and a dispute with no paper trail. The fix is process:
- Catch it. Surface the conflict before installation, not after.
- Check the hierarchy. Read the order-of-precedence clause and scan for a later addendum or change order that already resolved it.
- Ask in writing. Submit an RFI so the design team rules on the record.
- Record it. Capture the resolution with citations in your project record, so the next person who hits it has the answer.
How IntelMS handles it
This conflict-detection problem is core to what IntelMS does. When you ask it a question and the governing documents disagree, it does not silently choose one — it surfaces both, with citations to each source, flags it as a conflict for human resolution, and works from the latest revision so a superseded sheet doesn't masquerade as current. Anything contractual, cost, code, or safety-related is escalated to a person rather than answered. You get the conflict caught and documented; your team makes the call.
Catch document conflicts before they cost you
Start a 14-day pilot on one real job. Ask IntelMS your actual questions and watch it cite — and flag — from your own documents.
Start a free pilot →Frequently asked
Do specs or drawings govern?
It depends on your contract's order-of-precedence clause. Some rank specifications over drawings; AIA A201 treats documents as complementary and requires an RFI. Later addenda and change orders generally supersede earlier documents.
What is an order-of-precedence clause?
A clause that ranks the contract documents so the higher-ranked one controls a conflict. Typical order: change orders → addenda → agreement → conditions → specifications → drawings, but it varies.
What should I do when they conflict?
Don't let the field pick. Document both, check the hierarchy and any later change order, submit an RFI for a written ruling, and record the resolution with citations.