The Plan contains many technical traps and practical pitfalls for applicants and advisers. The following are concrete “gotchas” grounded in the Plan text and the way the clauses interact.
Maps are operative, not advisory (cl 1.7, cl 2.2). The Plan repeatedly makes maps the operative spatial record. A development’s legality can turn on a symbol or annotation on an adopted map, and maps may be amended. Practitioners must check the current version of every relevant map (Land Zoning, Lot Size, Dwelling Opportunity, Heritage, Natural Resource layers, Sewage Treatment Plant Buffer, Land Reservation Acquisition Map and others) before advising or lodging an application. A map annotation can convert a permissive use into a prohibited one.
Exempt and complying development exclusions and qualifications (cl 3.1-3.3). Even where a State SEPP or this Plan lists a development as exempt or complying, the status may be lost by location in an environmentally sensitive area (cl 3.3), failure to meet BCA requirements, lack of a current fire safety certificate for certain buildings (cl 3.1(4)), or the presence of heritage items (cl 3.1(3)(d)). Blanket assumptions that “it is exempt” can therefore be wrong.
Minimum lot sizes and multiple carve‑outs (cl 4.1 and related clauses). Minimum lot sizes on the Lot Size Map are primary constraints on subdivision. However, the Plan contains multiple exceptions and special‑area clauses (cl 4.1AA, 4.1A, 4.1B, 4.1C, 4.1D, 4.2, 4.2A, 4.2B). Practitioners must map the proposal against the Lot Size Map and check whether a specific exception applies, whether the lot is in a “Dwelling Opportunity” area (cl 4.2A(3)(e)), or whether strata or community title rules alter application (cl 4.1(4) notes strata exceptions). Ignoring these cross‑references is a frequent source of error.
Limits on using the “exceptions to development standards” provision (cl 4.6). Clause 4.6 allows departures from development standards but contains explicit limits: for subdivision in many rural and conservation zones the clause cannot be used where the subdivision will create two or more lots below the minimum or create a lot below 90% of the specified minimum (cl 4.6(6)). The clause also excludes contravening standards for complying development or certain BASIX‑linked standards (cl 4.6(8)). Applicants must prepare the document required under the regulations and the consent authority must keep a record (cl 4.6(3)-(4)).
Suspension of covenants is limited and public rights preserved (cl 1.9A). Clause 1.9A can be misread as a blanket abolition of private covenants that inhibit development. In fact the suspension only operates "to the extent necessary" to enable development under the Plan and excludes covenants imposed by the Council and a list of conservation and Crown instruments (cl 1.9A(1)-(2)). The clause preserves rights and interests of public authorities under registered instruments (cl 1.9A(3)). Sellers and buyers should not assume private covenants are irrelevant.
Heritage consent traps and notification obligations (cl 5.10). Heritage items and conservation areas are extensively listed in Schedule 5. Consent is required for demolition, exterior alteration, works within conservation areas and for disturbance of archaeological sites (cl 5.10(2)). The consent authority may require heritage management documents and might be required to notify the Heritage Council or local Aboriginal communities in certain circumstances (cl 5.10(5)-(9)). Failure to lodge the necessary heritage documentation can delay consent or render a consent vulnerable to challenge.
Aquaculture and intensive livestock location constraints (cl 5.19, cl 5.18 and Schedule 6). The Plan allows some small intensive livestock activities to proceed without consent only if they meet a set of distance and location constraints (cl 5.18(4)-(5)), and pond/tank aquaculture must satisfy detailed site and operational requirements in Schedule 6. A common error is assuming that because a use is permitted in the Land Use Table it will proceed without additional environment‑specific approvals; in many cases mapped overlays or Schedule requirements will still restrict or require consent.
Noise and live music protections for licensed premises (cl 5.20). Clause 5.20 prevents the consent authority from refusing development on licensed premises on the basis of genre, live or amplified status, number of musicians, presence of dance floors or decorations, and requires refusal on noise grounds only if the authority is not satisfied the noise can be managed to an acceptable level (cl 5.20(1)-(2)). That creates particular evidentiary issues for neighbours and consent authorities when assessing licensed premises, and developers should prepare noise management evidence early.
Flood planning requires climate‑aware risk assessment (cl 5.21). The Plan requires the consent authority to consider projected changes as a result of climate change and to use the Considering Flooding guideline and the Flood Risk Management Manual in assessing flood planning matters (cl 5.21(1), (3)-(5)). Applicants should therefore supply flood modelling and evacuation analysis aligned with the referenced guidance.
Development near zone boundaries has a narrow spatial window (cl 5.3). Where a site lies within 20 metres of a zone boundary, the Plan allows the consent authority to permit development that would otherwise only be allowed in the adjoining zone, subject to compatibility tests and explicit exclusions (cl 5.3(2)-(4)). Practitioners should precisely measure distances to boundaries and not assume a wide margin.
Classification and reclassification of public land may discharge trusts (cl 5.2). Schedule 4 lists parcels reclassified as operational or community land and the Plan notes that reclassification under the Plan may discharge trusts where permitted under the Local Government Act, subject to Governor approval for Part 2 items (cl 5.2(5) note). This can affect future use of the land and should be checked by parties acquiring or using public reserves.
In sum, many “gotchas” arise from the Plan’s reliance on maps and schedules, the interaction of local exceptions with State instruments, procedural notification obligations, specific industry thresholds and technical requirements, and the narrow applicability of some exceptions. Practitioners should map the site to every referenced map and read the linked Schedule and clause to avoid surprises.