Map dependency and interpretation risk. The Plan’s operative rules are heavily map-dependent (cl 1.7, cl 2.2 and repeated references across Part 4 and Part 6). Small differences in map annotation (for example whether a parcel is shown as "Riparian land", on a Height of Buildings Map entry, or in the "MIA Irrigation Area") will determine applicable controls. Misreading the maps or relying on an outdated map version can produce an incorrect assessment of permitted land uses, minimum lot sizes or overlay constraints.
Exempt and complying development exclusions for sensitive areas. Clauses 3.1-3.3 limit the use of exempt and complying development in environmentally sensitive areas. Even where a development appears to meet Schedule 2 or 3 standards, if it lies within a mapped sensitive area (cl 3.3 lists a non-exhaustive set), the exempt or complying pathway is unavailable. Reading Schedule 2/3 without cross-checking the environmental overlays is a common error.
Covenant suspension is partial and exception-laden. Clause 1.9A gives the Plan the power to suspend private covenants, agreements and similar instruments to the extent necessary to enable development under the Plan. However, cl 1.9A(2) lists key exclusions (for example covenants imposed by Council, relevant instruments under the Crown Land Management Act 2016, conservation agreements, certain biobanking agreements, and planning agreements under Division 7.1). Practitioners should not assume all covenants can be overridden; the suspension is expressly limited and does not affect public authority rights under registered instruments (cl 1.9A(3)).
Savings rule for development applications. Clause 1.8A requires that DAs made before the Plan’s commencement and not finally determined must be determined as if the Plan had not commenced. That can be important for applicants who relied on the previous instrument; failing to recognise this can lead to an incorrect choice of application pathway, or misadvice about applicable standards or thresholds.
Contraventions pathway requires evidence and records. Use of the exceptions mechanism in cl 4.6 requires the applicant to demonstrate that compliance with a development standard is unreasonable or unnecessary and to provide environmental planning grounds; the consent authority must record its assessment (cl 4.6(3)-(4)). Practitioners should be alert to the evidentiary expectations (and the regulation-cited requirement for an accompanying document) or risk having an application refused as inadequately justified.
Heritage procedural obligations are mandatory and specific. For development affecting an archaeological site, the consent authority must notify the Heritage Council and consider any response within 28 days (cl 5.10(7)). For nominated State heritage items proposed for demolition, the same notification and consideration duty applies (cl 5.10(9)). For Aboriginal places, the consent authority must conduct adequate investigation and notify local Aboriginal communities (cl 5.10(8)). Failure to follow these procedures is a concrete legal vulnerability; consent granted in the absence of required consultation can be subject to challenge.
Essential services precondition. Clause 6.12 is a blunt precondition: consent must not be granted unless the consent authority is satisfied essential services (water, electricity, sewage disposal, stormwater, vehicle access) are available or arrangements are in place. This is a non-technical “no services, no consent” rule in practice and is frequently a gating issue for rural subdivisions, tourist accommodation and dwellings.
Flood planning and canal estate prohibition. The Plan's flood planning clause places substantive obligations on the consent authority to ensure development is compatible with flood function, does not increase flood affectation and supports safe evacuation (cl 5.21). Clause 2.9 prohibits canal estate development, and its definition links to flood planning areas. Proposals that try to raise land to meet flood criteria for residential development are caught by the canal estate definition if they involve fill or excavation to create waterway features (cl 2.9). Practitioners proposing works in flood-prone areas must provide flood modelling and consider climate-change projections as the clause requires consideration of projected changes (cl 5.21(3)(a)).
Overlap with State licences and approvals. Several Plan clauses require the consent authority to consider whether licences or approvals are required under other Acts (for example cl 5.17(4)(b)). A planning consent does not replace licensing under other regimes (water, fisheries, environment), and applicants must secure those licences separately. Confusing planning consent with regulatory approvals is a frequent practical pitfall.
Music/noise protection is conditional. Clause 5.20 prevents refusal of licensed-premises development purely on certain music-related grounds, and requires the consent authority not to refuse for noise grounds “if the consent authority is satisfied the noise may be managed and minimised to an acceptable level” (cl 5.20(2)). That means applicants still must demonstrate noise-management measures; the clause is not an absolute right to operate without regard to noise impacts.
Strata and community title nuance. Clauses 4.1(4) and 4.1AA(4)-(4) exclude certain subdivisions (strata and Community Land Development subdivisions) from minimum lot size rules, but Clause 4.2A imposes minimum lot size rules for strata plan schemes in certain rural/conservation zones. Practitioners must read those clauses together and check the exact land and development type for applicable exemptions or constraints.
Local specifics on river and Murrumbidgee matters. Clauses 6.7-6.8 contain bespoke definitions and numeric setbacks for the Murrumbidgee River and set limits (for example 40 metres in RU1; 100 metres in SP2) and constraints on moorings and structure placement. Those are tailored, non-generic rules , check them when development is adjacent to the river.
Registration of covenants as a consent condition. Clause 4.5(9) enables a condition of consent to require the registration of a covenant preventing the creation of floor area that would only arise because the site included an additional lot. That tool can be used to prevent double counting of floor space across consolidated sites; practitioners should look for such conditions.
Summary: the most common practical pitfalls are failing to consult the mapped overlays, misreading the scope of clause 1.9A covenant suspension, overlooking heritage and Aboriginal consultation obligations, underestimating essential services pre-conditions, and conflating planning consent with other statutory licences.