The Plan organises Mosman’s planning controls around a set of recurring legal and spatial concepts. These are the levers decision‑makers and applicants will encounter repeatedly.

• Zoning and the Land Use Table (Part 2, cl 2.1-2.3). The Plan identifies zones (R2, R3, E1, E3, SP1, SP2, RE1, RE2, C1, C2, C4) and for each zone sets objectives and a Land Use Table that specifies what is permitted without consent, permitted with consent, and prohibited (cl 2.1; cl 2.3(1); Land Use Table). Decision‑makers must have regard to zone objectives when determining applications (cl 2.3(2)).

• Maps and spatial standards (cl 1.7). Key standards (minimum lot sizes, height, floor space ratio, land zoning, heritage areas, acid sulfate soils) are fixed by maps referred to in clauses. The Plan treats maps as adopted by the local plan‑making authority and subject to amendment processes; maps may be in electronic or paper form (cl 1.7(1), (3)-(4)).

• Development pathways: consent, exempt, complying (Part 3, cl 3.1-3.3 and Schedules 2-3). The Plan identifies additional local exempt development and local complying development beyond the State SEPP codes and sets conditions that must be met for these pathways to apply (cl 3.1(2)-(5); cl 3.2(2)-(4)). Environmentally sensitive areas are excluded from exempt/compliant pathways (cl 3.3).

• Development standards (Part 4). The Plan fixes minimum lot sizes (cl 4.1), exceptions to them (cl 4.1A-4.1C), height limits (cl 4.3 and additional provisions at cl 4.3A), floor space ratios (cl 4.4, cl 4.4A, cl 4.4B) and rules for calculating site area and FSR (cl 4.5). It permits the consent authority to allow contraventions of development standards in defined circumstances (cl 4.6) but sets out some express exclusions from that flexibility (cl 4.6(8)).

• Heritage and archaeology (cl 5.10 and Schedule 5). The Plan lists heritage items and conservation areas (Schedule 5) and requires consent for demolition, external alteration and certain internal alterations of listed items; it also authorises the consent authority to require heritage management documents and conservation management plans prior to consent (cl 5.10(2), (5)-(6)). The consent authority must notify the Heritage Council in specified archaeological and State heritage demolition cases (cl 5.10(7), (9)).

• Coastal, foreshore and flood planning (cl 6.3, cl 5.7, cl 5.21). The Plan restricts development in foreshore areas, requires consent for works below mean high water mark, and sets flood planning obligations and matters the consent authority must consider regarding flood risk and climate‑change projected impacts (cl 6.3(2)-(3); cl 5.7(2); cl 5.21(2)-(3)).

• Environmental protection overlays and operations: acid sulfate soils, natural watercourses, public bushland, scenic protection, and earthworks (cls 6.1, 6.2, 6.3, 6.4, 6.7, 5.23). These clauses prescribe when consent is required, procedural preconditions (e.g. an acid sulfate soils management plan, cl 6.1(3)), and substantive matters the consent authority must address.

• Localised permissions and constraints (Schedule 1 and Schedule 2). Schedule 1 contains site‑specific additional permitted uses (for example, limited retail at certain Military Road properties, Schedule 1 cll 3-6), while Schedule 2 lists local exempt development with detailed numeric and locational limits (for example, outdoor dining, signage, fowl houses, Taronga Zoo works). These operate alongside statewide SEPP exemptions.

• Administrative tools and land administration (cl 5.2, cl 5.1, cl 4.5(9)). The Plan identifies acquiring authorities for owner‑initiated acquisition (cl 5.1) and enables the Council to classify or reclassify public land (cl 5.2). It authorises the consent authority to impose covenants to prevent floor‑space “double dipping” and to reduce allowable floor space on consolidated sites accordingly (cl 4.5(9)-(10)).

• Interaction with State law and instruments (cl 1.9). The Plan is expressly subject to SEPPs that prevail under s 3.28 of the Act and records which SEPPs or provisions do not apply locally (cl 1.9(1)-(2)), while also cross‑referencing the Act and numerous other statutes and codes throughout.

Those concepts are the operational building blocks by which the Council and applicants will negotiate development permissions, conditions and constraints across the Mosman area.

The Plan affects a defined set of actors in predictable ways because it allocates decision rights to the Council and regulates the activities of landowners, developers, occupiers and certain State authorities.

• Landowners and prospective purchasers in Mosman. The Plan directly binds any person proposing to develop land in the mapped area (cl 1.3: land to which the Plan applies). It determines what uses are permitted on any parcel (Land Use Table, cl 2.3) and what limits apply to height, FSR and lot sizes (cls 4.1, 4.3, 4.4). Owners seeking subdivision, dual occupancy, demolition, or other works must comply with Plan requirements and obtain development consent where required (eg cl 2.6 subdivision requires consent; cl 2.7 demolition requires consent).

• Developers and design professionals. Development proponents must design to the maps and standards in the Plan and prepare supporting material listed as required (heritage management documents, acid sulfate soils management plans, flood risk measures). For example, works in acid sulfate areas require an acid sulfate soils management plan consistent with the Acid Sulfate Soils Manual before consent can be granted (cl 6.1(3)-(4)). Those obligations shift costs to project proponents in the form of technical studies and contingency measures.

• Licensed premises and hospitality operators. The Plan curtails the use of certain standards as a ground of refusal where the playing or performance of music is at issue. Clause 5.20 prevents the consent authority refusing consent to licensed premises on grounds such as genre, live vs amplified music, dancing, stage direction, or associated décor, and limits refusal on noise grounds to cases where noise cannot be managed and minimised to an acceptable level (cl 5.20(1)-(2)). That changes the negotiation space between operators and councils over entertainment uses.

• Heritage custodians and Aboriginal communities. Heritage listed owners and anyone proposing development affecting heritage items, conservation areas or Aboriginal places must comply with cl 5.10 requirements: notification obligations, potential heritage management documents, and consultation with local Aboriginal communities for Aboriginal places of heritage significance (cl 5.10(4)-(9)). That imposes procedural steps and may lengthen assessment timelines.

• The Council as consent authority and land manager. The Plan names the Council as the consent authority (cl 1.6) and grants it functions under classification and reclassification rules for public land (cl 5.2). The Council is responsible for granting consent, imposing conditions, requiring covenants (cl 4.5(9)) and enforcing compliance with the Act and the Plan.

• State authorities and acquiring bodies. Clause 5.1 designates State authorities as acquiring authorities for particular types of reserved land where owner‑initiated acquisition occurs, for instance Transport for NSW for classified roads and the corporation constituted under s 2.5 of the Act for regional open space (cl 5.1(2) table). Clause 1.9(1) signals that State environmental planning policies may prevail where they do.

• Public users of foreshore, parks and recreation facilities. The Plan sets constraints and objectives for public recreation zones and private recreation areas (Land Use Table zones RE1 and RE2) and contains specific provisions for The Spit and Balmoral that limit development types and require protection of public access (eg cl 6.3(3)(d) foreshore public access considerations; RE2 objectives referencing The Spit).

• Utilities and infrastructure providers. The Plan exempts or recognises certain infrastructure actions (cl 5.12) and allows public authorities to carry out emergency and routine works subject to some exclusions (eg acid sulfate soils: cl 6.1(5) permits certain public authority works without consent). It also prescribes acquisition authorities (cl 5.1). Infrastructure proponents must account for mapped constraints.

Who pays. The Plan shifts direct compliance costs chiefly to landowners and developers through the requirement to prepare reports (heritage documents, acid sulfate plans), to fund remediation measures or design changes required by consent conditions, to meet minimum landscaped areas (cl 6.6) and to abide by lot size, height and FSR rules that can reduce developable area. The Council bears administrative costs of processing applications, maintaining maps and enforcing conditions. State authorities may bear acquisition costs when land is acquired under owner‑initiated acquisition provisions (cl 5.1 note). The Plan also creates potential opportunity costs for owners whose preferred development is prohibited or constrained (eg ban on canal estate development, cl 2.9).

This section summarises core statutory duties and rights created by the Plan and the principal procedural or substantive obligations applicants and the Council must observe.

Duties imposed on applicants and owners

• Obtain development consent where required. The Plan repeatedly states that development permitted only with consent must not be carried out without consent (for example, subdivision requires consent, cl 2.6(1); demolition requires consent, cl 2.7). Exempt and complying development are limited to the forms and conditions in Schedules 2 and 3 and cl 3.1-3.2.

• Comply with mapped numerical standards. Applicants must design proposals to be within the limits shown on the Lot Size Map, Height of Buildings Map and Floor Space Ratio Map. For example, building height must not exceed the maximum shown on the Height of Buildings Map (cl 4.3(2)); minimum subdivision lot sizes must not be less than those shown on the Lot Size Map (cl 4.1(3)).

• Provide specified technical documentation when required. The Plan mandates an acid sulfate soils management plan where works trigger cl 6.1(2) requirements and allows the consent authority to require heritage management documents or conservation management plans for listed items or areas (cl 6.1(3); cl 5.10(5)-(6)). Flood‑related considerations (cl 5.21) require applicants to show that development is compatible with flood function and includes measures for evacuation and risk to life.

• Meet local use and scale controls. The Land Use Table and additional controls (cl 5.4) set specific limits for particular uses (for example bed and breakfast limited to no more than three guest bedrooms, cl 5.4(1); home businesses limited to 30 m2 of floor area, cl 5.4(2)).

• Abide by heritage procedural obligations. If an application concerns an archaeological site or nominated State heritage item, the consent authority must notify the Heritage Council and consider its response (cl 5.10(7), (9)). For Aboriginal places of heritage significance, the consent authority must notify local Aboriginal communities and consider their responses (cl 5.10(8)).

Rights created or preserved

• Right to assert exempt or complying development pathways when criteria are met. If a proposal meets the standards in Schedule 2 (exempt) or Schedule 3/State SEPP (complying), it may proceed without development consent, though other approvals under other Acts might still be necessary (cl 3.1(2); Schedule 2 note 2).

• Right to request assessment under exceptions to development standards. Clause 4.6 permits consent authorities to grant consent in spite of a contravention of a development standard provided the applicant demonstrates the compliance is unreasonable or unnecessary and there are sufficient planning grounds (cl 4.6(2)-(3)). The Plan records that the EPA Regulation requires applicants to lodge a document justifying the variation (cl 4.6 note).

• Right to seek specified floor space incentives. On land in Area 2 (Spit Junction), the Plan allows an uplift to a 3:1 FSR where specified site consolidation and access conditions are met (cl 4.4B(3)).

• Right to apply for temporary uses within the period limits. The Plan permits temporary use for up to 28 days in any 12‑month period subject to criteria ensuring no adverse impacts (cl 2.8(2)-(3); exceptions for sales offices in new release areas, cl 2.8(4)-(5)).

Decision rights and process powers

• The consent authority is the Council (cl 1.6). The Plan instructs the consent authority to have regard to zone objectives in determining applications (cl 2.3(2)), to consider specified matters in particular contexts (for example cl 5.21 flood matters, cl 5.10 heritage matters, cl 6.2 natural watercourse impacts), to keep an assessment record of any exercise of discretion under cl 4.6(4) and to take specified notification steps (cl 5.10(7)-(9)).

• Power to impose covenants. When granting consent for development on a consolidated site, the consent authority may require a covenant preventing creation of floor area on a restricted lot to avoid “double dipping” (cl 4.5(9)-(10)). That obligation changes the legal rights associated with titles and can reduce developable capacity on other lots.

• Power to classify or reclassify public land. The Council may classify or reclassify public land as operational or community land under cl 5.2, with consequential effects on trust obligations and land management under the Local Government Act 1993 (cl 5.2(1)-(5)).

Limits and express exclusions

• Environmentally sensitive areas are excluded from exempt or complying development (cl 3.3(1)-(2)), limiting streamlined pathways in such places.

• The clause allowing suspension of private covenants for enabling development under the Plan contains express exclusions,covenants imposed by the Council, certain restrictive covenants on Markham Close, instruments under the Crown Land Management Act 2016, conservation or trust agreements under specified Acts, biobanking agreements, and planning agreements (cl 1.9A(2)). The clause also preserves public authority rights under registered instruments (cl 1.9A(3)).

Procedural recordkeeping and consultation duties

• Consent authorities must keep assessment records when applying cl 4.6 (cl 4.6(4)) and must follow notification timeframes when Heritage Council or local Aboriginal communities are to be advised (cl 5.10(7)-(9) and cl 5.10(8)). These are process obligations that create administrative burdens and potential appeal points.

The Plan itself is a local environmental planning instrument that prescribes development controls and procedural requirements. It does not specify monetary penalties or detailed enforcement sanctions within its text. Enforcement mechanisms and penalties for non‑compliance with development consent, unlawful development, or breaches of planning conditions are matters governed by the Environmental Planning and Assessment Act and its regulations and by other relevant statutes. The Plan does, however, embed a number of mechanisms and compulsory steps that are relevant to enforcement practice and compliance risk:

• Consent as prerequisite and the Act’s enforcement machinery. Clauses such as 2.6(1) (subdivision only with consent), 2.7 (demolition requires consent), and many permissibility provisions in the Land Use Table create legal prerequisites: carrying out development without required consent would be development contrary to the Plan and therefore subject to enforcement under the Act. The Plan assumes the Act’s compliance and enforcement framework applies (see cl 1.6 reference to the Act and cl 1.9 on State policies).

• Conditions and covenants recorded on title. The Plan expressly permits a consent authority to require as a condition of consent the registration of a covenant preventing creation of floor area on a restricted lot to prevent “double dipping” (cl 4.5(9)). Covenants are enforceable against future owners and are recorded on title. Their breach may give rise to actions in equity or land law remedies, and the Plan prescribes their use as a regulatory tool to secure Plan‑based outcomes.

• Notification and consultation duties as compliance steps. The Plan requires notification to Heritage Council in relation to archaeological sites and nominated State heritage item demolition applications (cl 5.10(7), (9)), and notification to local Aboriginal communities for works in Aboriginal places of heritage significance (cl 5.10(8)). These procedural duties create legal obligations whose non‑observance may expose a decision or development to legal challenge on procedural fairness or statutory error grounds.

• Conditions imposed on complying development certificates. Schedule 3 states that complying development certificates are subject to the same conditions as in Schedule 6 to the State SEPP (sch.3-sec General conditions). Non‑compliance with those conditions can be enforcement grounds.

• Ministerial and Governor approvals for map and classification actions. Clause 1.7 requires maps to be kept and made available under arrangements approved by the Minister. Clause 5.2(5) notes the Governor’s approval is required for discharging trusts when public reserves are inserted into Schedule 4 Part 2 and reclassified as operational land. Missing procedural approvals can render decisions vulnerable to challenge.

• Public authorities and certain works. The Plan exempts from certain consenting requirements a set of public authority works or authorises limited public authority activity without consent in specific circumstances (eg cl 6.1(5) permits certain emergency and routine public authority works without consent). The Plan simultaneously preserves the rights of public authorities under registered instruments (cl 1.9A(3)). Enforcement against public authorities is therefore constrained by those provisions.

What the Plan does not do in enforcement terms

• No schedule of fines or fines rates. The Plan does not itself set out fine amounts, infringement notices or detailed administrative penalty regimes. Those are contained in the Act and associated regulation and enforcement instruments.

• No independent prosecutorial provisions. The Plan relies on the Act’s compliance architecture and Council powers rather than creating a bespoke enforcement tribunal or penalty schedule in the instrument.

Practical enforcement implications

• The Plan provides tools for the Council to secure compliance through conditions, registered covenants, and refusal or imposition of consent. It increases the evidentiary and documentation requirements for developers (heritage management documents, acid sulfate soils management plans, flood risk assessments), producing both longer assessment timeframes and more grounds for refusal or conditioning where those documents are unsatisfactory.

• Procedural notification steps (Heritage Council, Aboriginal communities) create additional windows for third‑party engagement and potential objections that can lead to enforcement risk or appeal.

For detailed penalty amounts and the mechanics of issuing notices, fines or orders against unlawful development, practitioners must consult the Environmental Planning and Assessment Act, the regulations and Council enforcement policies. The Plan is the spatial and substantive standard-setting instrument; enforcement relies on the Act.

The Plan is framed and operates as an environmental planning instrument under the Environmental Planning and Assessment Act (the Act). It repeatedly cross‑references the Act and a number of specialist statutes and State environmental planning policies; those cross‑references determine which provisions prevail and where additional statutory approvals remain necessary.

Hierarchy and prevailing instruments

• Subordination to SEPPs and the Act. Clause 1.9(1) expressly provides that the Plan is subject to any State environmental planning policy that prevails over it as provided by s 3.28 of the Act. This means State SEPPs can invalidate or amend the Plan’s operation where they are inconsistent. The Plan also notes particular State SEPPs and Chapters that may be relevant in the Land Use Table note (for example SEPP (Housing) 2021; SEPP (Transport and Infrastructure) 2021; SEPP (Resilience and Hazards) 2021 etc).

• Savings and transition arrangements tied to the Act. Clause 1.8A contains savings provisions for development applications made before the Plan’s commencement and for later specified amendments, indicating that the Act’s transitional frameworks and Division 3.5 options for combined draft EPI and development applications must be respected (cl 1.8A note referencing Division 3.5 of the Act).

Cross‑statutory requirements and consents

• Other statutes retain independent approval regimes. The Plan repeatedly notes that exempt development under the Plan does not remove the need for approvals under other Acts (Schedule 2 note 2). Examples include the Heritage Act 1977 (heritage items and interim heritage orders referenced at cl 3.1(3)(d) and cl 5.10), the Land Acquisition (Just Terms Compensation) Act 1991 (cl 5.1), the Local Government Act 1993 (cl 5.2 and definitions of public place), the Rural Fires Act 1997 (cl 5.11) and various fisheries and biodiversity Acts in relation to aquaculture (cl 5.19 and Schedule 6).

• Heritage regime overlays. The Plan intersects with the Heritage Act regime: development on land listed on the State Heritage Register or subject to interim heritage orders is excluded from exempt development (cl 3.1(3)(d)). The Plan requires Heritage Council notification for archaeological site development and State heritage demolition (cl 5.10(7), (9)). These clauses create a dual planning/heritage approval pathway.

• Native vegetation and biodiversity controls. The Plan refers applicants to SEPP(Biodiversity and Conservation) 2021 and to Local Land Services Act requirements for vegetation disturbance in the exempt development clause (cl 3.1(5) note), signalling that biodiversity and native vegetation licensing regimes continue to apply.

• Crown and public land compatibility. Clause 1.9A suspends covenants and agreements to the extent necessary to enable development under the Plan, but expressly excludes covenants imposed by the Council, certain Crown or conservation instruments (1.9A(2)(a)-(g)), and preserves public authority interests under registered instruments (1.9A(3)). Clause 5.12 reiterates that the Plan does not restrict development permitted under SEPP (Transport and Infrastructure) Chapter 2 or use of existing Crown buildings by the Crown. These provisions delineate where the Plan yields to Crown or statutory trust interests.

• Flood and coastal policy alignment. Clause 5.21 requires consideration of flood risk including projected changes due to climate change and explicitly adopts the Department’s Considering Flooding guideline as a definitional reference (cl 5.21(4)-(5)). That creates an expected alignment between local consent assessments and State flood guidance and manuals (Flood Risk Management Manual referenced). Developers must therefore align technical studies with those State documents.

• Building Code and BASIX interactions. Clauses dealing with exempt and complying development require compliance with the Building Code of Australia (cl 3.1(3)(a) and 3.2(3)(b)) and exclude contraventions of BASIX‑related standards from the exceptions to development standards (cl 4.6(8)(b)). This preserves the interaction between local planning standards and State building sustainability and construction regulatory frameworks.

Practical interaction implications

• Applicants must treat the Plan as one component of a multi‑instrument compliance task: maps and tables under the Plan, State SEPPs, the Act and its Regulations, the Building Code, heritage and biodiversity legislation, and any approvals under infrastructure, Crown or transport statutes.

• Where the Plan allows flexibility (for example under cl 4.6 exceptions to development standards), applicants will still need to comply with cross‑statutory obligations , demonstrating that a planning standard variation remains acceptable in light of heritage, biodiversity, flood and building standards.

• The Plan’s references to consultation/notification (Heritage Council, local Aboriginal communities) insert external procedural dependencies into the local consent timetable, and State policy references (flooding, aquaculture industry development plans) require alignment with State‑issued technical documents.

In short, the Plan sits within a layered statutory system: it fixes local standards and processes but expressly recognises and defers to State planning instruments and the regulatory regimes of other Acts where they apply.

The Plan carries a number of explicit amendment annotations within clause and Schedule notes. The text supplied includes those amendment references; practitioners should use them as pointers to the legislative history available in the NSW legislation database. The instrument itself records amendment entry points beside many clauses and Schedules. Highlights from the Plan’s internal amendment notes:

• General and clausal amendments recorded. Multiple clauses record amendments across several years. Examples include:

  • Clause 1.8A (savings provision) shows amendments in 2014 (Mosman Local Environmental Plan 2012 Amendment No 5, 2014 (806) Sch 1[1]), 2019 (621) Sch 5[1], and 2025 (597) Sch 6[1] (cl 1.8A annotation).
  • Clause 1.9A (suspension of covenants) notes amendment in 2019 (621) Sch 5[2]-[4].
  • Clause 4.3 (height of buildings) records amendments 2014 (806) Sch 1 [3]-[6]; 2022 (255) Sch 1[4]; 2022 (831) Sch 1.18[3].
  • Clause 4.4 (FSR) notes amendments 2014 (806) Sch 1 [8]; 2022 (255) Sch 1[6]; 2022 (831) Sch 1.18[4] [5].
  • Clause 4.6 (exceptions to development standards) amended 2022 (255) Sch 1[7] [8].
  • Clause 5.4 (controls relating to miscellaneous permissible uses) amended 2018 (406) Sch 1.93[1] [2]; 2023 (458) Sch 1[1].
  • Clause 6.6 (landscaped areas) inserted 2014 (806) Sch 1[9] and amended 2022 (255) Sch 1[10].
  • Clause 6.7 (earthworks) inserted 2022 (547) Sch 1[5].
  • Clause 6.8 (development in local centres) inserted 2022 (831) Sch 1.18[6].

• Schedule amendments. Schedule 2 carries amendment annotations across years: am 2013 (288) Sch 1[1]; 2022 (255) Sch 1[11]; 2022 (547) Sch 1[6]; 2022 (831) Sch 1.18[7]; 2023 (523) Sch 1.5. Schedule 3 and Schedule 5 contain multiple amendment entries across 2012-2018. Schedule 6 (aquaculture) and various Part/Clause insertions carry dates associated with the Fisheries Management and other Acts cited.

• Recent additions (2022-2025). Several clauses show insertion or amendment in 2022 and even 2025, notably clauses relating to zoning, height, FSR, floor space calculation, and minimum lot size exceptions (for example cl 4.1A inserted 2025 (597) Sch 6[2]; cl 4.1B and 4.1C inserted 2025 (597) Sch 6[3]). These annotations indicate ongoing local adjustments to dual occupancy, lot size and secondary dwelling policy.

• Site‑specific additions. Schedule 1 and Schedule 5 entries include historical amendment flags showing item additions and map updates through 2012-2018 and beyond (sch 5 annotations: am 2013, 2015, 2016, 2018). The Plan’s maps have been the subject of periodic updates, and the text notes that as of July 2021 map updating responsibility moved to the Department of Planning, Industry and Environment.

What to do with these notes

• Use the amendment annotations to retrieve the amending instruments. Each parenthetical reference (for example “Am 2014 (806), Sch 1[3]-[6]”) corresponds to an amending instrument that can be opened on the NSW legislation website for the full text of the changes and the precise operative dates.

• Track recently inserted clauses that materially affect development rights. For example, the 2025 insertions to minimum lot size and dual occupancy rules (cl 4.1A-4.1C) alter subdivision and dual occupancy assessment outcomes. Practitioners must confirm whether a given application is assessed under earlier or later versions per savings transitional rules (cl 1.8A).

• Be alert to map updates. Several clauses depend on maps maintained by the Department and the Plan contains notes indicating maps are to be available on the NSW Planning Portal (cl 1.7 note and Schedule 5 map notes). Map amendments may change numeric or categorical parameters without reprinting the entire LEP text.

This Amendment history section is a record drawn from the Plan’s internal annotations. For authoritative amendment texts and commencement dates consult the NSW legislation database and the specific amending instruments referenced in the clause notes.

The Plan text supplied contains no case law citations or records of judicial challenges. It names no decisions of the Land and Environment Court or appellate determinations and does not include any reported litigation outcomes.

What is absent in the Plan text

• No judicial interpretations. There are no decisions or excerpts of judicial reasoning in the instrument that would interpret clauses or resolve disputes arising from their application.

• No recorded appeals or orders. The Plan does not report any enforcement orders, injunctions, or decisions under the Act or other statutes.

Practical consequence for practitioners

• You must research case law and administrative decisions externally. Because the Plan text does not include litigation history, lawyers and advisors must search Land and Environment Court and appellate decisions to identify how specific clauses (for example cl 4.6 exceptions to development standards, cl 5.10 heritage obligations, cl 4.5 covenants preventing double dipping) have been interpreted and applied in contentious matters.

• Check for precedent on key contested topics. Likely contested areas (noted in the Plan) include: the exercise of discretion under cl 4.6 to contravene development standards, the scope and effect of covenants under cl 4.5(9)-(10), heritage assessment sufficiency under cl 5.10, and the interpretation of “environmentally sensitive areas” exclusions under cl 3.3. Because the Plan imposes process and notification duties, practitioners should seek reported decisions to guide arguments on procedural fairness and review grounds.

• Use administrative review routes. While the Plan does not list litigation steps, review and appeal mechanisms typically arise under the Act (merit review in the Land and Environment Court, judicial review in Supreme Court jurisdiction). Practitioners should identify applicable appeal timeframes and standing rules in the Act when an application is refused or conditions are imposed.

In sum, the Plan provides the statutory framework but contains no litigation history in its text; independent case law research is required to understand how its provisions have been applied and contested in practice.

This instrument contains several detailed procedural and substantive traps for the unwary. The following are specific practical pitfalls drawn from the Plan text that can affect timing, cost and the prospects of obtaining consent.

• Maps fix quantitative limits that trump textual ambiguity. Many key standards are not in the clause text but shown on maps: Lot Size Map (minimum lot size, cl 4.1(3)), Height of Buildings Map (cl 4.3(2)), Floor Space Ratio Map (cl 4.4(2)), Heritage Map and Scenic Protection Map (cl 6.4(2), Schedule 5). A plan‑preparation or due diligence exercise must include the current authoritative maps on the Planning Portal. Changes to maps can change outcomes without an amendment to the LEP text.

• Environmentally sensitive areas exclude exempt/compliant pathways. Clause 3.3 prohibits exempt or complying development in environmentally sensitive areas listed (coastal waters, coastal lakes, coastal wetlands, aquatic reserves, world heritage or Ramsar sites, land identified as high Aboriginal cultural significance or high biodiversity significance, etc). Relying on exempt or complying pathways without properly checking these overlays is a common error.

• Savings, staged amendments and which Plan applies. Clause 1.8A requires applications made before certain amendments or commencement to be determined as if the later instrument had not commenced. That means timing of lodgement affects which rules apply. The clause also records that specified 2014, 2019 and 2025 amendments carry transitional application rules. Practitioners must confirm the operative date and which instrument governs an application.

• Covenant suspension has express and important exceptions. Clause 1.9A allows agreements and covenants to be suspended to enable development under the Plan but excludes covenants imposed by Council, certain Markham Close restrictive covenants, relevant Crown Land instruments, conservation agreements under the National Parks and Wildlife Act, Nature Conservation Trust Act instruments, property vegetation plans under the Native Vegetation Act, biobanking agreements, and planning agreements. Where a covenant is protected by those exclusions it will survive Plan implementation. Also public authority rights under registered instruments are preserved (cl 1.9A(3)).

• “Double dipping” prevention via covenants can reduce developable capacity. Clause 4.5(9) authorises conditions of consent requiring covenants preventing creation of floor area on a restricted lot when development consent has been granted to a site comprised of multiple lots. That reduces the effective FSR available across a consolidated site and can be imposed at consent stage. Development proposals relying on aggregation for FSR calculations should expect such conditions as a risk.

• Heritage procedural duties can add time and cost. Where development affects archaeological sites or nominated State heritage items the consent authority must notify the Heritage Council and consider its response within 28 days (cl 5.10(7), (9)). For Aboriginal places of heritage significance the consent authority must notify local Aboriginal communities and consider responses within 28 days (cl 5.10(8)). Heritage management documents and conservation management plans may be required (cl 5.10(5)-(6)). These are potential cause of delays and additional consultancy costs.

• Flood and climate change obligations expand assessment scope. Clause 5.21 requires consent authorities to consider projected changes due to climate change when deciding flood risk compatibility and evacuation/safety measures (cl 5.21(3)(a)). Applicants must therefore align flood modelling and design responses with State guidance referenced in the clause, increasing technical assessment demands.

• Restrictions on subdivision involving secondary dwellings. Clause 2.6(2) prohibits consent for subdivision that would separate principal and secondary dwellings onto different lots unless minimum lot sizes per the Lot Size Map are met. This can trap owners who try to subdivide after adding a secondary dwelling unless the lot sizes meet mapped minima.

• Exempt development still requires compliance with other Acts and the BCA. Schedule 2 note 2 and cl 3.1(3)-(5) underline that exempt development cannot contravene the Building Code of Australia, affect State‑listed heritage items, or be designated development. Practitioners must check building classification, fire safety obligations, and other regulatory approvals even for “exempt” works.

• Local numeric limits are tight and vary by zone and site. Examples: bed and breakfast limited to no more than three rooms (cl 5.4(1)); home business and home industry floor area capped at 30 m2 each (cl 5.4(2)-(3)); neighbourhood shop retail floor area capped at 80 m2 (cl 5.4(7)). These apparently small numeric constraints can be outcome‑determinative and differ from State SEPP thresholds.

• The Plan restricts refusal grounds for music but not absolute approvals. Clause 5.20 prevents refusal on several specified grounds relating to music and entertainment, but still allows refusal on noise grounds where noise cannot be managed and minimised to an acceptable level (cl 5.20(2)). Operators should not treat cl 5.20 as a guarantee; it shifts the issue to noise management measures and proof of mitigation.

• Aquaculture rules are detailed and cross‑referenced to industry plans. Schedule 6 sets out site and operational requirements for pond/tank/oyster aquaculture and links to aquaculture industry development plans and the NSW Oyster Industry Sustainable Aquaculture Strategy (cl 5.19 and Sch 6). Aquaculture proponents must align with industry plans and the Plan’s operational constraints, including conservation exclusion zones.

• The Plan leaves key enforcement detail to the Act. Because the instrument does not set penalty levels or enforcement procedures, enforcement action (infringement notices, orders) will use the Act’s machinery; practitioners must consult the Act and Council policy for enforcement risk.

Each “gotcha” above flows directly from the text. Addressing them in a planning strategy requires careful map checks, early heritage and flood assessments, confirmation of which version of the Plan applies to the application, and expectation of covenant conditions where site consolidation is proposed.

This compliance checklist is a practical, clause‑referenced roadmap for preparing and assessing development proposals under the Plan. It organises steps in chronological order for an applicant or adviser.

1. Confirm which instrument and maps apply to the land

   • Check that the land is within the Plan’s area (cl 1.3).
   • Download and inspect the current Land Zoning Map, Lot Size Map, Height of Buildings Map, Floor Space Ratio Map, Heritage Map, Acid Sulfate Soils Map, Scenic Protection Map and any other relevant overlay maps referenced in the Plan (cl 1.7; multiple clauses referencing specific maps).
   • Verify whether any recent amending instruments changed those maps and note transitional rules in cl 1.8A.

2. Determine permissible uses and whether consent is required

   • Use the Land Use Table and zone objectives (cl 2.3 and the Land Use Table) to confirm whether the proposed use is permitted without consent, permitted with consent or prohibited.
   • If in doubt about permissibility, confirm with the Council early, since the consent authority is the Council (cl 1.6).

3. Check for exempt or complying development options

   • If the proposal seeks to use an exempt or complying pathway, confirm the proposal meets the detailed standards in Schedule 2 (exempt) or Schedule 3/State SEPPs (complying) and that the land is not an “environmentally sensitive area” as defined in cl 3.3 (cl 3.1-3.3; Sch 2-3).
   • For complying development, ensure conformance with the Building Code of Australia and any conditions referenced in sch.3‑sec General conditions (cl 3.2(3); sch.3).

4. Confirm site constraints that mandate technical studies

   • Heritage: If the land is listed in Schedule 5 or within a heritage conservation area, anticipate the need for a heritage management document or heritage conservation management plan and possible notification to the Heritage Council (cl 5.10(2), (4)-(6), (7)-(9); Schedule 5).
   • Acid sulfate soils: Where the Acid Sulfate Soils Map triggers cl 6.1, commission a preliminary assessment and, if required, an acid sulfate soils management plan prepared in accordance with the Acid Sulfate Soils Manual (cl 6.1(2)-(4)).
   • Flooding: For land in the flood planning area (cl 5.21), prepare a flood risk assessment aligned with the Considering Flooding in Land Use Planning Guideline and the Flood Risk Management Manual, addressing evacuation, compatibility with flood function, and climate‑change projections (cl 5.21(2)-(3), (4)-(5)).
   • Natural watercourses and public bushland: If the site adjoins mapped watercourses or public bushland (cl 6.2; cl 5.23), include studies or plans showing non‑impact or mitigation.
   • Scenic protection / foreshore: For land in Scenic Protection or within the foreshore area, include visual impact assessments and ensure the design maintains landform and views (cl 6.4; cl 6.3).

5. Design to mapped numerical standards

   • Ensure building height and FSR are within the maximums shown on the relevant maps (cl 4.3(2); cl 4.4(2); cl 4.4A, cl 4.4B for area‑specific rules).
   • If proposing an uplift (for example cl 4.4B Spit Junction incentives), document site consolidation, access arrangements and how the development will be compatible with desired future character (cl 4.4B(3)(a)-(d)).
   • For subdivision or dual occupancy, check Lot Size Map minimums and the specific exceptions (cl 4.1; cl 4.1A; cl 4.1B; cl 4.1C). Remember the prohibition on subdivision that separates principal and secondary dwellings unless minimum lot sizes are met (cl 2.6(2)).

6. Prepare required supporting documentation

   • For heritage matters, be ready to prepare a heritage management document or heritage conservation management plan if requested (cl 5.10(5)-(6)).
   • For earthworks or disturbance in acid sulfate soil areas, prepare an acid sulfate soils management plan or preliminary assessment as required (cl 6.1(2)-(4); cl 6.7).
   • For aquaculture, follow Schedule 6 site and operational requirements and reference relevant aquaculture industry development plans (cl 5.19; Sch 6).
   • For proposals contravening a Plan development standard, prepare the statutory clause 4.6 statement required by the Environmental Planning and Assessment Regulation showing why compliance is unreasonable or unnecessary and the environmental planning grounds that justify the contravention (cl 4.6(3) and note on the Regulation).

7. Anticipate consent conditions and potential covenants

   • Expect conditions to secure heritage conservation works where consent is granted for conservation incentives (cl 5.10(10)).
   • When applying for development on consolidated sites, expect the consent authority may require a covenant preventing creation of floor area on a “restricted lot” to prevent double dipping under cl 4.5(9)-(10). Factor registration costs and potential reduction in developable floor area into the project budget.

8. Engage early with consultees and the Council

   • Where the proposal may affect Aboriginal heritage, notify and consult local Aboriginal communities early because the consent authority must take their response into account under cl 5.10(8).
   • Anticipate the Heritage Council’s 28‑day response window for archaeological or State heritage demolition matters (cl 5.10(7), (9)).
   • Where development involves temporary use, check the 28‑day or 12‑month limits and the specific exception for sales offices (cl 2.8).

9. Ensure compliance with other statutory approvals

   • Verify whether other licences or approvals are necessary under the Heritage Act, Crown land or land management statutes, Local Government Act consents for effluent disposal (cl 3.2(3)(c)), building permits under the BCA, SEPP requirements (cl 1.9), and any transport or infrastructure approvals (cl 5.12).

10. Recordkeeping and appeal risk management

• Maintain records of discretionary assessments under cl 4.6 as the consent authority must keep a record (cl 4.6(4)).
• Ensure procedural correctness in notifications to avoid grounds for legal challenge. Procedural missteps can produce reviewable error because the Plan sets notification duties (cl 5.10(7)-(9)).

11. Post‑consent management

• If consent triggers conditions that require remedial or conservation work, ensure those works are carried out as required. Conditions for heritage conservation must be satisfied before changes are implemented (cl 5.10(10)(c)).
• When covenants are registered as conditions, ensure title documentation is updated and disclosed to purchasers and future owners.

In short, compliance under the Plan is a maps‑first exercise, followed by zone/land‑use permissibility checks, identification of technical overlays (heritage, soils, flood, scenic), preparation of supporting documents where required, and anticipation of covenants and conditions that will likely be used to secure Plan outcomes. Early engagement with Council and relevant heritage/Aboriginal stakeholders reduces procedural risk and shortens approval timelines.