Developer obligations on NSW residential projects: what builders need to know

On a NSW residential project the developer is not just the party paying the invoices. The developer holds a set of statutory obligations that exist whether or not a builder is on site, and those obligations are the reason the contract you are asked to sign looks the way it does. The conditions about programme, inspection, handover and defects are not arbitrary. They are the developer passing down the parts of its own obligations that it cannot discharge without you.

Builders who understand the developer’s side of the framework negotiate better. They know which conditions are statutory and immovable, which are the developer’s commercial preferences dressed up as requirements, and which are simply a transfer of risk that the developer should be carrying. That distinction is worth real money over the life of a project.

This article deals with the developer’s obligations and how they land on the builder. It does not cover the builder’s own licensing and CPD obligations, which are dealt with elsewhere on the site.

Why the developer carries obligations at all

NSW regulates residential building from two directions at once. One direction is the licensing and conduct regime that applies to the people doing the work. The other direction is the set of obligations that attaches to the person who sells or leases the finished product to a consumer. A developer can be both, and often is, but the obligations are distinct.

The practical consequence is that a developer cannot contract out of its obligations to a purchaser by pointing at the builder. If a purchaser has a complaint about the finished home, the developer remains in the frame. That is exactly why developers push so much detail into the building contract: every obligation they cannot escape, they try to make enforceable against the builder instead.

For a builder, this is not a reason to refuse the work. It is a reason to read the contract as a risk allocation document rather than a scope document. The scope tells you what to build. The risk allocation tells you who pays when something outside the scope goes wrong.

What the developer is actually obliged to do

Broadly, a developer of NSW residential work holds obligations in four areas. First, disclosure: the developer must give a purchaser the information the framework requires about the property and the building work, at the time the framework requires it. Second, compliance: the completed work must comply with the approvals and the applicable standards. Third, completion: the developer must deliver what was promised on the terms promised. Fourth, rectification: defects that appear after completion must be dealt with within the statutory framework.

None of these are discharged by engaging a competent builder. A developer who engages a competent builder and then directs that builder to vary the approved design has not discharged its compliance obligation. It has created a problem that will surface at inspection, at sale, or years later during a defects claim.

This is the point where builders get caught. If you follow a verbal direction from a developer that takes the work outside the approved documents, you are the person on site doing non-compliant work. The developer’s obligation does not shield you from the consequences of your own execution. Get variations in writing, and if a direction would take the work outside the approval, say so in writing before you proceed.

How obligations move from the developer to you

The transfer happens through three channels, and it is worth naming them because they fail in different ways.

The first channel is the contract. Standard form residential building contracts allocate risk on payment, delay, variations and defects. Developers with legal support will amend those clauses. The amendments are where the builder’s margin lives or dies.

The second channel is the approvals. Conditions attached to a construction certificate or a complying development certificate bind the person carrying out the work. Those conditions often impose inspection hold points, documentation requirements and sequencing that the builder must meet. A builder who never reads the certificate is working blind.

The third channel is site control. Once the developer gives possession of the site, the work health and safety duties for that site sit with the principal contractor, which is normally the builder. The developer’s ownership of the land does not change that. If the developer insists on bringing its own trades onto site, or on controlling access, the builder needs to be clear in writing about who is directing those people.

Understanding how these channels interact is part of the broader picture covered in the PointCPD guide to how NSW builder CPD works, which sets out the categories of knowledge the scheme expects a licensee to maintain.

Reading the approval conditions before you price

Most builders price from drawings. On a developer project that is not enough. The approval conditions can add cost that no drawing shows: additional inspections, hold points that stop work until a certifier attends, documentation that must be prepared before a stage can proceed, or conditions about hours, access and sediment control that constrain how the site can be run.

Ask for the consent and the certificate, not a summary. Read them against the programme. If a condition requires an inspection before a slab can be poured, that inspection is a date in your programme, and if the certifier cannot attend on that date the programme moves. Decide now who carries that risk. If the answer is you, price it.

The related article on construction certificate conditions goes through the categories of condition you are likely to meet and how they interact with the programme.

Conditions that commonly catch builders out

• Inspection hold points that require a certifier to attend before work is covered up, with no allowance in the programme for the wait.
• Stormwater and sediment control conditions that restrict when earthworks can proceed.
• Conditions requiring documentation to be lodged before a stage can be signed off, where the documentation is not the builder’s to produce.
• Conditions about tree protection, access or working hours that constrain the sequence of trades.
• Conditions that require the work to be carried out substantially in accordance with the approved plans, with no tolerance for the developer’s later design changes.

Contract terms that decide who pays

Four clauses do most of the damage on developer projects: payment, variations, delay, and suspension.

On payment, the question is not just the amount but the mechanism. Who certifies the claim, what evidence is required, how long after certification the money arrives, and what happens if the certifier sits on a claim. A payment regime that depends on the developer’s own assessment, with no backstop, transfers cash flow risk to you for the whole project.

On variations, the risk is scope creep that is never priced. A developer who issues directions on site and expects them to be absorbed into the contract sum is relying on your reluctance to stop work. Agree the mechanism before you start: who can direct a variation, in what form, and what happens if you are directed to proceed before the price is agreed.

On delay, the question is who owns the developer’s decisions. If the developer changes the design, delays an approval, or holds up a selection, and the programme moves, the contract should say who carries the cost. Where it does not, the builder does.

On suspension, the builder’s right to stop work for non-payment is a real lever, but only if the contract and the legislation allow it on the facts. The article on suspending work under an NSW residential contract covers when that right arises and how to exercise it without exposing yourself.

Payment, security and the developer’s funding position

A developer’s obligation to pay you is only as good as its funding. Before you commit plant and labour, understand how the project is funded and what security is available to you. On larger projects that may be a bank facility with a quantity surveyor certifying progress. On smaller ones it may be nothing more than the developer’s own equity and pre-sales.

Ask plainly what happens if pre-sales do not reach the level the developer needs, and what the contract says about suspension or termination in that case. A builder who has poured slabs and framed a building on a site where the developer’s funding has stalled is in a worse position than one who asked the question at tender.

Retention and security arrangements matter here too. If the contract allows the developer to hold retention for an extended period, or to call on security for defects that are not yours, that is risk you are carrying at no price. Read those clauses as carefully as you read the scope.

Site control and who is the principal contractor

On a residential project the builder is normally the principal contractor, which means the work health and safety duties for the site are yours. That includes managing the trades the developer brings on, if the developer brings them on.

Developers sometimes want to run their own consultants, their own surveyor, or their own finishing trades through the site. That is workable, but only with clear written arrangements about who directs those people, who inducts them, and who is responsible if something goes wrong. Ambiguity here is how a builder ends up holding a duty it never had the authority to discharge.

If the developer wants to retain control of part of the site while you are working, get that documented. Who controls access, who signs people in, who maintains the site diary, and who has authority to stop work. The answer should be one person, and on a construction site that person is normally you.

Completion, handover and the defects period

Practical completion on a developer project is rarely just a builder-to-developer event. The developer has obligations to purchasers, and those obligations have dates. That pressure flows down into your completion date, whether or not the contract says so.

At handover, make sure the documentation the approval conditions require is complete: inspection records, certification, and any manuals or warranties the conditions call for. Missing documentation surfaces later as a condition that was never satisfied, and by then the certifier may not be willing to sign off retrospectively.

Through the defects period, the developer will receive claims from purchasers and pass them to you. Your contract should define what counts as a defect, how claims are notified, what response times apply, and how disputes about whether an item is a defect are resolved. Without those definitions you are responding to a stream of items on the developer’s timetable and at your cost.

Where the developer has also been the owner-builder at some stage, or is running the project under a permit rather than through a licensed builder, the obligations can be more complicated again. The article on owner-builder permit obligations sets out how that changes the picture.

Worked example: a townhouse project in western Sydney

A builder in western Sydney tenders for a multi-dwelling residential project. The developer provides architectural drawings, a specification and a draft contract. The builder prices from those documents and signs.

What the builder did not obtain was the construction certificate. The conditions attached to it require the certifier to inspect the footing system before concrete is placed, and require a stormwater design to be lodged before the drainage is covered. Neither requirement appears on the drawings. Neither is mentioned in the specification.

On site, the footing excavation is ready and the certifier cannot attend for several days. The crew stands down. The developer’s project manager directs the builder to pour and have the inspection done afterwards. The builder, knowing that covering work before inspection is a compliance breach, declines and puts the direction in writing.

That written refusal is the thing that saves the builder. The programme moves, the developer claims liquidated damages for delay, and the builder points to the direction it refused and the condition it was working to. Because the refusal is documented, the delay is the developer’s. Had the builder poured and sought the inspection later, it would have been carrying the cost of the delay and the cost of any rectification the certifier required.

The lesson generalises. On a developer project, the documents that decide the outcome are the approval conditions and the contract clauses, not the drawings. The builder who reads both before pricing is not being difficult. It is doing the only thing that makes the price meaningful.

What to do before you sign

• Obtain the development consent and the construction certificate, and read the conditions against the programme.
• Identify every hold point and every document the conditions require, and decide who produces each one.
• Read the amended contract clauses on payment, variations, delay, suspension and defects as risk allocation, not boilerplate.
• Confirm in writing who is the principal contractor and who directs any trades the developer brings onto site.
• Establish the variation mechanism, including what happens if you are directed to proceed before the price is agreed.
• Ask how the project is funded and what security is available to you if it stalls.
• Define in the contract what a defect is, how it is notified, and how a dispute about it is resolved.

None of this is exotic. It is the ordinary commercial work of taking on a developer project, and it is the reason the CPD scheme expects licensees to keep their contract and compliance knowledge current. If you want to work through the categories in more detail, the PointCPD course catalogue and the NSW builder CPD courses on the home page cover the contract, approval and site management topics that come up on projects like these.

Questions builders ask

• Approvals
• Compliance
• Contracts

Published 16 September 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.