Self-Assessable vs Development Application in QLD: Reading the Planning Act 2016

What it is

Queensland development sits under the Planning Act 2016 and the Planning Regulation 2017. The Act sets five categories of assessment. Accepted development needs no Development Application (DA) provided every requirement in the accepted-development requirements is met. Code-assessable development requires a DA but the assessment is bounded by the assessment benchmarks set in the planning scheme. Impact-assessable development requires a DA, public notification, and an assessment that can consider any relevant matter. Prohibited development cannot be approved.

The old language of self-assessable development was folded into accepted-subject-to-requirements when the Planning Act 2016 commenced. Builders and designers still hear the term self-assessable on site. It now means accepted development with conditions in the planning scheme that the work must meet on its face.

How to tell which category applies

Three documents drive the answer. The Planning Regulation 2017 sets the state categories of assessment including referral triggers for environmentally relevant activities, heritage places, koala habitat and state transport corridors. The local planning scheme sets the category for each zone and use. The State Planning Policy 2017 sits behind both and binds local schemes.

Open the local planning scheme. Find the zone code applicable to the lot. Find the use. The scheme tells you whether the proposal is accepted, accepted-subject-to-requirements, code-assessable or impact-assessable. For a house on a residential lot the answer is often accepted development if the design meets the dwelling house code and the small lot requirements. Add a secondary dwelling, a height variation or a setback dispensation and the project pushes into code-assessable.

Triggers that push to impact-assessable

A material change of use that conflicts with the zone purpose, development on environmentally significant land, work in a flood hazard area beyond the accepted thresholds, larger subdivisions and operational works that need referral to the State Assessment and Referral Agency (SARA) typically land in impact-assessable. Impact-assessable applications must be publicly notified for at least 15 business days. Properly made submissions create third-party appeal rights to the Planning and Environment Court.

Process for code-assessable and impact-assessable DAs

Lodge through the MyDAS2 portal or the council e-lodgement system. The Development Assessment Rules (DA Rules) set the timing. There is a confirmation period (5 business days), an information request period (up to 10 business days for the council to request more information), the applicant response period and the decision-making period. Code-assessable applications run on a tighter timeline because there is no public notification stage. Impact-assessable applications add the notification period and a submission stage between information response and decision.

A decision notice issues with conditions. Conditions can attach to building work, infrastructure charges, hydraulic design, stormwater management and operational works. The applicant has 20 business days to start a representations process or 20 business days to start an appeal in the Planning and Environment Court.

How this interacts with building work

Planning approval is separate from building approval. Building work in QLD sits under the Building Act 1975 and the Queensland Development Code (QDC). A private building certifier under the Building Act issues the building approval. The Queensland Building and Construction Commission (QBCC) regulates the licensing side. A DA does not authorise building work and a building approval does not cure a missing DA.

Practical sequence

Confirm planning category first by reading the scheme. If accepted, document the compliance check and proceed to building approval. If code or impact-assessable, lodge the DA, work through the conditions, then lodge for building approval. Starting building work without the right planning approval exposes the builder to enforcement notices, show cause notices and potentially a magistrates court prosecution under section 168 of the Planning Act.

Common traps

The biggest trap is treating accepted-development requirements as guidance rather than as binding gates. If a single requirement is missed, the development is no longer accepted and a DA is required retrospectively. The second trap is reading only the zone code and missing an overlay code (heritage, flood hazard, bushfire, character precinct) that applies an extra layer. The third trap is missing the SARA referral trigger on a state-controlled road frontage or near rail infrastructure. The QLD Globe and the planning scheme online mapping show these layers for free and should be checked before the contract is signed.