FAR 52.215-8—Order of Precedence-Uniform Contract Format.
Plain-English Summary
FAR 52.215-8, Order of Precedence—Uniform Contract Format, tells the reader how to resolve conflicts when different parts of a solicitation or contract say different things. It applies to documents prepared using the Uniform Contract Format and establishes a fixed hierarchy among the Schedule (excluding the specifications), representations and other instructions, contract clauses, other documents/exhibits/attachments, and the specifications. Its purpose is to prevent ambiguity and litigation over which provision controls when terms appear inconsistent across sections of the solicitation or contract. In practice, this clause is a tie-breaker: if a requirement in the specifications conflicts with a clause, the clause controls; if instructions conflict with the Schedule, the Schedule controls, and so on down the list. This matters for both offer preparation and contract administration because contractors must price and perform to the controlling text, while contracting officers and acquisition teams must draft documents carefully to avoid unintended conflicts. The clause does not eliminate the need to read the whole solicitation or contract together, but it provides a clear rule for resolving inconsistencies when they cannot be reconciled.
Key Rules
Fixed hierarchy controls conflicts
Any inconsistency in the solicitation or contract must be resolved using the clause’s stated order of precedence. The listed order is mandatory and applies only when provisions cannot be read consistently.
Schedule outranks most sections
The Schedule, excluding the specifications, has the highest priority. If the Schedule conflicts with instructions, clauses, attachments, or specifications, the Schedule controls unless the conflict is within the Schedule’s excluded specifications portion.
Instructions and representations next
Representations and other instructions come after the Schedule. This means proposal instructions, certifications, and similar guidance yield to the Schedule but take precedence over contract clauses, attachments, and specifications when the clause’s hierarchy is applied.
Contract clauses control lower-level documents
Contract clauses outrank other documents, exhibits, and attachments, as well as the specifications. If a clause conflicts with an attachment or specification, the clause governs unless another higher-ranked section resolves the issue.
Specifications are lowest priority
Specifications are last in the order of precedence. They control only when they do not conflict with any higher-ranked part of the solicitation or contract.
Applies to both solicitation and contract
The clause governs inconsistencies in either the solicitation or the resulting contract. That means it is relevant during proposal preparation, award, and performance when interpreting the final agreement.
Responsibilities
Contracting Officer
Draft the solicitation and contract so the Uniform Contract Format sections are consistent, and use the clause to resolve any unavoidable conflicts. The contracting officer should ensure the hierarchy is understood during evaluation, award, and administration.
Contractor
Review the entire solicitation and contract for inconsistencies, identify which provision controls under the clause, and base pricing, proposals, and performance on the controlling text. The contractor should not assume a lower-level document overrides a higher-level one.
Agency/Acquisition Team
Prepare the Schedule, instructions, clauses, attachments, and specifications in a coordinated way to minimize conflicts. The team should align requirements across sections so the order of precedence is needed only as a backstop.
Legal/Policy Staff
Advise on interpretation when conflicts arise and help ensure the solicitation structure follows the Uniform Contract Format and applicable prescription. They may also help determine whether a purported inconsistency is real or can be harmonized.
Practical Implications
This clause is a built-in conflict resolver, so parties should always check the hierarchy before claiming one section overrides another.
A common pitfall is assuming the specifications always control technical requirements; under this clause, specifications are actually the lowest-ranked item.
Another frequent issue is overlooking that the Schedule excludes the specifications, so not every item in the Schedule has the same priority.
Contractors should flag inconsistencies during the solicitation phase, because relying on a lower-ranked document can lead to proposal errors, performance disputes, or uncompensated work.
Contracting officers should use careful cross-referencing and editing to avoid accidental contradictions, since the clause resolves conflicts but does not prevent them.
Official Regulatory Text
As prescribed in 15.209 (h) , insert the following clause: Order of Precedence-uniform Contract Format (Oct 1997) Any inconsistency in this solicitation or contract shall be resolved by giving precedence in the following order: (a) The Schedule (excluding the specifications). (b) Representations and other instructions. (c) Contract clauses. (d) Other documents, exhibits, and attachments. (e) The specifications. (End of clause)