What Should a Subcontractor Proposal Include So a GC Can Actually Level It?

Key takeaways

• A level-ready proposal states the exact drawings, specifications, and addenda priced.
• A lump-sum number is not enough for bid leveling without a clear base scope and trade boundaries.
• Assumptions, inclusions, exclusions, alternates, and unit prices should be separated so the GC can read the proposal quickly.
• Proposal clarity reduces bid-day clarification calls and post-award scope disputes.
• Connected takeoff workflows still depend on human scope writing to make proposals comparable.

A subcontractor proposal should show the exact document basis, the full base scope, and every scope qualifier that affects the number. A GC can level a proposal quickly when the bid amount, inclusions, exclusions, alternates, unit prices, and breakouts are easy to find.

If the GC has to call on bid day to ask which addendum you carried or whether a common scope item is included, the proposal is not level-ready.

The first page should show the bid amount, document basis, and major qualifiers

The first page should give the GC enough information to place your number into a leveling sheet without guessing. The commercial summary and the scope summary should be visible immediately.

A strong first page usually includes:

• Project name and location
• Bid package or trade name
• Proposal date
• Total base bid amount
• Tax treatment, if relevant to the bid form
• Drawing, specification, and addenda basis
• Alternates and allowances listed separately
• Major exclusions and assumptions
• Requested breakouts
• Contact name for same-day clarifications

If the base bid, alternates, or document basis are hard to find, the proposal creates friction before the GC even starts comparing scope.

The document basis should identify the exact drawings, specs, and addenda priced

“Per plans and specs” is not enough. The proposal should state the exact document basis so the GC knows what set you priced.

Your proposal should identify:

• Drawing set name or issue date
• Relevant specification sections used for pricing
• Addenda included in the proposal
• Any bulletin, sketch, or revision that materially affected price
• Any known document gap that still needs clarification

Many leveling problems start here. Two bidders may both say they included the full scope, while one carried a later addendum and the other did not.

Trade examples:

• Electrical: reflected ceiling plans, power plans, panel schedules, fixture schedules, and addenda that changed device counts or fixture types
• Drywall: partition types, reflected ceiling plans, finish schedules, and revisions affecting rated assemblies or shaft wall details
• Roofing: roof plan issue, detail sheets, specification sections, and addenda revising insulation thickness or edge metal scope
• Plumbing: sanitary, vent, domestic water, fixture schedules, and whether site utility sheets were included
• Concrete: structural sheets, civil sheets if they affect pads or paving tie-ins, and addenda affecting slab thickness, reinforcing, or site concrete limits

If something is unresolved, state the assumption clearly and flag the need for clarification.

The base scope should define exactly what work the number buys

A GC needs more than a lump-sum number. The proposal should state what work is included, what areas or phases are covered, and where the trade boundaries sit.

The base scope should answer these questions:

• What work are you furnishing and installing?
• What areas, phases, or bid packages are included?
• Which related items are included because they are normal to your trade?
• Which scope interfaces depend on another trade, vendor, or existing condition?

Examples by trade:

• Electrical: whether the price includes feeders, branch wiring, devices, fixtures, gear terminations, lighting controls, fire alarm rough-in, low-voltage raceway, temporary power, trenching, core drilling, and final equipment connections
• Drywall: whether framing, insulation, gypsum board, shaft walls, rated assemblies, backing, blocking, corner bead, taping, texture, and above-ceiling framing are included, plus finish level assumptions where Level 5 applies only in selected areas
• Roofing: whether tear-off, deck prep, insulation, cover board, membrane, flashing, edge metal, curbs, pipe boots, sealants, temporary dry-in, and related accessories are included
• Plumbing: whether underground, above-slab, in-wall, above-ceiling, storm, domestic water, gas piping, insulation, supports, equipment connections, excavation, backfill, sawcutting, and patching are included
• Concrete: whether layout, subgrade prep, vapor barrier, reinforcing placement, formwork, embeds, housekeeping pads, slab finishing, curing, sawcutting, joint sealant, and patch-back are included

The point is not to make the proposal longer. The point is to define the items that usually move money or create post-award disputes.

Assumptions, inclusions, exclusions, and unit prices should be separated

These categories do different jobs, so they should not be blended together.

Use them this way:

• Inclusions confirm items the GC may otherwise question
• Assumptions explain the pricing basis where the documents leave room for interpretation
• Exclusions identify scope not carried in the number
• Unit prices create a pricing method for quantities that may change

Examples of useful assumptions:

• Electrical: fixture counts and types per the latest schedule, with substitutions priced separately
• Drywall: standard work hours unless phasing or off-hours are identified in the bid documents
• Roofing: deck repairs beyond visible patch areas treated separately unless quantified
• Plumbing: excavation and backfill by site contractor where that scope is assigned elsewhere
• Concrete: dewatering, rock excavation, or winter protection included only when shown or quantified

Examples of useful exclusions:

• Electrical: fire alarm by others if the package is split that way
• Drywall: painting by others in a framing and drywall package
• Roofing: hazardous material abatement by others in a tear-off package
• Plumbing: utility company fees by others
• Concrete: surveying by others if it is not part of the bid documents

Unit prices are useful when quantity drift is likely and the GC needs a clean way to compare risk. A vague line such as “additional work at extra cost” does not help. A stated unit rate tied to a defined scope item does.

Alternates, breakouts, lead-time notes, and scope splits should be listed separately

Each alternate, breakout, and scope split should have its own line so the GC can place it directly into the bid form or leveling sheet.

A clean format is:

• Base bid
• Add alternates
• Deduct alternates
• Allowances carried
• Requested breakouts
• Unit prices
• Lead-time notes

Examples:

• Electrical: separate fixtures, lighting controls, and fire alarm rough-in if the GC requested distinct comparisons
• Drywall: separate standard partitions, rated assemblies, acoustical ceilings, and specialty soffits when they may be bought separately
• Roofing: separate tear-off, new membrane, sheet metal, and curb work where buyout paths may differ
• Plumbing: separate underground, rough-in, and fixture trim where schedule phasing affects procurement and labor
• Concrete: separate slab-on-grade, site concrete, foundations, and equipment pads where sequencing or self-perform decisions may vary

Lead-time notes should stay short and relevant. They should identify items that may affect scope acceptance, schedule planning, or substitution review.

Scope splits matter wherever overlap is common, such as roofing versus sheet metal flashing, electrical versus low-voltage, plumbing versus site utilities, drywall versus insulation, and concrete versus excavation. State the split in plain language.

Proposal clarity helps the bid move cleanly into buyout and project execution

A clear proposal does more than help on bid day. It gives the GC a usable scope position that can carry into buyout, submittals, procurement, and change documentation.

Procore Estimating and Autodesk Takeoff both present estimating and takeoff as connected workflows. That makes proposal language more important, not less, because quantities alone do not define trade boundaries, exclusions, or alternates.

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

That workflow connection matters. Drawing review, takeoff, pricing, qualifications, bid leveling, vendor follow-up, and post-award documentation all depend on clear proposal language.

A practical next step is to review your current proposal template against the last few bid-day clarification calls your team had to answer. If you want another set of eyes on that process, Tribuild can review one upcoming project or your current vendor-pricing and proposal workflow.

Sources

• https://tribuildconsultancy.com
• https://www.procore.com/products/estimating
• https://construction.autodesk.com/products/takeoff/