Scope of Work and Exclusions: Closing the Gaps That Trigger Disputes

Indemnity and payment clauses get the attention, but the claims that actually bleed a subcontractor's margin usually start with a scope gap: work someone assumed was included, priced by no one, and demanded at the worst possible moment. The contract's exhibits — the drawings, the specifications, the prime contract, the schedule, and a stack of addenda — define the universe of what you owe. A vague scope statement lets the general contractor read that universe broadly and the subcontractor read it narrowly, and a vague clause is resolved by who has leverage on the day, not by what was fair.

The fix is precision. The more concretely the scope ties to specific, dated, numbered documents, the less room there is for the elastic phrases that turn a fixed-price job into a series of unpaid favors.

Subcontracts routinely state that the subcontractor is bound by the prime contract "as if fully set forth herein," and that the work includes everything "shown or reasonably inferable" from the contract documents. Both phrases expand obligations well beyond the page in front of you. Incorporation by reference can bind a sub to prime-contract terms it never saw — schedule obligations, liquidated damages, dispute procedures, and broad indemnities flowing down from the owner.

Ask for the documents being incorporated and review them, and limit the flow-down to provisions that are genuinely applicable to your trade and scope. "Reasonably inferable" is harder to delete, but you can anchor it to the specific drawings and specification sections for your trade, so it cannot be used to import work from another scope entirely.

Courts and arbitrators construe an ambiguous scope against the party that could have clarified it — often the subcontractor who prepared the quote. The remedy is an explicit exclusions list. Common items worth stating out loud: layout and survey, hoisting and rigging, temporary power and lighting, cutting and patching, fire-stopping at other trades' penetrations, removal of unsuitable soils, dewatering, as-built drawings, and final cleaning. If your price did not include it, the contract should say so.

Exclusions are not adversarial; they prevent the dispute. A general contractor who reads your exclusions before signing can price the gap elsewhere instead of discovering it during construction, when the cheapest person to absorb it is whoever the contract leaves holding the ambiguity.

Confirm the subcontract scope matches your quote word for word and dollar for dollar, attach your assumptions and exclusions as an exhibit that controls over conflicting language, and pin every "reasonably inferable" or "as required" phrase to a specific, dated document list. Flag any incorporation-by-reference clause so your team can read what is actually being flowed down before signing.

This is exactly the kind of pass a first-read tool should surface for you: where the contract's scope language is broader than your quote, where exclusions are missing, and where catch-all phrases could absorb unpriced work — so your team can lock the scope down before it becomes a change-order fight.