Construction cost estimate accuracy changes because the information behind the estimate changes. Early in a project, the team may only have a business objective, a site, an approximate capacity, and a few benchmark assumptions. By tender stage, the team should have drawings, specifications, scope definition, quantities, commercial assumptions, and a clearer procurement route.
The problem is not that early estimates are useless. The problem is treating them as if they carry tender-level certainty.
For owners, the useful question is not "Is this number accurate?" It is: "What decision can this estimate safely support, and what uncertainty still sits behind it?"
Recognised estimating guidance points in the same direction. AACE International describes estimate classification as a way to connect estimate purpose, methodology, and project definition maturity. RICS NRM 1 gives a structured approach to order of cost estimating and cost planning for capital building works. The CIOB Code of Estimating Practice describes estimating as a systematic process, not a single number produced in isolation.
That is the practical lens this article uses. Estimate confidence improves when scope maturity, measurement detail, pricing evidence, risk review, and reconciliation improve together.
Why Estimate Accuracy Changes
A cost estimate is only as strong as its inputs.
At the start of a project, the estimator may not know the final layout, structural system, equipment specification, ground conditions, utility requirements, construction sequence, procurement route, or market timing. Those unknowns do not disappear because a spreadsheet produces a clean total.
As design develops, more of the estimate can move from broad assumptions to measured quantities and project-specific pricing. The estimator can test the design against previous projects, current market rates, supplier input, preliminaries, logistics, escalation, risk allowances, and owner requirements.
This is why a mature estimate should show more than a bottom-line cost. It should show:
- the basis of estimate
- the level of design information used
- inclusions and exclusions
- assumptions and qualifications
- measurement basis
- pricing source
- risk and contingency logic
- reconciliation against previous estimates
- the decision the estimate is intended to support
Without those items, the owner may see a number but not understand the confidence behind it.
Feasibility Estimate: Is the Investment Worth Testing?
A feasibility estimate helps an owner decide whether the project is worth further development. It usually comes before detailed design. The information may include project objectives, approximate size, location, capacity, high-level scope, site constraints, and benchmark data from similar work.
At this stage, the estimate should not pretend to be a procurement number. It is a business decision tool.
A useful feasibility estimate helps answer questions such as:
- Does the project sit within a realistic funding range?
- Which scope options are likely to drive cost?
- Is the preferred site commercially viable?
- What major risks need investigation before design money is spent?
- What budget range should be carried into the next stage?
The strongest feasibility estimate is transparent about uncertainty. It should identify the main cost drivers rather than hiding them inside a single total. For example, ground risk, import materials, long-lead equipment, temporary works, abnormal logistics, and authority requirements may all affect the early cost range.
If the feasibility estimate is used correctly, it prevents false confidence. It gives the owner a commercial frame for the next decision: continue, pause, change the scope, or test alternatives.
Concept Estimate: Is the Design Direction Commercially Sensible?
Once the project has a concept design, the estimate can become more specific. The team may now have early drawings, outline specifications, massing, functional areas, major systems, and a clearer view of the project requirements.
The estimator can start replacing some benchmark assumptions with project-specific allowances. Areas, major quantities, system choices, site conditions, and procurement assumptions can be tested more directly.
This stage is where cost planning starts to protect the design.
A concept estimate should make trade-offs visible. If the design direction requires a more complex structure, longer construction duration, higher-specification finishes, or heavier MEP systems, the owner should see the cost effect early enough to respond.
The estimate should also be reconciled against the feasibility estimate. Reconciliation is not admin. It is where the team explains why the cost moved.
Typical reconciliation questions include:
- Did the scope increase?
- Did the specification change?
- Did quantities become clearer?
- Did market rates move?
- Did the team identify a risk that was previously missing?
- Did an allowance become too low once the design was better understood?
When this reconciliation is skipped, the owner only sees cost drift. When it is done properly, the owner sees the reason for the movement and can decide what to do.
Developed Design Cost Plan: Is the Budget Still Controlled?
By developed design, the estimate should be more structured. The design information is stronger, specifications are clearer, and quantities can be measured with more discipline. The estimator can test the project against a cost plan rather than only a high-level benchmark.
This is where a quantity surveyor becomes especially useful. The QS can break the cost into meaningful packages, measure work items, review scope completeness, challenge missing allowances, and compare the current design against the approved budget.
At this stage, the cost plan should help the owner control decisions before tender. It should show whether the design is still aligned with the budget, where pressure is building, and which design choices need commercial review.
A developed design cost plan should usually cover:
- construction works by element or package
- preliminaries and time-related costs
- provisional sums or undefined work
- design development allowances
- escalation or market movement assumptions
- contingency and risk allowances
- exclusions and owner-supplied items
- taxes, duties, permits, and project-specific commercial assumptions where applicable
The estimate is still not a guarantee. But it should now be strong enough to guide active budget management. If the owner waits until tender to find out the design is unaffordable, the project has already lost time and negotiating position.
Pre-Tender Estimate: Is the Tender Baseline Defensible?
The pre-tender estimate should be the most disciplined estimate before the market is formally tested. By this point, the team should have coordinated drawings, specifications, tender documents, a clearer procurement route, and a defined scope for pricing.
The estimator should be working from measured quantities, current market intelligence, package logic, preliminaries, risk review, and a documented basis of estimate. This is also the stage where the bill of quantities or pricing schedule becomes commercially important because tenderers will price against the information issued.
A defensible pre-tender estimate helps the owner evaluate tender returns. It gives a baseline for checking whether bids are realistic, incomplete, heavily qualified, or carrying hidden assumptions.
Before tender, the owner should ask:
- Are drawings and specifications coordinated enough for pricing?
- Are the measured quantities aligned with the tender scope?
- Are provisional sums and undefined items clearly identified?
- Are preliminaries, temporary works, logistics, and sequencing properly considered?
- Are market rates current?
- Is the risk allowance still appropriate?
- Has the estimate been reconciled against the previous cost plan?
The pre-tender estimate should not be used to force the market into an unrealistic number. It should be used to understand the market response with discipline.
The Estimate Range Matters More Than False Precision
Owners often want one number because one number feels easier to approve. But a single number without confidence context can be misleading.
Estimate accuracy is affected by design maturity, market volatility, procurement route, contractor appetite, site risk, specification clarity, programme pressure, currency exposure, and the completeness of tender information. Some of these can be reduced through better information. Others can only be carried as risk.
That is why estimate communication should include a range, assumptions, exclusions, and a clear basis. It is more professional to say "this is the current confidence range and the reasons behind it" than to present a polished total that hides uncertainty.
For owners, this is not just a technical issue. It affects funding approvals, scope decisions, tender strategy, value engineering, and project governance.
How GEMS Reviews Estimate Confidence
GEMS looks at estimate confidence through the information behind the cost, not only the final number.
For pre-contract quantity surveying and estimating support, the review should test:
- whether the estimate matches the current design stage
- whether quantities are measured at the right level of detail
- whether assumptions and exclusions are visible
- whether key packages have suitable pricing evidence
- whether contingency reflects real project risk
- whether cost movement has been reconciled from the previous stage
- whether the estimate supports the decision the owner is about to make
This matters because different project stages need different commercial answers. A feasibility estimate helps decide whether to proceed. A concept estimate tests the design direction. A developed design cost plan controls the budget. A pre-tender estimate sets the baseline for procurement.
Using the wrong estimate for the wrong decision creates avoidable risk.
Owner Checklist Before Relying on an Estimate
Before approving the next project step, ask these questions:
- What stage is this estimate intended for?
- What design information was available when it was prepared?
- What is included, excluded, assumed, or still undefined?
- Which quantities are measured, and which are allowance-based?
- What pricing evidence supports the major cost items?
- How have risk, contingency, and escalation been treated?
- What changed from the previous estimate?
- What decision is this estimate safe to support?
If those answers are unclear, the estimate is not ready to carry a major decision.
FAQs
Can an early feasibility estimate be accurate?
It can be useful, but it should be treated as an early cost range, not a tender-level commitment. Its job is to support feasibility decisions and identify major cost risks that need further investigation.
Why does the estimate increase as design develops?
Cost movement does not always mean poor estimating. It may reflect scope definition, specification decisions, quantity development, risk discovery, market pricing, or missing allowances becoming visible. The important step is reconciliation, so the owner understands the reason for the movement.
When should an owner bring in a quantity surveyor?
The earlier the budget risk matters, the earlier a QS should be involved. A QS can help test feasibility assumptions, set up the cost plan, review design decisions, prepare tender baselines, and keep estimate confidence aligned with project maturity.
Build the Estimate Around the Decision
Construction cost estimate accuracy improves as the project becomes better defined, but the estimate should always be judged against its purpose.
An early estimate can support investment screening. A concept estimate can guide design direction. A developed design cost plan can control the budget. A pre-tender estimate can support procurement and tender evaluation.
The owner does not need false certainty. The owner needs a clear basis, a realistic range, and a cost plan that improves as the project moves forward.
Discuss the right estimating basis and confidence range for your next investment decision with GEMS.
