Subcontractor bid-leveling template: compare scope as well as price

Define the common bid package before opening the comparison

Identify the trade package, drawings, specifications, addenda and scope instructions that form the comparison basis. Record the document revision and relevant issue dates. If bidders priced different information, the first task is to identify that difference, not to line up their totals as though the work is identical.

Choose scope rows that the estimator and bidders can interpret. A single row called “complete electrical work” may hide meaningful differences; hundreds of tiny rows can make the sheet difficult to maintain. Use the package's actual interfaces and risk points to decide the level of detail. The matrix should help reveal a question the team can resolve.

Keep the common baseline visible when a clarification arrives. A bidder's later response may change an inclusion, price or condition. Preserve what changed and which revision is now being compared. A well-designed template is a record of the estimator's review, not merely a prettier place to copy the submitted numbers.

Use columns that preserve the source and decision

A useful starting sheet has a scope item, baseline requirement, bidder response, proposal reference, clarification status, estimator adjustment and decision owner. Repeat the bidder-specific fields for each offer, or maintain linked detail rows behind a summary. Keep the original proposal accessible so the reviewer can check the context of a short label.

Do not force ambiguous language into included or excluded simply to fill the matrix. Use an explicit unclear or clarification-needed state. “By others,” “as noted” and “subject to final coordination” can require a focused question. Preserve the quoted or accurately summarized wording and its source location before deciding the treatment.

The following field structure is an original starting template. Adapt it to the package and the tool your team maintains. It is not a claim that every bidder must complete the same form or that every commercial difference can be reduced to a price adjustment. The estimate reviewer should be able to identify the source and status of each important assumption.

Read the proposal before trusting an extracted cell

A proposal can state a base amount on the first page and qualify it later through exclusions, alternates or terms. Review the relevant sections and attachments. An extracted price without its conditions can be accurate as a number and misleading as a comparison. Keep the source document and version with the review.

If software helps extract the fields, check the important values and wording against the original. A blank field is not automatically an inclusion. A line that says “testing by others” should not become “testing included” because the overall trade description sounds comprehensive. Preserve uncertainty and ask the bidder or responsible reviewer to resolve it.

Also distinguish the bidder's statement from an estimator's interpretation. The worksheet may use a short category for review, but the source language remains important. If the team later changes an interpretation, record the reason and supporting clarification. The objective is a comparison another estimator can reconstruct without guessing how the first reviewer reached a total.

A worked comparison of three fictional bids

Consider an invented package with three bids. Bidder A offers $100,000 but excludes temporary power. Bidder B offers $104,000 and includes temporary power, while the controls scope remains unclear. Bidder C offers $98,000 but excludes temporary power and testing. Assume the other scope shown in the example is aligned for this teaching exercise only.

The estimator uses provisional review inputs of $3,500 for temporary power, $5,000 for testing and $1,500 for the unresolved controls allowance. These are invented amounts, not market prices or bidder quotations. Every plug needs a stated basis and appropriate review in a live estimate. An unresolved item should remain visible even when a working allowance is added.

On that simplified basis, A becomes $103,500, B $105,500 and C $106,500 in the working comparison. C is the apparent low on submitted base price but not the lowest working leveled amount. That result helps focus clarification; it does not establish the award decision or turn the estimator's assumptions into contractual commitments from the bidders.

Keep estimator plugs separate from submitted prices

A plug is a working adjustment used to compare a scope difference. It should identify the amount, source or estimating basis, reason, reviewer and status. A bidder's confirmed revised offer is a different record. Preserve both values so a summary does not imply the supplier offered a price the estimator actually invented.

If a clarification confirms that the work is included, review whether the plug should be removed and preserve the response. If the bidder provides a price to add it, record that as a new source and check the corresponding scope and revision. Avoid retaining the provisional plug and the confirmed addition together unless the actual treatment calls for both; otherwise the comparison may count the same issue twice.

BuildingConnected's published bid-leveling overview describes notes and adjustments within its existing comparison workflow. That is a useful example of an available system of record. Whatever tool you use, the important review question remains the same: can another person trace the adjusted number to the source and see which assumption is still unresolved?

Sources: Autodesk BuildingConnected: bid-leveling overview and adjustments

Compare alternates and allowances on a consistent basis

An alternate may add work, remove work or replace a base component. Read the stated condition before combining amounts. Adding every displayed alternate to every base bid can produce a total that no bidder intended. Define which option the estimate is evaluating and preserve the other options separately.

For allowances, record what the amount covers, the assumptions behind it and the treatment of any difference. Two equal dollar allowances can cover different quantities or responsibilities. A comparison needs the scope basis as well as the number. Route commercial interpretation to the authorized reviewer where the proposal or bid instructions are unclear.

Keep unit rates and quantities distinct too. A lower unit rate with a different quantity or measurement basis is not automatically the lower cost for the required work. Identify the agreed comparison quantity or the open question. Do not hide a missing quantity inside a rounded plug simply to make the rows add cleanly.

Ask a bidder to resolve one specific scope question

Use the package reference, document revision and proposal section when asking for clarification. Identify the specific inclusion or exclusion and the response needed. For the fictional B bid, the question might be: “Please confirm whether your current base includes the controls scope identified in the package instructions. If excluded, identify the scope boundary and provide the corresponding proposed addition under the current revision.”

Preserve the response, date and person who supplied it. A delivered message is not a clarification. “We can take care of it” may still leave price and scope unresolved. Ask the next focused question through the approved procurement process rather than translating an informal reply into a confirmed inclusion or a revised offer.

Keep communication consistent with the company's bidding and commercial rules. The coordinator can collect an answer, while the estimator and authorized team decide how it affects the comparison and next negotiation. A clear question and source-linked reply reduce the need to reconstruct the bidder's position during the award review.

Review schedule and terms alongside the leveled amount

A price comparison should not erase meaningful differences in schedule, capacity, lead time, exclusions, validity or other commercial conditions. Identify which matter to the package and have the responsible people review them. Some differences may support a reviewed cost adjustment; others remain conditions or risks that a simple total does not adequately represent.

For example, a bidder may price a schedule assumption that differs from the project's required sequence. Record the stated basis and ask for clarification. Do not assume that the bidder can meet a different sequence because the base amount is attractive. Keep any later commitment with the source and current proposal version.

The award recommendation should show the reviewed scope and unresolved conditions, not only a ranked list of amounts. The authorized team needs to understand why a particular offer fits the work and what still needs confirmation. A lower working leveled number can be informative without being the sole basis for a responsible decision.

Keep Excel flexibility without losing the comparison history

Use the tool the team can reliably maintain, with clear source references and version control. A spreadsheet can provide flexible calculations and a familiar review format. A project platform can hold proposals, notes and workflow history. The important question is how those records remain connected when values or scope assumptions change.

BuildingConnected's official documentation describes exporting base or leveled bids to a formatted XLSX file, including relevant leveling information in the leveled export. An estimator does not need to assume that adopting a project platform requires abandoning Excel. Verify the actual export and its contents for the configuration you use rather than repeating an outdated feature limitation.

When you export, identify the date, package revision and source system. If the spreadsheet becomes a working copy, record subsequent changes and the authoritative review outcome. Avoid circulating several contradictory files with the same “final” name. The office should be able to connect the award recommendation to the exact proposals and clarifications used to prepare it.

Sources: Autodesk BuildingConnected: exporting bid leveling to XLSX

Coordinate the missing bidder answers with Buildalytic

Buildalytic's subcontractor bid-follow-up and custom workflows coordinate requests, responses and human decisions around an existing process. A useful bid-leveling demonstration starts with a scope matrix containing one unresolved exclusion or acknowledgment. Ask to see the right contact identified, the focused question sent through the approved workflow and the response preserved for the estimator.

Test an incomplete reply or a revised proposal. The workflow should keep the outstanding question and source version visible rather than marking the package fully covered because a bidder responded. The estimator should retain control of the scope interpretation, pricing adjustment and award recommendation. Confirm where the authoritative proposals and comparison remain.

Bring a redacted leveling sheet and one difficult bidder question to a demo. Walk through the follow-up, source record and next review task. You can evaluate whether Buildalytic helps the team spend less effort chasing and reconstructing answers while continuing to use its established estimating and project systems. That is a concrete workflow to inspect, rather than a promise that software can choose the winning subcontractor automatically.

Sources: Buildalytic: subcontractor bid follow-up