This chapter is not legal advice. It is a plain-English tour of the small number of contract clauses that interact most directly with scope — the ones every estimator and PM should know exist, even if drafting them is counsel's job. The goal is to make the financial cost of weak contract language as visible as the financial cost of a weak scope of work.
Flow-down: AIA A401 and ConsensusDocs 750
Both AIA A401-2017 (Standard Form of Agreement Between Contractor and Subcontractor) and ConsensusDocs 750 (Standard Constructor and Subcontractor Agreement — Long Form) use a flow-down structure: prime-contract obligations bind the subcontractor through the subcontract. AIA A401 incorporates the AIA A201 General Conditions by reference; ConsensusDocs 750 integrates general terms and the agreement into a single document. The structures are slightly different; the practical effect is similar.
The implication for scope: anything you have committed to the owner in the prime contract that you want the sub to be responsible for needs a flow-down clause to survive at the sub level. Working hours. Site security. Indigenous-hire mandates. Additional BIM requirements. Site-specific safety policies. The most-organized teams consolidate every prime-contract flow-down into a single dated, version-controlled appendix — “Appendix X” in one VP's vocabulary — attached to every subcontract package. The body of the scope sheet stays project-specific. The flow-downs stay in their own document.
Order of precedence: a critical gap in unmodified AIA
AIA A201-2017 does not include an order-of-precedence clause for interpreting contract documents. The AGC's own commentary on A201 calls this out: “The A201 does not include an order of precedence for interpreting contract documents. Failure to include such a provision leads to needless uncertainty and litigation costs.” ConsensusDocs forms include an order-of-precedence framework by default.
For GCs working with AIA: this is a critical drafting gap to address in Supplementary Conditions, in the subcontract itself, or both. When the architectural drawings say one thing and the structural drawings say another — see the $45K stone-depth example in Chapter 1 — the order-of-precedence clause is what determines who pays. Without one, the answer is litigation.
Pay-if-paid vs. pay-when-paid
Pay-if-paid clauses make owner payment a condition precedent to subcontractor payment; pay-when-paid clauses are generally a timing mechanism. Pay-if-paid clauses are unenforceable as contrary to public policy in New York and California; South Carolina has a similar statutory bar; most other states enforce them only with clear and specific language. This matters for scope disputes because contested scope items often surface as withheld payment — the sub claims the scope was extra, the GC withholds, the owner withholds the GC, and the cascade begins.
“Readily inferable”
The clause that animated the strongest reactions in our interviews. A Senior PM at a Canadian ICI GC: “The whole project design contingency or readily inferable thing is really a terrible clause in a contract. Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers.” The clause is enforceable. The defensive response is operational: when the GC signs a contract with readily-inferable language, they need a corresponding design-review allowance in their bid, and they need to pass the same flow-down to every sub. Otherwise the GC is single-handedly absorbing every gap in the architect's drawings.
Time-stamped emails as evidence
A Director of Pre-Construction at a Mid-Market US GC offered one of the most practical pieces of contract-adjacent advice we heard: when bid documents are ambiguous and the team adds an allowance based on an internal interpretation, document the assumption in a time-stamped internal email. “An email is a legal binding document in court. It's pretty easy to say it's excluded if it's time-stamped.” The same discipline applies to addenda — every reissue gets a documented re-scope pass with a date, not informal note-taking.
The scope of work as Exhibit A
The principle that ties this chapter to the rest of the book: the scope of work is most powerful when it is incorporated directly into the subcontract as Exhibit A. A PM at a Mid-Market Self-Perform GC: “Our scope of work basically becomes the Exhibit A of their subcontract.” Lead-letter exclusions get migrated into the scope sheet. The scope sheet becomes the binding document. The subcontract references it directly. There is no daylight between what the sub priced and what the GC bought.