Infrastructure charges and development costs: the cost layer builders miss

Infrastructure charges are one of the few development costs that attach to a project before anyone orders a trade, and they are also one of the most commonly missed when a builder prices a job. The reason is structural: the charge is not a building cost. It is a contribution the consent authority or a utility requires because the development increases demand on local infrastructure. It sits in the client’s development budget, not in the trade breakdown, and because it never appears as a line in the take-off, it quietly disappears from the estimate until someone opens the consent conditions.

For a builder, that matters commercially. On a small project the charge may be modest, but on a multi-dwelling or subdivision job it can be large enough to change the feasibility of the whole scheme. If it surfaces late, the client is short of funds at exactly the point they need a construction certificate, and the builder wears the programme delay. On a fixed-price contract, an unpriced charge can become a dispute about whose cost it was always meant to be.

This article looks at the specific cost layer that infrastructure charges represent: what triggers them, when they are paid, how they interact with other development costs, and how to carry them in an estimate without pretending to know a figure you do not have.

What infrastructure charges actually are

An infrastructure charge is a monetary contribution required by a condition of development consent. It is levied because the development is expected to place additional demand on infrastructure — local roads, drainage, open space, community facilities, or the water and sewer network. The consent authority or the relevant utility sets the charge, and the applicant or owner pays it. The builder is rarely the payer, but the builder is almost always the person who discovers the charge was not in the budget.

The charge is calculated from the expected demand the development creates, not from the builder’s cost to construct. That is why it does not behave like a trade cost. A larger dwelling, an extra lot, or a change of use can all increase the demand and therefore the contribution, even if the building work itself has not changed. A variation that adds a secondary dwelling, for example, can trigger a fresh contribution even though the builder sees only a small addition to the scope.

Contribution plans are the documents that set out how charges are calculated and what they fund. Those plans are reviewed and updated from time to time, so a figure quoted at feasibility may be out of date by the time the construction certificate is applied for. The correct approach is to check the current requirement in the relevant contribution plan or with the consent authority, rather than relying on a number from an earlier project or an old quote.

Where the charge sits in the development cost stack

Builders are used to thinking in layers: preliminaries, structure, envelope, services, fit-out, margin. Development costs are a different stack that sits above the building contract. That stack includes planning fees, consultant fees, council contributions, utility headworks, and the infrastructure charges discussed here. Some of these are paid by the owner, some by the applicant, and some, under a works agreement, by the utility. The builder’s job is to know which of them touch the contract and which do not.

Infrastructure charges usually sit outside the building contract entirely. They are paid to the consent authority or utility, not to the builder, and they fall due at a point set by the consent or the relevant legislation — commonly before the construction certificate or subdivision certificate is issued. That timing is the trap. The owner may have enough cash to start building but not enough to release the certificate, and the builder’s programme stops while the money is found.

It helps to think of the charge as a gate rather than a trade. You cannot build past it, and you cannot negotiate it away after consent is granted. The only real control is to identify it early and make sure the client has funded it.

What triggers a charge and what changes it

A charge is triggered by the development consent, and the amount depends on the demand the development creates. In practice, the triggers a builder should watch for are changes to the development itself: additional dwellings, subdivision of land, a change of use to something more intensive, or an increase in the number of lots or bedrooms. Each of these can increase the calculated demand and therefore the contribution.

The commercial consequence is that a variation to the building contract can have a planning cost attached that never appears in the variation. A client who asks to convert a garage into a habitable room, add a secondary dwelling, or split a lot may be creating a fresh planning application and a fresh infrastructure charge. If the builder prices only the construction work, the client gets a nasty surprise, and the builder gets blamed for not warning them.

There is also a timing trigger. Because the charge is generally payable before the construction certificate is issued, any delay in paying it delays the certificate, which delays the start on site. Interest and holding costs on an idle programme are real money, and they usually land on the applicant. A builder who has flagged the charge early can at least sequence the payment so it does not sit on the critical path.

The mistake that costs the most

That mistake is avoidable with a single question at quoting stage: has the infrastructure charge been paid or provided for? If the answer is vague, treat the charge as an unknown cost and manage it in writing. Do not absorb it into the contract sum on the assumption it is small. On larger schemes it is not small, and on any scheme it is not the builder’s cost to carry.

How to carry the charge in an estimate

There are three workable ways to handle an infrastructure charge in an estimate, and the right one depends on what you know at the time. If the charge has been paid or a notice has been issued with a known amount, you can list it as a client cost with the figure and the due date recorded. If the charge is expected but not yet calculated, carry it as a provisional sum with a clear scope note explaining what it covers and that it will be adjusted when the notice issues. If the consent conditions are not available, exclude the charge in writing and get the client to acknowledge the exclusion before you sign.

Whichever route you take, keep the charge in its own section of the estimate rather than buried in preliminaries. A separate line makes it visible at every review, and it makes the conversation with the client straightforward. It also protects you if the charge changes because the development changes: you can point to the original line and show what moved.

Do not attempt to calculate the charge yourself from a rate per lot or per dwelling. Rates change, plans are updated, and the calculation depends on matters outside the builder’s scope. The correct source is the contribution plan or the consent authority, and the correct answer is a figure or a range confirmed by them.

Other development costs builders routinely miss

Infrastructure charges are the headline, but they travel with a group of related costs that also sit outside the building contract. Long service levy, planning and construction certificate fees, utility connection charges, and the cost of complying with conditions such as BASIX or other sustainability requirements all fall into the same layer. None of them are trade costs, and all of them can delay a certificate if they are unpaid or unaddressed.

BASIX is a good example of a condition that carries both a compliance cost and a programme cost. A BASIX certificate is required for certain residential development, and the commitments it records — such as water and energy measures — become obligations the builder must meet on site. If the certificate is not in place or the commitments are not priced, the builder discovers the cost during construction, when it is hardest to recover. The same logic applies to any condition that specifies a standard the building work must meet.

The practical response is to build a development cost schedule alongside the trade estimate. It lists every approval, charge, fee, and condition that could carry a monetary or programme cost, who is responsible for it, and when it falls due. That schedule is the builder’s early warning system, and it is far cheaper than discovering the cost at certificate stage.

Worked example: a builder in western Sydney

A builder in western Sydney is asked to quote a two-lot subdivision with a new dwelling on the rear lot. The client has development consent and is keen to start. The builder prices the dwelling from the plans, adds preliminaries and margin, and issues a fixed-price contract. What the builder has not done is read the consent conditions.

Several months later, when the construction certificate is applied for, the consent authority confirms that an infrastructure charge applies to the subdivision and must be paid before the certificate issues. The client has spent the contingency on landscaping and does not have the funds available immediately. The certificate is held up, the site sits idle, and the builder’s programme slips. The client argues the charge should have been in the contract price. The builder argues it was never a building cost.

Neither party is entirely wrong, and that is the problem. If the builder had asked for the consent conditions at quoting stage, the charge would have appeared as a client cost with a due date. The client would have funded it, or the job would not have proceeded. The cost of the omission is not just the charge itself; it is the delay, the idle programme, and the damaged relationship on a job that may have repeat work behind it.

The lesson is not that builders should pay infrastructure charges. It is that builders should know about them before they sign, because the charge controls access to the site whether or not it appears in the contract.

Getting the paperwork right before you sign

The documents that matter are the development consent, any contribution notice, any utility works agreement, and the current contribution plan. Ask for them in writing at quoting stage. If the client cannot produce them, say so in the quote and make the charge an excluded cost. That single sentence protects both parties and sets the expectation that the charge is the client’s responsibility.

If the charge is already known, record the amount, the payee, and the due date in the estimate. If it is not known, record the basis on which it will be calculated and who will confirm it. If the development changes during the job, revisit the charge before you price the variation, because the change may have triggered a fresh contribution. A variation order that ignores the planning consequence is an invitation to a dispute.

For builders working under the Home Building Act and the broader NSW planning framework, this is also a professional knowledge issue. The regulatory environment changes, contribution plans are updated, and the conditions attached to consent are not always obvious from the drawings. Keeping current is part of running a compliant business, and it is the kind of thing covered in the PointCPD guide to how NSW builder CPD works. If you want to build the estimating side of this into your own systems, the article on construction cost drivers is a useful companion, as is the piece on land supply and development in NSW.

Frequently asked questions

Who pays infrastructure charges on a residential job?

The applicant or owner pays the charge, not the builder. It is a contribution required by a condition of development consent and is paid to the consent authority or the relevant utility. The builder’s role is to identify it early and make sure it is funded, because an unpaid charge can stop the construction certificate being issued.

When does an infrastructure charge fall due?

Timing is set by the consent condition or the relevant legislation, and it commonly falls due before the construction certificate or subdivision certificate is issued. Because it sits before construction, an unpaid charge can stall the programme before work starts. Check the consent condition for the exact trigger rather than assuming it is paid at the end of the job.

Can a builder pass the charge through as a variation?

Only if the contract allows it and the client agrees. The cleaner approach is to exclude the charge in writing at quoting stage or carry it as a provisional sum with a clear scope note. Trying to recover it as a variation after the certificate is refused is far harder than flagging it before the contract is signed.

Does a change to the design change the charge?

It can, because the charge is calculated from the expected demand the development places on infrastructure. Adding a dwelling, subdividing land, or changing the use can increase that demand and trigger a fresh contribution. Before pricing a variation, check whether the change requires a new or amended consent and whether a new charge applies.

Where do I find the current charge figure?

The current figure comes from the relevant contribution plan or from the consent authority, not from a previous project or an old quote. Contribution plans are updated from time to time, so a figure from last year may no longer be correct. Ask the consent authority or the utility to confirm the amount in writing.

Is BASIX part of the same cost layer?

BASIX is a separate requirement, but it belongs in the same development cost schedule because it carries both a compliance cost and a programme cost. A BASIX certificate records commitments the building work must meet, and those commitments need to be priced before construction. The PointCPD course catalogue covers how these obligations interact with contract administration.

Questions builders ask

• Certification
• Costs
• Housing supply

Published 29 July 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.