Development application types

The Sustainable Planning Act 2009 identifies a number of ways planning applications may be assessed. The way an application will be assessed will depend on the development being undertaken and the development site details. The following outlines ways in which an application may be assessed under Brisbane City Plan 2014.

To find out more for your project, you need to obtain key facts about your site such as area, zoning, neighbourhood plan and overlays.

You can find out this information by using one of Brisbane City Council's online tools:

Compliance assessment

A compliance assessable development application fits within the compliance outcome rules set out in the codes of the City Plan for compliance assessment. It can be assessed relatively quickly and does not require public notification.

Code assessment

A code development application is assessed against the codes identified for the use within City Plan. These codes can include use codes, prescribed secondary codes, overlay codes and neighbourhood plan codes. This type of application can be assessed relatively quickly and does not require public notification. Where a self-assessable development does not meet one or more of the acceptable outcomes of the relevant code, a code application is triggered. The application will only need to address the aspects of development that do not meet the self-assessable requirements.

Impact assessment

An impact assessable development application is for development that must be assessed against all identified codes and City Plan as a whole to the extent relevant. This is to ensure that identified development impacts are addressed. These applications must be publicly notified to take into account the community's views.

Council condition compliance assessment

Council condition compliance assessment is a development assessment process for checking that the proposed development complies with any conditions of a development approval. This usually entails the applicant to submit drawings and/or documents for Council approval.

 

29 June 2014