Many subcontract disputes are not caused by a missing term. They are caused by two documents saying different things: the proposal assumes one scope, the statement of work requires another, and the flowdown exhibit incorporates a third set of obligations.
An order-of-precedence clause is the contract's conflict-resolution rule. It deserves attention before signature because a document that appears secondary may control a critical scope, price, delivery, or compliance issue.
The FAR uses an express hierarchy in some contracts
FAR 52.215-8 provides an order for resolving inconsistencies under the Uniform Contract Format: the Schedule, representations and other instructions, contract clauses, other documents and attachments, and then specifications. That federal hierarchy does not automatically govern every subcontract, but it shows why written precedence rules matter.
Official source: FAR 52.215-8 — Order of Precedence—Uniform Contract Format.
Map the entire subcontract package
- Subcontract or purchase order terms.
- Statement of work and technical specifications.
- Proposal, quote, assumptions, and exclusions.
- Prime-contract clauses and flowdown exhibits.
- Drawings, schedules, data-item descriptions, and quality documents.
- Cybersecurity, CMMC, data-rights, labor, or sourcing attachments.
- Task orders, change orders, and later modifications.
Watch for a proposal placed at the bottom
A subcontractor may price a job around express proposal assumptions or exclusions. If the contract incorporates the proposal but gives it lower precedence than the prime's statement of work or specifications, those assumptions may not protect the subcontractor when the documents conflict.
The same issue can arise when a flowdown exhibit says it controls over negotiated commercial terms.
Resolve known conflicts before execution
Order-of-precedence language is useful for unexpected inconsistencies, but it should not substitute for fixing a conflict everyone already knows exists. If scope, delivery, workshare, data rights, or price assumptions differ across documents, identify the specific conflict and resolve it in the signed agreement or modification.