The Plan operates through a set of interlocking legal and spatial mechanisms. Those mechanisms are set out below, referenced to the instrument.

Zoning and the Land Use Table (clauses 2.1-2.3). The Plan creates discrete zones (RU, R, E, SP, RE, C and W series) and for each zone the Land Use Table prescribes: (a) objectives for development, (b) what may be carried out without consent, (c) what may be carried out only with consent, and (d) what is prohibited (clause 2.3(1)). The consent authority must have regard to the zone objectives when determining applications (clause 2.3(2)). The Land Zoning Map fixes which land is in which zone (clause 2.2).

Maps as binding instruments (clause 1.7). Maps adopted by the Plan (for example, Lot Size Map, Height of Buildings Map, Floor Space Ratio Map, Land Reservation Acquisition Map, Terrestrial Biodiversity Map, Acid Sulfate Soils Map, Heritage Map, Active Street Frontages Map and Local Clauses Map) are incorporated by reference and can be amended or replaced only as provided by environmental planning instruments and with the approval of the local plan‑making authority (clause 1.7(1)). The Plan therefore delegates substantive regulatory detail to maps that are public and kept as electronic or paper records (clause 1.7(4)).

Development consent framework and exceptions. The Plan distinguishes development that is exempt (Schedule 2; cl 3.1) from complying development (Schedule 3; cl 3.2) and development requiring development consent. Exempt or complying development is excluded from doing certain things in environmentally sensitive areas (clause 3.3). Clause 1.8A preserves the rule that development applications made before the Plan’s commencement (or before specified SEPP commencements) are determined under the previous instrument.

Principal standards and flexibility. Primary measurement standards are set by map values and rules: minimum subdivision lot sizes (clause 4.1 and related clauses 4.1AA-1C), building height (clause 4.3), floor space ratio with explicit calculation method and anti‑double dipping covenants (clause 4.5). Clause 4.6 provides a statutory avenue to seek consent for developments that would contravene a development standard, but it sets limits: the consent authority must be satisfied the breach is unreasonable or unnecessary and that sufficient environmental planning grounds exist, and clause 4.6(8) identifies some development standards that this flexibility cannot affect.

Topic‑specific constraints and preconditions. The Plan contains an array of local and topic‑specific controls that operate either as preconditions to consent or as outright prohibitions. Representative examples:

• Canal estate development is prohibited (clause 2.9).
• Heritage items and conservation areas require development consent for demolition, alteration and certain forms of subdivision (clause 5.10; Schedule 5).
• Flood planning needs tests and compliance with NSW guidance documents; consent must not be granted in flood planning areas unless a range of flood‑safety and environmental criteria are met (clause 5.21; clause 5.22 for special flood considerations).
• Acid sulfate soils maps trigger the need for an acid sulfate soils management plan except where a preliminary assessment excludes it, and public authorities retain a limited class of emergency or routine exemptions (clause 6.1).
• Terrestrial biodiversity protections apply to land identified on the Terrestrial Biodiversity Map and require the consent authority to be satisfied development will avoid or minimise significant adverse impacts (clause 6.5).
• Airspace and aircraft noise controls require consultation with the relevant Commonwealth body if the Limitation or Operations Surface for Illawarra Regional Airport will be penetrated (clause 6.7) and require noise attenuation in areas within higher ANEF contours (clause 6.8).
• The Plan protects live music and performance: clause 5.20 forbids refusal of consent to licensed premises on certain expressive grounds (music genre, dancing, stage orientation, etc), and prevents refusal on noise grounds where the consent authority is satisfied the noise can be managed.

Parcel‑specific and local clauses. The Plan contains site‑specific permissions and limits in Schedule 1 and Part 6 (for instance, local clauses 6.14-6.16), which override or supplement the general Land Use Table as expressed in clause 2.5.

Interaction with State instruments and other Acts. The Plan is explicitly subject to State environmental planning policies where they prevail (clause 1.9). It cross‑references many other statutes that govern water, heritage, biodiversity, Crown land and local government procedures (for example, the Heritage Act, Local Government Act, Crown Land Management Act and various SEPPs and manuals referenced in particular clauses).

Decision‑making architecture. The Council is the consent authority for the Plan subject to the Act (clause 1.6). The consent authority must apply the Plan’s objectives and standards, consider State instruments where they prevail, keep records of assessments when development standards are contravened (clause 4.6(4)) and, in many topic areas (heritage, aviation, flood planning), follow specific consultation or notification steps (clauses 5.10, 6.7, 5.21).

Overall, the Plan is a map‑driven, standards‑plus‑exceptions instrument. Its primary practical operation is to allocate land uses and to attach process and documentation obligations to higher‑risk topics (flooding, heritage, biodiversity, acid sulfate soils, aviation), while providing limited pathways for flexibility (exceptions to standards, additional permitted uses for identified parcels).

Primary persons and entities affected are specified in the Plan and follow from its territorial scope and function.

Landholders and developers in Shellharbour. The Plan applies to the land shown on the Land Application Map (clause 1.3). Owners, prospective purchasers, developers, builders and tenants for that land are directly affected because the Plan defines what development is permitted with consent, without consent, or prohibited (clause 2.3 and the Land Use Table). Specific parcel owners listed in Schedule 1 and Schedule 4 are materially affected by additional permitted uses or reclassification of public land.

Council and the consent authority. The Plan designates the consent authority as the Council, subject to the Act (clause 1.6). The Council performs the day‑to‑day decision making: interpreting objectives, applying development standards, requiring and assessing management plans (for example acid sulfate soils management plans, heritage management documents) and deciding whether an application may lawfully proceed.

State agencies and Commonwealth bodies. The Plan interacts with State instruments and agencies. Clause 1.9 expressly subjects the Plan to State environmental planning policies that prevail under the Act. Where development would penetrate Illawarra Regional Airport obstacle surfaces, the consent authority must consult the relevant Commonwealth body and act on its advice (clause 6.7). The Plan also identifies relevant State authorities as relevant acquisition authorities for owner‑initiated acquisitions (clause 5.1).

Indigenous groups and the Heritage Council. The Plan prescribes consultation and considerations for Aboriginal places of heritage significance and Aboriginal objects (clause 5.10(8)): the consent authority must notify local Aboriginal communities and consider responses within 28 days in many cases. For archaeological sites and nominated State heritage items the consent authority must notify the Heritage Council and consider its response (clause 5.10(7) and (9)).

Owners of heritage items and occupants of conservation areas. Owners of listed heritage items and land within heritage conservation areas face mandatory consent requirements for demolition, exterior alteration and subdivision (clause 5.10(2)), and may be required to prepare heritage management documents or conservation management plans (clause 5.10(5)-(6)).

Public authorities and infrastructure providers. The Plan sets rules for land reserved for public purposes and identifies acquiring authorities in the Land Reservation Acquisition Map (clause 5.1). It expressly preserves infrastructure development by or on behalf of public authorities under SEPP (Transport and Infrastructure) (clause 5.12). Public authorities conducting emergency or routine works related to acid sulfate soils have limited exemptions (clause 6.1(5)).

Businesses and particular industries. The Plan shapes opportunities for a range of commercial activities via the Land Use Table and Schedule 1 additional permitted uses. It also specifically addresses aquaculture operators (clause 5.19 and Schedule 6), oyster aquaculture and priority oyster aquaculture areas (clause 5.19(5)-(6)), intensive livestock agricultural uses (clause 5.18), artisan food and drink industries (clause 5.4(10)), and licensed premises playing live music (clause 5.20). The Plan therefore affects operators’ ability to locate and operate businesses and the compliance obligations they must meet.

Adjacent landholders and the wider community. The Plan’s environmental controls (stormwater cl 6.4, terrestrial biodiversity cl 6.5, flood planning cl 5.21, acid sulfate soils cl 6.1) assign duties that protect neighbours’ amenity and environmental assets; neighbours may be consulted, and are the parties whose amenity the consent authority must often weigh (clause 2.3(2), cl 6.4(3)(c)).

Financial and professional intermediaries. Lawyers, town planners, heritage consultants, ecologists, surveyors and engineers are affected because many development paths require professional reports (heritage management documents cl 5.10, acid sulfate soils management plans cl 6.1, flood risk assessments cl 5.21, aquaculture plans Schedule 6).

Crown land and other land under public control. The Plan references the Crown Land Management Act and several Crown interest protections (clause 1.9A(2)-(3)). The Plan does not displace rights of public authorities under registered instruments (clause 1.9A(3)). It also provides for the classification and reclassification of public land as operational or community land (clause 5.2 and Schedule 4).

Who pays and who decides , mechanism. The immediate cost of complying with the Plan falls on the applicant/developer and the landowner: the Plan requires management plans, specialist studies and may require conservation works or infrastructure. The Council (consent authority) decides whether to grant consent and under what conditions (clause 1.6; cl 2.3(2)). State agencies and the Commonwealth can impose additional constraints through consultation and prevailing SEPPs (clause 1.9; cl 6.7).

Concentrated vs diffuse effects. The Plan concentrates benefits of parcel‑specific additional uses (Schedule 1) on particular owners; the costs of environmental safeguards (for example heritage conservation, biodiversity offsetting or management plans) are dispersed across applicants and potentially influence land values and development feasibility across the municipality.

This section summarises the principal duties the Plan places on applicants, the consent authority and other actors, together with rights conferred or preserved.

Duties of applicants (developers/landowners)

• Determine applicability: applicants must identify if their land is in the Plan’s area (clause 1.3) and the applicable zone on the Land Zoning Map (clause 2.2). They must check the Lot Size Map, Height of Buildings Map, Floor Space Ratio Map and other maps before lodging applications (clause 1.7).
• Consent vs exempt vs complying: ascertain whether proposed development is exempt (clause 3.1; Schedule 2), complying (clause 3.2; Schedule 3) or requires development consent (clause 2.3). Note that exempt/compliant pathways are excluded on some environmentally sensitive areas (clause 3.3).
• Provide required documentation: certain development requires specialised documentation before consent can be granted. Examples in the Plan include:
  • acid sulfate soils management plan prepared in accordance with the Acid Sulfate Soils Manual where required by the Acid Sulfate Soils Map (clause 6.1(2)-(3));
  • heritage management document or a heritage conservation management plan where required for heritage items or conservation areas (clause 5.10(5)-(6));
  • aquaculture proposals must comply with the site location and operational requirements of Schedule 6 and consider aquaculture industry development plans (clause 5.19(2)-(5); Schedule 6);
  • flood planning needs assessments consistent with the Considering Flooding in Land Use Planning Guideline and consideration of projected climate change impacts (clause 5.21(3)-(5)).
• Demonstrate compliance with standards or justify an exception: where a proposal contravenes a development standard the applicant must demonstrate (and the consent authority must record) that compliance is unreasonable or unnecessary and that sufficient environmental planning grounds exist (clause 4.6(2)-(4)). The Environmental Planning and Assessment Regulation requires an accompanying document for contraventions (note under clause 4.6(3)).

Duties of the consent authority (Council)

• Consider objectives and map values: the consent authority must have regard to the objectives for each zone when assessing applications (clause 2.3(2)), and satisfy itself that height and floor space ratio limits on the applicable maps are not exceeded except where the Plan or consent permits otherwise (clauses 4.3-4.4).
• Apply topic checks and require management plans: the consent authority must not grant consent in flood planning areas unless satisfied of compatibility with flood function and safe evacuation (clause 5.21(2)); must require and consider heritage management documents (clause 5.10(4)-(6)); must require acid sulfate soils management plans where the Acid Sulfate Soils Map triggers clause 6.1(2)-(3); and must be satisfied of aquaculture compliance with Schedule 6 (clause 5.19(2)-(3)).
• Consult and notify where required: notify the Heritage Council for archaeological sites (clause 5.10(7)) and Aboriginal communities for Aboriginal places (clause 5.10(8)). Consult the relevant Commonwealth body if a development will penetrate airport obstacle surfaces (clause 6.7(2)).
• Record assessments and maintain procedural memory: keep a record of assessment where development standards are contravened (clause 4.6(4)).
• Manage spatial exceptions: apply local clauses (Part 6) and Schedule 1 additional permitted uses consistently and subject to their stated conditions (clause 2.5).
• Apply mandatory prohibitions: the consent authority must refuse consent where a proposal is prohibited by the Land Use Table, the Plan’s clauses (for example clause 2.9 canal estates) or where special flood considerations or special heritage constraints rule consent out (clauses 2.3; 2.9; 5.21; 5.10).

Rights and preserved interests

• Owners retain rights under registered public authority instruments: clause 1.9A(3) preserves rights or interests of any public authority under registered instruments.
• Suspension but not extinguishment of private covenants: clause 1.9A suspends covenants, agreements and similar instruments to the extent necessary to enable development under the Plan, but expressly excludes certain categories from suspension (for example, covenants imposed by the Council, relevant Crown instruments, conservation agreements, planning agreements) (clause 1.9A(1)-(2)).
• Savings for pending applications: applications lodged before a Plan (or certain SEPP) commencement are to be determined under the previous instrument (clause 1.8A(1)-(2)), preserving applicants’ existing rights.
• Conservation incentives: the consent authority may grant consent for otherwise prohibited uses where conservation is facilitated and a heritage management document is approved and its conservation works are required (clause 5.10(10)).

Procedural rights for particular actors

• Heritage Council and Aboriginal communities have statutory notification and consultation windows before certain determinations (clause 5.10(7)-(9)).
• Relevant Commonwealth body can effectively veto developments that penetrate airport operational surfaces where it advises the consent authority that the development should not be constructed (clause 6.7(4)).

Limits and absolute prohibitions

• The Plan contains absolute prohibitions on some forms of development (for example canal estate development cl 2.9, “No Development” areas cl 6.13(2) except roads, and the constraints embedded in the Land Use Table for each zone). Clause 4.6 expressly prevents the exceptions power being used for certain standards (clause 4.6(8)).

Practical obligations that have cost implications

• Mandatory management plans and studies, mapping checks, consultation steps and potential covenant registrations (clause 4.5(9) on covenants) impose up‑front costs on applicants. The Plan’s repeated references to other statutory regimes mean applicants must secure licences and approvals beyond development consent , for example under fisheries, heritage or Crown land statutes (see cross‑references in clauses 1.9A, 5.19, 5.10).

The Plan itself does not set out detailed penalty provisions or specific enforcement sanctions in the text supplied. Instead, it frames permissions, prohibitions and process requirements under the Environmental Planning and Assessment Act and other statutes; non‑compliance with the Plan’s requirements will engage the enforcement and penalty mechanisms available under those statutes and the Act’s regulations. The instrument explicitly states development may be carried out “only with development consent” in multiple clauses (for example clauses 2.6, 2.7, 4.1), thereby invoking the Act’s development consent regime and its compliance and enforcement apparatus.

What the Plan does specify that affects enforcement posture

• Mandatory conditions and preconditions: the Plan prescribes specific documentation and preconditions (for example, acid sulfate soils management plans, heritage management documents, aquaculture site requirements). Where consent is given subject to conditions, monitoring and compliance with those conditions become operative obligations; failure to comply would normally attract statutory penalties and enforcement under the Act, though the Plan itself does not reproduce penalty schedules.
• Covenant registry for floor space control: clause 4.5(9) allows conditions requiring covenants to be registered to prevent creation of floor area on a restricted lot. Covenants, once registered, can be enforced as property instruments; failure to comply with covenant obligations or conditions of consent can lead to enforcement action.
• Notification and consultation duties: the Plan requires the consent authority to notify the Heritage Council and local Aboriginal communities in specified cases (clause 5.10(7)-(9)). These notification steps create procedural preconditions; failure to observe them could be material to judicial review of a decision.
• Prohibitions that are absolute in the Plan: where the Plan expressly prohibits development (for example clause 2.9 canal estate development; clause 6.13 No Development areas), carrying out the prohibited activity without amendment to the Plan or without development being lawfully allowed under another instrument would be an unauthorised development and thereby actionable under the enforcement powers in the Act.

Who enforces. The consent authority (Council) plays a front‑line role in monitoring and enforcing development consents and development standards because it issues consents and registers covenants. State agencies remain able to enforce statutory regimes that intersect with the Plan, for example, heritage enforcement by the Heritage Council where State heritage instruments apply, fisheries enforcement for aquaculture licences, or Crown agencies in relation to Crown land.

Practical enforcement risks and implementation concerns

• The Plan’s reliance on external instruments (SEPPs, manuals and Acts) fragments enforcement responsibility. That fragmentation can increase uncertainty as to which body should be approached for enforcement or for remedy.
• Procedural omissions (for example failing to secure required heritage or Aboriginal consultation) can lead to decisions being vulnerable to jurisdictional challenge. The Plan requires the consent authority to record assessments where development standards are contravened (clause 4.6(4)); incomplete records increase review risk.
• Covenants used to prevent “double dipping” in floor space calculations (clause 4.5(9)-(10)) create a property‑law enforcement layer that is enforced through land registers and potentially private litigation, not just planning enforcement mechanisms.

In sum, penalties and enforcement are exercised through the Act, the consent authority’s conditions and registration requirements (for example covenants), and through related statutory regimes referenced throughout the Plan. Practitioners must therefore manage development consent compliance in tandem with the enforcement machinery of the Environmental Planning and Assessment Act and the other statutes that the Plan cross‑references.

The Plan repeatedly cross‑references and defers to State and other statutory regimes. The instrument is designed to operate within a web of overlapping laws; several interactions are explicit and significant.

Primacy of State environmental planning policies. Clause 1.9(1) makes explicit that the Plan is subject to any State environmental planning policy that prevails under section 3.28 of the Act. Clause 1.9 also lists State EPIs that may be relevant (for example, SEPP (Housing) 2021; SEPP (Transport and Infrastructure) 2021; SEPP (Resources and Energy) 2021; SEPP (Resilience and Hazards) 2021; SEPP (Industry and Employment) 2021; SEPP (Primary Production) 2021). Those SEPPs can modify or override local provisions where the statutory hierarchy requires.

Reference to the Act and environmental assessment processes. Throughout the Plan development rights are expressed “with development consent” or “without development consent” under the Environmental Planning and Assessment Act (not reproduced in full in the instrument). Clause 1.6 designates the consent authority “subject to the Act”, and clause 1.8A and notes reference Division 3.5 of the Act for applications coincident with draft environmental planning instruments. The Plan is therefore proceduralised by the Act’s development application, public notice and appeal procedures.

Heritage law overlap. Clause 5.10 is framed to operate alongside the Heritage Act 1977: it requires notification of the Heritage Council in particular circumstances and provides the consent authority with powers to require heritage management documentation. For State heritage items listed in Schedule 5, additional statutory controls under the Heritage Act may be triggered. The Plan’s heritage obligations do not displace statutory duties under the Heritage Act; rather they operate in parallel and require consultation (clause 5.10(7)-(9)).

Crown land and Crown instruments. Clause 1.9A suspends private covenants to the extent necessary to enable development under the Plan, but explicitly preserves “relevant instruments within the meaning of section 13.4 of the Crown Land Management Act 2016” and other Crown arrangements (clause 1.9A(2)). Clause 5.12 records that the Plan does not restrict infrastructure development allowed under SEPP (Transport and Infrastructure) 2021, Chapter 2, or the use of existing buildings of the Crown by the Crown.

Biodiversity, fisheries and aquaculture frameworks. Aquaculture provisions (clause 5.19 and Schedule 6) require consent authority consideration of any aquaculture industry development plan (Fisheries Management Act framework) and the NSW Oyster Industry Sustainable Aquaculture Strategy (clause 5.19(5)). The Plan’s biodiversity protections (clause 6.5) apply to land mapped as Environmentally Sensitive Land and require assessment of impacts on ecological values; these operate alongside the Biodiversity Conservation Act and State biodiversity SEPPs referenced in the instrument.

Local Government Act and public land classification. Clause 5.2 implements classification and reclassification of public land as “operational” or “community” land under Part 2 of Chapter 6 of the Local Government Act 1993. It also identifies land in Schedule 4 for classification and reclassification, which can discharge trusts subject to Governor’s approval where required (clause 5.2 note and cl 5.2(5)).

Works affecting water, wetlands and acid sulfate soils. Clause 6.1 ties works to an Acid Sulfate Soils Map and requires management plans consistent with the Acid Sulfate Soils Manual; this cross‑links to the State manual and potentially to water legislation and environment protection standards. Clause 3.3 excludes environmentally sensitive areas for exempt/compliant development paths, listing coastal waters, coastal lakes, coastal wetlands, aquatic reserves, Ramsar and World Heritage areas and land protected under other Acts as examples , bringing in protections under the Coastal Management Act, Fisheries Management Act and Biodiversity Conservation Act.

Flood planning guidance and manuals. Clauses 5.21-5.22 explicitly adopt and cross‑refer to the Considering Flooding in Land Use Planning Guideline and the Flood Risk Management Manual, and require consent authorities to consider projected changes as a result of climate change. These are technical instruments external to the Plan but mandatory reference points within the Plan’s framework.

Development standards and BASIX. Clause 4.6(8)(b) prevents the exceptions power from being used to contravene development standards that arise from BASIX commitments under the BASIX policy. That cross‑links to the State BASIX regime and the Environmental Planning and Assessment Regulation which requires applicant documentation when contravening standards.

Airspace and Commonwealth controls. Clause 6.7 requires the consent authority to consult the “relevant Commonwealth body” where proposed development would penetrate Limitation or Operations Surfaces for Illawarra Regional Airport. The consent authority must accept that body’s advice where the body says the development should not be constructed (clause 6.7(4)). This creates a direct interaction with Commonwealth aviation regulation that can impose a veto on development that would create aerial safety hazards.

Practical effect of cross‑references. The Plan does not operate in isolation: it embeds a governance network where local determinations must be consistent with, and sometimes subordinate to, State and Commonwealth instruments, technical manuals and cross‑sector licensing regimes. Practitioners must therefore map obligations across multiple statutes and guidance documents and ensure consents and licences are obtained in the correct order.

The instrument records a series of marginal amendment notations across multiple clauses and schedules. Those notations identify statutory amendment instruments by year and schedule number. The Plan has been adjusted through time; the text supplied shows amendment entries at particular clauses. Examples recorded in the Plan include:

• Clause 1.8A: recorded amendments “Am 2019 (621), Sch 5[1]; 2023 (609), Sch 1.1[1]” which indicates clause 1.8A was amended by instruments referenced in 2019 and 2023 (marginal note in the Plan).
• Clause 1.9A: recorded amendments “Am 2019 (621), Sch 5[2]-[4]”.
• Clause 2.1 (Land use zones): “cl 2.1: Am 2022 (831), Sch 1.22[1]”.
• Clause 3.2 and Schedule changes: the Land Use Table and associated amendments are annotated “Land Use tbl: Am 2016 (168), Sch 1 [2] [5]; 2017 (493), Sch 1.1 [1] [2]; 2018 (488), Sch 1.1 [1]; 2019 (137), Sch 6 [1]; 2022 (831), Sch 1.22[1A] (ins 2023 (82), Sch 1.5[27]) [2] (am 2023 (82), Sch 1.5[28]); 2023 (458), Sch 2.69.”
• Clause 4.1AA: added/modified 2022 entries “cl 4.1AA: Am 2022 (831), Sch 1.22[3]-[5]”.
• Clause 4.2 and related clauses: records note the insertion and amendment dates, for example clause 4.1C “Ins 2015 (787), Sch 1. Am 2022 (831), Sch 1.22[3]-[6]”.
• Clause 4.2A: amended 2022 “cl 4.2A: Am 2022 (831), Sch 1.22[4] [5] [7] [8]”.
• Clause 4.6: includes references to repeal and limitations with notes on timings and clauses amended.
• Clause 5.1: “cl 5.1: Am 2015 (161), cl 5 (1).”
• Clause 5.21/5.22: clause 5.22 shows “cl 5.22: Subst 2023 (609), Sch 1.1[2]”.
• Many local clauses (Part 6) show insertion and amendment dates: e.g., clause 6.14 “cl 6.14: Ins 2016 (760), Sch 1 [1]. Am 2022 (831), Sch 1.22[4]”; clause 6.16 “cl 6.16: Ins 2022 (549), Sch 1.”

The marginal annotations record legislative instruments by year and schedule reference, which evidences iterative change rather than wholesale replacement. The nature of amendments includes inserted local clauses, new development standards, map changes and updates to cross‑referenced State guidance (for example flood planning and biodiversity). The Plan’s structure (with maps and schedules kept outside the main text) facilitates targeted amendments by instrument and schedule.

What the marginal notes show

• Regular updates between 2014 and 2023 to maps, local clauses and standards, reflecting progressive local planning adjustments.
• Amendments that align with State policy changes (for instance the introduction or update of State EPIs and new technical guidance like flood manuals which are referenced in later amendments).
• Parcel‑specific additions in Schedule 1 appear over time to authorise particular uses for defined lots (for example Schedule 1 clauses 1A-1C, 2A etc).

Implication for practice

• Because the Plan is map‑driven and contains marginal amendment traces, practitioners must consult the consolidated and current published Plan on the NSW Planning Portal and inspect the named maps and schedules as amended. The marginal notes in the instrument are useful signposts but do not replace the need to verify the current maps and schedules (clause 1.7(3) and the Plan’s notes).

The Plan itself does not include case law or list judicial decisions. The instrument’s text names no court decisions or litigation. As enacted, it references statutory consultation and review obligations (for example notification to the Heritage Council, cl 5.10(7); and the requirement for recorded assessments when standards are contravened, cl 4.6(4)), but it does not record litigation outcomes or judicial interpretations.

What practitioners should note

• Because the Plan interacts with the Environmental Planning and Assessment Act and multiple State statutes and technical guidelines, litigation and judicial review are possible avenues for challenging consent decisions, particularly where notification, mandatory consultation, or required assessments have not been properly undertaken. The Plan emphasises procedural steps in multiple clauses (for example in heritage and flood planning) that, if omitted, can make a decision vulnerable to review.
• Clause 4.6(4) requires the consent authority to keep a record of its assessment where the development standard is contravened. Failure to maintain an adequate record can be material in any merits review or judicial review proceeding.
• Practitioners seeking precedent or guidance on interpretation of specific Plan clauses (for example the scope of clause 1.9A suspension of covenants or the application of clause 5.20 protecting music) must locate relevant decisions in the NSW courts and the Planning and Environment Court. Those decisions are not supplied in the Plan and must be separately researched.

Because the Plan does not record litigation, practitioners should undertake a targeted search of:

• Planning and Environment Court decisions that interpret particular clauses of local environmental plans in Shellharbour or similar LEPs;
• Administrative decisions and merits review matters under the Environmental Planning and Assessment Act that address the Plan’s application; and
• Any relevant appeals, particularly around heritage items, flood risk, or aviation safety where Commonwealth advice has been decisive.

The Plan contains numerous provisions that can surprise applicants and decision makers unless specifically checked. These “gotchas” are concrete traps or substitution effects intrinsic to the Plan’s design.

1. Savings and timing traps (clause 1.8A)

• Development applications lodged before the Plan or certain SEPPs commenced must be determined as if the Plan had not commenced (clause 1.8A(1)). Applicants who assume the new Plan’s permissive provisions apply after commencement can be surprised to find their application is governed by the prior instrument. Likewise, clause 1.8A(2) preserves the same approach for a specified SEPP Amendment (Flood Planning) 2023. Practitioners must check the lodgement date against commencement dates.

2. Suspension of private covenants is limited,not absolute (clause 1.9A)

• Clause 1.9A allows suspension of covenants to the extent necessary to allow development under the Plan, but excludes covenants imposed by the Council, certain Crown instruments, conservation agreements, nature conservation trust agreements, property vegetation plans, biobanking agreements and planning agreements (clause 1.9A(2)(a)-(g)). Relying on clause 1.9A to bypass a Council‑imposed covenant is not possible. Public authority rights under registered instruments are preserved (clause 1.9A(3)).

3. Exempt/compliant development excluded in environmentally sensitive areas (clause 3.3)

• The exemptions and complying development pathways are not available on identified environmentally sensitive areas (clause 3.3). If land lies within coastal waters, coastal wetlands, aquatic reserves, within 100 metres of those areas or is mapped as high Aboriginal or biodiversity significance, the apparently quicker exempt/compliant routes are closed and the full consent pathway applies.

4. Canal estate is a categorical prohibition with a wide definition (clause 2.9)

• Clause 2.9 prohibits canal estate development and defines that to include constructed canals or waterways that drain or are inundated and relate to erection of a dwelling, and that use fill or excavation to achieve residential development in flood planning areas. Proposals that might aim to create waterfront lots using excavation/fill should be assessed against this prohibition. The clause includes narrow exceptions for drainage or water supply works carried out by authorised utilities, but otherwise the prohibition is absolute.

5. Limits to the “exceptions” power (clause 4.6)

• The exceptions to development standards (clause 4.6) are not a free pass. The applicant must show compliance is unreasonable or unnecessary and set out environmental planning grounds (clause 4.6(3)). Crucially, clause 4.6(8) prevents its application to certain standards, including standards for complying development and BASIX‑derived commitments, and identifies a suite of zones where subdivision cannot be permitted under the exceptions power if it would create lots below minimum areas (clause 4.6(6)). Practitioners must not assume a contravention can be cured merely by argument.

6. Heritage procedural strictness and possible conservation works (clause 5.10)

• Demolition or alteration of heritage items and items in conservation areas requires consent (clause 5.10(2)). The consent authority may require a heritage management document or a conservation management plan (clause 5.10(5)-(6)). The Plan allows the consent authority to grant permission for otherwise prohibited purposes if the conservation of the heritage item is facilitated, but only if strict conditions are met (clause 5.10(10)). Failure to notify the Heritage Council or Aboriginal communities where mandated can invalidate or expose decisions to challenge (clauses 5.10(7)-(9)).

7. Music protection is limited and conditional (clause 5.20)

• Clause 5.20 prevents refusal of development for licensed premises on a list of expressive grounds (genre, live/amplified status, dancing, stage orientation, decorations) and forbids refusal on noise grounds provided the consent authority is satisfied the noise may be managed and minimised to an acceptable level (clause 5.20(1)-(2)). However, this does not remove the need to address noise impacts: if the authority is not satisfied noise can be managed, refusal may still occur.

8. Double‑dipping floor space and covenant traps (clause 4.5)

• Clause 4.5 allows conditions of consent to require registration of covenants preventing the creation of floor area on a restricted lot to avoid “double dipping” of floor space ratios across consolidated sites (clause 4.5(9)-(10)). Applicants who assume a site’s consolidated status automatically entitles them to multiple FSR allocations may find covenants imposed that reduce buildable floor area elsewhere on the site.

9. Airport obstacle surfaces can create a Commonwealth veto (clause 6.7)

• If a proposed development penetrates the Limitation or Operations Surface for Illawarra Regional Airport, the consent authority must consult the relevant Commonwealth body and may not grant consent if that body advises the development should not be constructed (clause 6.7(2)-(4)). This creates a de facto veto that can be decisive even where local planning objectives might otherwise favour development.

10. “No Development” zoning with a narrow exception (clause 6.13)

• Land identified as “No Development” on the Development Area Map cannot be developed for any purpose, except development consent may be granted for a road (clause 6.13(2)-(3)). Applicants should not expect ad hoc approvals for dwellings or other buildings on such areas.

11. Exemptions for public authorities are not universal (clauses 6.1(5), 5.12)

• The Plan grants limited exemptions for public authorities in specific narrow circumstances , e.g., emergency and routine works by public authorities for acid sulfate soils (clause 6.1(5)); and the Plan states it does not restrict development by or on behalf of a public authority permitted under SEPP (Transport and Infrastructure) 2021 (clause 5.12(1)). However, those exemptions have thresholds and do not automatically permit broader public works without proper assessment.

12. Parcel‑specific additional permitted uses can materially change entitlement (Schedule 1; clause 2.5)

• Schedule 1 entries grant tailored additional uses to identified land and can operate despite other Plan provisions (clause 2.5(2)). Developers must check Schedule 1 carefully because it can create specific opportunities or constraints not evident from zone alone.

Each of these “gotchas” is created by the Plan via a concrete rule or mapping decision; practitioners should check the current maps and schedules and confirm whether local clauses apply to an allotment before relying on general zone narratives.

Compliance requires a methodical, map‑driven and evidence‑based approach. The Plan ties many permissions to named maps, schedules and external technical manuals. The following stepwise checklist is grounded in the Plan’s provisions.

1. Confirm the Plan applies to the land (clause 1.3)

• Check the Land Application Map to ensure the property is within the Plan’s geographic scope (clause 1.3(1)). Confirm the land is not identified as “Deferred matter” on the Land Application Map (clause 1.3(1A)).

2. Identify applicable zoning and map values (clauses 2.2; 1.7)

• Use the Land Zoning Map to identify the zone (clause 2.2).
• Inspect the Lot Size Map, Height of Buildings Map, Floor Space Ratio Map, Terrestrial Biodiversity Map, Acid Sulfate Soils Map, Development Area Map (No Development), Active Street Frontages Map, Land Reservation Acquisition Map and any Local Clauses Map that might alter entitlements (clause 1.7; see Part 6 and Schedules).
• Determine whether the proposal is one of the uses permitted without consent, permitted with consent or prohibited under the Land Use Table for that zone (clause 2.3 and Land Use Table entries).

3. Establish the correct development pathway (clause 3.1-3.3)

• If the activity is exempt development in Schedule 2 and meets the schedule’s standards and Building Code of Australia requirements, it may proceed without consent (clause 3.1). Confirm the land is not an environmentally sensitive area that excludes exempt/compliant paths (clause 3.3).
• If the activity is complying development in Schedule 3 Part 1 and meets the conditions in Part 2, apply for a Complying Development Certificate rather than a full DA (clause 3.2).
• Otherwise, prepare a development application seeking development consent from the Council (clause 2.3).

4. Prepare the technical documents the Plan requires

• Heritage: if heritage item, Aboriginal place or conservation area is involved, prepare a heritage management document or conservation management plan as required; expect notification obligations to the Heritage Council and local Aboriginal communities (clause 5.10(4)-(9)).
• Acid sulfate soils: if the Acid Sulfate Soils Map triggers clause 6.1(2), prepare an acid sulfate soils management plan consistent with the Acid Sulfate Soils Manual; a preliminary assessment may avoid the requirement if confirmed in writing by the consent authority (clause 6.1(3)-(4)).
• Flooding: for land in a flood planning area, prepare a flood risk assessment that addresses compatibility with flood function, safe evacuation, projected climate change impacts and relevant guidance documents (clause 5.21(2)-(5); see Considering Flooding in Land Use Planning Guideline and Flood Risk Management Manual references).
• Terrestrial biodiversity: if the land is on the Terrestrial Biodiversity Map, prepare ecological assessments demonstrating avoidance, minimisation or mitigation measures and justification that adverse impacts will not be significant (clause 6.5).
• Stormwater: include stormwater management demonstrating maximised permeable surfaces, on‑site retention where practicable and avoidance/minimisation of adverse impacts (clause 6.4).
• Aquaculture: if proposing pond, tank or oyster aquaculture, ensure compliance with the site location and operational requirements in Schedule 6 and alignment with aquaculture industry development plans (clause 5.19 and Schedule 6).
• Airport airspace: if the proposal would penetrate an Obstacle Limitation Surface or Operations Surface for Illawarra Regional Airport, obtain early contact with the relevant Commonwealth body and prepare to demonstrate any design change or mitigation the Commonwealth requires (clause 6.7).

5. Address development standards and identify if an exception is sought (clause 4.6)

• Check minimum lot sizes (clause 4.1 and related clauses 4.1A, 4.1B, 4.1C), height limits (clause 4.3) and floor space ratio limits (clause 4.4).
• If the proposal contravenes a development standard, prepare the document required by the Environmental Planning and Assessment Regulation to demonstrate why compliance is unreasonable or unnecessary and set out the environmental planning grounds (clause 4.6(3) and note).
• The consent authority must keep a record of its assessment of such contraventions (clause 4.6(4)).

6. Check local clauses and Schedule 1 additional permitted uses (clause 2.5; Part 6; Schedule 1)

• Verify whether Schedule 1 grants an additional permitted use for the subject parcel or whether Part 6 contains a local clause that applies to the land (for example clauses 6.14-6.16). Where Schedule 1 authorises a use “despite anything to the contrary in the Land Use Table” that takes precedence (clause 2.5(2)).

7. Address covenant and floor space considerations (clause 4.5)

• If consent will create floor area on a consolidated site, anticipate a condition requiring a covenant preventing “double dipping” to be registered. Plan for the legal and conveyancing costs of registering such covenants (clause 4.5(9)-(10)).

8. Prepare for consultation and timing constraints

• Allow time for statutory notifications to the Heritage Council and Aboriginal communities and for responses within prescribed periods (clause 5.10(7)-(9)). Where airport or Commonwealth consultation is required, build in longer lead times (clause 6.7).
• If the proposal is for a temporary use (clause 2.8), note the 52‑day cap for temporary uses unless the proposal is a dwelling sales office connected to a new estate (clause 2.8(2)-(4)).

9. Design to meet local numeric limits in clause 5.4 and others

• For permitted home businesses, home industries and bed and breakfast accommodation there are explicit floor area or room limits that affect design feasibility (clause 5.4(1)-(3), (5)). For example, home businesses and home industries are limited to 50 square metres of floor area (clause 5.4(2)-(3)).

10. Anticipate conditions and cross‑sector licences

• The Plan does not remove the need for licences under other statutes. For example, an aquaculture consent will not exempt the proponent from fisheries licences required under the Fisheries Management Act; heritage consent does not remove statutory duties under the Heritage Act; and Crown land dealings require separate Crown processes (see clauses 1.9A, 5.12, 5.19 and 5.10).

11. Get early engagement with the Council

• Early pre‑lodgement meetings with Council to confirm the required maps, likely conditions and the need for specific technical studies (eg acid sulfate or ecology) will help ensure applications are complete and reduce the risk of refusal or delay. The Plan empowers the consent authority to require documentation in several contexts, so early contact reduces information risk.

12. Check for potential prohibitions and local constraints

• Before committing resources, check for absolute prohibitions applicable to the land: canal estate prohibition (clause 2.9), “No Development” areas (clause 6.13), or local clauses that prohibit dwellings in particular mapped areas (for example clause 6.15(4)). If a proposed use is prohibited, seek whether an amendment to the Plan or reclassification is possible (but also check the Act for the amendment pathway).

13. Register covenants and secure titles work where required

• If the consent requires a covenant under clause 4.5 or otherwise triggers obligations on title, coordinate with legal/conveyancing advisers to register the covenant in the correct form and to ensure it is reflected in contract documentation for any sale.

14. Maintain administrative records

• Where standards are contravened and exceptions applied the consent authority must keep a record (clause 4.6(4)). Applicants should provide full documentation and preserve audit‑grade records of environmental planning grounds, consultants’ reports and communications.

15. Monitor consent conditions and compliance

• Once consent is granted, implement the management plans and conditions (heritage works, stormwater retention, monitoring regimes) and be ready to show compliance on audit. Non‑compliance risks enforcement action under the Act.

In sum, compliance is a procedural exercise with substantive technical inputs. The Plan’s map‑centric architecture makes an initial map and schedule check the most important compliance action; many subsequent obligations flow from those maps. Where multiple statutory regimes interact, secure the non‑planning licences early to avoid stranded consents.