Construction subcontract agreements: carry awarded scope and prime obligations into the subcontract

Convert bid-review decisions into a subcontract scope exhibit. Reconcile exclusions, prime-contract obligations and unresolved interfaces before award.

Guide3 min read

Published

Tower crane against an overcast sky

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Freeze the award basis
  2. Translate the bid into an interface register
  3. Trace prime obligations to the trade's work
  4. Resolve conflicts and authorize the handoff
  5. Connect the proposal comparison to award

Before a commercial GC awards a trade subcontract, reconcile the selected proposal with the intended scope, current project documents and applicable prime obligations. The lowest leveled number is not a complete subcontract: an estimator's add-back or assumed inclusion is not automatically the trade partner's commitment.

The pre-award handoff should show what the parties have agreed, what remains open and who must resolve it. The agreement and applicable law determine legal effect. This is a scope and commercial review, not legal drafting or legal advice.

Freeze the award basis

Identify the selected bidder, proposal date and revision, accepted alternates, negotiated clarifications, price, schedule assumptions and unresolved conditions. List drawings, specifications, addenda and other relevant documents by title and revision. Verify that the proposal and project team used the same set; a late addendum can change both the scope and the price basis.

Preserve the original bid and the leveling adjustments. Separate bidder-confirmed revisions from GC allowances and internal add-backs. If an exclusion was priced by the estimator but the bidder never accepted the work, it remains a gap in the subcontract handoff. Resolve quote exclusions with written responses and an explicit disposition before treating them as assigned.

Translate the bid into an interface register

Use the register to reconcile the work, not to substitute for the actual subcontract documents. For each interface identify the source, intended performer, price treatment and confirmation. Record accepted exclusions as such and name the party carrying any resulting work.

Illustrative example: an HVAC bidder includes rooftop units and setting them on curbs but excludes electrical final connections and roof flashing. The GC's leveling sheet includes an internal $12,000 add-back for the excluded work. That add-back is not a promise by the HVAC bidder to perform it.

InterfaceAward basisAction before execution
Rooftop units and settingHVAC proposal includes workConfirm equipment schedule and lifting conditions
Final electrical connectionsHVAC exclusion and GC add-backAssign electrical trade and confirm price and termination points
Curb flashingHVAC exclusion and GC add-backConfirm roofing trade scope and warranty interface
Controls and startupProposal silentClarify vendor and controls responsibilities and commissioning support

The $12,000 is illustrative and should remain a GC estimate until the team receives appropriate trade commitments. If the roof or electrical trade has not accepted its assigned work, the interface is still open even if the estimate contains enough money. Identify the owner and due date for each response and update both the buyout forecast and subcontract exhibits.

Trace prime obligations to the trade's work

Read the prime agreement and incorporated documents against the actual subcontract form. AIA's A401-2017 summary describes that form as adopting the prime contract by reference and passing contractor duties for the designated portion of work. That description applies to the form as used and modified; it does not establish the effect of another agreement.

For the specific trade, review schedule milestones, submittals, coordination, safety, quality, testing, change notices, insurance, warranty and closeout obligations. Identify the source clause, applicable work, required response or deliverable, timing and proposed assignment. Check whether the trade has the documents necessary to understand its obligations. A general incorporation reference should not end the operational review of the work and its interfaces.

For example, a requirement for equipment manuals can affect both the trade's scope and the GC's turnover schedule. Identify the person collecting and accepting construction closeout documents, the required content and the delivery date in the project handoff.

Resolve conflicts and authorize the handoff

Flag mismatched document versions, conflicting exclusions, scope holes, overlapping assignments, unaccepted schedule dates and unclear prime provisions. The estimator and PM should reconcile the intended allocation and cost; procurement should confirm the trade's written response. Have counsel and the appropriate commercial approvers review contract language and any conflicts. Do not assume a generic order-of-precedence rule resolves a particular conflict.

Release the award package only with the agreed scope, document list, qualifications and clarifications, interface register, pricing and schedule basis, and the remaining issues with owners and deadlines. If an issue remains unresolved, escalate it and document the authorization and cost treatment rather than presenting it as agreed.

Connect the proposal comparison to award

Piper Bid Leveling compares subcontractor proposals against intended scope and links findings to sources. The project team must confirm the resulting scope and terms with the trade and approve the subcontract commitment.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.