Blog · Territory, capacity and quota planning · Construction
Pre contract cost control compares construction estimates and subcontract bids before award. Use a scope comparison, bid-leveling formulas and a full project budget check to find omissions and preserve a documented allowance for uncertainty.
Pre contract cost control compares a construction project's estimated cost with its approved budget before contracts are awarded. The essential step is to put bids on the same scope, then include costs that sit outside those bids. A low quote does not establish affordability if exclusions and owner costs remain unpriced.
Start with the current drawing revision, specifications, quantity schedule and package boundaries. Record which party supplies, installs, tests and disposes of each relevant item. A scope question answered after award may become a cost dispute; answer it while the price is still being evaluated.
Keep an independent estimate beside the bid comparison. For federal construction procurement, FAR 36.203 requires an independent government estimate with substantial estimating detail. This is a federal requirement, rather than a rule for every private job, but it illustrates why a buyer should have a view of cost beyond the prices received.
Use that estimate to challenge both high and low quotes. Ask whether a difference comes from quantity, productivity, specification, market conditions or an omission. Do not force the estimate to match a preferred supplier's number merely to make the review reconcile.
Bring the approved budget schedule, tender estimate, subcontract quotations and a scope-clarification log into the review. Use a package ID and document revision to match records. Supplier names alone are unreliable because a bidder may submit several versions or optional prices.
| Field | What to capture | Why it matters |
|---|---|---|
| Package and cost code | Common budget identifier | Matches quotes to the correct allowance |
| Scope revision | Drawing and specification version | Prevents comparison of different designs |
| Base quote | Submitted price for the stated scope | Preserves the supplier's offer |
| Addition | Supported cost of excluded required work | Makes missing scope visible |
| Deduction | Supported removal of duplicated or unwanted work | Avoids paying for overlapping scope |
| Clarification reference | Document, date and responsible reviewer | Explains each adjustment |
| Validity and schedule | Quote expiry and delivery assumptions | Tests whether the price remains usable |
Keep the base quote unchanged. Add comparison adjustments in separate columns, with the underlying clarification attached or referenced. If an exclusion cannot be priced credibly, mark it unresolved rather than inserting zero.
Federal proposal guidance distinguishes comparison of overall prices from analysis of individual cost elements. FAR 15.404-1 describes both approaches and lists techniques such as comparing proposed prices and independent estimates. For a commercial bid review, those are useful ways to test reasonableness; they do not replace scope clarification.
Leveled comparison cost = Base quote + Required-scope additions − Supported deductions
Package variance = Leveled comparison cost − Package budget
A US contractor is preparing award recommendations for a building project. The following illustrative schedule shows the preferred bid for each package after the team has reviewed competing offers. It does not suggest that supplier prices are directly comparable before scope review.
| Package | Package budget (USD) | Base quote (USD) | Required-scope additions (USD) | Supported deductions (USD) | Leveled comparison cost (USD) | Overrun / (headroom) (USD) |
|---|---|---|---|---|---|---|
| Sitework | 200,000 | 184,000 | 18,000 | 2,000 | 200,000 | 0 |
| Structure | 420,000 | 395,000 | 12,000 | 5,000 | 402,000 | (18,000) |
| Mechanical, electrical and plumbing | 330,000 | 312,000 | 26,000 | 0 | 338,000 | 8,000 |
| Total | 950,000 | 891,000 | 56,000 | 7,000 | 940,000 | (10,000) |
For example, the sitework addition covers required work excluded from its base quote; the deduction removes an item supplied elsewhere. Both need written support. A deduction taken from one package must leave the scope and cost in the package that actually owns it.
With headers in row 1, enter the leveled comparison cost in F2:
=C2+D2-E2
Enter the package variance in G2, then copy both formulas down through row 4:
=F2-B2
The total comparison cost is $891,000 + $56,000 − $7,000 = $940,000. Its $10,000 headroom is much smaller than the apparent gap between the unadjusted quotes and the package budgets. Whole-dollar inputs produce whole-dollar results, so no rounding is required.
The package comparison is only part of the award decision. In this example, the approved project budget also contains a separate owner testing allowance and an unallocated risk reserve. Neither is included in the package comparison above.
| Budget component | Approved amount (USD) | Current comparison amount (USD) |
|---|---|---|
| Trade packages | 950,000 | 940,000 |
| Owner testing | 15,000 | 15,000 |
| Unallocated risk reserve | 25,000 | 25,000 |
| Full project | 990,000 | 980,000 |
The full project remains $10,000 below budget: $990,000 − $980,000 = $10,000. The reserve stays in the comparison because it has not been released. Treating it as a saving would hide the risks it is meant to cover.
Prove the package variance in the first table independently. Enter the summed package variances in G5 and the independent comparison in G6:
=SUM(G2:G4)
=SUM(F2:F4)-SUM(B2:B4)
Both return negative $10,000. Then reconcile every addition and deduction to the scope log. A table can add correctly while still omitting testing, permits, temporary works or a responsibility between trades.
The estimator owns quantities and estimate assumptions. Procurement owns the submitted terms, quote validity and written clarifications. The project manager owns package boundaries and the overall affordability recommendation. The person authorized to approve the award decides whether remaining risks are acceptable.
Separate three outcomes in the review: an agreed price, an estimated allowance for unresolved scope and a proposed change to requirements. Only the first is ready to become a commitment on its stated terms. Carry unresolved amounts visibly until they are confirmed, removed by an authorized scope decision or replaced by a supported estimate.
Do not rewrite the original budget to erase an unfavorable package. If requirements change, preserve the original baseline and document the approval; the cost change control process explains that distinction. A concise cost control report can carry the package gap, explanation, owner and next action to the decision maker.
After award, transfer agreed commitments and the remaining allowances into the job review. The construction cost management workflow covers actual costs and the forecast to completion; that is a different review from comparing offers before award.
Upload a sample of your own budget, bid schedule and scope-adjustment file, or bring a Google Sheet. Covirage maps the columns, and its tools compute and check the comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring the schedules behind your next award review.
See project cost control in Covirage for the supporting product context.
Bid leveling adjusts competing proposals to a common scope so their prices can be compared. It identifies exclusions, alternatives, quantities and responsibilities before adding supported comparison adjustments. The resulting comparison amount is an evaluation figure; it becomes an agreed contract price only through the award process.
A low quoted price may exclude work included by another bidder. Compare the completed scope, schedule assumptions and documented qualifications before making an award recommendation. Missing work still has to be bought, and an unsupported adjustment can make a bid look better without reducing project cost.
Keep an explicit provision for the risks that remain after the bid review, with its scope and ownership documented. Check whether bidders already carry allowances for those same risks. Unused contingency is a reserve against uncertainty, rather than a confirmed saving available for unrelated additions.