Should GCs Send a Scope Sheet With the ITB? How to Pre-Level Subcontractor Bids Before Bid Day

Key takeaways

• Send the scope sheet with the ITB if you want comparable subcontractor pricing on bid day.
• Bid leveling starts before proposals arrive, not after the recap is already under pressure.
• A useful scope sheet standardizes addenda, alternates, allowances, breakouts, qualifications, and exclusions.
• General contractors should control scope boundaries without over-directing subcontractor execution choices.
• Early scope alignment supports cleaner buyout, handoff, procurement review, and change backup.

Yes. General contractors should usually send a trade-specific scope sheet with the ITB and build the bid-leveling template before proposals arrive. Pre-leveling before bid day gives subcontractors a common pricing structure and gives the estimating team a clearer scope review when proposals land.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration company.

Send the scope sheet with the ITB

Send it with the ITB when you already know the trade boundaries that tend to create inconsistent proposals. If bidders receive the same scope structure up front, the GC spends less time decoding qualifications and less time normalizing scope under bid-day pressure.

This does not require a long checklist for every package. It requires enough structure for each bidder to price the same base scope, acknowledge the same addenda, and separate the same commercial items.

That matters most on packages that often carry different inclusions from bidder to bidder, including:

• Drywall and framing
• Roofing
• Mechanical
• Electrical
• Glazing
• Sitework
• Interior finishes

If one bidder includes temporary protection, another excludes layout, and another hides patchback in a qualification note, the totals are not truly comparable. The scope sheet brings those differences into the open before the recap is built.

A scope sheet should define comparison points, not rewrite the project manual

A scope sheet should tell bidders what must be separated, acknowledged, and clarified for bid comparison. It should not restate the full specifications.

For most trade packages, the sheet should cover:

• Package identity: trade name, package number if used internally, drawing date, specification sections, and proposal due date
• Addenda acknowledgment: a place to confirm each addendum reviewed
• Base bid scope: the core work expected under the package
• Required breakouts: items the GC wants priced separately
• Alternates: adds, deducts, or design-option pricing requested in the bid documents
• Allowances and unit prices: separated from the lump sum
• Qualifications and exclusions: stated in one consistent location
• Schedule and procurement notes: milestone assumptions, phased work, shift work, or long-lead items that affect pricing
• Clarification items: known drawing conflicts, scope boundaries, or pending RFIs that bidders need to address

The required breakouts are the most important part. They should match the decisions the team will need during leveling, buyout, and handoff.

Examples by trade include:

• Sitework: demolition, earthwork, off-haul, erosion control, paving, striping, site concrete, and utilities
• Drywall and framing: framing, board types, shaft wall, insulation, backing, acoustical ceilings if packaged together, and scope boundaries around firestopping
• Roofing: tear-off, deck repair assumptions, insulation, membrane, sheet metal trims, curb flashings, and warranty-related scope required by the specifications
• Mechanical: equipment by tag or system, ductwork, piping, insulation, controls interface assumptions, startup items, and testing responsibilities stated in the documents
• Electrical: fixtures, devices, distribution components, lighting controls, fire alarm interface assumptions, and testing or commissioning items required by the documents

If a scope item will affect award review or post-award administration, it belongs on the front end of the package.

Keep scope boundaries clear, but leave bidder execution choices open

Keep the sheet focused on what must be included, not on directing every installation decision. Over-scoping can make proposals look aligned while masking real pricing differences.

Items that often stay performance-based include:

• Crew mix and production approach
• Sequencing within the project schedule requirements
• Equipment selection where the documents do not require a specific setup
• Minor accessory preferences when acceptable products are already defined in the specifications
• Internal vendor strategy, if major dependencies are identified in the proposal

The GC should control scope boundaries, not every means-and-method choice. For example, the key question is whether layout is included, not how the subcontractor staffs layout. The key question is whether temporary dry-in or rooftop coordination is carried, not the bidder's exact sequencing plan.

Pre-level bids by building the recap structure before the ITB goes out

Pre-leveling works when the same structure appears in the ITB, the proposal form, and the bid recap. That lets the GC compare responses against planned review points instead of inventing the recap on bid day.

A workable process looks like this:

• Review known scope breaks: mark items that often move between trades, such as demolition, temporary protection, blocking, sleeves, supports, patchback, testing, controls, startup, and closeout documents
• Build a trade-specific scope sheet: use a different scope form for sitework, roofing, drywall, electrical, mechanical, and other packages that carry different drawing references and interface risks
• Build the leveling template before release: create rows for base bid, addenda, alternates, allowances, unit prices, required breakouts, proposal qualifications, exclusions, schedule assumptions, procurement flags, and follow-up items
• Issue the ITB with the same structure you plan to level against: bidders respond to the same prompts the team will later compare
• Track gaps as proposals arrive: mark missing or unclear items before the deadline instead of waiting for the final hour
• Carry the same structure into handoff: if an award decision depends on a scope normalization assumption, that assumption should stay visible after bid day

Some teams manage this in spreadsheets, while others use bidding platforms such as Procore, STACK, or ConstructConnect. The tool matters less than using one scope structure from ITB through recap.

Track addenda, alternates, allowances, and qualifiers as separate fields from the start

Track them as separate comparison fields from day one. If they are buried in proposal notes, the recap becomes harder to trust.

Each bidder response should make these questions easy to answer:

• Which addenda were acknowledged?
• Were all required alternates priced?
• Were allowances carried exactly as instructed?
• Were unit prices provided where requested?
• Did a qualification change the bidder's interpretation of the base scope?
• Did the bidder price an option instead of the stated base requirement?

A simple review status system also helps:

• Confirmed: clearly included and aligned with the package
• Qualified: included, but with a condition that affects comparison
• Excluded: not carried
• Assumed: likely included, but not stated clearly enough to rely on without follow-up
• Pending clarification: bidder question still open

Those labels matter after award. If the buyout or project team inherits a low number without the scope notes behind it, the team may treat an assumption as settled scope.

Early scoping improves buyout, handoff, procurement review, and change backup

Early scoping helps because the same scope decisions keep showing up after award. A scope sheet is not just a bid-day form. It becomes part of the project record.

The downstream value usually shows up in these areas:

• Buyout: awarded scope is easier to confirm when inclusions, exclusions, alternates, and allowances were separated during bidding
• Project handoff: project managers can see what drove the award decision without reconstructing the bid from email threads
• Procurement review: long-lead items, vendor dependencies, and deferred selections are easier to flag early
• Submittals and shop drawings: package boundaries are easier to assign when the bid file already identifies who carried which scope elements
• Change documentation: backup is easier to assemble when the original package already separated the affected scope
• Billing and closeout support: the team has a clearer record of base scope versus added work

Documents are prepared within the contractor's established review and approval workflow.

If you want to review one estimating workflow or discuss a multi-trade estimating requirement, Tribuild can help map the scope-sheet and bid-leveling process to your current bid packages.

Sources

• https://tribuildconsultancy.com
• https://www.procore.com/products/bidding
• https://www.stackct.com/
• https://www.constructconnect.com/