top of page

The Building Costs Nobody Budgets For, and How to Avoid Them

  • Jul 15
  • 5 min read

Updated: Jul 24


Ask anyone who has been through a build that went over budget where the money went, and the answer is rarely the things priced at the start.


The framing, roofing, cladding, kitchen and services were quoted, compared and negotiated. The overruns usually come from the things nobody priced because nobody knew about them yet. A surprising share of those costs sit in the ground, in the structure, and in decisions made earlier than most people realise decisions were being made.


This article sets out how to reduce those costs, stage by stage, from before you own the site to the day construction starts.


But first, an honest boundary: much of what determines build cost, including materials, labour, procurement and contract type, sits with your builder and quantity surveyor. This article does not pretend otherwise.


What follows is the part engineering controls. It is a bigger part than most budgets acknowledge.


Before you buy: get pre-purchase geotechnical advice

The cheapest ground problem is the one you know about before you own it.


A pre-purchase geotechnical review of existing reports in the property file, or a walkover and desktop assessment where no report exists, can tell you what the site is likely to demand before you commit to the purchase.


Sometimes it changes what you offer. Occasionally it changes whether you offer. Most often, it means your budget starts realistic rather than optimistic.


Two sites that look identical from the street can differ by six figures in what they cost to build on. That difference is often knowable before you buy.



Before you design: spend where the risk is

Ground investigation is not a fixed-price commodity. The right scope should follow the risk.


A flat, well-understood site with no obvious hazard flags may only need a modest investigation. A sloping site, suspected fill, soft ground, high groundwater or natural-hazard risk justifies more investigation, but that spending should still be targeted.


Test positions should be placed to answer the questions the site raises, not scattered to a standard pattern. On larger or variable sites, geophysics can help map ground conditions first, so intrusive testing is placed where it resolves the most uncertainty.


The output should not just be a report. It should be a ground model: a coherent picture of the layers, groundwater and variability beneath the site.


Just as importantly, it should state what remains uncertain. Every ground model has uncertainties. The expensive ones are the ones nobody writes down. A project that knows its unknowns can carry them deliberately, with targeted contingency or staged investigation, rather than discovering them with a digger.



Optioneer early, not after consent

One of the biggest cost levers on any project is comparing genuinely different options while everything is still cheap to change.


Where should the building sit? How should it address the slope? Are shallow foundations, piles or ground improvement the best answer? Should the site be retained, regraded or redesigned around the terrain?


At feasibility stage, those questions cost sketches and engineering judgement. After consent, they cost redesign fees, programme time and consent amendments.


The pattern to avoid is common: a design develops almost to completion on assumptions, gets lodged or consented, and is then value-engineered when the price lands. By then, the best options may already be gone.


During design: integrate the ground and the structure

Geotechnical and structural design are often done in sequence. The geotechnical report is completed, the structural engineer designs to its parameters, and each discipline adds its own conservatism at the handover.


That can be safe, but it is not always efficient.


Better outcomes often come from treating the foundation, structure and ground as one system. That means understanding how the building actually loads the ground, how the ground responds, and where stiffness, settlement and foundation performance need to be balanced.



This is one of the quiet advantages of geotechnical and structural engineers working in the same team rather than exchanging reports between firms.


While you are there, ask for visibility on design optimisation. It is fair to ask:


  • “what options were considered? “

  • “what was ruled out?”

  • “where is the conservatism in this design?”


A good engineer should be able to answer. The conversation itself can surface savings, not because anyone was careless, but because conservatism accumulates silently at every interface unless someone deliberately reviews it.


Design for construction, not just compliance

A design can comply with every code and still be unnecessarily expensive to build.


The excavation may not suit the machinery available. The retaining may require temporary works nobody priced. The details may fight the sequence a contractor would naturally follow. Material may be carted off site as waste while similar material is carted back in.


Designing for construction means thinking about access, sequence, tolerances, availability of materials, temporary works, earthworks balance and whether site-won material can be reused as engineered fill where suitable.


Code compliance is the floor. It is not the whole objective.



Use AI tools intelligently

AI is entering engineering quickly, including data processing, options analysis, drafting and design iteration.


Used well, it can help engineers explore more options, make sense of large datasets and speed up routine work. For clients, that can mean more optioneering and better use of the design fee.


Used badly, it can make unverified assumptions look polished.


The discipline that matters is the same one that governs the rest of this article: output is only as good as the information beneath it, and professional verification still matters. Accountability does not transfer from the engineer to the model.


It is reasonable to ask your consultants how they use these tools and how outputs are checked. The good answer includes both enthusiasm and verification.


Make cost a design input from day one

Underneath all of this sits one habit: treating cost as a design input, not a design outcome.


On many projects, cost is discovered late. The design develops, it gets priced, and everyone reacts.


The better approach is to carry a cost lens through every decision from the first sketch, think:


  • What does this siting choice cost?

  • What does this foundation option cost?

  • What does this uncertainty cost to carry, compared with resolving it now?


None of that means compromising safety or performance. It means knowing what each decision costs while there is still time to make a better one.


Projects run this way rarely need rescuing at pricing time, because there is less left to discover.


Where we come in

This is how Cook Costello prefers to work from the start: pre-purchase advice before you commit, investigations scoped to the actual risk, ground models with the uncertainties stated, optioneering at feasibility, and geotechnical and structural design considered together.


We also bring visibility to where conservatism sits, design with construction in mind, use AI tools responsibly with verification, and where possible we treat cost as an input from the first conversation.


If you are at the start of a project, ideally before you have bought the site or locked in the design, tell us what you are planning. We will discuss what is worth knowing while knowing it is still cheap.




OR



bottom of page