Cost control is not about squeezing trades—it’s about clarity, timing, and documentation. In New Zealand, where labour availability, weather, and inspections all affect programme, unmanaged changes quickly turn into margin loss.
1) Variations: where margin usually leaks
A variation is any change to the agreed scope after the contract is signed. Common triggers include:
- late design changes,
- incomplete documentation at contract stage,
- unforeseen site conditions,
- compliance-driven changes (consent conditions, inspections).
Developer takeaway: variations are normal; uncontrolled variations are not.
In Hamilton and across Waikato, late design changes often interact with consented drawings—meaning changes may also require council approval, adding time as well as cost.
2) Provisional sums: necessary risk, not free flexibility
Provisional sums are allowances for work that can’t be fully defined at contract signing (e.g. rock excavation, service upgrades).
Why they’re risky
- Actual costs are often higher than allowances.
- They can mask real feasibility issues.
- They shift risk from contractor to developer.
Best practice
- Minimise provisional sums through early investigation (geotech, services checks).
- Where unavoidable, stress-test provisional sums in feasibility models.
- Track them separately so overruns are visible early.
3) Contract clarity matters more than price
Standard NZ residential contracts (often used with Master Build-style agreements) rely on:
- clear scope definitions,
- agreed variation procedures,
- documented approvals before work proceeds.
Practical risk: verbal approvals on site almost always become disputes later. Councils don’t arbitrate commercial disagreements—developers carry that risk.
4) Compliance-driven cost changes
Some variations are triggered by:
- council RFIs,
- inspection failures,
- updated compliance requirements (e.g. detailing for weathertightness or H1).
These aren’t optional costs. The key is anticipation:
- design for compliance early,
- allow contingency for known risk areas (stormwater, foundations, RBW).
5) Programme delays = hidden cost overruns
Every delay adds:
- interest and holding costs,
- site overheads,
- rebooking fees for trades and inspections.
In Waikato’s climate, weather delays can compound programme risk—especially when buffer time isn’t built in.
Developer mindset: time overruns often cost more than material overruns.
6) A simple cost-control system that works on site
Use this four-part approach:
1. Locked scope before contract
Freeze design where possible before signing.
2. Variation register
Track every variation with:
- description,
- cost,
- programme impact,
- approval status.
3. Weekly cost review
Compare committed spend vs feasibility—don’t wait for month-end.
4. Clear approval rules
No work proceeds without written variation approval.
7) Renovations: higher risk, tighter controls
Renovations carry more unknowns than new builds:
- concealed structure,
- legacy services,
- compliance upgrades triggered mid-build.
Best practice: higher contingency, more detailed pre-contract investigations, and faster decision-making on site.
A developer’s margin-protection checklist
- Design sufficiently complete before contract
- Provisional sums identified and stress-tested
- Written variation process enforced
- Programme buffers included
- Weekly cost tracking in place