Why Do Building Projects Go Over Budget in NZ? Five Causes

Ask a client whose build went over budget what happened and they will describe a surprise: the invoice that was double the figure they had in their head. Ask the builder and they will describe a series of small, reasonable decisions that each made sense at the time. Both are right. Over-runs are almost never one event. They are five habits, and every one of them is visible weeks before the invoice.

Allowances that were guesses

A quote says “allow $8,000 for tiles”. Nobody chose the tiles. The client picks a $14,000 tile six weeks later, often without being told it is a $6,000 decision, and the allowance quietly becomes the first over-run. Multiply by kitchen, bathroomware, lighting, flooring, landscaping. Allowances are the single biggest cause of residential over-runs, and the fix is simple: state every allowance as an allowance on the quote, show the client the running total when a selection is made, and get the selection signed off with its price before it is ordered.

Variations agreed on the phone

A client rings, asks for a window to be made bigger, the builder says “no problem”, and the change is built. It appears on an invoice a month later, un-priced in advance, and the client who heard “no problem” assumed it meant “no cost”. Every variation needs to be written down the day it is raised, priced, and approved before the work happens. A variation form takes five minutes. A variation argument takes a week.

Nobody tracked committed costs

The budget said $20,000 for electrical. The electrician’s quote came in at $26,000 and was accepted because the job needed to keep moving. In a business that tracks only invoices, that $6,000 does not exist until the electrician bills, which might be at the end. In a business that tracks committed costs, the forecast final moved the day the quote was accepted and the builder had a month to recover it somewhere else or tell the client.

The programme slipped and preliminaries ran on

Site costs run with time: scaffold hire, site toilet, fencing, supervision, insurance. A job that runs eight weeks late carries eight weeks of those costs, and they are rarely in anyone’s budget as a function of time. Track the programme alongside the money, and when the end date moves, move the preliminaries line with it.

The client found out at the end

The over-run that damages the relationship is not the biggest one. It is the one the client learned about last. Across 13,567 publicly posted reviews of NZ builders and outdoor and civil contractors, value is the lowest-scoring of the four rated dimensions at 97.6 out of 100 for both groups, while transparent pricing is praised in 21.6% of positive builder reviews and 25.0% for civil work. Clients who were shown the numbers all the way through rate the price better than clients who were shown the same numbers at the end, because the first group made the decisions and the second group received them.

What to do about it

Code every cost and track four numbers per code: budget, committed, invoiced, paid, with the forecast final as the largest of the first three. Log every variation the day it is raised and price it before it is built. State every allowance as an allowance and sign off every selection with its price. Move preliminaries with the programme. Send the client a one-page budget summary with every progress claim.

None of that is sophisticated. It is a weekly fifteen-minute habit and a spreadsheet, and it turns the end-of-job surprise into a series of small, documented decisions the client was part of.

The construction cost tracker in our resource library is a free Excel workbook built around exactly that: cost codes, the four columns, the forecast-final rule, a variations log that feeds the budget, and the client summary page. Pair it with the scope of works and variation form in the same library, and the five causes above have a document each.

Building projects do not go over budget. People stop looking at the number, and the number keeps moving.