What Should a Sitework and Utility Proposal Include for a Commercial Job?

Key takeaways

• A commercial sitework proposal should show what is in the base bid, what is separate, and what assumptions control the price.
• Optional scope belongs in alternates, quantity risk belongs in unit prices, and bid-form placeholders belong in allowances.
• GCs can level civil bids faster when grading, each utility system, paving, testing, dewatering, rock, and restoration are broken into separate scope buckets.
• Short, job-specific clarifications are more useful than a long generic exclusion list.
• Clean proposal structure carries forward into buyout, change backup, and project administration after award.

A sitework and utility proposal for a commercial job should define the base scope, separate uncertain work into alternates, unit prices, or allowances, and state the assumptions that affect price. It should also break out grading, each utility system, erosion control, paving, curb, sidewalk, testing, dewatering, rock, and restoration so a GC can level the bid without guessing.

The base proposal should define the assigned package scope

The base number should cover the scope clearly assigned in the bid documents and the normal incidental work required to install it. It should also identify the drawing set, specification sections, and addenda used for pricing.

For most commercial sitework and utility bids, the base proposal should identify these scope buckets in writing:

• Mobilization and site access assumptions.
• Clearing, stripping, and demolition if those items are assigned to the package.
• Earthwork such as cut, fill, trench excavation, backfill, grading, and compaction.
• Underground utilities separated by system, such as storm, sanitary, domestic water, fire line, and related structures.
• Aggregate base, bedding, or stone backfill where shown.
• Erosion and sediment control required to perform the included work.
• Surface restoration tied to the included work, such as trench patching or disturbed-area restoration, if assigned to the package.

A proposal that says only sitework per plans and specs forces the GC to guess where scope lives. A proposal that separates storm sewer, sanitary sewer, water, paving, curb, and erosion control is easier to compare and less likely to create a scope gap.

Alternates, unit prices, and allowances should handle uncertainty separately

Optional scope belongs in alternates, quantity risk belongs in unit prices, and owner-required placeholders belong in allowances. Do not bury uncertain work inside the base number.

Use alternates for optional or package-boundary scope

Alternates work best when the scope may or may not be awarded with the package.

Common examples include:

• Asphalt paving when the GC may buy paving separately.
• Curb, gutter, sidewalk, or other site concrete when package boundaries are still being decided.
• Finish grading, seeding, sod, or final landscape restoration when another contractor may carry that work.
• Off-site tie-ins or utility extensions that depend on owner direction, agency approval, or schedule.

Use unit prices for quantity-driven risk

Unit prices work best when the scope is required but the final quantity is uncertain.

Typical examples include:

• Rock excavation.
• Undercut of unsuitable soils.
• Imported fill beyond a stated base quantity.
• Export and disposal beyond a stated base quantity.
• Additional trench depth beyond a stated baseline.
• Extra pavement patching or restoration beyond a measured quantity.
• Dewatering when the documents do not define the required effort clearly.

A usable unit price should state the unit of measure, the basis, and what is included. A bare line item is harder to level and harder to administer after award.

Use allowances only when the bid instructions call for them

Allowances are most useful when the bid form or owner instructions require them. If a testing allowance, permit allowance, or agency fee allowance is carried, label it clearly and keep it separate from direct work pricing.

Each major site scope should have its own line item

Break out earthwork, utilities, erosion control, paving, site concrete, testing, dewatering, rock, and restoration as separate scope buckets. That structure helps the GC compare bidders and helps the project team trace changes back to the original proposal.

A practical breakout looks like this:

• Earthwork and grading: Separate stripping, excavation, fill, import, export, rough grading, fine grading, and compaction assumptions.
• Storm sewer: Separate pipe, fittings, structures, inlets, manholes, bedding, backfill, and tie-ins.
• Sanitary sewer: Break out sanitary linework and structures separately from storm.
• Domestic water and fire line: Price these as separate systems, with taps, utility charges, and final connections addressed directly if they are part of the package.
• Erosion and sediment control: Separate initial installation from maintenance if the documents make that distinction.
• Aggregate base and paving: If subbase is included but asphalt is not, say that directly. If both are included, separate base, binder, surface course, striping, and patching.
• Curb, gutter, and sidewalk: Break out linear curb and gutter from sidewalk and other flatwork.
• Testing and inspections: Identify whether the price includes compaction testing support, utility testing, video inspection, mandrel testing, chlorination support, or third-party testing coordination.
• Dewatering: State whether the base number includes normal trench water management, active dewatering, well points, discharge treatment, or permit-related controls.
• Rock excavation: If rock is not clearly quantified in the documents, separate it from the base number or pair a stated allowance with a unit price.
• Restoration: Clarify whether restoration means trench patching, gravel repair, topsoil replacement, seeding, sod, landscape replacement, or hardscape restoration.

Assumptions should answer the GC's leveling questions

The most useful assumptions are short, specific, and tied to package boundaries or measured quantities. Job-specific clarifications are more useful than a long generic exclusion list.

The assumptions that usually help most are:

• Package boundaries: State whether paving, signs, striping, landscaping, irrigation, fencing, light pole bases, and utility company work are included.
• Quantified basis: If import, export, trench depth, pavement patch quantity, or structure count is based on plan takeoff, say so.
• Existing conditions: Note whether pricing assumes documented utility locations, access as shown, and ordinary conditions consistent with the bid documents.
• Disposal basis: Identify whether disposal is based on clean soils and debris or whether special handling was carried where the documents required it.
• Testing responsibility: Clarify whether testing is by others, contractor-arranged, or supported within the package scope.
• Permit and agency scope: Spell out whether fees, bonds, utility company charges, or permit revisions were included where applicable.
• Traffic control and sequencing: Call out phased access, temporary road maintenance, or off-hours work if those requirements affect price.
• Survey and layout: State whether basic layout, as-built pickup, or certified survey deliverables are included.

Proposal structure affects bid leveling, buyout, and changes

A clear proposal helps before bid day, at buyout, and during change pricing. The same scope structure that helps the estimator level bids also helps the project team administer the work after award.

A well-structured proposal helps in three places:

• Before bid: The GC can compare bidders faster and spot scope gaps earlier.
• At buyout: The awarded scope is easier to convert into subcontract language or purchase scope.
• During changes: Added paving, utility reroutes, extra rock, agency revisions, and restoration growth can be tied back to named original scope buckets.

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

A practical format is a short scope summary plus separate pricing sections

The most usable format is a header, a base scope summary, separate breakout lines, and a short clarification section. A GC should be able to scan the proposal and answer three questions fast: what is in the base number, what is separate, and what assumptions drive the price.

A practical format includes:

• Project header with project name, bid date, drawing references, specification references, and addenda acknowledged.
• Base scope summary in a few bullets.
• Separate breakout lines for grading, each utility system, erosion control, paving-related work, site concrete, testing, dewatering, rock, and restoration.
• Alternates and unit prices in their own section, not mixed into the base scope narrative.
• Clarifications and assumptions tied to package boundaries and quantity risk.
• Acceptance language that matches the contractor's normal proposal workflow.

If you want a second review of one sitework bid package or proposal template, Tribuild can review one estimating workflow within your existing process.

Sources

• https://www.csiresources.org/standards/masterformat
• https://www.agc.org/
• https://www.consensusdocs.org/