Order of precedence: who wins when the scope of work and drawings contradict
Order of precedence is the contractual rule that decides which document controls when a tender's documents contradict each other. When the scope of work (or specification) and the drawings disagree, the winner is whichever document the contract's order-of-precedence clause ranks higher, not whichever you read first or would prefer. Most standard forms rank the negotiated agreement and any addenda at the top, then the conditions of contract, then the specification, then the drawings, with schedules below, but the exact order varies by contract form and region, so you read the actual clause before deciding. Where there is no precedence clause (as under AIA contracts, which treat every document as complementary), a contradiction is resolved by interpretation and, in practice, by a written direction, not by silently choosing. For a bid, the safe move is never to price around a contradiction quietly: log every conflict to a register and raise it as a clarification, because a discrepancy you resolve in your own favour without confirmation becomes a variation you absorb after award.
What is an order of precedence clause?
An order of precedence clause is a term in the conditions of contract that ranks the contract documents, so that when two of them conflict, the higher-ranked one governs. It exists because a tender is assembled from many documents (the agreement, the conditions of contract, the specification, the drawings, the schedules and any addenda) written by different people at different times, and they inevitably disagree somewhere. The clause turns "which one is right?" from an argument into a lookup. Not every contract has one: some standard forms deliberately omit it and treat the documents as complementary instead. The first thing to do on any tender is establish which regime you are in, because it changes how you must treat every contradiction you find.
Which document wins when the scope of work and the drawings contradict?
When the scope of work (or specification) and the drawings contradict, the document that wins is the one ranked higher by the contract's order-of-precedence clause, and in most standard forms that is the written specification over the drawings. The reasoning is that words are less ambiguous than a drawing, and the specification is usually the more considered document. But this is a default, not a law: some forms rank them differently or treat them as equal, and a specific, detailed drawing can still override a general specification note on the same point. Two conventions apply within the drawings themselves: a figured (written) dimension governs over a dimension you scale off the sheet, and a large-scale detail governs over the same feature shown at small scale. Never assume the specification wins; confirm it in the clause, then confirm the more-specific-governs rule does not flip it.
What is the typical order of precedence, by contract form and region?
The typical order of precedence runs from the most negotiated document down to the most general, but the exact ranking is set by the contract form, which varies by region. Internationally, FIDIC contracts (Sub-Clause 1.5) rank them: the Contract Agreement, the Letter of Acceptance, the Letter of Tender, the Particular Conditions, the General Conditions, the Specification, the Drawings, then the Schedules. In US federal procurement, FAR 52.215-8 ranks the Schedule (pricing and delivery terms) first and the specifications last. In US private construction the standard forms diverge sharply: ConsensusDocs gives the specifications priority over the drawings, while AIA A201 includes no precedence clause at all and treats every document as complementary. In Australia and New Zealand, AS 4000 and AS 2124 leave discrepancies to be notified and directed by the Superintendent, with any fixed hierarchy usually written into the special conditions or annexure. The table below sets these out. Read your own contract's clause; do not carry an order across from the last job.
What if there is no order of precedence clause?
If there is no order of precedence clause, a contradiction is resolved by interpreting the documents as a whole rather than by a ranking, and in practice by a written direction from the contract administrator. This is the AIA position: the documents are complementary, and what is required by one is binding as if required by all. Where a court has to interpret such a contract, it tends to favour the specific provision over the general, the typed or handwritten term over the pre-printed one, and it reads a genuine ambiguity against the party that drafted it (the contra proferentem rule). None of that is a safe basis to price a bid on, because it is decided after the fact. During a tender the correct response is to raise the contradiction as a formal question and obtain a written answer before you commit a number to it.
How do you handle a contradiction during a bid?
During a bid you handle a contradiction by recording it, pricing it on a stated assumption, and raising it as a formal clarification, never by silently resolving it in your own favour. Log every conflict to a conflict and variation register the moment you find it, noting the two clashing documents, the clause and drawing numbers, and the interpretation you have adopted. Then raise it as an RFI or a formal clarification to the issuer, because only a written answer (an addendum) binds; your own reading does not. If the deadline forces you to price before the answer arrives, state the assumption in your returnable schedules and departures so the interpretation is on the record. A discrepancy you resolve quietly, with no clarification and no stated assumption, becomes a variation you absorb after award, which is exactly the cost the order-of-precedence exercise exists to prevent.
How does this show up in a compliance check?
Every contradiction between the scope, the specification and the drawings becomes a row in your compliance matrix and your conflict and variation register: the requirement, the two documents that clash, the order-of-precedence position, and the clarification you have raised. Missing one is not a footnote; it is an unpriced variation waiting to surface after award. This is the document-intensive work Elora Grid is built for: hand it the scope of work, the specification and the drawings, and it cross-reads them, flags every contradiction with both sources cited to document and page, and applies the contract's order-of-precedence clause to show which one governs. The commercial judgment (which assumption to price, when to qualify, when to raise a clarification) stays with your team; the tool finds the conflicts and shows its working, so nothing is resolved silently.
How standard contract forms rank the documents
| Contract form / regime | Where it applies | Top of the hierarchy | Specification vs drawings |
|---|---|---|---|
| FIDIC (Sub-Clause 1.5) | International (common in the EU, Middle East and Asia) | Contract Agreement, then the Letters of Acceptance and Tender | Specification ranks above the drawings |
| FAR 52.215-8 (Uniform Contract Format) | US federal procurement | The Schedule (pricing and delivery terms) | Specifications rank last; drawings fall under the specifications or exhibits |
| ConsensusDocs 200 | US private construction | Change orders and written amendments | Specifications given priority over the drawings |
| AIA A201 | US private construction | No ranking: documents are complementary | Neither governs; a discrepancy goes to the architect for direction |
| AS 4000 / AS 2124 | Australia and New Zealand | Not fixed by the standard form | Superintendent directs; any hierarchy is set in the special conditions |
Common contradictions and the usual tie-breaker (always confirm your clause)
| Contradiction | Usual resolution | Why |
|---|---|---|
| The specification says one thing, a drawing another | Specification governs in most forms | Words are less ambiguous than a drawing, though a specific detail can override a general note |
| A figured dimension differs from a scaled one | The figured (written) dimension governs | Scaling off a sheet is unreliable; the written value is the one intended |
| A large-scale detail differs from a small-scale view | The large-scale (more detailed) drawing governs | The detail is the more considered representation of the same feature |
| A general note conflicts with a specific clause | The specific provision governs | The specific is read as the deliberate exception to the general |
| An addendum conflicts with the base document | The later addendum governs | Addenda amend the documents they follow; the latest issue binds |
| The priced schedule conflicts with the specification | Depends on the form (the Schedule wins under FAR; the specification often wins elsewhere) | Exactly why you read the clause rather than assume a default |
- 01Find the order-of-precedence clause first. Locate it in the conditions of contract, or note its absence, before you read the technical documents, so you already know how every contradiction will be resolved.
- 02Read the documents against each other. Cross-read the scope, specification and drawings on each requirement, because a contradiction only appears when two documents describe the same thing differently.
- 03Log every conflict to a register. Record each contradiction with the two clashing documents, the clause and drawing numbers, and the interpretation you have adopted, in a conflict and variation register.
- 04Apply the precedence clause. For each conflict, apply the contract's ranking to determine which document governs, and note where the more-specific-governs rule overrides the default.
- 05Raise a clarification, do not assume. Send each material contradiction to the issuer as an RFI or clarification; only a written answer (an addendum) binds, so obtain one before you commit a price.
- 06State the assumption if you must price first. Where the deadline beats the answer, record your interpretation as a stated assumption in the returnable schedules and departures, so it is on the record rather than hidden in the number.
Common questions
Do specifications always take precedence over drawings?
No. Most standard forms (FIDIC, FAR and ConsensusDocs) do rank the specification above the drawings, but not all: AIA contracts include no precedence clause and treat the documents as complementary, and a specific, detailed drawing can override a general specification note on the same point. Always read the contract's own order-of-precedence clause rather than relying on the "specs win" rule of thumb.
What wins if a dimension on a drawing looks wrong?
A figured (written) dimension governs over a dimension you scale off the sheet, because scaling is unreliable and the written value is the one intended. If two written dimensions conflict, or a dimension conflicts with the specification, it is a discrepancy to raise as a clarification, not one to resolve yourself. Never scale a drawing to settle a dimension the figures already state.
What is the order of precedence in a FIDIC contract?
FIDIC Sub-Clause 1.5 ranks the documents: the Contract Agreement, the Letter of Acceptance, the Letter of Tender, the Particular Conditions, the General Conditions, the Specification, the Drawings, then the Schedules. A higher-ranked document governs a lower one on any inconsistency. FIDIC is common on international, European, Middle Eastern and Asian projects, so confirm the exact list in the edition your tender uses.
What should you do if the tender documents contradict each other?
Log the contradiction to a conflict and variation register, apply the contract's order-of-precedence clause to see which document governs, and raise the conflict as a formal RFI or clarification to the issuer. Only a written answer (an addendum) binds; your own interpretation does not. If you must price before the answer arrives, state your assumption in the returnable schedules so it is on the record and not an absorbed variation later.
Send a real tender. Get the output back.
Hand Elora Grid one real task and judge the result yourself.