Original source · versioned page text
2017-06-06 - P&E Agenda Attachment 1 to Item 6 Draft Alignment Amendments Part 1 (Pages 1-907)
Very large file: it may take a few minutes
The original of this document is very large (18.9 MB). Opening the original or downloading it may take a few minutes. Please be patient and don't click again. The page text is quick to read. If you are on mobile data, it is best to wait until you are on Wi-Fi.
Including amendments to 3 July 2017
The Noosa Plan
2.6.4 Determining the requirements for accepted development and assessment
benchmarks and other matters for assessable development
a) Accepted development does not require a development approval and is not subject
to assessment benchmarks. Notwithstanding this, certain requirements may apply
to some types of development for it to be accepted development. Where
nominated in the tables of assessment, accepted development must comply with
the requirements identified as acceptable solutions in the relevant parts of the
applicable code(s) as identified in the relevant column.
b) Accepted development that does not comply with one or more of the nominated
acceptable solutions in the relevant parts of the applicable code(s) becomes code
assessable development unless otherwise specified.
c) The following rules apply in determining assessment benchmarks for each level of
assessment.
d) Code assessable development:
i. is to be assessed against all the assessment benchmarks identified in the
assessment benchmarks column;
ii. that occurs as a result of development becoming code assessable pursuant to
sub-section (b) to this subheading 2.6.4 must:
a. be assessed against the assessment benchmarks for the
development application, limited to the subject matter of the required
acceptable solutions that were not complied with or were not capable
of being complied with under sub-section (b) to this subheading 2.6.4;
b. comply with all required probable solutions identified in sub-section (a)
to this subheading 2.6.4 other than those mentioned in sub-section (b)
to this subheading 2.6.4;
iii. that complies with:
a. the overall outcomes of the code complies with the code; and
b. the probable solutions complies with the overall and specific
outcomes of the code;
iv. is to be assessed against any assessment benchmarks for the development
identified in schedule 11 of the Planning Regulation 2017.
Editor’s note—schedule 11 of the Regulation also identifies the matters that code assessment must
have regard to.
e) Impact assessable development:
i. is to be assessed against the identified assessment benchmarks in the
assessment benchmarks column (where relevant);
ii. assessment is to have regard to the whole of the planning scheme, to the extent
relevant;
iii. is to be assessed against any assessment benchmarks for the development
identified in schedule 12 of the Planning Regulation 2017.
Note—The first row of each table of assessment is to be checked to confirm if there are
assessment benchmarks that commonly apply to general scenarios in the zone, local plan or
overlay.
2-7
See the original
The page text is free to read. Viewing or downloading an original file needs an account.
Log in to see the originalLog in to download the original file
Very large file: the download may take a few minutes. If you are on mobile data, it is best to wait until you are on Wi-Fi.
Searchable page text hides email addresses. Original files are unchanged and may show email addresses.