Sub Bidding Process for GCs: Inviting, Comparing, and Awarding Bids

The Sub Bidding Workflow Stage by Stage

The workflow has distinct stages with different objectives and different operational requirements at each.

Stage 1: Project Setup and Scope Definition

Before any sub bidding begins, the GC defines the project's scope structure: which trades are involved, how scope gets divided among them, what the scope boundaries are between adjacent trades, and what the GC self-performs versus subs.

Strong scope definition prevents the gap and overlap problems that emerge during sub bidding. Specific patterns:

• Drawings and specifications get reviewed for trade scope clarity

• Scope boundary issues get identified upfront (who handles what when trades intersect)

• Self-perform vs sub decisions get made deliberately rather than by default

• Schedule structure gets developed enough to inform sub bidding

Weak scope definition produces sub bidding that has gaps (no one is bidding certain work) or overlaps (multiple subs are bidding the same work, with confusion about who's responsible).

Stage 2: Bid List Development

For each scope, the GC develops a list of qualified subs to invite. The list balances multiple considerations:

• Subs prequalified for the work type (insurance, financial, safety, technical capability)

• Subs with capacity for the project size and schedule

• Subs with productive past relationships

• Geographic relevance (subs who actually work in the project location)

• Competitive coverage (enough bidders to produce real competition)

• Diversity considerations where applicable

Strong bid list development produces lists with appropriate qualified subs likely to bid. Weak bid list development produces lists with too few credible bidders, lists with subs who won't actually bid, or lists with subs who shouldn't be on the list (unqualified, mismatched capacity, problematic history).

Stage 3: ITB Distribution

Once the bid list is set, the GC sends invitations to bid. The ITB package typically includes:

• Project description and basic information

• Specific scope being bid (defined enough that subs understand what's expected)

• Drawings and specifications (current versions)

• Bid form or instructions for the sub's bid format

• Bid due date and submission process

• Required documentation (insurance acknowledgment, schedule confirmation, etc.)

• Pre-bid meeting schedule if applicable

• Contact for questions

Modern GCs use ITB management platforms (BuildingConnected, Procore, ConstructConnect, Building Engines, others) that handle the distribution mechanics: sending invitations, tracking who received them, managing drawing distribution with version control, capturing acknowledgments.

Stage 4: Pre-Bid Coordination

Between ITB distribution and bid due date, GCs typically handle:

• Pre-bid meetings (mandatory or optional, on-site or virtual)

• Site visits and walkthroughs

• Questions from prospective bidders

• Addenda issuance for clarifications or modifications

• Updates to drawings and specifications

Strong pre-bid coordination ensures all bidders have the same information and base their bids on the same scope. Weak pre-bid coordination produces bids based on different understandings, which makes leveling difficult and produces dispute risk during execution.

Stage 5: Bid Receipt and Initial Review

As bid due dates approach, sub bids come in. Strong workflow:

• Bids received through the ITB management platform with timestamp documentation

• Initial review for completeness (did the sub address all required scope items?)

• Identification of bids that need clarification before full review

• Tracking of bidders who didn't respond or declined to bid

Weak workflow allows bids to come in through email or other channels without consistent documentation, which creates problems later when comparison happens.

Stage 6: Bid Leveling and Comparison

This is where bid management complexity peaks. Sub bids for the same scope rarely come in identical: one includes specific items, another excludes them; one assumes specific schedule, another doesn't; one uses different waste assumptions, etc.

Bid leveling normalizes the bids for comparison. The deeper coverage lives here.

Stage 7: Scope Gap Identification

After bid leveling, scope gaps become visible: items that no sub priced, items priced inconsistently across bids, items where assumptions differ between subs.

Identifying scope gaps before award matters because gaps that emerge after award produce change order disputes or absorbed costs. Identifying them at the bid stage allows the GC to:

• Request supplementary pricing from subs for the gap items

• Adjust the scope structure if appropriate

• Plan for the gap items as additional cost

• Self-perform the gap items

• Solicit specialty subs for gap items

Stage 8: Award Decisions

Once bids are leveled and scope gaps identified, the GC makes award decisions. The decision considers:

• Total cost (after leveling)

• Sub performance history

• Schedule reliability

• Quality reputation

• Communication and coordination capability

• Capacity to handle the project

• Bonding capability if required

Strong award decisions consider total project value rather than just lowest price. The lowest sub bid sometimes isn't the right award if other factors make it net more expensive (poor schedule performance, quality issues, coordination problems).