Why Do Building Projects Go Over Budget?
Most building projects go over budget because of a decision made before the build, not a problem that appeared during it.
The overrun feels like it happens on site: a variation here, a price rise there. But trace it back and the cause is usually earlier. A brief that was never confirmed against the budget. A site assumption that didn’t hold. An approval that took longer and cost more than anyone planned for. The blowout was set at the front. It just became visible later.
Which means the answer isn’t tighter control during the build. It’s making your decisions earlier, while they’re still cheap to make.
The real reasons projects blow the budget
A handful of front-end gaps cause most overruns.
- The brief was never confirmed against the budget. The design was always going to cost more than the money allowed.
- The site carried costs no one checked. Slope, rock, services, flood or bushfire requirements that only surfaced once work began.
- The approval pathway was assumed rather than confirmed. The real one added time and fees.
- The design ran ahead of the decisions. Changes were made late, when changes are most expensive.
- The budget was a round number. Not a figure worked out against what the project actually involved.
None of these are construction problems. They’re decision problems, and they’re all cheaper to settle before design starts.
Why late changes cost the most
A change costs almost nothing as a conversation at the front. The same change costs a redraw mid-design, and a small fortune once it’s on site.
The further a project travels, the more is built on top of each decision. Move a wall on a sketch and nothing else is affected. Move it after documentation and approval, and the drawings, the costings and sometimes the approval all have to follow. Momentum is expensive to reverse. That’s the whole reason to do the thinking before the momentum builds.
Deciding when you’re fresh, not when you’re exhausted
Here’s the part nobody warns you about. A renovation or a new build can run for two or three years from first thought to moving in, and the whole way through you are making decisions. Hundreds of them.
By the time you reach the part you were actually looking forward to, choosing finishes, fittings, the things you’ll touch every day, a lot of people are simply done. They’ve been deciding for two years. They pick something to end the conversation rather than because it’s right.
That’s not a character flaw. It’s what happens when decision-making is spread thin across years instead of concentrated at the front.
Deciding early fixes this in two ways. You make the significant calls while you still have the energy and interest to make them well. And every decision you settle early removes options later, which makes the remaining choices smaller and faster. Clear direction is what makes the rest of the project feel manageable.
How deciding early protects the budget
Settle the big things first: what you’re actually asking for, what the site will carry, which approval you need, and what the money will realistically stretch to. Get those clear before design starts and the design has something solid to work against.
The budget stops being a number you hope holds and becomes one the project is built around.
That’s what Decide is for. I confirm the brief, read the site and establish the approval pathway before any design is committed, so the expensive surprises turn up while they’re still cheap to deal with.
Before you commit to a design
If you’re about to start a project and the budget matters, settle the decisions before the design runs ahead of them. The Decision Session is a focused block of time to do exactly that: I confirm your brief, work through the site and your budget with you, and you leave knowing what you’re actually asking for and what stands between you and it. Not sure that’s the right fit yet? Start with a short call and we’ll work out the best next step. It’s far cheaper to make the decisions at the front than to discover the gap on site.
For the bigger picture on front-end timing, refer to my earlier article: when to engage an architect.