Key takeaways
- Exempt development needs no development approval, but only while the work meets every condition the planning rules set, and one failed condition takes the job out of the exempt pathway.
- The boundary of qualifying work depends on the site as well as the job, so a heritage listing, a bushfire or flood constraint or an easement can remove work that would otherwise qualify.
- Approval is a question of pathway, but liability is not, so the builder remains answerable for the quality and compliance of exempt work exactly as for work that was approved.
- Licensing still applies to residential building work, so an exempt project does not sit outside the contractor licence regime, or the insurance and warranty arrangements that go with it.
- The safe habit is to record the pathway decision, the conditions checked and the site constraints considered before the first tool is switched on, because that record is what a dispute will be decided on.
Exempt development is the part of the planning system builders hear about most and understand least. The name suggests the work is outside the rules. It is not. Exempt development is work that does not need a development approval, because the planning rules have already decided that the work is minor enough to proceed without one, provided it stays within the conditions the rules set. The approval is removed. The obligations are not.
That distinction is the one that gets builders into trouble. A job that looks small, that a client wants done quickly and that nobody seems to need to approve is easy to start without checking the conditions. The conditions decide whether the job is exempt at all, and they are often checked against the site rather than the drawings. A job that stops qualifying halfway through the design is a job the builder has been doing without the approval it needed, and the builder carries the consequence.
This article is written from the builder’s side. It covers where the boundary of qualifying work sits, which conditions still apply to exempt work, why the builder stays liable for it, and how to make the pathway decision in a way that will survive a dispute. It is not a substitute for the current planning rules, which are the authority on what qualifies, and it is not legal advice on any particular project.
What exempt development means on the job
Exempt development is a category in the planning rules for minor works that the rules have decided can proceed without a development application, a complying development certificate or a construction certificate. The list of works is set out in the planning rules, and each entry carries conditions that describe the size, the location, the materials and the features the work may have. Work that meets those conditions is exempt. Work that does not meet the conditions falls to another pathway, or needs an approval altogether.
The practical effect is that the builder does not lodge an application for exempt work. That saves time and cost, and it is the reason the pathway is attractive. It also means there is no council assessment of the design at the start, and no council inspection at the end that confirms the work matches what was proposed. The check that an approval would have provided falls to the builder, and the builder does it without the council’s review behind it.
Exempt development is therefore a matter of self-assessment. The builder decides whether the work qualifies, and the builder is answerable if the decision is wrong. That is the mechanism to keep in mind for every job that looks exempt, because the decision is made by the person doing the work, not the person who approves it.
Where the boundary of qualifying work sits
The boundary is set by the conditions in the planning rules, and it moves with each feature of the job. A change to the height, the setback, the footprint, the materials or the use of a structure can take the work from the exempt pathway into another pathway, or out of the planning system altogether and into the need for approval. The boundary is not a single line on a map. It is a set of conditions, each of which the design has to meet.
Think about the boundary in terms of the features that change most often during a job. A structure that is exempt as drawn may stop being exempt when a roof is added, when a wall is extended or when a window is moved closer to a boundary. A design that started as a simple structure can drift across the boundary through a series of small changes, none of which seemed to matter on its own. The discipline is to re-check the conditions whenever the design changes, not only at the start.
The description of the work in the rules also matters. The rules describe what qualifies, and a feature that is not in the description may not be covered by the exempt pathway even if it looks similar to something that is. A builder who treats a close resemblance as a match is relying on a judgement the rules did not give.
The site constraints that move the boundary
The conditions in the rules are only part of the test. The site carries constraints that can remove work that would otherwise qualify, and these are the constraints most often missed. A property in a heritage listing or a heritage conservation area, a property on bushfire-prone land, a property subject to flood controls or an easement over part of the lot may all be treated differently from the general rule. Local controls can add to the state rules as well.
Check the property before the design is finalised, not after. The planning portal and the local council records will show most of the constraints that apply, and the certificates for the land will show others. A constraint discovered after construction has started is a constraint that has to be dealt with in the most expensive way available, which is usually by stopping the work and seeking an approval that should have been identified at the start.
The question to ask is simple. Does the site carry any constraint that changes what the rules allow here? If the answer is yes or not known, the job is not ready to be treated as exempt until the question is answered.
Conditions that still apply to exempt work
An exempt project still has to meet the conditions of the exempt pathway, and it has to meet the standards that apply to the building work itself. The approval has been removed. The requirement that the work be safe, durable and built to the relevant standards has not. A builder who treats exempt work as a lighter category of building work is making a mistake that the rules do not support.
The conditions that matter most are the ones the builder is most likely to skip. The setbacks, the height and the materials are checked against the drawings, but the conditions about the use of the structure and the features that can be added later are the ones that get forgotten. A condition that restricts the use of a structure does not stop applying because the client wants something different once the work is finished.
Conditions that still bind exempt work
- The work matches the description in the planning rules, with no added features that take it outside the list.
- Every condition on the exempt pathway is met on the drawings and on the ground, not only on paper.
- Site constraints such as heritage, bushfire, flood and easements have been checked and cleared.
- The work is carried out by a licensed builder where the licence regime requires one for the work.
- The building standards that apply to the work are met, whether or not a council inspects it.
- Any change to the design during construction has been checked against the conditions again.
Carry the list into the job. Each condition should be checked against the work as built, not only as designed, and the check should be recorded by the person who made it. The check is quick when it is done at each stage, and slow and expensive when it is done at the end.
Why the builder stays liable whatever the council saw
The absence of an approval does not reduce the builder’s responsibility for the work. The council is not the only check on quality, and the builder is the one who carried out the work. Defects in residential building work can give rise to claims for a long period after the work is finished, and the builder’s liability does not depend on whether the council was asked to look at the job first.
This matters most when the exempt work is later sold, altered or inspected. A buyer, an inspector or an insurer looking at a structure built under the exempt pathway will ask whether it met the conditions and the standards. The question will be put to the builder who built it, and to the owner who relied on the builder. A record that shows the pathway decision and the checks made at the time is the answer that holds up.
The liability is also a reason to be careful with the client. A client who asks for something that falls outside the exempt conditions is asking the builder to take a risk that the client does not carry alone. Say so in writing, and do not build the feature until the position is resolved.
Licensing, insurance and the paperwork that still applies
Exempt development does not remove the licensing regime from residential building work. A builder doing residential building work still needs the licence the work requires, and an individual licensed to do the work has to hold the correct class of contractor licence. The route to an individual contractor licence is set out by Service NSW, and a builder who has not checked the class against the work should do that before the job starts, not after a complaint.
Insurance and warranty arrangements also travel with the work. Residential building work that is insured under the Home Building Compensation Fund carries cover for certain defects, and the position depends on the work and the contract. Check the insurance position for the project before the work begins, and do not assume that an exempt project falls outside the insurance regime. The client should be given the paperwork they are entitled to, and the builder should keep copies of everything issued.
BASIX and the projects that look exempt but are not
BASIX is the sustainability assessment that applies to certain residential development, and it is tied to the approval pathway. A project that is exempt may fall outside BASIX, but a project that tips over into another pathway may bring it back in. The Planning Portal sets out how BASIX and planning approvals fit together, and it is the place to confirm the position for the specific project.
The trap is the project that changes pathway during the design. A builder who priced an exempt project, started the work and then found that a feature brought the project into a different pathway may find that the BASIX commitments apply to work already built. That is an expensive position, and it is avoided by making the BASIX question part of the pathway decision from the start.
Deciding the pathway before the work starts
The pathway decision should be made on paper before the first quote is accepted, and it should be re-made whenever the design changes. The steps below are the sequence to follow. Each step is simple. Skipping one is how a job that looked exempt ends up without the approval it needed.
Deciding the pathway before the work starts
- 1Confirm the work is the kind the planning rules listRead the current list of exempt works rather than working from memory or from what a neighbour did.
- 2Check the site constraintsLook up the property for heritage, bushfire, flood, easements and any local controls that override the general rules.
- 3Measure against each conditionCheck every condition against the design as drawn, not against the design as first discussed.
- 4Check whether BASIX appliesConfirm whether a BASIX certificate is needed, because a project that falls outside the exempt pathway may bring it in.
- 5Record the decisionWrite down the pathway chosen, the conditions checked and who checked them, and keep it with the job file.
The decision is the builder’s to make, but it is best made with the advice of a qualified person where the job is complex or the site is constrained. A short conversation with the council or a planning consultant can save much more than it costs when the site has a constraint that is not obvious from the records.
A worked example: the deck that drifted
Consider a builder in western Sydney who was engaged to build a timber deck at the rear of a house. The initial design was a low deck with no roof, and the builder checked it against the exempt conditions and found it qualified. The builder priced the job on that basis and began the work without a written record of the check.
Partway through, the client asked for a roof over part of the deck and a privacy screen along one side, and the builder agreed to add both as variations. Nobody re-checked the conditions. The roof and the screen together took the structure outside the exempt description, and the property also turned out to be subject to a local control that the initial check had not picked up. The work was finished, and the council later issued a notice requiring the structure to be dealt with.
The builder had to seek an approval after the fact, rework part of the structure to meet the conditions, and deal with the client’s expectations about the roof. The cost was far above what the approval would have cost at the start. The change that caused it was a variation, and the variation was priced without asking whether it changed the pathway. The lesson is simple. Every variation is a re-check of the pathway, and the record of the check is what protects the builder when the work is looked at later.
The mistake that costs the most. Pricing a variation without re-checking the pathway. A small change to the design can take the work out of the exempt category, and the approval that should have been sought at the start is then needed after the work is built.
Keeping a file that proves the decision
The file for an exempt project should contain the pathway decision, the list of conditions checked, the site constraints considered and the date of each check. It should also contain any variation that was tested against the pathway, and the result of the test. A short file with those items is far more useful than a long one with no decision in it.
Keep the file with the job records for as long as the work is open to question, and make sure it is available to whoever takes over the job or the property. A builder who can produce the decision and the reasoning at the time is in a much stronger position than one who has to reconstruct it from memory. The file is the record that a dispute will be decided on.
Staying current with the rules
The planning rules change, and the list of what qualifies can change with them. A check that was correct when the job was priced may not be correct when the work starts. Read the current rules at the time of each decision, and do not rely on a list from a previous job or a colleague’s recollection. A builder’s own learning has to keep pace with the same changes, and our guide to how NSW builder CPD works sets out the scheme.
The safe habit is the one that protects the builder whatever changes. Confirm the pathway, check the site, record the decision and re-check whenever the design moves. A builder who does that will rarely be caught out by the boundary, and will be able to explain the decision to anyone who asks.
Closing the question properly
Exempt development is a useful tool for the builder who understands it, and a trap for the builder who treats it as a shortcut. The approval is removed, and the conditions, the standards and the liability remain. The boundary sits in the conditions and in the site, and it moves whenever the design moves. Make the decision on paper, check the site, and keep the record.
Our PointCPD home page lists the NSW builder courses we offer. The related article on complying development covers the pathway that sits next to exempt work, and the decision about which pathway applies belongs at the start of every job.
Questions builders ask
Can I start exempt development work without any approval?
Yes, but only if the work is on the exempt list in the planning rules and meets every condition that applies to it, including any site constraints. If it does not meet them, it needs a different pathway or an approval before it starts.
Does exempt development mean the work is not inspected?
The council does not usually approve or inspect exempt work in advance, so the check that an approval would have provided falls to the builder. The builder remains responsible for the quality and compliance of the work whether or not anyone inspects it.
Do I still need a builder’s licence for exempt work?
Exempt development does not remove the licensing regime for residential building work. Check the class of licence the work requires, and make sure the person doing the work holds it before the job starts.
What if the client wants a feature added partway through an exempt job?
Re-check the pathway before agreeing to the change. A feature that was not part of the original description can take the work outside the exempt pathway, so the change should be priced and recorded only after the check is made.
Can a site constraint make a job that looks exempt need an approval?
Yes. Heritage listings, bushfire and flood controls, easements and local controls can all remove work that would otherwise qualify. Check the property records and the planning portal before the design is finalised.
Does BASIX apply to exempt development?
It depends on the project. BASIX is tied to the approval pathway, so an exempt project may fall outside it, but a project that moves into another pathway may bring it back in. Confirm the position on the Planning Portal for the specific job.
Sources
- Continuing professional development for builders and swimming pool builders · NSW Government
- General building work licensing · NSW Government
- Home Building Act 1989 (NSW) · NSW Legislation
Published 26 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.
