The Plan rests on a few organising legal and planning concepts that determine how it will be applied.

• Zoning and the Land Use Table (Pt 2, cl 2.1-2.3 and Land Use Table). The Plan is a rules‑based zoning instrument. Each parcel is placed in a zone (Land Zoning Map, cl 2.2) and the Land Use Table lists per zone what is exempt, permitted with consent and prohibited. The consent authority must “have regard to the objectives for development in a zone” when determining an application (cl 2.3(2)). That creates a statutory framing: permitted uses are not the only criterion, the zone objectives guide compatibility assessments.

• Development consent as gatekeeper. Many activities expressly require development consent (for example, subdivision cl 2.6, demolition cl 2.7, works in acid sulfate soils cl 7.1(2), heritage actions cl 5.10(2), development below mean high water mark cl 5.7(2)). Conversely, the Plan identifies exempt development (Schedule 2) and complying development (Schedule 3 and cl 3.1-3.2). Whether a proposal is exempt, complying or requires consent determines the procedural pathway, the level of assessment and the ability to impose conditions.

• Spatially‑fixed standards via maps. Minimum lot sizes (cl 4.1 and related clauses) and other numerical standards (height of buildings cl 4.3, floor space ratio cl 4.4) are set on maps (Lot Size Map, Height of Buildings Map, Floor Space Ratio Map). This relies on accurate map reading by proponents and regulators; the maps may be amended and combined under cl 1.7.

• Exceptions and flexibility. The Plan provides mechanisms for flexibility: clause 4.6 allows development consent to be granted even though a development would contravene a development standard, provided the applicant demonstrates compliance is unreasonable or unnecessary and there are sufficient environmental planning grounds (cl 4.6(2)-(3)). That flexibility is constrained in rural and conservation zones for subdivisions (cl 4.6(6)) and some standards are expressly non‑delegable to this clause (cl 4.6(8)).

• Localised calibrations and site‑specific permissions. Schedule 1 contains land‑specific additional permitted uses (for example, limited industrial or commercial uses on specific lots). Part 7 contains many local provisions (e.g. Horizons at Salamander Way cl 7.16, Paul’s Corner cl 7.20, active street frontage controls cl 7.22) that tailor the general rules to local planning objectives.

• Environmental and hazard filters. The Plan limits the reach of exempt and complying development in environmentally sensitive areas (cl 3.3). It embeds specific hazard screens and decision triggers for acid sulfate soils (cl 7.1), flood planning and special flood considerations (cl 5.21 and cl 5.22), bush fire hazard reduction (cl 5.11), wetlands (cl 7.9), drinking water catchments (cl 7.8) and aircraft noise/airspace considerations (cl 7.4-7.5).

• Heritage layering. Schedule 5 lists heritage items and conservation areas; where a heritage item or Aboriginal place is involved, development consent will often be required (cl 5.10(2)) and the consent authority may require a heritage management document or plan (cl 5.10(5)-(6)). Statutory notice/consultation obligations apply for archaeological sites and nominated State heritage items (cl 5.10(7), (9)).

• Interface with other public interests. The Plan imposes procedural controls where State or Commonwealth agencies have interests: Transport for NSW sign‑off for Pacific Highway access (cl 6.5), consultation with “the relevant Commonwealth body” where an obstacle surface for RAAF Base Williamtown is penetrated (cl 7.4), and references to State SEPPs that prevail where applicable (cl 1.9).

These concepts together structure who can do what, where and on what conditions in Port Stephens. They allocate decision rights to the Council while reserving certain technical matters (heritage, flood risk, airspace) for specialist input or standards.

The Plan’s regulated population is defined geographically and functionally.

• Landowners and developers in the Port Stephens planning area (cl 1.3). Every person proposing to carry out works, change the use of land, subdivide or demolish on the mapped land must use the Plan to determine whether consent is needed, what standards apply and what uses are permitted (Land Zoning Map cl 2.2; Schedule maps referenced across the Plan).

• The Council. The Plan names the Council as the consent authority (cl 1.6) and gives it many statutory duties: to determine applications, keep records (for example, cl 4.6(4) requires a consent authority to keep a record of assessments under the exceptions clause), to require heritage or environmental documents (cl 5.10(5)-(6)) and to certify public land classification changes (cl 5.2 and Schedule 4).

• State agencies and utilities. Multiple clauses allocate state agency roles: Transport for NSW must be satisfied on Pacific Highway access (cl 6.5); the corporation constituted under s 2.5 of the Act is the acquiring authority for some regional open space (cl 5.1(2) table); the Department of Primary Industries and Planning Secretary produce guidelines affecting intensive livestock and aquaculture (cl 5.18(3)(h), cl 5.19(7)). For Crown infrastructure the Plan does not impede works consistent with State SEPP (cl 5.12).

• Commonwealth interest holders. The Plan requires consultation with the “relevant Commonwealth body” (defined by Commonwealth legislation) where development would penetrate the Limitation or Operations Surface for RAAF Base Williamtown Airport (cl 7.4). This directly affects proponents near the airport and yields a de facto veto where the Commonwealth body objects (cl 7.4(4)).

• Aboriginal communities and heritage stakeholders. The Plan requires notification and consideration of responses in relation to Aboriginal places of heritage significance (cl 5.10(8)). Archaeological sites and State heritage items trigger statutory notice obligations to the Heritage Council (cl 5.10(7), (9)).

• Neighbouring landowners and the public. Many controls are explicitly protective of neighbours or the public: temporary uses must not adversely impact adjoining land and must be restored (cl 2.8(3), Schedule 2 temporary use); intensive livestock agriculture has separation and environmental safeguards (cl 5.18(4)-(5)); music‑related refusals are constrained for licensed premises but subject to noise management (cl 5.20).

• Specific industries and local businesses. The Plan contains industry‑specific rules that affect operating models: oyster and aquaculture operators (cl 5.19 and Schedule 6) have minimum site and operational requirements; intensive livestock operations face both assessment criteria and thresholds for development without consent (cl 5.18); retail and supermarket size caps are imposed in certain zones and sites (cl 5.4(7AA), cl 7.14, cl 7.20, cl 7.24).

• Owners/occupiers of mapped or scheduled land. Owners of parcels listed in Schedule 1 (additional permitted uses), Schedule 4 (public land reclassification), and Schedule 5 (heritage items) face bespoke provisions and consent requirements that differ from ordinary zoned land.

In short, the Plan affects all parties proposing to alter land use or physical form in the Port Stephens area; it particularises the obligations of the Council as consent authority, brings State and Commonwealth agencies into decisionmaking where their statutory interests intersect, and gives special status and constraints to identified heritage, environmental and infrastructure parcels.

The Plan establishes duties for the consent authority, rights (or limits) for landowners and obligations for applicants. Key duties and rights, with clause references, include:

• Duty of the consent authority to have regard to zone objectives. When determining applications the consent authority must consider the objectives for development in the relevant zone (cl 2.3(2)). This places an evaluative duty beyond strict use permissibility.

• Right to development where permitted. If a use is permitted in the Land Use Table in a zone, it may proceed subject to satisfying applicable standards and obtaining consent where the Table requires it (cl 2.3(1)-(3)). Schedule 1 grants site‑specific additional permissions (cl 2.5).

• Duty to apply consent pathways correctly. Applicants and the consent authority must identify whether a proposal is exempt (cl 3.1 and Schedule 2), complying (cl 3.2 and Schedule 3), or requires development consent. Exempt/comprising development is expressly barred in environmentally sensitive areas (cl 3.3).

• Duty to refuse consent where standards cannot be met. For flood planning, the consent authority must not grant consent unless satisfied the development is compatible with flood function and will not increase risk to life or adversely affect flood behaviour or the environment (cl 5.21(2)). Similar tests apply for special flood considerations (cl 5.22).

• Duty to require heritage assessments or management plans. Where development affects a heritage item or area, the consent authority may require a heritage management document or heritage conservation management plan before granting consent (cl 5.10(5)-(6)). It must notify the Heritage Council for archaeological site applications and consider any response (cl 5.10(7)).

• Duty to consult for airspace penetrations. If a proposed development will penetrate the Limitation or Operations Surface for RAAF Base Williamtown, the consent authority must consult the relevant Commonwealth body before granting consent and cannot grant consent where that body advises it should not be carried out (cl 7.4(2)-(4)).

• Conditional discretionary powers on exceptions to standards. The consent authority may grant consent to contravene a development standard if the applicant demonstrates compliance is unreasonable or unnecessary and there are sufficient planning grounds (cl 4.6(2)-(3)). The authority must keep a record of that assessment (cl 4.6(4)). However, clause 4.6(6) prevents consent in rural/conservation zones if subdivision would produce multiple undersized lots.

• Duty to ensure service availability for urban release. Development consent in an urban release area must not be granted unless the Council is satisfied essential public utility infrastructure is available, or adequate arrangements are in place to make it available when required (cl 6.2).

• Right to temporary uses subject to constraints. The Plan allows temporary uses for up to 52 days in any 12‑month period where consent is granted and certain tests are satisfied (cl 2.8). Schedule 2 creates an exempt category for temporary use of Council land, schools and places of worship subject to similar constraints.

• Duty to comply with specific limits on types of permissible activities. The Plan prescribes numerical and location limits for particular uses (e.g. bed and breakfast max 4 bedrooms cl 5.4(1); industrial retail floor area limits cl 5.4(4); secondary dwelling size limits cl 5.4(9), cl 5.5). Consent cannot be granted in breach of those limits unless otherwise allowed by the Plan.

• Duty to make and maintain maps available. Clause 1.7(3) requires maps be kept and made available for public access in accordance with Minister‑approved arrangements; notes say maps are available on the NSW Planning Portal.

These duties structure procedural obligations on planning officers and legal obligations on applicants. Rights are primarily permissive: where the Plan permits a use (including site‑specific permissions), applicants have the right to seek consent and may rely on complying/exempt pathways where the Plan deems applicable.

The Plan itself is an environmental planning instrument; it does not set out an independent schedule of criminal or civil fines. Instead, enforcement flows from the Act and the development control framework that this Plan operates within. The document provides the following enforcement‑relevant mechanics:

• Consent requirement as regulatory trigger. The Plan converts many activities into development that either is exempt, complying or requires development consent. The need for consent is the principal regulatory lever: carrying out development that requires consent without consent exposes a landowner to enforcement action under the Act and its regulations (see cl 2.6, 2.7, 5.7, 5.10(2), 7.1(2), 7.2(2), and many others). The Plan does not itself specify the sanctions; enforcement and penalties for unauthorised development are provided under the Act and associated regulations.

• Conditions and approval pathways. Where development is permitted only with consent, the consent authority may grant, refuse or grant consent subject to conditions. Those conditions become enforceable as part of the development consent. The Plan provides specific mandatory condition types and constraints (for example, complying development certificates are subject to the conditions in Part 2 of Schedule 3 and the general conditions in Schedule 6 of the State SEPP referred to in sch.3-sec).

• Consultation and referral obligations as a gating mechanism. For certain classes of development the consent authority must consult or notify a third party and consider their response before granting consent: Heritage Council for archaeological sites and nominated State heritage item demolitions (cl 5.10(7), (9)); relevant Commonwealth body for airspace penetrations (cl 7.4(2)-(4)); Transport for NSW for Pacific Highway access (cl 6.5). A refusal may follow the agency response. These referral steps are enforcement in practice because they can prevent consent.

• Record keeping and administrative obligations. Clause 4.6(4) requires the consent authority to keep a record of its assessment when using the exceptions to standards power. The Plan contains several other procedural duties (notification periods in cl 5.10(7) and (9), time limits for applicant action under cl 5.9) which, if not complied with, could be reviewable or give rise to administrative error.

• Heritage, environmental and hazard pre‑conditions. The Plan prohibits exempt/compliant pathways in environmentally sensitive areas (cl 3.3) and requires acid sulfate soils management plans before consent is given (cl 7.1(3)). Failing to provide these prescribed pre‑conditions would prevent lawful development and could give rise to enforcement and refusal.

• No express penalty schedule in the Plan. The instrument does not itself set fines, infringement notices or criminal offences. Sanctions for breaches sit with the Act. Where the practitioner needs exact penalty provisions, the Act and the regulations should be consulted because this Plan operates as a spatial and procedural code that feeds into the Act’s enforcement machinery (see cl 1.9(1) noting the Plan is subject to State SEPPs and the Act).

In practice, enforcement will proceed through refusal of retrospective consent, orders to rectify or remove unauthorised development, and monetary penalties under the Act. The Plan’s main enforcement effect is to define the permitted/consent/exempt boundaries and procedural steps that, if breached, trigger the Act’s enforcement remedies.

The Plan is expressly framed to operate within a network of State and Commonwealth laws and policies. Key interactions set out in the text include:

• The Plan is subject to State environmental planning policies. Clause 1.9(1) provides that the Plan is subject to any State environmental planning policy that prevails over it under s 3.28 of the Act. The Land Use Table and notes reference a number of State SEPPs as relevant (for example, SEPP (Housing) 2021, SEPP (Transport and Infrastructure) 2021 and others in the Land Use Table note). Practically, where a SEPP applies and prevails, its requirements displace inconsistent local provisions.

• The Plan cross‑references the Act and environment/heritage statutes. Many operational duties are qualified with references to the Act and other legislation, for example: cl 1.6 making the consent authority subject to the Act; heritage provisions referencing the Heritage Act 1977 (cl 5.10); aquaculture references to the Fisheries Management Act 1994 and aquaculture industry development plans (cl 5.19); acid sulfate soil measures referencing the Acid Sulfate Soils Manual (cl 7.1).

• Local Government Act interactions for public land classification. Clause 5.2 operates to classify/reclassify public land for the purposes of the Local Government Act 1993 and notes section 30 of that Act allows the Plan to discharge trusts when land is reclassified (cl 5.2 note and Schedule 4).

• Commonwealth aviation/defence law overlay. Clause 7.4 requires the consent authority to consult and act on advice from the relevant Commonwealth body responsible for approvals that affect airport obstacle limitation surfaces. Where the Commonwealth body objects because an obstacle surface would be penetrated, the consent authority “must not” grant consent (cl 7.4(4)). That creates a cross‑jurisdictional veto arising from Commonwealth aviation/defence law.

• Building Code and BASIX. The Plan requires exempt or complying development to meet the Building Code of Australia (BCA) and not result in contraventions of the BCA (cl 3.1(3)(a)-(b)). Clause 4.6(8) prevents the exceptions process being used to override development standards arising from BASIX commitments.

• Environmental and natural resources statutes. The Plan expressly disapplies suspension of covenants for certain instruments and public authority rights (cl 1.9A(2)-(3)). It cross‑references the Crown Land Management Act 2016 and National Parks and Wildlife Act 1974 in the same clause. Aquatic or marine reserve designations under the Marine Estate Management Act 2014 are treated as exclusion zones in Schedule 6 (cl 1 and cl 3) and cl 5.19 invokes Fisheries Management Act material and industry plans.

• State SEPPs dealing with exempt and complying development. The Plan’s Schedules 2 and 3 are additional to the State‑wide SEPP (Exempt and Complying Development Codes) 2008. The Plan notes that the State SEPP continues to specify exempt/comprising development and this Plan contains additional items (Schedule 2 and 3 notes).

• Flood, climate and guideline materials. Clauses 5.21 and 5.22 adopt external technical guidance into assessment: they require the consent authority to consider “Considering Flooding in Land Use Planning Guideline” (cl 5.21(5)) and the Flood Risk Management Manual ISBN referenced (cl 5.21(5)). The Plan thus imports State technical guidance into local consent tests.

• Industry codes and Departmental guidance. For intensive livestock and aquaculture the consent authority must consider industry codes and Departmental guidance (cl 5.18(3)(g)-(h); cl 5.19(2)(a) and (5)). These are not given force of law by the Plan, but the Plan makes them mandatory assessment matters.

Overall, the Plan is interleaved with State legislation, State SEPPs, Commonwealth aviation/defence requirements, industry codes, technical manuals and local government law. Where inconsistency exists the higher‑order instrument (State SEPP or Act or Commonwealth law) will prevail, and the Plan includes specific referral hooks so that specialists can insert their statutory controls into the local consent decision.

The Plan text contains multiple amendment annotations; the Plan has been amended repeatedly since its commencement and those annotations provide a partial amendment trail embedded in the instrument. Key points drawn from the internal amendment notes:

• Commencement. The Plan commenced on 22 February 2014 (cl 1.1AA).

• Ongoing amendments. The Land Use Table and many clauses have amendment notes across multiple years indicating iterative changes: amendments listed in the Land Use Table footnote include 2017 (493), 2018 (488), 2019 (137), 2019 (594), 2019 (621), 2021 (714), 2022 (multiple instruments and Sch references), 2024 (42) and 2025 (153). Clause 2.1 identifies amendments in 2022 and 2025 (cl 2.1: Am 2022 (828), Sch 1.18[1] [2]; 2025 (153), Sch 1[1]).

• Insertions and repeals. Several clauses were added, substituted or repealed over time. Examples:

  • Savings provision cl 1.8A was inserted and amended (cl 1.8A: Am 2019 (621), Sch 5[1]).
  • Suspension of covenants cl 1.9A was amended in 2019 (cl 1.9A: Am 2019 (621), Sch 5[2]-[4]).
  • Principal standards and subdivision rules have been modified: cl 4.1AA (minimum subdivision lot size for community title schemes) was added in 2022 (cl 4.1AA: Am 2022 (828), Sch 1.18[4]-[6]), cl 4.1A and 4.1B were added/substituted in 2022 (cl 4.1A: Am 2022 (828) etc; cl 4.1B: Am 2022 (828), Sch 1.18[8]).
  • Clause 4.6 (exceptions to development standards) was amended in 2023 (cl 4.6: Am 2023 (554), Sch 2.25[1]).
  • New flood‑related clause 5.22 (special flood considerations) was substituted in 2024 (cl 5.22: Subst 2024 (455), Sch 1[1]).
  • Clause 5.9 (natural disaster repair) inserted in 2021 (cl 5.9: Ins 2021 (302), Sch 1.26) and amended subsequently.

• Additions to local provisions and schedules. Schedule 1 (additional permitted uses) lists amendment years including 2015, 2016, 2018, 2020, 2022, 2024 and 2026 (sch 1: Am 2015 (726); 2016 (10); 2016 (673); 2018 (198); 2020 (47); 2022 (200); 2024 (85); 2026 (92), Sch 1). Schedule 2 (exempt development) was amended 2022 (sch 2: Am 2022 (83), Sch 1[11] [12]). Schedule 6 (aquaculture) and related parts have insertion and amendment notes, including most recently 2025 (cl 7.25: Ins 2025 (578), Sch 1[1]).

• Repeals of earlier local instruments. Clause 1.8 repeals the previous Port Stephens Local Environmental Plan 2000 and other LEPs, and notes that Williams River Catchment Regional Environmental Plan 1997 was repealed under cl 1.8(2A).

This embedded amendment trail indicates an active program of local and State change. For a practitioner, the annotated plan text will show which provisions were recent and which are longstanding; but for a complete statutory amendment history, the official NSW legislation database should be consulted because the Plan references numerous amending instruments with their own schedules and years (as shown in the footnotes). The Plan’s notes also show that certain transitional provisions were time‑limited (for example, a Standard Instrument Order treated the Plan as applying to a precinct as if certain amendments had not commenced until 26 April 2025 , see Land Use Table Note 2).

The Plan itself does not name any judicial decisions or list litigation outcomes. There are no cases cited within the text provided. Consequently:

• The Plan contains no internal litigation history entries; it does not record judicial interpretations or precedent decisions within its schedules or notes.

• Practitioners must therefore rely on external jurisprudence under the Environmental Planning and Assessment Act and case law interpreting the Act, State SEPPs and Standard Instrument clauses when assessing how courts have interpreted analogous standard instrument provisions (for example, exceptions to development standards). Because this Plan contains many standard instrument clauses and references to the Act, the general line of statutory interpretation and case law on the Act will be relevant, but any specific judicial consideration of Port Stephens LEP 2013 is not memorialised in the instrument text.

• Where the Plan requires consultation with third parties (Commonwealth body, Heritage Council, Transport for NSW) those statutory referral outcomes can be the subject of merits review or judicial review under the Act and general administrative law principles; the Plan itself does not summarise any such decisions.

If litigation history is required for a particular provision or parcel, the practitioner should search NSW tribunal and court databases and review decisions under the Act that reference Port Stephens LEP 2013 or the relevant standard instrument provisions (for example, cases dealing with s 4.6‑style exceptions to development standards, heritage consents, or flood planning assessments). The Plan’s text does not provide that history.

Several features of the Plan are commonly missed or produce unintended compliance outcomes unless specifically checked.

• Maps are decisive. Numerous standards (lot size, height, floor space ratio, precincts, wetlands, drinking water catchments, active street frontages, heritage areas, acid sulfate soils, waste facility buffers and many more) are tied to named maps (cl 1.7; cl 2.2; cl 4.1; cl 4.3; cl 4.4; cl 7.1; cl 7.11; cl 7.22, etc.). Misreading or failing to check the correct current map or an updated map will generate fundamental errors about permissibility. The Plan explicitly allows maps to be combined and amended (cl 1.7), so always check the latest online maps on the Planning Portal.

• Pre‑commencement applications and savings. If a development application was lodged before the Plan commenced and was not finally determined before commencement, it must be determined as if the Plan had not commenced (cl 1.8A). Practically, a planner assessing a lodged application must verify lodgement and determination dates; otherwise incorrect legal pathway could be followed.

• Suspension of covenants is limited and conditional. Clause 1.9A can render private covenants inoperative to enable development under the Plan, but it expressly excludes covenants imposed by the Council and certain statutory instruments (cl 1.9A(2)(a)-(g)). It also does not affect rights or interests of public authorities under any registered instrument (cl 1.9A(3)). Users must check whether their covenant is the sort suspended and whether Crown or public authority interests remain in effect.

• Rural subdivision and dwelling entitlements traps. Clause 4.2 allows creation of smaller lots for primary production without dwellings, but a dwelling cannot be erected on such lots (cl 4.2(3)-(5)). Clause 4.2B restricts erection of dual occupancies and dwelling houses in specified rural and conservation zones unless lot sizes meet the Lot Size Map or specific historical criteria (cl 4.2B). Clause 4.6(6) further prohibits use of the exceptions clause to create multiple undersized lots in rural/conservation zones. Together these create a tight ring fence around rural fragmentation; practitioners must check the Lot Size Map and the precise mode of subdivision before advising clients.

• Exempt and complying development exclusions. Environmentally sensitive areas are excluded from exempt and complying pathways (cl 3.3). The definition of environmentally sensitive area is broad and includes coastal waters, Ramsar wetlands, land of high Aboriginal cultural or biodiversity significance and land within 100 m of many of those features (cl 3.3(2)). A proposal that looks exempt on face may be ineligible if it sits near one of these mapped features.

• Exceptions to standards require robust justification and recordkeeping. Clause 4.6 allows contraventions if compliance is unreasonable or unnecessary and there are sufficient environmental planning grounds, but the consent authority must keep an assessment record (cl 4.6(3)-(4)) and some standards are excluded from the exceptions process (cl 4.6(8)). An applicant relying on cl 4.6 must prepare the document required by the Regulation and be prepared for scrutiny.

• Airport airspace controls can produce an effective veto. Clause 7.4 requires the consent authority to consult the relevant Commonwealth body where a development would penetrate the Limitation or Operations Surface and to refuse consent if that body advises the development should not be carried out (cl 7.4(2)-(4)). This can make some developments uninsurable or unsaleable if Commonwealth objections are likely.

• Heritage pre‑conditions and consultation timeframes. For archaeological sites and nominated State heritage items the Plan mandates notices to the Heritage Council and requires the consent authority to consider responses within 28 days (cl 5.10(7), (9)). Failing to allow or obtain that consultation can invalidate a consent or lead to review. The Plan also allows the consent authority to require heritage management documents for nearby developments; those requirements can substantially delay applications and add costs (cl 5.10(5)).

• Flood and special flood considerations import technical guidance. Clause 5.21 and 5.22 require consideration of State flood guidelines and the Flood Risk Management Manual, meaning assessments must address climate change projections and evacuation impacts (cl 5.21(3) and cl 5.21(5)). Practitioners must use the latest guidance and technical expertise; superficial compliance may not satisfy the consent authority’s statutory tests.

• Detailed local caps and site limits. Clauses and schedules impose granular caps that can be overlooked: e.g. bed and breakfast limited to 4 bedrooms (cl 5.4(1)); farm stay accommodation no more than 12 bedrooms (cl 5.4(5)); neighbourhood shop and supermarket gross floor area caps (cl 5.4(7), (7AA)); retail floor area caps in specific sites (cl 7.20 and cl 7.24); MU1 retail gross floor area limit 750 m2 (cl 7.14). Practitioners must check site‑specific clauses in Schedule 1 and Part 7.

• Temporary uses require restoration. Temporary use consents and exempt temporary use categories require the site to be restored, as far as practicable, to its pre‑use condition (cl 2.8(3)(d) and Schedule 2). This creates potential post‑use liabilities.

• Multiple overlapping constraints. For many sites several constraints can apply concurrently (heritage listing, flood planning, acid sulfate soils, drinking water catchment). The consent authority’s tests in each relevant clause must be satisfied; meeting one test does not waive another.

Careful early due diligence on zoning, maps, schedule entries, heritage status, flood profiles and relevant State SEPPs is essential to avoid these traps.

A practitioner checklist and procedural roadmap, grounded in the Plan’s text, will help applicants and advisers comply.

1. Locate the land and read the maps. Start with the Land Application Map, Land Zoning Map, Lot Size Map, Height Map, Floor Space Ratio Map, Heritage Map, Wetlands Map, Acid Sulfate Soils Map, Drinking Water Catchment Map and any precinct/active frontage maps referenced in the Plan (cl 1.7; cl 2.2; cl 4.1; cl 4.3; cl 4.4; cl 5.10; cl 7.1; cl 7.9; cl 7.8; cl 7.22). The Plan ties many permissions and constraints to those maps, and the notes direct users to the NSW Planning Portal for the current maps.

2. Identify the zone and permitted uses. Use the Land Use Table and Schedule 1 to determine whether the proposed use is:

   • exempt development (Schedule 2 and cl 3.1) , if so, check the exempt standards and the environmentally sensitive area exclusion (cl 3.3);
   • complying development (Schedule 3 and cl 3.2) , if so, ensure the proposal meets the specified deemed‑to‑satisfy provisions of the BCA and any local complying conditions (cl 3.2(3)-(4)); or
   • development requiring consent (cl 2.3, cl 2.6, cl 2.7 etc). If consent is needed prepare to lodge a development application.

3. Test for special overlays and pre‑conditions. Check for:

   • heritage items, conservation areas or archaeological sites in Schedule 5 (cl 5.10), and be prepared to prepare heritage management documents or conservation management plans if required (cl 5.10(5)-(6));
   • environmentally sensitive areas (cl 3.3) that exclude exempt/comprising pathways;
   • flood planning area and special flood considerations (cl 5.21 and cl 5.22) and apply the Considering Flooding guideline and Flood Risk Management Manual as required (cl 5.21(5));
   • acid sulfate soils mapping (cl 7.1) and the need for an acid sulfate soils management plan (cl 7.1(3));
   • drinking water catchments (cl 7.8) and wetlands (cl 7.9);
   • aircraft noise/airspace constraints near RAAF Base Williamtown (cl 7.4-7.5) , if your development will penetrate obstacle surfaces consult the Commonwealth body and follow required acoustic design standards (cl 7.5(3)(b)-(c));
   • public infrastructure buffers (cl 7.11), public land classifications (cl 5.2 and Schedule 4) and any Schedule 1 site‑specific constraints.

4. Confirm service availability for urban release and essential services. In an urban release area do not assume consent will be granted without public utility availability; the Council must be satisfied essential public utilities are available or arrangements are in place (cl 6.2). For any development check essential services requirements (cl 7.6).

5. Prepare supporting technical documentation. Depending on overlays, the application may require:

   • heritage impact statements or heritage management plans (cl 5.10(5)-(6));
   • acid sulfate soils management plan consistent with the Acid Sulfate Soils Manual (cl 7.1(3));
   • flood risk assessments and evacuation/escape strategies consistent with the Considering Flooding guideline and Flood Risk Management Manual (cl 5.21(3));
   • odour, emissions and site suitability assessments for intensive livestock (cl 5.18(3));
   • aquaculture site and operational plans per Schedule 6 and relevant aquaculture industry development plans (cl 5.19 and Sch 6);
   • building compliance documentation for complying development (cl 3.2(3)(b)) and BASIX compliance where applicable (cl 4.6(8)).

6. If relying on a standards exception, prepare the s 4.6 document. Clause 4.6 requires a document demonstrating why compliance with the standard is unreasonable or unnecessary and providing sufficient environmental planning grounds. The Environmental Planning and Assessment Regulation requires that this document accompany the development application. Keep in mind cl 4.6(6) forbids consent under cl 4.6 that would result in multiple undersized rural/conservation lots.

7. Observe prescribed size caps and operational thresholds. Check local caps: bed and breakfast max four bedrooms (cl 5.4(1)), home business/home industry floor area limits (cl 5.4(2)-(3)), industrial retail caps (cl 5.4(4)), secondary dwelling size limits (cl 5.4(9) and cl 5.5), and site specific caps in Part 7 and Schedule 1 (cl 7.14, cl 7.20, cl 7.24, Sch 1 sites). Non‑compliance may require the exceptions pathway or be outright prohibited.

8. Factor in third‑party referrals and mandatory notifications. Budget time for required referrals:

   • Heritage Council notifications and 28‑day response windows for archaeological sites and nominated State heritage demolitions (cl 5.10(7), (9));
   • Commonwealth body consultation for airspace (cl 7.4(2));
   • Transport for NSW advice for access to Pacific Highway (cl 6.5);
   • local Aboriginal community consultation for Aboriginal places of heritage significance (cl 5.10(8)).

9. Temporary uses and restoration obligations. If seeking temporary use approval, observe the 52‑day cap (cl 2.8(2)) unless an exception applies for sales offices (cl 2.8(4)-(5)); ensure restoration commitments are explicit in the DA or conditions (cl 2.8(3)(d); Schedule 2 temporary use).

10. Consider covenant suspension carefully. If private covenants impede development, check whether cl 1.9A renders them inoperative for the purpose of enabling development under the Plan and whether any exceptions in cl 1.9A(2) require the covenant to continue to apply.

11. Check for site‑specific permissions. Review Schedule 1 for parcels that have additional permitted uses (for example, specific service station, retail or subdivision permissions) and ensure proposed development fits within those site‑specific conditions (cl 2.5).

12. Prepare for conditions and post‑approval compliance. Expect the consent authority to impose conditions tied to environmental management, restoration, staging, infrastructure provision (cl 6.3) or heritage conservation. Conditions will be enforceable; set up compliance systems and construction management plans accordingly.

13. Use the Plan with higher‑order instruments. Always check relevant State SEPPs (cl 1.9(1)), the Act and Regulations for procedural requirements, timeframes, and the details for the exceptions to standards document. The Plan frequently cross‑refers to State guidance and regulations, and those instruments can override local clauses.

14. Seek early liaison with the Council. Given the Plan’s numerous discretionary tests and the Council’s central role as consent authority (cl 1.6), early pre‑lodgement meetings can identify required studies, likely referral agencies and site‑specific constraints such as heritage or flood overlays.

Following this roadmap will align an application with the Plan’s statutory structure and reduce the risk of misclassification (exempt/comprising/DA), avoid missing referral steps, and ensure required technical studies are lodged up front.