
The bid tab stops being comparable when a revised scope reaches one shop while another prices the original package. I recommend issuing the same revision to every bidder, preserving each original quote, and recording every comparison adjustment with its source before ranking prices.
By Marco Ruiz
Comparable subcontractor bids price the same work under the same purchasing and schedule assumptions. A bid tab is the comparison record that makes those assumptions visible.
That matters on school construction with a fixed reopening date. A proposal based on unrestricted access cannot be evaluated cleanly against a proposal that includes work around occupied areas. The access requirement belongs in the bid package before shops decide how to staff and price the work.
I recommend starting with a common pricing basis: the issued drawings and specifications, acknowledged revisions, scope boundaries, and required work sequence. Each bidder should identify departures from that basis in writing.
Federal sealed bidding offers a useful reference. FAR 14.301 requires a bid to comply in all material respects with the invitation for bids to be considered for award, putting bidders on equal footing. Private subcontract procurement follows its own documents and procedures, but a common pricing basis is a useful operating discipline.
A low total becomes meaningful when the estimator can explain what that total buys.
Keep every shop on the same revision by maintaining a distribution record and obtaining written acknowledgment of the package each shop priced.
The file name alone cannot establish that. A subcontractor may receive revised drawings while continuing to use an earlier scope letter. The bid tab needs a field for the pricing basis that connects the proposal to the actual documents.
I recommend a bid-package register with these fields:
When a question changes the work, circulate the answer to every affected bidder. A private conversation about a scope boundary can change the price just as much as a drawing revision.
For federal sealed bidding, FAR 14.208 requires changes to quantities, specifications, or delivery schedules to be issued through an amendment furnished to everyone who received the invitation before bid opening. That requirement applies even when the change was mentioned at a pre-bid conference.
For a private bid exercise, I recommend carrying that distribution principle into the clarification log. Record the question, the issued answer, and who received it. Then ask bidders to confirm whether their proposal incorporates the answer.
If a shop has priced an earlier package, flag its proposal as awaiting revision. Leave its price visible while keeping its comparison status explicit.
The subcontractor’s quoted price and the estimator’s evaluated price should occupy separate fields, with a traceable explanation for every adjustment.
A quoted price is the amount in the subcontractor’s proposal. An evaluated price is the comparison figure developed under the stated evaluation method. Keeping both visible lets a reviewer distinguish the offer from the estimator’s analysis.
The same separation applies to scope status. “Included,” “excluded,” and “awaiting clarification” carry different meanings. An empty cell leaves the next reviewer guessing.
| Comparison field | What to record for each bidder |
|---|---|
| Original proposal | Submitted price, proposal date, and source document |
| Pricing basis | Acknowledged package and revision |
| Scope status | Written inclusion, exclusion, or unresolved clarification |
| Comparison adjustment | Reason, supporting source, and evaluation treatment |
| Evaluated price | Result under the stated comparison method |
| Award readiness | Outstanding scope, schedule, or qualification issue |
Preserve the original proposal when a clarification arrives. Attach the response and update the comparison record so another estimator can follow the change.
FAR 14.403 requires the bid opening officer to complete an abstract of offers or an automated equivalent and certify its accuracy as soon after bid opening as practicable. A private subcontract bid tab has its own workflow; the useful lesson is to make the record reviewable while the supporting documents are available.
Handle exclusions by asking for written pricing against the common scope and labeling any unresolved item before ranking the bids.
A comparison adjustment needs an identifiable basis. If the subcontractor supplies a revised price that includes the missing work, retain that response. If the estimator uses a separate estimate for evaluation, identify its source and assumptions, and keep the item open until the proposed subcontract scope is settled.
Do not silently turn an exclusion into an accepted subcontractor obligation. An internal spreadsheet entry cannot establish that the shop has agreed to perform the work.
I recommend writing clarification requests around the exact scope reference. Ask whether the proposal includes the work described there, what qualification applies, and whether incorporating it changes price or timing. That gives the bidder something definite to answer.
Apply the same treatment across shops. If an access restriction requires clarification from one bidder, review every proposal for that restriction. Otherwise, the comparison can favor whichever proposal says the least.
An unresolved inclusion can become a change-order argument after award. Carry the accepted clarification into the subcontract scope exhibit so the purchasing decision and the field obligation share the same wording.
Bids from different buying periods need a review of their commercial assumptions before they can support a current purchasing decision.
A past proposal may reflect different quantities, delivery conditions, or market pricing. Its total can be useful background, but the estimator needs to identify what changed before treating it as a benchmark.
FAR 15.404-1 states that historical prices used for comparison must be adjusted for materially different terms and conditions, quantities, and market and economic factors. That is a federal proposal-analysis requirement; it also provides a practical set of questions for reviewing an older subcontract quote.
Ask the shop to confirm current price validity and delivery assumptions. Keep that confirmation with the proposal. If it changes the basis of comparison, update the affected fields across the bid tab.
A school reopening deadline makes delivery assumptions especially consequential. Record the bidder’s stated procurement duration and its dependency on approvals, then compare that statement with the project sequence. A price can be complete while its delivery basis remains unresolved.
Subcontractor vetting belongs alongside price evaluation, with qualification status visible as a separate award consideration.
SubSource supports finding and vetting verified construction subcontractors, including license, insurance, and bond verification. The bid tab still needs to show how each candidate’s documentation relates to the requirements of the proposed subcontract.
I recommend keeping qualification status distinct from price adjustments. A missing verification is an open purchasing issue. Assigning it an arbitrary dollar value would imply a level of certainty the supporting documents do not provide.
Record the outstanding document, the person responsible for obtaining it, and the decision it affects. Questions about contract language or legal sufficiency belong with the appropriate contract reviewer or lawyer.
Before the next invitation goes out, add a pricing-basis acknowledgment to the scope sheet and matching fields to the bid tab. Require each shop to identify the revision it priced and list its departures. That gives the estimator a documented starting point for every comparison.