Planning & documentation
How to Level Steel Building Bids Before Award
Compare steel building proposals on common scope, documented exclusions, installation boundaries, and accepted alternates before award.
Define the condition and its scope
Bid leveling exposes differences hidden behind identical building dimensions and different package totals.
A steel building proposal is a boundary between several businesses: the building-system supplier, concrete contractor, erector, enclosure installer, and trades that complete the occupied space. Cold-formed components may be included in one package and field-installed under another. Comparing the headline amount alone hides these handoffs. Start with the issued scope and give every bidder the same drawings, revision list, delivery assumptions, and request for written exclusions. Keep owner decisions visible beside contractor commitments so that an unresolved preference does not become an assumed inclusion.
References: Project Planning Guide · Commissioning documents: process, contents, and acceptance
Gather the inputs before deciding
Create a bid worksheet with one row for each delivered outcome: engineered steel package, freight, unloading, erection, roof installation, wall installation, openings, insulation, and final interface completion. Add columns for included, excluded, conditional, and unclear. Preserve each bidder's exact scope language alongside the normalized row. If a proposal combines several outcomes, request a clarification rather than forcing an assumed allocation. Record the referenced drawings and quote validity information as stated by the bidder; do not replace an uncertain date with a standard purchasing assumption.
- Base package inclusions
- Erection and unloading boundaries
- Accepted alternates
- Current bidder exclusions
References: Project Planning Guide · Commissioning documents: process, contents, and acceptance
Set observable handoff deliverables
A shell-only offer and an installed-shell offer cannot be compared without explaining the missing work.
| Input | Evidence to keep with it | Review status |
|---|---|---|
| Base package inclusions | Issued scope and bidder response | Identify reviewer and written decision |
| Erection and unloading boundaries | Named unloading and erection contractor | Identify reviewer and written decision |
| Accepted alternates | Separate base and alternate comparison | Identify reviewer and written decision |
Sequence review and release
Freeze the comparison baseline before asking bidders to resolve omissions. Number the questions and send the same factual clarifications to all affected bidders. When replies arrive, change the scope-status cells and retain the original response behind them. Review alternates with the designers and adjoining trades before including their effects in the decision. A bidder's discount does not close a scope gap. Complete the comparison by stating the proposed award scope, remaining owner purchases, unresolved technical reviews, and the evidence required before fabrication release.
- Locate base package inclusions in the current record.
- Compare erection and unloading boundaries with the table's evidence.
- Document the decision: Resolve exclusions and identify the owner of every remaining interface.
Worked project coordination example
Two warehouse bidders include the same bay layout. One excludes unloading; the other includes it but excludes insulation installation. The owner requests separate written allocations, then compares the same completed scope instead of subtracting a guessed allowance.
Apply the stated release decision to the case: Resolve exclusions and identify the owner of every remaining interface. The responsible team determines acceptance for the actual project and records any condition that still requires resolution.
Keep a closeout record another team can use
The award record should explain why the chosen proposal satisfies the agreed scope, including clarifications incorporated into the order or contract. Carry any owner-retained work into a separate procurement action, not a footnote that disappears after award. Give the superintendent the final allocation of unloading, installation, and interface work. If later clarification changes that allocation, reopen the affected comparison row and follow the change process. This keeps the bid worksheet useful as the starting scope record rather than an abandoned spreadsheet containing numbers nobody can explain.
For this issue, include separate base and alternate comparison in the handoff. If review remains pending, identify the dependent work and its owner; do not present the record as a completed technical acceptance.
Common questions
Should excluded work be estimated silently?
No. Show any estimate separately and obtain the missing contractor commitment before award.
How should base package inclusions be documented?
Resolve exclusions and identify the owner of every remaining interface. Retain issued scope and bidder response and check that the decision reached the team performing the dependent work.
Sources & further reading
Use the current documentation for the exact product and project. Source links do not imply a partnership or endorsement.
- Project Planning Guide U.S. General Services Administration / WBDG
- Commissioning documents: process, contents, and acceptance Whole Building Design Guide
Prepared with AI assistance. Linked references require current project-specific review. How these guides are prepared.
Prepare a supply inquiry
- Record the project drawing or detail and the specified product, profile, or system.
- List the complete configuration, physical units, quantities, and cuts per piece.
- Request current manufacturer documents; confirm compatibility, price, and availability before ordering.
- Obtain the responsible professional's review for loads, code requirements, or installation.