The Plan organises the local planning framework around a small set of recurring legal and technical concepts. Those concepts are the practical levers by which the Plan shapes private behaviour and public decision‑making.

• Zoning and objectives: Zones are defined (cl 2.1) and each zone has stated objectives that the consent authority must have regard to when determining applications (cl 2.3(2)). The objectives operate as the statutory yardstick for appropriateness. The Land Use Table cross‑references uses to zones and classifies them as either permitted without consent, permitted with consent, or prohibited (cl 2.3; Land Use Table).
• Maps as statutory data: multiple named maps are adopted by reference and may be combined and updated (cl 1.7). The Plan makes map data available via the NSW Planning Portal and sets the map suite as the spatial ground truth for zoning, lot sizes and overlays (cl 2.2; cl 1.7). Users must therefore consult the spatial maps alongside the textual Land Use Table.
• Development consent gates and exemptions: the Plan distinguishes development that requires development consent, exempt development (Schedule 2) and complying development (Schedule 3 and related SEPP) (cl 3.1-3.2). Exempt or complying development is still subject to other statutory approvals and codes, for example the Building Code of Australia and other Acts referenced in the Plan (cl 3.1(3), 3.2(3)).
• Minimum lot sizes and subdivision controls: clause 4.1 provides the primary subdivision rule by reference to the Lot Size Map, with several nuanced subclauses that create exceptions (for example area‑specific minimums in cl 4.1(3A)), special rules for strata and community title schemes (cl 4.1AA, cl 4.2A), and a suite of rural and lot‑averaging exceptions (cl 4.1B, 4.2-4.2G). The Plan therefore regulates housing density primarily through minimum lot sizes rather than, for example, FSR.
• Exceptions to development standards: cl 4.6 provides a local mechanism to allow departures from development standards where compliance is "unreasonable or unnecessary" and there are sufficient planning grounds, but it explicitly excludes certain standards from being varied and limits its application for subdivisions in key rural and conservation zones (cl 4.6(2), (3), (6), (8)).
• Environmental and heritage overlays: a set of overlay clauses require specific considerations and impose positive gates before consent. For biodiversity, groundwater, riparian areas, wetlands and salinity the consent authority must consider specific listed matters and must be satisfied that impacts will be avoided, minimised or mitigated (cl 7.3-7.7). Heritage and Aboriginal places attract both consent requirements and a procedural duty to notify and consult relevant bodies (cl 5.10).
• Sector rules and thresholds: the Plan contains sector‑specific thresholds and locational constraints, for example for intensive livestock agriculture (cl 5.18 sets capacity thresholds and locational exclusions), and aquaculture (cl 5.19 and Schedule 6 set site location and operational requirements and where small scale operations may be permitted without consent). Those rules functionally change the marginal cost of particular agricultural and aquaculture investments.
• Infrastructure sequencing and DCPs: for land identified as an urban release area the Plan requires certification by the Director‑General of satisfactory arrangements for State infrastructure before certain subdivisions (cl 6.1) and prevents consent for development unless a DCP with specific matters is prepared (cl 6.3). This gives infrastructure sequencing statutory teeth in release areas.
• Interaction with State instruments and other Acts: cl 1.9 makes the Plan subject to State environmental planning policies that prevail. The Plan repeatedly references other Acts (for example the Heritage Act, Local Government Act, Crown Land Management Act, Land Acquisition (Just Terms Compensation) Act) and embeds procedural linkages such as notification under those statutes (cl 1.9A; cl 5.1; cl 5.2; cl 5.10).

Those concepts together create a planning architecture that privileges spatial data (maps), uses zoning/objectives as the first filter for permissible activity, employs lot size and specialised overlay tests as control points on density and environmental impact, and routes particular project types through bespoke procedural requirements. The Plan therefore prescribes both substantive standards and decision‑making processes for Council and applicants.

This Plan directly affects a defined set of actors and indirectly affects several others because it changes permissions, duties and approval pathways in municipal territory.

Primary affected parties

• Landowners and prospective purchasers in the Griffith area: the Plan dictates permissible uses for each parcel via the Land Zoning Map and Land Use Table (cl 2.2; cl 2.3). Owners proposing subdivision are affected by minimum lot sizes (cl 4.1) and by many of the Part 7 overlay controls (for biodiversity, riparian land, wetlands, groundwater).
• Developers, builders and project proponents: they must navigate the consent gates for subdivision, demolition, new dwellings, industrial developments and other uses identified in the Land Use Table (cl 2.6; cl 2.7; cl 2.3). Complying development options are available where Schedule 3 and the State SEPP apply (cl 3.2), but BCA and other approvals remain binding (cl 3.2(2)-(3)).
• Council (Griffith City Council): the Council is the designated consent authority under the Plan (cl 1.6). Council is responsible for assessing applications against zone objectives (cl 2.3(2)), for keeping certain records (for example review records under cl 4.6(4)), and for preparing DCPs where required (cl 6.3). Council also has powers over classification and reclassification of public land through Schedule 4 and cl 5.2, with consequential local management effects.
• State agencies and persons with statutory roles: Transport for NSW is identified as the relevant acquiring authority for classified roads (cl 5.1 table). The Director‑General has certification powers for State infrastructure arrangements in urban release areas (cl 6.1(2)). Commonwealth bodies must be consulted where development may penetrate airport obstacle surfaces (cl 7.8). The Heritage Council and local Aboriginal communities have consultation or notification roles for archaeological and Aboriginal heritage matters (cl 5.10(7)-(9)).
• Primary industries, aquaculture and livestock operators: the Plan contains tailored rules that change the approval burden for those activities. Intensive livestock operations are exempt below stated thresholds and subject to locational limits, and consent authorities must consider odour, pollution and industry codes of practice (cl 5.18). Pond, tank and oyster aquaculture are regulated by site and operational requirements in cl 5.19 and Schedule 6.
• Licensed premises and live‑music venues: cl 5.20 prevents consent authorities refusing development for licensed premises on enumerated grounds relating to playing and performing music, and bars refusal on noise grounds only where noise cannot be managed and minimised to an acceptable level.
• Heritage owners and custodians of Aboriginal places: owners of listed heritage items, conservation areas, archaeological sites and Aboriginal heritage places face additional consent triggers, and the Council may require heritage management documents and conservation plans before granting consent (cl 5.10; Sch 5).

Indirectly affected parties

• Neighbouring landowners and the community: overlay provisions require consideration of amenity impacts (for example odour in cl 5.18, riparian/water quality in cl 7.5) and the Plan contains location controls for potentially sensitive uses such as sex services premises (cl 7.11).
• Utility providers and infrastructure funders: the Plan requires that essential services are available or arranged for before consent (cl 7.10; cl 6.2), and DCP and urban release area rules require infrastructure staging and contributions arrangements (cl 6.1-6.3).
• Regulators under other Acts: the Plan defers where other legislative approvals are required (for example Fisheries, Crown land, Native Vegetation instruments excluded from covenant suspension), so agencies administering those Acts will be involved in multi‑agency decision pathways (cl 1.9A; multiple cross references).

The Plan therefore reshapes the incentives and compliance requirements for a wide set of local actors. It places the primary administrative burden on the Council as consent authority and applies specialised assessment and notification duties to proponents in environmentally or culturally sensitive locations.

This Plan frames a set of statutory duties for consent authorities and for applicants, and establishes rights of use and development by reference to zones, the Land Use Table and schedules. Below are the principal duties and rights set out in the instrument.

Duties on the consent authority (Council)

• Have regard to zone objectives: when determining development applications the consent authority must have regard to the objectives of the zone (cl 2.3(2)).
• Apply map‑based controls and gates: the Council must apply lot size limits from the Lot Size Map for subdivision (cl 4.1(3)), and observe overlay triggers on biodiversity, groundwater vulnerability, riparian land and wetlands (cl 7.3-7.6).
• Heritage and Aboriginal obligations: before granting consent for works affecting heritage items, archaeological sites or Aboriginal places Council must consider heritage significance, may require heritage assessment documents or conservation plans and must notify the Heritage Council or local Aboriginal communities where prescribed (cl 5.10(4)-(9)).
• Flood planning assessment: in flood planning areas the consent authority must be satisfied that the development is compatible with flood function and does not increase flood risk, and must consider climate change projection impacts and evacuation capacity (cl 5.21(2)-(3)).
• Recordkeeping: when granting consent that contravenes a development standard, the consent authority must keep a record of the assessment under cl 4.6(4).
• Consultation for airspace matters and airport operations: if a proposal will penetrate Limitation or Operations Surfaces the consent authority must consult the relevant Commonwealth body and accept its advice where it objects (cl 7.8(2)-(4)).

Duties on applicants and developers

• Obtain development consent where required: subdivision, demolition and many other developments require consent (cl 2.6; cl 2.7). Exempt or complying development are set out in Schedule 2 and Schedule 3, but are still subject to other approval requirements (cl 3.1(2)-(3); cl 3.2(2)-(4)).
• Meet technical standards: exempt and complying development must meet the Building Code of Australia deemed‑to‑satisfy provisions or be structurally adequate (cl 3.1(3)(a)). Complying development must also be permissible in the zone (cl 3.2(3)(a)).
• Prepare supporting documents: where relying on cl 4.6 to depart from a development standard, applicants must demonstrate that compliance is unreasonable or unnecessary and provide a statement addressing the matters set out in the regulations under the Act (cl 4.6(3); note re EP&A Regulation).
• Heritage, biodiversity and water assessments: developments in mapped heritage, biodiversity, groundwater vulnerable or riparian areas must provide appropriate assessment material and where required heritage management documents, conservation plans or statements of environmental effects (cl 5.10(5)-(6); cl 7.3(3)-(4); cl 7.4(3)-(4); cl 7.5(3)-(4)).
• Infrastructure and service arrangements: proponents in urban release areas must ensure adequate arrangements for designated State public infrastructure before subdivision and DCP compliance where required (cl 6.1-6.3). For ordinary development, essential services must be available or arranged (cl 7.10).

Rights conferred on landholders and developers

• Permitted uses under zoning: where a use is identified as "permitted without consent" in the Land Use Table and meets any applicable exempt development standards, the use can be carried out without development consent subject to other approvals (cl 2.3; Sch 2).
• Additional permitted uses on specific land: Schedule 1 provides for particular additional permitted uses on specified parcels (for example freight facility at Lot 3 Irrigation Way, cl Sch 1.1).
• Access to exceptions and variations: cl 4.6 provides a statutory pathway to seek consent to contravene a development standard where planning grounds are demonstrated, subject to exclusions and recordkeeping (cl 4.6(2)-(8)).
• Complying development certificate pathway: where development meets the complying development criteria in Schedule 3 and the State SEPP, proponents can seek a complying development certificate as an alternative to development consent (cl 3.2(2)-(4)).

Limits and special procedural features

• Suspension of covenants: cl 1.9A permits suspension of private covenants to the extent they restrict carrying out development under this Plan, subject to explicit exclusions (for example Council‑imposed covenants and certain Crown or conservation instruments) (cl 1.9A(1)-(3)).
• Non‑adoption of certain standards: where the Plan has "Not adopted" entries for height, floor space ratio and calculation rules (cl 4.3-4.5), the absence of a local numerical cap means development assessment must rely on zone objectives, design controls and other applicable instruments rather than a fixed local numerical standard.

These duties and rights design the administrative interaction between applicants and Council, with tiered obligations for sensitive areas and specific sector thresholds. The Plan frequently cross‑references other legislation and State policies, so the rights it confers are conditional on obtaining all other required statutory approvals.

The Plan itself sets permissions, assessment duties and procedural gates, but it does not prescribe monetary penalties or criminal offences within its text. Enforcement and penalties for non‑compliance with development controls therefore arise under the Environmental Planning and Assessment Act 1979 and related legislation rather than within the LEP text. The instrument does, however, create specific compliance and enforcement triggers that will be relevant to any enforcement action taken under the Act.

Key enforcement‑relevant features in the Plan

• Requirement for development consent for specified activities: the Plan establishes that subdivision (cl 2.6) and demolition (cl 2.7) are subject to development consent, and lists uses that are prohibited (Land Use Table). Carrying out development without required consent will be an operational breach that enforcement authorities act on pursuant to the Act.
• Recordkeeping when departing development standards: where cl 4.6 is used to approve a contravention of a development standard, the consent authority must keep a record of the assessment (cl 4.6(4)). That record forms part of the administrative record that would be examined in any challenge or enforcement proceeding.
• Heritage and Aboriginal place procedural protections: cl 5.10 requires the Council to notify the Heritage Council (cl 5.10(7), (9)) and local Aboriginal communities (cl 5.10(8)) in certain cases. Failure to follow prescribed procedural steps can be relevant in judicial review or merits review of a consent decision.
• Overlay compliance conditions: consent authorities must be satisfied about avoidance, minimisation or mitigation of impacts for biodiversity, groundwater, riparian land and wetlands (cl 7.3-7.6). Conditions attached to consents to secure mitigation measures become enforceable consent conditions; non‑compliance with those conditions is enforceable under the Act.
• Infrastructure sequencing: Part 6 prohibits certain subdivisions in urban release areas absent certification that satisfactory infrastructure arrangements exist (cl 6.1). If a subdivision proceeds in contravention, it would be subject to enforcement action under the Act and any relevant land management statutes.
• Industry thresholds and locational exclusions: cl 5.18 establishes thresholds and locational restrictions for intensive livestock agriculture; cl 5.19 and Schedule 6 impose site and operational restrictions for aquaculture. Undertaking such development in contravention of the Plan will attract enforcement attention and potential remedial or penal measures under the Act and relevant environmental protection statutes.

Who enforces

• The designated consent authority (Council) administers the Plan and will be the primary regulator for breaches in its area when a development is undertaken without consent or in contravention of consent conditions (cl 1.6).
• State agencies and the courts exercise enforcement and review powers under the Act and associated statutes. The Plan references those Acts and policies, making clear that compliance obligations are multi‑instrument in practice (see cross‑references throughout, for example cl 1.9 and the various notes linking to other Acts).

Practical note on penalties

• Because the Plan contains no standalone penalty schedule, the quantification of fines, orders for remediation, stop work notices or compulsory acquisition remedies is governed by other legislation cited in the Plan and by the enforcement provisions of the Act. Practitioners should therefore pair any enforcement strategy with the Act and relevant regulations that specify penalties and enforcement procedures.

In short, the Plan creates the compliance obligations and procedural steps that trigger enforcement under broader statutory regimes. The Plan itself provides the substantive controls; the Act provides the enforcement machinery.

The Plan is expressly drafted to interlock with State environmental planning policies and multiple subject‑specific Acts. It both defers to and incorporates procedural and substantive requirements emanating from those laws. The Plan contains explicit cross‑references and express exclusions that define the interaction.

Primary interactions called out in the text

• State environmental planning policies (SEPPs): cl 1.9(1) states that the Plan is subject to any SEPP that prevails as provided by section 3.28 of the Act. The Plan also lists a number of SEPPs as potentially relevant in the Land Use Table preface (for example SEPP (Housing) 2021, SEPP (Transport and Infrastructure) 2021, SEPP (Industry and Employment) 2021). That means where a SEPP applies and is expressed to prevail it will override inconsistent provisions in this LEP.
• Environmental Planning and Assessment Regulation 2021: cl 4.6 references that the Regulation requires an applicant to accompany a development application that proposes to contravene a development standard with a specified document explaining the grounds. The Regulation therefore prescribes procedural materials required where cl 4.6 is engaged.
• Heritage Act 1977 and Heritage Council: cl 5.10 gives effect to the procedural interface with the Heritage Act by requiring notification of the Heritage Council and referencing State heritage listing and interim heritage orders.
• Local Government Act 1993: cl 5.2 links classification and reclassification of public land under this Plan to Part 2 of Chapter 6 of the Local Government Act and notes the Plan’s ability to discharge trusts under section 30 of that Act.
• Land Acquisition (Just Terms Compensation) Act 1991: cl 5.1 adopts the owner‑initiated acquisition provisions and designates which State authority will acquire certain reserved land types, referencing section 3.15 of the Act.
• Crown Land Management Act 2016 and other Crown instruments: cl 1.9A(2) excludes certain Crown instruments from the Plan’s power to suspend covenants. The Plan therefore does not disturb Crown land instruments that are within the meaning of s 13.4 of the Crown Land Management Act.
• Fisheries, Water and Rural Land statutes: cl 5.19 and Schedule 6 cross‑reference the Fisheries Management Act and aquaculture industry development plans. cl 5.17 links to the Water Management Act 2000 for irrigation corporation areas. cl 1.9A excludes property vegetation plans, biobanking agreements, and other instruments under the Native Vegetation Act, Threatened Species Conservation Act and related Acts.
• Rural Fires Act 1997: cl 5.11 confirms that bushfire hazard reduction work authorised by the Rural Fires Act may be undertaken without development consent, acknowledging a direct statutory carve‑out.
• Building Code of Australia and BASIX: cl 3.1(3)(a) requires exempt development to meet the Building Code deemed‑to‑satisfy provisions, and cl 4.6(8)(b) excludes BASIX commitment standards from variation via the exceptions clause.
• Commonwealth aviation regulation: cl 7.8 requires consultation with the relevant Commonwealth body where development would penetrate Limitation or Operations Surfaces for Griffith Airport, thereby connecting local planning controls to Commonwealth aviation safety and airspace laws.

Consequences of these interactions

• Supremacy where applicable: SEPPs and the Act retain precedence where they are expressed to prevail (cl 1.9(1)). Practically, applicants and Council must check both State instruments and this LEP before taking action.
• Multi‑agency approvals: many developments require approvals or licences under other Acts in addition to Plan consent, for example aquaculture licences under Fisheries legislation, water entitlements under the Water Management Act, or approvals for works on Crown land. The Plan repeatedly requires that consent authorities consider whether other authorisations are needed (for example cl 5.17(4)(b)).
• Procedural coordination: the Plan prescribes notification duties (Heritage Council, Aboriginal communities) and consultation (Commonwealth for airspace) that must be factored into the statutory timetable for application processing and can affect viability and timing.
• Limited displacement of private covenants: cl 1.9A grants a limited power to set aside private covenants that conflict with the Plan, but with a defined list of excluded instruments. That alters the legal effect of private encumbrances in some cases but preserves others (for example Council covenants remain effective).

For practice, the Plan is not a stand‑alone instrument: every assessment must be carried out against the Plan and the suite of State and Commonwealth laws it references. The Plan sets the local rules and gates; other Acts supply licences, technical standards and enforcement powers.

The instrument text contains in‑line marginal amendment notes identifying the legislative instruments and years that altered specific clauses. The amendment record presented in the Plan shows iterative changes since the Plan was made. The Plan itself records these amendments at clause level; salient entries in the embedded notes are as follows.

Notable amendments recorded in the text

• 2015 amendments: multiple clauses show amendment annotations to 2015 (for example cl 4.1 amended 2015 (574), Sch 1[6]; the Land Use Table notes include 2015 amendments).
• 2017 and 2018: the Land Use Table and specific clauses record amendments in 2017 (493), and cl 5.4 notes amendments in 2018 (406), inserting or modifying use controls and floor area caps.
• 2019 package of amendments: several clauses carry the annotation Am 2019 (621), Sch 5, including the savings provision cl 1.8A (Am 2019 (621), Sch 5[1]) and suspension of covenants cl 1.9A (Am 2019 (621), Sch 5[2]-[4]). Cl 6.1 also records an amendment 2019 (621), Sch 5[5].
• 2021 changes: some repeals and insertions are noted in 2021; for example cl 7.2 is marked as repealed 2021 (225), Sch 1.
• 2022 updates: cl 2.1 shows amendments 2022 (832), Sch 1.7[1], and cl 4.1AA and several lot size/strata related clauses reference 2022 (832), Sch 1.7[3-5]. Schedule and zone updates also record 2022 changes.
• 2023 adjustments: multiple new clauses and insertions in 2023 (576) appear: cl 2.1 amendment 2023 (576), Sch 1[1]; cl 4.1C inserted 2023 (576), Sch 1[5]; cl 5.5 was substituted 2023 (576), Sch 1[6]; cl 7.13 was inserted 2023 (576), Sch 1[7]; Schedule 5 amended 2023 (576), Sch 1[8].
• 2024: cl 4.1 notes an amendment 2024 (81), Sch 1[1] in the marginal note.

How the Plan records changes

• Clause‑level marginal notes: the Plan shows amendment provenance beside affected clauses with the year and instrument identifier (for example "Am 2019 (621), Sch 5[1]").
• Insertions and repeals: the text indicates where provisions were inserted or repealed, for example cl 1.9A shows "Am 2019 (621), Sch 5[2]-[4]" and cl 7.2 is shown as "Rep 2021 (225), Sch 1".
• Schedules updated: amendments to schedules (Schedules 1, 4, 5 and 6) are similarly footnoted in the Plan.

Practitioner implications

• Dynamic content: because the Plan has a history of frequent amendments across many clauses, practitioners must check the consolidated instrument on the NSW legislation website and the associated maps on the Planning Portal to ensure they work from the current operative text and current maps (cl 1.7 note).
• Clause‑specific changes: several substantive operational rules have been introduced or modified over time, notably around lot size exceptions, aquaculture and rural subdivision. The marginal notes provide a trace for legislative provenance but do not substitute for checking the operative consolidated instrument.

The Plan’s embedded amendment notes are the authoritative internal record of staged changes. For precise drafting history and to identify the current operative wording, consult the consolidated Plan on the legislation website and the associated amendment instruments cited in the marginal notes.

The text of the Plan does not list judicial decisions or administrative appeals. No cases are named in the instrument itself. The Plan therefore contains no recorded litigation history within its text.

Practical observation on likely dispute areas (based on text)

Although the Plan does not report cases, the following provisions are ones that commonly generate disputes in practice and therefore are potential sources of litigation or merits review proceedings under the Act and related statutes:

• Exceptions to development standards (cl 4.6): departures from development standards frequently form the subject matter of merits review, judicial review or merits challenges because they engage discretionary trade‑offs and require a written rationale where standards are contravened. cl 4.6 requires demonstration that compliance is unreasonable or unnecessary and that there are sufficient environmental planning grounds, and requires the consent authority to keep a record (cl 4.6(3)-(4)). Those administrative materials are often central to any challenge.
• Minimum lot sizes and subdivision exceptions (cl 4.1 and related clauses): disputes can arise over whether proposed subdivisions comply with the Lot Size Map and where exceptions (for example lot averaging cl 4.1B, rural subdivision cl 4.2, boundary adjustments cl 4.2G) are lawfully applied. Disagreements over interpretation of "existing holding" (cl 4.2C(5)) and calculation of areas for split zones (cl 4.1C) can provoke review.
• Heritage and Aboriginal site decisions (cl 5.10): consents for demolition, alterations or subdivision affecting heritage items and Aboriginal places require procedural steps including notices to the Heritage Council and local Aboriginal communities. Procedural failures or contested assessments of heritage significance are common grounds for objections and legal challenges.
• Environmental overlay decisions (cl 7.3-7.6): decisions in mapped biodiversity, riparian and groundwater vulnerable areas require detailed environmental assessments and explicit consideration of avoidance, minimisation and mitigation measures. The Plan instructs consent authorities to be satisfied about these matters; disputes commonly allege inadequate assessment or insufficient mitigation.
• Flood planning and climate change considerations (cl 5.21): the Plan requires consent authorities to consider projected changes due to climate change when assessing flood impacts. Disputes can centre on the adequacy of the flood risk assessment and the interpretation of "compatible with flood function and behaviour" and evacuation capacity.
• Aquaculture and intensive livestock thresholds and locational rules (cl 5.18, cl 5.19, Sch 6): technical disputes about whether a proposed operation falls within exempt thresholds, whether locational exclusions apply, or about adequacy of management plans, can trigger regulatory review and objections.

Process‑level notes relevant to litigation risk

• Procedural compliance matters: several Plan provisions mandate pre‑application notifications and the right to comment for external bodies (Heritage Council, local Aboriginal communities, Commonwealth aviation bodies). Failure to follow these procedures can be a legal weakness in a consent decision.
• Multi‑instrument decision making: because the Plan cross‑references other SEPPs and Acts that may prevail (cl 1.9), litigation may involve multi‑instrument arguments about which instrument governs a particular component of a proposal.

Because the Plan contains no internal case law record, parties seeking to understand precedent should examine decisions under the Act and relevant administrative tribunals or courts, focusing on the issues highlighted by the Plan’s high‑risk clauses.

This Plan contains several provisions and drafting features that can create traps for practitioners and proponents if not checked carefully. The following items are practical "gotchas" sourced directly from the Plan.

Maps and combined map layers: the Plan relies on multiple named maps and permits maps to be combined into a single map (cl 1.7(1)-(2)). Practitioners must check the current consolidated map set on the Planning Portal rather than relying on a single paper map, because combined mapping may obscure overlay extents that trigger obligations such as heritage or biodiversity assessments.

Savings for pre‑commencement DAs: cl 1.8A ensures that development applications lodged before the Plan commenced and not finally determined are to be determined as if the Plan had not commenced. That can produce counterintuitive outcomes: an application submitted earlier may escape new constraints in the LEP while new applicants are subject to them (cl 1.8A). Check lodgement dates carefully.

Suspension of private covenants with enumerated exclusions: cl 1.9A allows the Plan to set aside private covenants to the extent necessary to permit development under the Plan but expressly excludes Council‑imposed covenants and a range of Crown and conservation agreements (cl 1.9A(2)). Do not assume that a private covenant is nullified; verify whether the covenant is one of the excluded classes.

Exceptions to standards are limited for subdivisions: cl 4.6 allows contravention of development standards in some circumstances but explicitly prevents the clause being used to permit subdivisions that would create two or more lots below minimum areas in specified zones or create a lot less than 90 per cent of a minimum area (cl 4.6(6)). Practitioners cannot rely on cl 4.6 to permit substantial under‑sizing in key rural and conservation zones.

"Not adopted" height and FSR: clauses 4.3-4.5 record "Not adopted". This means there are no local numeric height and floor space ratio controls in the Plan. Do not assume that an absence of numeric limits gives free rein; Council will assess against zone objectives (cl 2.3(2)), design controls, DCPs and any relevant State policy. Also check if other instruments (SEPP, DCP) impose numeric limits.

Complying development does not remove other approvals: cl 3.2 requires complying development to meet the Building Code and any Council approvals for on‑site effluent where needed. Even where complying development certificates are available, other licences or approvals (for example environmental licences) may still be required (cl 3.2(3)).

Heritage procedural traps: cl 5.10(3) and (7)-(9) set out when consent is required and when the Heritage Council or local Aboriginal communities must be notified. Failure to notify where required, or to provide a heritage management document or conservation plan when demanded by Council, can lead to procedural challenges.

Part 6 urban release sequencing: in urban release areas, subdivision creating lots smaller than previously permitted is not allowed unless the Director‑General certifies satisfactory arrangements for designated State public infrastructure (cl 6.1(2)). Practitioners must anticipate an extra certification step for such subdivisions and the possibility of a certificate condition precedent.

Aquaculture and intensive livestock locational exclusions and thresholds: cl 5.18(4) sets explicit locational exclusions for exempt intensive livestock activities (for example not in environmentally sensitive areas, within specified distances of dwellings, or within a set distance of other farms). Similarly, cl 5.19 and Schedule 6 impose operational requirements and conservation exclusion zones. Mistakes in measuring distances, or misclassifying the area as environmentally sensitive, can invalidate an exemption claim.

Music protections for licensed premises: cl 5.20 prevents consent authorities from refusing licensed premises on enumerated grounds relating to music and limits refusal on noise grounds only if the consent authority is satisfied the noise cannot be managed to an acceptable level. Neighbours opposing a venue on the basis of music should consider that the Plan constrains refusal grounds.

Development near zone boundaries: cl 5.3 allows uses permitted in an adjoining zone to be granted within 20 metres of a boundary in certain circumstances, but it explicitly excludes several sensitive zones (cl 5.3(3)). Misreading the excluded zones can lead to incorrect assumptions about cross‑zonal rights.

Essential services requirement: cl 7.10 requires proof of availability or arrangements for essential services. This is a non‑technical but critical gate: a consent may be refused where proponents cannot demonstrate water, electricity, sewage and access arrangements.

Special local land clauses: the Plan contains site‑specific rules and DCP prerequisites for parcels (for example Sch 1 additional permitted uses, cl 7.12 Nericon, cl 7.13 Crossing Street release). Always check schedules and Part 7 provisions for parcel‑level requirements.

In practice, the safe approach is to begin any project by checking the current maps, identifying overlay triggers, confirming whether a consent or a complying certificate is needed, and reviewing any parcel‑specific schedule entries. Don’t assume that an absence of a numeric standard means an absence of constraint.

Practical step‑by‑step approach to assessing and securing development under this Plan, grounded in the Plan’s clauses and schedules.

1. Confirm spatial status and zoning

   • Consult the Land Zoning Map, Lot Size Map, Heritage Map, Terrestrial Biodiversity Map, Riparian Lands and Watercourses Map, Groundwater Vulnerability Map, Wetlands Map and any other relevant named maps maintained on the NSW Planning Portal (cl 1.7; cl 2.2). These maps determine permissible uses, minimum lot sizes and overlay triggers.

2. Identify use permissibility and pathway

   • Use the Land Use Table and Schedule 1 to determine whether the proposed use is permitted without consent, permitted with consent, or prohibited in the zone (cl 2.3; Sch 1). If the use sits in "permitted without consent" and meets Schedule 2 specifications it may be exempt development (cl 3.1). If it matches Schedule 3 criteria and complies with the required standards it may be complying development (cl 3.2).

3. Check lot size and subdivision rules

   • For any proposed subdivision, calculate resulting lot areas against the Lot Size Map and the specific rules in cl 4.1 and related clauses (cl 4.1, 4.1A, 4.1B, 4.1C). If parcels straddle zones, apply cl 4.1C (split zones). For strata or community title schemes consult cl 4.1AA and 4.2A.

4. Identify overlay triggers and required assessments

   • If the land is mapped for biodiversity, groundwater vulnerability, riparian land, wetlands or is in a flood planning area, compile the specific assessment material set out in those clauses. For biodiversity (cl 7.3) and riparian land (cl 7.5) ensure the proposal proves avoidance, minimisation or mitigation and prepares relevant studies. For flood planning (cl 5.21) incorporate climate projections, evacuation and design measures in the EIS or statement of environmental effects.

5. Heritage and Aboriginal places

   • If the site is a heritage item, within a conservation area, an archaeological site or an Aboriginal place, prepare heritage management documents or conservation plans if required (cl 5.10(5)-(6)). Notify the Heritage Council or local Aboriginal communities where the clause prescribes (cl 5.10(7)-(9)) and consider obtaining pre‑application advice.

6. Sector‑specific compliance

   • For intensive livestock agriculture, check capacity thresholds and locational exclusions in cl 5.18 and prepare odour, effluent and management plans where consent is required. For aquaculture, apply the site location and operational requirements in cl 5.19 and Schedule 6; ensure species are consistent with industry development plans (cl 5.19(2)(a) and Sch 6 Div 2).

7. Use exceptions and variations carefully

   • If a development standard cannot be met, and if cl 4.6 is available, prepare the required justification demonstrating compliance with cl 4.6(3) and any documentation required by the EP&A Regulation. Remember cl 4.6 excludes certain standards and limits variation for subdivisions in specified zones (cl 4.6(6), (8)).

8. Infrastructure, DCPs and urban release areas

   • If the land is within an urban release area consult cl 6.1-6.3: ensure the Director‑General has certified satisfactory arrangements for designated State public infrastructure where necessary (cl 6.1(2)), and confirm if a development control plan has been prepared that covers staging, transport, landscaping, stormwater, hazards and urban design (cl 6.3(2)-(3)). Council will not grant consent in the absence of a required DCP.

9. Procedural and external approvals

   • Confirm other statutory approvals required under other Acts identified by the Plan (for example fisheries licences, water entitlements, Crown land approvals). The Plan frequently requires the consent authority to consider whether a licence or approval under other legislation is required (for example cl 5.17(4)(b)). Factor these into the project timeline.

10. Consult and document

    • Engage early with Council as consent authority (cl 1.6) and with any external agencies identified by the Plan (Heritage Council, relevant Commonwealth aviation body, Transport for NSW, Director‑General for infrastructure certification). Prepare environmental impact statements, heritage management documents and technical reports as needed. Keep records of consultations and all supporting documents; cl 4.6(4) requires the consent authority to keep records where standards are varied.

11. Consider exempt and complying development pathways

    • Where development is specified in Schedule 2 or Part 1 of Schedule 3 and meets the relevant standards, consider the exempt or complying development pathway (cl 3.1-3.2). Remember that complying development requires satisfaction of BCA provisions and any local Council conditions for on‑site effluent systems on unsewered land (cl 3.2(3)).

12. Special procedural obligations

    • For proposals that may penetrate airport surfaces consult the relevant Commonwealth body early (cl 7.8). For licensed premises relying on live music, be aware of the protections in cl 5.20 and prepare a noise management plan showing how noise will be managed and minimised.

13. Verify covenant status

    • Before relying on cl 1.9A to argue a private covenant is displaced, confirm whether the covenant is excluded (Council covenants, Crown instruments and other listed instruments under cl 1.9A(2)). If the covenant is excluded it remains effective even if inconsistent with the Plan.

14. Prepare for conditions and enforcement

    • Expect Council to impose conditions that secure mitigation measures for biodiversity, water quality, heritage conservation, flood resilience and infrastructure delivery. These conditions will be enforceable under the Act; ensure the operation plan and compliance arrangements are prepared to meet them.

15. Final checks and certifications

    • Prior to lodgement, ensure all required technical reports, BCA/BASIX commitments (where applicable) and any other statutory statements are assembled. If seeking to contravene a development standard, include the required variation justification document mandated by the EP&A Regulation.

Following these steps aligns a project with the Plan’s spatial controls, the statutory consent gates and the overlay‑specific assessment matters. Always confirm the current consolidated text and maps on the NSW legislation website and the Planning Portal because the Plan records multiple amendments and map updates (cl 1.7 notes and amendment marginalia).