How Should a GC Level Fire Sprinkler Proposals When the Bid Set Has No Sprinkler Drawings Yet?

Key takeaways

• A GC should level fire sprinkler bids without drawings by comparing written assumptions, not by treating proposals as final designed scope.
• One written bid basis is the fastest way to make incomplete sprinkler proposals comparable.
• Unanswered pre-bid RFIs should become issued bid assumptions for all bidders.
• Bid leveling works when scope gaps are adjusted openly and documented in the file.
• Allowances and alternates are often more reliable than forcing a hard number around unresolved sprinkler scope.

A GC should level fire sprinkler proposals without drawings by standardizing the bid basis, requiring written assumptions from every bidder, and normalizing exclusions before award. When the bid set has no sprinkler drawings, compare scope assumptions, connection assumptions, ceiling conditions, administrative scope, and coordination requirements instead of treating each proposal as a final designed number.

Level the bid basis, not the final sprinkler layout

The right comparison is the basis of price, not the final sprinkler layout. If sprinkler drawings are not issued, the useful bid-day review is whether each fire protection subcontractor priced the same building areas, ceiling conditions, system assumptions, tie-in assumptions, and post-award coordination scope.

That means the GC should compare:

• building areas and room uses shown on the bid documents
• ceiling types, ceiling heights, soffits, clouds, and open-structure areas
• new work versus tie-in to an existing system
• assumed point of connection
• assumed system type if the specifications or bid instructions indicate one
• likely head conditions based on finish and ceiling conditions
• seismic bracing, hangers, sleeves, penetrations, and core drilling
• permits, testing, inspections, record documents, and closeout requirements
• related scope such as standpipe work, underground fire service, fire pump scope, backflow scope, and fire department connection scope if those items are part of the package
• coordination scope, including shop drawings, BIM coordination, sleeve coordination, and field coordination meetings if required by the project workflow

Applicable fire protection standards and project specifications govern final layout, shop drawings, and system requirements during the post-award process. For bid day, the GC needs a comparable scope basis.

Issue one written bid basis before proposals come back

A GC should issue one written bid basis before proposals come back. If bidders fill in missing design information on their own, the bid tab will compare different jobs.

The bid basis should state:

• the exact drawing sets, reflected ceiling plans, specifications, and addenda used for pricing
• whether sprinkler layout will be developed after award under the project requirements
• the connection basis, including any available existing-system information
• ceiling condition assumptions that affect head type and labor
• whether special spaces, exterior covered areas, attics, mezzanines, or interstitial areas are included
• whether seismic bracing, supports, sleeves, penetrations, and patch-related coordination are included
• whether permits, testing, inspections, closeout documents, and record documents are included
• whether fire alarm interface and related coordination are included in this trade package or carried elsewhere
• whether phasing, off-hours work, lifts, access constraints, or protection requirements should be included

A short bidder scope matrix is usually the cleanest tool. Require every bidder to mark each scope line as included, excluded, or by others, with a short note where needed.

Put the biggest pricing swing items into pre-bid RFIs

The most useful pre-bid RFIs are the ones that remove major pricing swings or turn unknowns into shared assumptions. If an issue can materially change sprinkler scope, it belongs in the bid file before award.

Useful RFI topics include:

• confirmation of the governing specification sections and performance requirements
• confirmation of occupancy or room use where the architectural set is unclear
• available information for existing water service, riser, or existing-system tie-in conditions on renovation work
• clarification of whether standpipe work, underground fire service, fire pump scope, backflow scope, or fire department connection scope is part of the package
• confirmation of permits, testing, inspections, final acceptance requirements, and closeout documentation
• confirmation of fire alarm interface responsibility where sprinkler coordination depends on it
• confirmation of whether revised reflected ceiling plans or ceiling details are expected before award

If an RFI is unanswered by bid day, issue one written assumption to all bidders. Do not let each bidder solve the same gap privately.

Normalize proposal differences line by line in the bid tab

A GC should normalize proposal differences line by line in the bid tab. The purpose of leveling is to expose scope variance, not to make inconsistent proposals look comparable.

Common differences to normalize include:

• concealed heads at hard ceilings versus exposed or standard head assumptions
• inclusion or exclusion of seismic bracing, supports, sleeves, penetrations, and core drilling
• minor tie-in assumption versus substantial modification assumption
• inclusion or exclusion of permits, testing, inspections, and closeout documents
• inclusion or exclusion of attic, canopy, mezzanine, or concealed spaces shown indirectly in the architectural set
• inclusion or exclusion of coordination drawings, BIM participation, and sleeve-location coordination
• qualifications tied to late ceiling revisions, phasing, or restricted access

Keep the original proposal language in the file and note every normalization adjustment. The clean record is not just the adjusted number. It is the reason the adjustment was made and the document that supports it.

Use allowances, alternates, or unit-rate items when the unknown is real

A GC should use allowances, alternates, or unit-rate items when a missing design input can materially change scope. Forcing a hard number too early often hides uneven contingency inside the base proposal.

This is usually appropriate when:

• existing water supply or existing-system conditions are not confirmed
• reflected ceiling plans are still changing
• room use is not final
• a special system question exists for a limited area
• related fire protection scope is still being assigned between packages

Clean ways to separate those unknowns include:

• an allowance tied to one defined risk item
• an alternate for a clearly separated scope branch
• an add or deduct item for a known variable
• a written post-bid clarification that must be resolved before subcontract issue

The base bid should still be clear. Separate unknowns so the subcontract scope can be written from a traceable bid record.

Keep a short award file that carries into subcontract drafting

Before award, the GC should have a short file that shows exactly what was leveled, what remains unresolved, and what must carry into subcontract drafting. If that file is missing, the same scope gaps usually return after award.

The file should include:

• the exact issued drawing, specification, and addenda list used for pricing
• the bidder scope matrix from each fire protection subcontractor
• the pre-bid RFI log and any issued bid assumptions
• normalization notes from the bid tab
• allowances, alternates, or unit-rate items used to isolate unknowns
• unresolved assumptions that must be addressed before final scope issue
• required post-award deliverables such as shop drawings, coordination submissions, testing requirements, and closeout requirements under the project workflow

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

Use the same process on the next incomplete delegated-design package

The simplest improvement is to issue a one-page sprinkler bid-basis form every time the bid set lacks sprinkler drawings. That one document usually does more for bid leveling than another round of phone calls after proposals arrive.

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

If you want to review one delegated-design bid-leveling workflow or one multi-trade estimating requirement, Tribuild can discuss an upcoming project.

Sources

• https://www.nfpa.org/codes-and-standards