How to Compare Bid Alternates, Allowances, and Unit Prices Without Distorting the Base Bid

Subcontractor proposals rarely organize pricing the same way. One bidder includes an allowance in the base bid. Another lists it as an add alternate. A third provides a unit price with an assumed quantity. If those numbers are copied into one total without their conditions, the leveling sheet can create a comparison that no bidder actually submitted.

The goal of normalization is not to rewrite the bids until they look identical. It is to preserve the original commercial position, make differences visible, and give the estimator a controlled place to apply project decisions.

Preserve the submitted base bid

The base bid should remain exactly as submitted unless the bidder issues a revision. Do not silently move alternates into the base, replace an allowance, or correct arithmetic inside the source number.

Create separate fields for submitted base bid, documented bidder revisions, accepted or rejected alternates, estimator adjustments, and leveled total. This structure protects the audit trail and lets reviewers understand why the comparison differs from the proposal cover page.

Treat alternates as decisions, not decorations

An alternate changes scope, material, system, schedule, or execution method for a stated price. Compare alternates only when they represent the same decision.

Bidder A's “deduct for PVC in lieu of cast iron” is not directly comparable to Bidder B's “deduct for value-engineered plumbing package” without examining the included systems and conditions. Keep the description, amount, add-or-deduct direction, source page, and acceptance status together.

Required alternates should receive their own comparison rows. Voluntary value-engineering options can be grouped separately so they do not make a bidder appear artificially low before the project team accepts the change.

Separate allowances from fixed-price scope

An allowance is not the same as a completed price. It reserves an amount for work or material that is not fully defined. Two identical allowance values may still carry different assumptions about labor, tax, markup, delivery, escalation, or reconciliation.

Record the allowance amount, what it covers, what it excludes, and how overages or underruns will be handled. If the bid package required a specific allowance and a bidder used a different value, preserve the submitted amount and show a leveling adjustment separately.

Allowances also need scope status. A bidder may include the allowance but exclude installation, handling, or related coordination. The matrix should not mark the entire requirement included based only on the presence of a dollar amount.

Keep unit prices connected to quantity and condition

A unit price has meaning only with its unit, assumed quantity, and application rule. A price per linear foot may include material and labor for standard conditions but exclude demolition, access, testing, or overtime. A unit price can also be an add, deduct, or net change depending on the proposal.

Store each unit price as a structured commercial item: description, unit, rate, assumed quantity if any, extension, condition, and source. Do not extend a rate into the leveled total unless the project team has a defensible quantity and a reason for applying it.

When bidders use different units, convert only with a documented basis. A lump sum should not be converted into a unit price merely to make the columns look consistent.

Distinguish bidder revisions from estimator adjustments

A bidder revision changes the proposal and should be supported by written bidder communication. An estimator adjustment is an internal comparison device used to account for scope differences. They are not interchangeable.

Keep both the amount and reason for every adjustment. Link the adjustment to the requirement or commercial item that caused it. If the cost is uncertain, record the uncertainty instead of presenting the adjustment as a bidder commitment.

This separation allows the team to answer three different questions: what did the bidder submit, what has the bidder formally changed, and what has the estimator carried for comparison?

Compare scope and price together

Commercial normalization should not happen in a pricing-only worksheet disconnected from scope. An alternate, allowance, or unit price often explains why a bidder's scope state differs from the others.

For each item, show the related requirement, bidder status, proposal evidence, amount, condition, and review decision. This prevents a reviewer from accepting a favorable number while missing the qualification attached to it.

How Mobus structures commercial differences

Mobus Bid Leveling extracts base bids, alternates, options, allowances, and other commercial items separately from the scope matrix. Proposal citations remain attached, and the estimator can review risks, correct findings, draft clarifications, and enter controlled adjustments before exporting to Excel.

The product never needs to pretend that unlike bids are identical. It gives the estimator a consistent structure for seeing why they differ and a traceable way to make them comparable.

The cleanest leveled total is not the one with the fewest rows. It is the one where every movement from submitted bid to reviewed comparison has a source, a reason, and an owner.