Order of Precedence of Contract Documents

1. Why the Order of Precedence Matters
Construction contracts are not a single document. They are a package: the Agreement, General Conditions, Supplementary Conditions, Specifications, Drawings, Addenda, and later Modifications (change orders, construction change directives, field orders). These pieces are written by different people, at different times, and are revised repeatedly before and after award. Conflicts, gaps, and ambiguities are inevitable. A drawing may call for one material while the specification calls for another; an addendum may revise a detail that the general conditions still describe the old way.

Without an agreed rule for resolving these conflicts, every discrepancy becomes a negotiation, an RFI with no clear answer, a potential change order, or a claim. The Order of Precedence clause establishes, in advance, which document governs when two documents cannot be reconciled. For the Construction Manager (CM), this clause is one of the most powerful tools in Contract Administration because it:
• Reduces disputes and claims by making interpretation predictable.
• Supports timely responses to RFIs and prevents schedule impacts.
• Protects the Owner from paying twice for the same requirement or paying for the Contractor's interpretation.
• Supports the CM's role in document coordination, constructability review, and change management.
• Provides a defensible basis for recommendations to the Owner when the CM is asked whether a Contractor's request is a legitimate change or simply contract compliance.

The CMAA Standards of Practice treat the development and coordination of contract documents, and the recommendation of clear interpretation provisions, as part of the CM's responsibility during design and procurement. The CM then administers that provision during construction.

2. What the Order of Precedence Is
The Order of Precedence (sometimes called the precedence clause, hierarchy of documents, or conflicts clause) is a contractual provision that ranks the contract documents so that, in the event of an irreconcilable conflict, the higher-ranked document controls. It is normally found in the General Conditions or Supplementary Conditions, and it is sometimes repeated or modified in the Agreement.

Two important qualifications:
• The clause applies only to true conflicts. Most standard forms (AIA, EJCDC, ConsensusDocs, DBIA) first state that the documents are complementary: what is required by one is as binding as if required by all. The Contractor must perform the work reasonably inferable from the documents as a whole as being necessary to produce the indicated result. Precedence is the tie-breaker used only after an attempt to read the documents together fails.
• The clause is contract-specific. The hierarchy below is typical, but the actual contract language always governs. Exam questions sometimes test exactly this point.

3. The Typical Hierarchy
A commonly used order, from highest to lowest authority, is:

1. Modifications – Change Orders, Construction Change Directives, written amendments, and (depending on the contract) field orders and Architect's/Engineer's written interpretations issued after execution. The latest-dated modification governs over earlier ones.
2. The Agreement (the signed contract form) – includes the contract sum, contract time, and the list of contract documents.
3. Addenda – issued during bidding; later addenda govern over earlier ones. Addenda modify the bidding and contract documents and are therefore above the documents they modify.
4. Supplementary (Special) Conditions – project-specific modifications of the General Conditions.
5. General Conditions – the standard legal and administrative framework.
6. Technical Specifications – Divisions of the Project Manual describing quality, materials, workmanship, and administrative requirements (Division 01).
7. Drawings – quantity, location, dimension, and arrangement of the work.
8. Referenced standards and other documents incorporated by reference (codes, ASTM, ACI, manufacturer's instructions) unless the contract states otherwise.

Within these categories, additional sub-rules are commonly stated:
• Specifications govern over Drawings in many public and federal contracts (FAR 52.236-21 Specifications and Drawings for Construction: in case of difference, the specifications govern). However, some private contracts give neither precedence and require the Architect/Engineer to interpret; others state that the more stringent requirement or the greater quantity or better quality governs. Read the clause.
• Large-scale drawings govern over small-scale drawings (a detail at 1 1/2 inch = 1 foot governs over a plan at 1/8 inch = 1 foot).
• Figured (written) dimensions govern over scaled dimensions. Never scale drawings to resolve a conflict when a dimension is given.
• Schedules on drawings (door schedules, finish schedules) typically govern over graphic representations when expressly stated.
• Written words govern over figures (numerals); handwritten governs over typed; typed governs over printed (boilerplate), reflecting the presumption that the more specific and more recent expression reflects actual intent.
• Later-dated documents govern over earlier-dated documents of the same type.
• Specific provisions govern over general provisions.

A useful way to remember the logic: the documents that are most recent, most specific, and most deliberately negotiated for this project sit at the top; standardized, general, and reference material sits at the bottom. Modifications are the most recent expression of the parties' intent, so they rank first. Printed general conditions were written for every project, so they rank below project-specific supplementary conditions.

4. How It Works in Practice

During Design and Procurement
• The CM reviews the proposed General and Supplementary Conditions and recommends that a clear order of precedence clause be included and that it be consistent across all contract packages (critical on multiple-prime projects).
• During constructability and coordination reviews, the CM identifies conflicts between drawings and specifications and has them corrected before bid, so the precedence clause is needed as rarely as possible.
• The CM confirms that addenda are issued, acknowledged on bid forms, and listed in the Agreement so they are unambiguously part of the contract.

During Construction
1. Contractor's duty to review and report. Standard conditions require the Contractor to carefully study and compare the contract documents and to promptly report to the Architect/Engineer (through the CM) any errors, inconsistencies, or omissions discovered before proceeding. A Contractor who proceeds with knowledge of a conflict without reporting it generally bears the cost of correction.
2. Complementary reading first. When a discrepancy is raised (usually by RFI), the first step is to determine whether the documents can be reconciled: does one document simply add detail the other omits? If so, there is no conflict and both apply.
3. Apply the precedence clause. If the documents truly conflict, the hierarchy identifies the governing requirement.
4. Interpretation authority. In most delivery methods, the Architect/Engineer of record is the initial interpreter of the design documents. The CM facilitates, logs, tracks response times, and evaluates the cost and schedule implications, but does not unilaterally redesign or waive requirements. In agency CM, the CM advises the Owner; in CM at-Risk, the CM also holds contractual risk and must be careful about its own reliance on the documents.
5. Change or no change? Once the governing requirement is identified, the CM determines whether the Contractor's bid reasonably should have included it. If the governing document clearly required the work, there is no change. If the governing requirement itself is being altered by the interpretation, or if the conflict was patent and the Contractor properly relied on the lower-cost interpretation after inquiry, a change order may be warranted.
6. Document everything. RFI logs, written interpretations, Architect's Supplemental Instructions, and field directives become part of the record and may themselves rank near the top of the hierarchy as modifications.

Patent vs. Latent Ambiguity
A patent ambiguity is obvious on the face of the documents; a reasonable bidder would notice it and is expected to ask before bidding. A Contractor who fails to inquire about a patent ambiguity usually cannot later claim extra compensation for the more expensive interpretation. A latent ambiguity is hidden and only becomes apparent during performance; here the rule of contra proferentem (ambiguities construed against the drafter, usually the Owner) may apply, provided the Contractor's interpretation was reasonable and actually relied upon at bid. The order of precedence clause reduces the number of ambiguities that reach this stage.

5. How to Answer Exam Questions on This Topic
CCM exam questions in the Contract Administration domain tend to present a short scenario (a conflict between a drawing and a specification, between an addendum and the general conditions, between a change order and the original drawings) and ask which document governs, what the CM should do, or whether the Contractor is entitled to a change. Approach them in this sequence:

Step 1 – Identify the document types in play. Translate the scenario into categories: is this a modification, agreement, addendum, supplementary condition, general condition, specification, drawing, or referenced standard?
Step 2 – Ask whether it is a real conflict. If one document is silent and the other speaks, there is no conflict; both apply and the Contractor must perform.
Step 3 – Apply the stated clause if the question gives one. If the question quotes contract language (for example, the contract states the more stringent requirement governs), that language overrides your memorized hierarchy.
Step 4 – Otherwise apply the typical hierarchy. Modifications > Agreement > Addenda > Supplementary Conditions > General Conditions > Specifications > Drawings. Later over earlier; specific over general; large scale over small scale; dimensions over scaling.
Step 5 – Choose the process answer that respects roles. The CM facilitates and advises; the Architect/Engineer interprets design intent; the Owner decides on changes; the Contractor must notify before proceeding.

Exam Tips: Answering Questions on Order of Precedence of Contract Documents

• Memorize the standard order and its logic. A mnemonic some candidates use: Must Always Ask Someone Great to Sort Drawings – Modifications, Agreement, Addenda, Supplementary Conditions, General Conditions, Specifications, Drawings. Understanding the logic (recent and specific beats old and general) lets you reconstruct the order if you forget the list.
• The contract always wins over the textbook. If the stem says the contract establishes a particular precedence, use it even if it differs from the typical order. Watch for phrases such as the contract documents state or the Supplementary Conditions provide.
• Change orders and other executed modifications generally rank highest because they are the latest agreement of the parties. A question that pits a signed change order against an original drawing is testing this.
• Addenda rank above the documents they modify but below the Agreement and modifications. If an addendum conflicts with a specification section, the addendum governs. If two addenda conflict, the later one governs.
• Supplementary Conditions beat General Conditions. Project-specific modifications override the standard printed form.
• Specifications typically beat Drawings, especially on public and federal work. But if answer choices include a reference to the Architect/Engineer interpreting or to the more stringent requirement governing, check whether the stem signals a private AIA-type contract where no fixed precedence between drawings and specifications is stated.
• Never scale a drawing when a written dimension exists. Figured dimensions govern. Large-scale details govern over small-scale plans.
• Words over numbers; handwritten over typed; typed over printed. These reflect the presumption of deliberate intent.
• Complementary first, precedence second. If an answer choice says both requirements apply because the documents are complementary and the scenario describes an omission rather than a contradiction, that is usually the correct answer, not the precedence hierarchy.
• Watch for the Contractor's notice duty. If the Contractor knew of a discrepancy and proceeded without reporting it, the Contractor is typically responsible for the cost of correction. If the Contractor properly submitted an RFI and waited, the analysis shifts to whether the governing requirement constitutes a change.
• Patent ambiguity = duty to inquire before bid. If the conflict was obvious in the bidding documents, the Contractor cannot rely on the cheaper interpretation after award. Latent ambiguity may be construed against the drafter if the Contractor's interpretation was reasonable.
• Respect the CM's role in answer choices. Eliminate options in which the CM unilaterally interprets design intent, redesigns, or directs extra work without Owner authorization. Prefer options in which the CM logs the RFI, coordinates with the Architect/Engineer, evaluates cost and schedule impact, and recommends a course of action to the Owner.
• Referenced standards are at the bottom unless the contract elevates them. A conflict between a spec and an ASTM standard it references is usually resolved in favor of the spec, which may require more than the minimum standard.
• Multiple-prime and multiple-package projects: the best practice answer is consistent precedence language across all packages, coordinated by the CM during procurement.
• Read for timing words. Later-dated, most recent, subsequently issued, and revised are cues that the newer document governs.
• Do not over-think with legal doctrines unless the question clearly asks about ambiguity or risk allocation. Most precedence questions are answered by the hierarchy and the complementary-documents rule.

Quick Reference Summary
• Purpose: resolve irreconcilable conflicts among contract documents predictably; reduce disputes, claims, and delay.
• Rule 1: documents are complementary; read them together before invoking precedence.
• Rule 2: typical hierarchy – Modifications, Agreement, Addenda, Supplementary Conditions, General Conditions, Specifications, Drawings, Referenced Standards.
• Rule 3: later over earlier; specific over general; specs over drawings (typically); large scale over small scale; figured dimensions over scaled; words over figures; handwritten over typed over printed.
• Rule 4: the actual contract clause governs over any memorized default.
• CM's role: recommend and coordinate the clause before bid, eliminate conflicts through document review, administer RFIs and interpretations during construction, evaluate change entitlement, and document the record.
• Contractor's role: study and compare the documents, report discrepancies before proceeding, and bear the cost of knowingly proceeding without notice.