PVA
All insights

Cost & Budget Owner-side insight

Your Construction Bids Came In Over Budget. Do This Before You Cut Scope.

When construction bids exceed the budget, owners should first normalize scope and assumptions, then test design and procurement options before cutting requirements.

By Sam CastelanPublished Updated 9 min read

Pause before reducing the project

When construction bids arrive above the budget, the total is a signal to investigate, not an instruction to remove scope immediately. Bidders may have priced different drawings, exclusions, allowances, alternates, schedule conditions, or assumptions. A quick cut can damage the project while leaving the gap unresolved.

Start by identifying which budget the bids are being compared with. An early feasibility allowance, a design estimate, a current forecast, and a contractor proposal may cover different scope or dates. Put the documents side by side and note the drawing set, estimate date, escalation basis, inclusions, exclusions, allowances, and contingency treatment behind each.

Separate awarded and committed work from proposed or unpriced work. The owner needs to know what can still change and what has already been authorized. If the estimate basis is inconsistent, first ask the estimating and design team to reconcile it. For a structured owner-side response, review what to do when a project is over budget.

Level bids before comparing totals

Bid leveling means comparing proposals against a common scope and recording meaningful differences. Build a scope matrix using the issued documents and bid forms. Include each trade or work package, identify whether each bidder included it, and capture qualifications, exclusions, allowances, alternates, and clarifications in the bidder's own terms.

Do not treat a blank line as an included item. Ask the bidder to confirm whether it is included, excluded, carried as an allowance, or not priced. An apparently low total may omit work that another bidder has included. Until the gap is resolved, the totals are not directly comparable.

Confirm that every bidder used the same drawing revision and addenda. Note where proposals rely on different quantities, specifications, site information, or construction sequence. Ask for written clarification and keep the response with the bid record. This helps the owner understand whether a price difference reflects execution, scope, or a different assumption.

Review the basis for allowances and alternates. An allowance should identify what it covers, what is excluded, and how the final amount will be adjusted. An alternate should explain the scope change and its effect on related trades. Do not simply subtract an alternate from the base bid until its implications for complete delivery have been checked.

When proposals still cannot be reconciled, ask bidders to price a common clarification or revised scope. Make the question consistent across bidders and allow them to identify qualifications. A clear comparison is more useful than negotiating against a headline number that does not represent the same work. PVA's bid-leveling and contractor bid review explains this process in greater detail.

Look for gaps and duplicate allowances

Scope gaps occur when required work is absent, assigned to no party, or described so vaguely that responsibility is disputed. Compare the drawings, specifications, contractor proposal, and trade proposals. Follow connections between packages, such as temporary work, access, patching, controls, testing, commissioning, and final coordination. Confirm the contract documents identify who owns each task.

A gap is not automatically a saving. If the work is required, the owner still needs a responsible party and a price basis. Record missing scope as an exposure and obtain a clear proposal or revise the package documents. Do not accept a bid simply because it omits required work.

Duplicate allowances can appear when multiple bidders or packages carry the same uncertain item, or when the owner's budget already contains a reserve for work also included in a proposal. Trace each allowance to its source, purpose, amount basis, and responsible party. Confirm whether it is genuinely additive or a placeholder repeated in multiple totals.

Reconcile contingencies separately. Contractor contingency, owner contingency, design contingency, and allowances can serve different purposes. Confirm who controls each, what it can cover, and how unused amounts are treated. Avoid removing a reserve merely because a similar label appears elsewhere; first establish whether they address the same risk.

Pay attention to exclusions and qualifications that transfer uncertainty to the owner. Ask for the practical consequence, not only the wording. A bidder may exclude a condition that another assumes is included, or price work subject to a design decision. Document who will resolve the issue and when, then bring the resolved information back to all bidders where appropriate.

Test design efficiency without eroding the brief

After bid normalization, identify the cost drivers that can be addressed through design. Ask the design team to show the specific requirement or feature behind a high-cost package and whether another approach can meet the same project purpose. Look at repeated layouts, structural and building systems, circulation, service spaces, site organization, and the alignment of drawings across trades.

Check for coordination-driven cost. Conflicting details, incomplete design, inconsistent schedules, or unclear boundaries can lead bidders to include risk or leave assumptions open. Closing a coordination issue may improve pricing certainty without eliminating a useful project feature. The architect and engineers should confirm the design solution and its code, approval, and performance implications.

Distinguish an owner requirement from a design assumption. Some criteria are necessary for approvals, financing, operations, or leasing. Others may be preferences that can be adjusted. Ask the right subject-matter professional to explain consequences before changing a specification or system. A lower first cost is not a complete comparison if it shifts risk to operations, durability, replacement, or schedule.

Develop options with enough definition to compare. State the current design, the alternative, what function is preserved, what changes, which packages are affected, and what validation remains. Request pricing against the same documents and assumptions. Keep unpriced concepts separate from confirmed bid revisions so no one mistakes a potential option for an established budget improvement.

An owner-side review can help prioritize this work. PVA's value engineering service examines plan, scope, budget, procurement, and contract decisions together. The construction cost reduction service describes another route for investigating cost drivers without treating across-the-board cuts as the starting point.

Consider procurement resequencing

Procurement order can affect price, design flexibility, and schedule. Review which packages need a decision now and which can wait for better coordination or competition. Early release may help secure a long-lead item, but it may also commit the owner to a design before interfaces, quantities, or performance requirements have been settled.

Ask the contractor or construction manager to show the sequence, decision deadlines, and consequences of holding each package. Confirm whether the schedule depends on a particular award date, submittal cycle, fabrication period, or site readiness. Check which assumptions are supported by the current schedule and which are still open.

Review whether packages invite appropriate bidders and define responsibilities clearly. Separate packages may increase competition but create interfaces; combined packages may simplify accountability while limiting bidder options. Compare delivery effects with the project team.

If procurement is resequenced, update the design and contract documents together. Make sure the revised approach states who coordinates interfaces, how design changes are handled, what information is required for release, and which schedule assumptions the owner accepts. Do not release work on the strength of an incomplete scope simply to show progress.

Negotiate from a clear, common record

Once scope and assumptions are aligned, negotiation becomes more productive. Ask each bidder to confirm a complete proposal against a common scope, identify any remaining qualifications, and explain the basis for proposed changes. Discuss schedule, alternates, allowances, exclusions, staffing, and contract terms alongside price.

Keep a written log of requests, responses, and revised proposals. Identify which items are accepted, rejected, or still open. Confirm that a concession does not depend on a scope reduction, schedule assumption, or exclusion that has not been recorded. When bidders offer different approaches, compare them as alternatives, not as equivalent prices.

Use negotiations to resolve uncertainty and improve the owner's position, not to request an unsupported reduction. If a proposal includes an allowance, ask what information would convert it to firm scope and price. If a bidder has qualified a design condition, determine whether the design team can close it and whether all bidders should receive the same clarification.

Before award, align the final proposal, scope exhibit, drawings, schedule, allowance treatment, and contract terms. The owner should know what is included, what remains exposed, and which decisions are still required. Have the appropriate legal, design, and construction professionals review the final documents within their roles.

Make the scope decision deliberately

If a gap remains after leveling, gap review, design analysis, procurement review, and negotiation, the owner may need to adjust the project. Compare defined alternatives against the project brief and operating requirements. Identify effects on approvals, value, schedule, financing, maintenance, and adjacent packages. Present the consequences plainly rather than hiding them in a revised total.

Use a decision record that names the change, its reason, the people who validated it, the pricing basis, unresolved assumptions, and required approval. Update the owner budget and project documents only after the change is accepted. Then communicate the revised scope consistently to bidders and consultants so future pricing uses a common baseline.

When the bid set is developing, flag open design and procurement questions early. Preserve clarifications and revisions in the award record. Clear records reduce the chance that an owner cuts required work to fit a comparison that was never based on equivalent proposals.

A team-led North Port example

North Port illustrates why bid work should follow a scope and design review. Team members working on a 50-unit multifamily project before PVA was formed standardized units, consolidated amenities, added rentable storage, and led bidding and negotiation. All reported financial figures are team estimates: proposals were about 20% below the originals, and estimated cost fell by about $5.5 million to about $12.5 million while completed value remained about $19 million. These are project-specific estimates, not a forecast. See the approved project examples and North Port case.

Frequently asked questions

Should we cut scope as soon as bids exceed the budget?

Not before checking the basis of the bids. First align drawings and scope, identify exclusions and allowances, and find missing or duplicated work. Then test design and procurement options against the owner's requirements before deciding whether any scope change is necessary.

What is the most important part of bid leveling?

Comparing each bidder's included work, exclusions, allowances, alternates, qualifications, and assumptions against the same issued scope. The owner needs to know whether a price difference reflects comparable work before using it to make an award or negotiation decision.

Can bid leveling guarantee that the lowest bid is the best choice?

No. Leveling clarifies what each proposal covers, but the owner must also evaluate schedule, qualifications, contract terms, capacity, coordination, and remaining risk with the project team. It supports a better-informed decision; it does not replace due diligence.

About the author

Sam Castelan

Chief Consultancy Officer (Senior Architect, Master Planner, MBA, MPL, MPA)

Brings development, master planning, and value engineering experience.

Meet the PVA team

Keep reading

A second set of eyes

Your next project decision deserves a closer look.

Scope and commercial terms are agreed in writing.

Request a project review
Confidential fit discussionRequest a project review