The Plan rests on several organising concepts that determine land use and development outcomes.

Zones and objectives. The Plan divides land into named zones (rural, residential, employment, mixed use, special purpose, recreation, conservation and waterway zones) and sets objectives for each zone type (clause 2.1 and the Land Use Table). The Land Use Table then enumerates three classes of activity for each zone: development permitted without consent, development permitted with development consent, and prohibited development (clause 2.3(1), Land Use Table). Consent authorities must have regard to those zone objectives when deciding applications (clause 2.3(2)).

Maps and spatial rules. The Plan operates by reference to several maps which are legally operative. Examples include the Land Zoning Map, Lot Size Map, Height of Buildings Map and Floor Space Ratio Map (clauses 1.7, 2.2, 4.1(2), 4.3(2), 4.4(2)). Many controls are map‑driven: the minimum lot size, height limit and FSR vary by land as shown on maps. The Plan expressly permits maps to be electronic and to be amended in the manner set out in the Act (clause 1.7).

Consent schema and exemptions. The Plan distinguishes exempt development (development of minimal environmental impact, Schedule 2; clause 3.1) from complying development (specified in Schedule 3 and subject to compliance conditions; clause 3.2). Exempt or complying development cannot be carried out on certain environmentally sensitive areas (clause 3.3), so the spatial context determines whether the easier approval pathways are available.

Development standards and flexibility. The Plan sets out principal development standards such as minimum lot sizes (clause 4.1), special lot rules for community title schemes and split zones (clauses 4.1AA, 4.1B, 4.1C), height (clause 4.3), floor space ratio and how it is calculated (clauses 4.4-4.5). Clause 4.6 permits limited flexibility to depart from a development standard where the applicant demonstrates reasons (the usual “exceptions to development standards” mechanism), subject to explicit exclusions for certain standards and particular zones (clause 4.6(2)-(8)).

Local overlays and subject‑specific controls. Part 7 contains local provisions that apply in mapped areas or to particular activities: acid sulfate soils (7.1), earthworks (7.2), koala management (7.4), karst areas (7.5), scenic protection (7.6), airport operations and aircraft noise (7.7-7.8), essential services (7.9), and others including rural land sharing communities (7.11) and design excellence controls for identified key sites (7.12). These provisions add site‑specific criteria consent authorities must consider or require before consent is given.

Interplay with State policy and other laws. The Plan is expressly subject to State Environmental Planning Policies that prevail under the Act (clause 1.9(1)). It cross‑references other legislation and instruments repeatedly, for example the Heritage Act 1977, Rural Fires Act 1997, Crown Land Management Act 2016, Fisheries and Biodiversity legislation, and the Building Code of Australia for exempt/compliant development (see clauses 3.1, 1.9A, 5.11, 5.19 and others). Several clauses require concurrence or certification by State officers for particular consents (for example clause 4.2D requires concurrence of the Planning Secretary).

Decision‑making and duties. The Plan frames the consent authority’s duties with mandatory phrasing, e.g. “must not grant” (see flood planning clause 5.21 and many others) and “must be satisfied” (heritage cl 5.10(4); height cl 4.3). That language creates substantive hurdles applicants must overcome and identifies threshold matters the consent authority must address.

Schedules and site‑specific permissions. Schedule 1 lists additional permitted uses for particular parcels of land. Those are discrete, concentrated permissions affecting specific owners and their development possibilities (Schedule 1 clauses 1-16). Schedules 2 and 3 set out exempt and complying development types and their conditions. Schedule 6 prescribes technical requirements for pond‑based and tank‑based aquaculture (clause 5.19 and Schedule 6).

Together these concepts make the Plan a hybrid of broad zoning rules and detailed local overlay controls, implemented through mapped instruments and procedural requirements.

The Plan allocates rights, duties and practical consequences across multiple stakeholders.

Private landowners and developers. The primary effect is on owners and prospective developers within Kempsey LGA. Landholders must identify the applicable zone and overlays on the Land Zoning Map and other maps (clause 2.2 and clause 1.7), and they must comply with development standards (minimum lot sizes clause 4.1, height clause 4.3, floor space clause 4.4) and any site‑specific overlay rules (e.g. koala areas clause 7.4, acid sulfate soils clause 7.1). Applicants who rely on exempt or complying development pathways must ensure their site is not in an environmentally sensitive area (clause 3.3). Owners of particular parcels benefit from Schedule 1 additional uses; those are concentrated, parcel‑specific permissions.

Local government and consent authority. The Plan designates the Council as the consent authority (clause 1.6). Council officers must apply the Plan’s mandatory tests, consult relevant State bodies where required (for example clause 7.7 airport limits; clause 4.2D Planning Secretary concurrence), and keep records of assessments (clause 4.6(4) requires the consent authority to keep a record of an assessment under clause 4.6). Council is also empowered to classify or reclassify public land in accordance with the Local Government Act (clause 5.2).

State agencies and statutory authorities. The Plan invokes State agencies in several ways. State Environmental Planning Policies can prevail over the Plan (clause 1.9(1)). For owner‑initiated acquisitions, the Plan names acquiring authorities for certain land types on the Land Reservation Acquisition Map (clause 5.1). The Planning Secretary, Director‑General and relevant Commonwealth bodies have roles in certifying arrangements or advising on airport/airspace matters (clauses 6.1(2)-(3), 7.7(2)-(4)). The Plan also cross‑references other Acts that place duties on State agencies and limit what the Plan can do, for example Crown Land Management Act, Heritage Act and Biodiversity Conservation Act (clauses 1.9A(2), 5.10, 5.19).

Neighbouring landowners and the community. Several provisions are designed to protect neighbouring amenity and public interests: flood planning and evacuation considerations (clause 5.21), controls on intensive livestock agriculture to manage odour and water pollution risks (clause 5.18), heritage protections that require notification of the Heritage Council and Aboriginal communities (clause 5.10(7)-(9)), and limits on temporary uses to avoid neighbourhood disturbance (clause 2.8).

Registered instruments and covenant holders. Clause 1.9A temporarily suspends agreements, covenants and other similar instruments to the extent necessary to enable development consistent with the Plan, but explicitly excludes covenants imposed by Council, certain Crown instruments, conservation agreements and planning agreements (clause 1.9A(1)-(3)). In practice this affects private covenant holders and those relying on registered instruments; the Plan preserves public authority rights under registered instruments (clause 1.9A(3)).

Aboriginal communities. Heritage and Aboriginal place provisions require notification and consideration of local Aboriginal communities for developments affecting Aboriginal places of heritage significance (clause 5.10(8)). The Plan also requires certain heritage assessments and may require heritage management documents before consent is granted (clause 5.10(5)-(6)).

Users of specific facilities. Licensed premises are granted a statutory protection against refusals based on musical style, live or amplified music, number of performers, presence of a dance floor and similar considerations where noise can be managed (clause 5.20). Similarly, aquaculture operators are subject to the aquaculture standards in clause 5.19 and Schedule 6.

Overall, the Plan affects every actor who proposes to use, subdivide, build on, or otherwise change land in the mapped area. Who pays: applicants bear compliance costs for studies, management plans, infrastructure provision and application processes; neighbours may bear amenity impacts or enforcement costs; Council and State bodies bear administrative costs and decision‑making responsibilities.

Duties imposed on applicants and consent authorities. The Plan repeatedly frames obligations in mandatory terms:

• Consent requirement duties. Many activities require development consent: subdivision (clause 2.6(1)), demolition (clause 2.7), erection of dwellings in certain rural zones (clause 4.2A), and works in mapped acid sulfate soils areas unless an approved preliminary assessment confirms no management plan is required (clause 7.1(2)-(4)). Exemptions are limited and mapped (clause 3.1).

• Assessment duties. The consent authority must consider zone objectives when determining applications (clause 2.3(2)), must be satisfied of particular matters before granting consent (heritage clause 5.10(4); eco‑tourist facilities clause 5.13(3); flood planning clause 5.21(2)), and must keep a record when exercising flexibility under clause 4.6 (clause 4.6(4)). For certain heritage and Aboriginal matters, the consent authority must notify the Heritage Council or local Aboriginal communities and consider responses (clause 5.10(7)-(9)).

• Site‑specific compliance duties. Applicants proposing works in acid sulfate soils areas must prepare and provide an acid sulfate soils management plan (clause 7.1(3)). Applicants in koala areas must show consistency with the Comprehensive Koala Plan of Management for the Eastern Portion of Kempsey Shire (clause 7.4(3)). Applicants proposing pond/tank aquaculture must comply with the site location and operational requirements in Schedule 6 and relevant aquaculture development plans (clause 5.19(2)-(3)).

Rights and discretionary entitlements. The Plan creates and limits rights to develop:

• Rights to apply. Landowners retain a right to apply for development consent for uses listed as permissible with consent in the Land Use Table, subject to mapped overlays and standards (clause 2.3(1)(c)).

• Exempt and complying pathways. Where development meets the tests in Schedule 2 (exempt) or Schedule 3 (complying) and is not in an environmentally sensitive area, applicants may proceed without a full development consent process (clause 3.1-3.2). However, exempt status does not negate other statutory approvals under other Acts (clause 3.1(5) note).

• Exceptions to standards. Clause 4.6 permits the consent authority to grant consent that contravenes a development standard where the applicant satisfies the authority that compliance is unreasonable or unnecessary and there are sufficient environmental planning grounds. The consent authority must keep a record of the assessment (clause 4.6(2)-(4)). Note that clause 4.6 explicitly excludes certain standards from variation, e.g. standards for complying development, certain BASIX commitments, and specified clauses including 5.4 and 5.5 and clause 7.9 (clause 4.6(8)).

• Parcel‑specific additional uses. Schedule 1 grants additional permitted uses for particular lots (Schedule 1 clauses 1-16). These are rights that apply only to identified parcels if the Schedule conditions are satisfied.

Limits on private contractual rights. Clause 1.9A suspends covenants, agreements and similar instruments to the extent necessary to enable development in accordance with the Plan, subject to exceptions (clause 1.9A(1)-(3)). That provision reduces the enforceability of some private restrictions where they obstruct Plan‑consistent development, but it preserves Council‑imposed covenants, certain Crown instruments and planning agreements.

Procedural rights. The Plan contains savings provisions that preserve rights attached to development applications made before commencement or amendment of the Plan (clause 1.8A). For example, DAs made before commencement must be determined as if the Plan had not commenced (clause 1.8A(1)), and specified amendments do not apply to certain pending or specified concept DAs (clause 1.8A(3)).

Who decides. The Council is the consent authority (clause 1.6). For certain matters the Plan requires consultation or certification by State agencies (e.g. Planning Secretary concurrence for certain Crescent Head subdivisions clause 4.2D; Director‑General certification for urban release lot size and infrastructure arrangements clause 6.1).

In sum, the Plan creates a system of procedural duties for applicants and mandatory assessment duties for the consent authority, with limited rights for applicants to seek variation or to rely on streamlined approval pathways where mapped and technical conditions are satisfied.

The Plan itself articulates substantive prohibitions and mandatory preconditions for consent, but it does not set out novel penalty schemes. Enforcement and penalties for non‑compliance are governed by the Environmental Planning and Assessment Act and other relevant legislation rather than by express penalty provisions within the Plan text.

What the Plan does enforce by mandatory language. The Plan uses mandatory phrasing,“may only be carried out with development consent” (clause 2.7 on demolition), “development consent must not be granted” (multiple clauses including 4.6(3) and 5.21(2)), and “must be satisfied” (clause 5.10(4) on heritage). Those mandatory formulations define legal preconditions for lawful development and create a basis for enforcement action if they are breached.

Enforcement mechanism,external to the Plan. The Plan is designed to be applied through the Act. Contraventions of the Plan (for example carrying out development requiring consent without consent, or failing to comply with approval conditions) will engage the enforcement powers, offences and remedies in the Act and associated regulations. The Plan references the Act repeatedly (for example clause 1.2 references the Act, clause 1.9 identifies the effect of State policies under section 3.28 of the Act), which indicates enforcement uses the Act’s framework. The Plan does not itself list fines, orders or enforcement steps.

Specific compliance prerequisites which create actionable obligations. A number of provisions create discrete compliance steps that must be satisfied or provided to the consent authority before consent can be granted. Examples include:

• Acid sulfate soils management plan requirement before consent for works in mapped classes (clause 7.1(3)); failure to supply such a plan would prevent lawful consent and could lead to refusal or enforcement.

• Heritage notification and consultation obligations (clause 5.10(7)-(9)); failure to follow statutory notification processes may invalidate approvals or be a ground for review.

• Flood planning thresholds that must be satisfied before consent (clause 5.21(2)-(3)); non‑compliance could be a basis for refusal or for remedial orders.

Administrative records and transparency. Clause 4.6(4) requires the consent authority to keep a record of assessments carried out under clause 4.6. That creates an administrative record which is relevant to any judicial review or merits review where an applicant or third party challenges a decision.

Practical enforcement consequences. Where a person carries out development contrary to the Plan, the Act provides mechanisms such as stop work and remediation orders, fines, and building orders. Those mechanisms are not set out in the Plan text; they are part of the general enforcement regime of the Act. The Plan does narrow or expand what is permissible and so constrains what enforcement action will target.

In short, the Plan establishes the legal framework that determines lawful development, the mandatory preconditions for consent and documents required. Actual penalties and enforcement procedures are implemented through the Act and other statutory regimes the Plan references.

The Plan is embedded in a broader legal framework and makes repeated cross‑references to State policies and other Acts. The interaction is both hierarchical and operational.

Hierarchy and State policies. Clause 1.9(1) makes the Plan explicitly subject to any State environmental planning policy that prevails over the Plan under section 3.28 of the Act. That means State policies can displace Plan provisions when the policy declares itself to prevail, and the Plan must be read subject to those overriding instruments. The Plan also depends on State‑wide instruments for exempt/compliant development regimes; Schedules 2 and 3 augment but do not replace the State policy baseline (Schedule 2 note, Schedule 3 note).

Cross‑referenced statutes and operational constraints. The Plan cross‑references a number of other Acts and their regimes in ways that create substantive restrictions or prerequisites:

• Heritage Act 1977. Heritage items and conservation areas are listed in Schedule 5 and the Plan’s heritage clause requires consent for demolition and certain alterations, and it requires notification to the Heritage Council for some matters (clause 5.10). This interacts with the Heritage Act’s separate protections and processes.

• Crown Land Management Act 2016. Clause 1.9A(2) excludes certain “relevant instruments” within the meaning of s 13.4 of the Crown Land Management Act from the Plan’s covenant suspension, which preserves Crown land interests.

• Rural Fires Act 1997. Clause 5.11 authorises bush fire hazard reduction work by the Rural Fires Act without development consent, confirming that the Rural Fires Act operates alongside the Plan and can authorise certain activities.

• Fisheries, Biodiversity and other environmental laws. Clause 5.19 on aquaculture and Schedule 6 refer to aquaculture industry development plans under the Fisheries Management Act and to declared areas under the Biodiversity Conservation Act, which constrain or determine where aquaculture can occur.

• Land Acquisition (Just Terms Compensation) Act 1991. Clause 5.1 designates relevant State acquisition authorities for land shown on the Land Reservation Acquisition Map and links to owner‑initiated acquisition provisions, thereby tying the Plan into land acquisition processes.

• Local Government Act 1993. Clauses 5.2 and related Schedule 4 provisions enable classification and reclassification of public land and relieve or preserve trusts per section 30 of the Local Government Act. That provides a mechanism to reclassify reserves subject to local government processes.

• Building Code and BASIX. Exempt and complying development rely on compliance with the Building Code of Australia, and clause 4.6(8) excludes contravening development standards that arise from BASIX commitments. This connects the Plan to building safety, sustainability and energy/water efficiency regulation.

Operational concurrency and certification. Some provisions require or invite State concurrence or certification before consent is granted. For example, clause 4.2D requires the concurrence of the Planning Secretary before subdivision of designated Crescent Head land and clause 6.1 requires the Director‑General to certify adequate arrangements for designated State public infrastructure in urban release areas. Clause 7.7 requires consultation with the relevant Commonwealth body where development will penetrate airspace limitation surfaces for Kempsey Airport.

Maps and technical guidelines. The Plan regularly incorporates or refers to external technical guidelines and manuals: the Considering Flooding in Land Use Planning Guideline is used in the flood provisions (clause 5.21(4)-(5)), and the Acid Sulfate Soils Manual is required to prepare management plans (clause 7.1(3)). Those references make the Plan operationally dependent on technical guidance maintained outside the Plan itself.

Savings and temporal interaction. Clause 1.8A contains savings provisions that require certain DAs made before commencement of the Plan or of State policies to be determined under the prior regime. That limits retroactive effect and preserves certain pre‑existing rights.

In sum, the Plan operates as part of a network of State and Commonwealth laws, interlocking with heritage, water, biodiversity, crown land and building regimes. Practitioners must read the Plan alongside these other instruments, not in isolation.

The Plan carries internal amendment annotations attached to a number of clauses and schedules. The instrument has been amended multiple times since commencement, and the text records the year and instrument references for many amendments. The Plan commenced on 3 February 2014 (clause 1.1AA).

Select notable amendments recorded in the Plan text (clause references and the amendment annotations as recorded):

• Clause 1.8A (savings relating to development applications) was amended over time (annotations: Am 2019 (621), Sch 5[1]; 2023 (609), Sch 1.1[1]; 2024 (229), Sch 1[1]). The clause now includes specific non‑application of Amendment No 33 to certain applications and identifies particular concept DA exclusions.

• Zones and zone list. Clause 2.1 shows amendments to the list of land use zones (annotation: Am 2017 (487), Sch 1[1]; 2022 (828), Sch 1.11[1]). The Land Use Table itself bears a long amendment history (amendments recorded across 2016-2023 at the head of the Land Use Table).

• Community title and lot size rules. Clause 4.1AA (minimum subdivision lot size for community title schemes) was inserted or amended in 2022 (annotation: Am 2022 (828), Sch 1.11[3]). Clauses 4.1A and 4.1B (exceptions and split zone rules) were inserted in 2020 and 2022 respectively (annotations: cl 4.1A Am 2020 (589), cl 4.1B Am 2022 (828), Sch 1.11[4]).

• Erection of dwelling houses and rural worker dwellings. Clause 4.2A has amendments recorded from 2017, 2022 and 2023 (annotation: Am 2017 (254), Sch 1[1]-[3]; 2022 (828), Sch 1.11[6] [7] [7A] with 2023 insertion). Clause 4.2B was also amended in 2022.

• Exceptions to development standards. Clause 4.6 shows amendment (annotation: Am 2017 (254), Sch 1[6]).

• Exempt, complying and overlay provisions. Part 3 Schedule 2 and Schedule 6 include multi‑year amendments (see headnotes: sch 2 Am 2017 (726); Sch 6 references; various amendments noted in clause footnotes).

• Flood and special flood considerations. Clause 5.21 (Flood planning) and clause 5.22 (Special flood considerations) bear recent updates; clause 5.22 was substantiated in 2023 (annotation: Subst 2023 (609), Sch 1.13).

• Heritage, koala, karst, scenic and airport provisions. Multiple local provisions have been amended or inserted over time; for example clause 7.12 (Design excellence for South West Rocks) was inserted 2024 (annotation: Ins 2024 (229), Sch 1[2]). Clause 7.4 (Koala habitat) applies a 2011 CKPoM as a required instrument and was referenced/updated (see clause annotations).

• Schedule and map changes. The Plan notes that maps may be amended or replaced and that maps are to be made available on the NSW Planning Portal (clause 1.7). Many schedule heads and clause annotation lines show years 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023 and 2024.

This instrument records the amendment provenance at the foot of many clauses (for example cl 1.8A, cl 4.1AA, cl 4.1B, cl 4.6, cl 5.22, cl 7.12). Practitioners must read the clause annotations to identify when particular rules were introduced or modified and to determine transitional savings (e.g. clause 1.8A).

To assess the current operative content you must rely on the most recent consolidated version available from the NSW legislation site and note the amendment annotations attached to relevant clauses and schedules in the instrument.

The Plan text supplied does not record any judicial or tribunal decisions that interpret or challenge its provisions. The instrument itself is a statutory planning instrument and does not include a litigation history or a register of challenges. Where decisions have been made under the Plan, those decisions would appear in administrative records, council minutes, and in case law reported by courts and tribunals.

If legal risk or precedent matters for a particular project, a practitioner should search administrative appeal records (for example the NSW Land and Environment Court and Planning Panels), judicial review records and any published decisions that reference the Plan or specific clauses (for example decisions engaging clause 4.6 exceptions to standards, heritage clause 5.10, flood planning clause 5.21, or noise/music protections clause 5.20). The Plan itself does not identify leading cases or decisions; it references procedural and substantive statutory tests that have been the subject of court interpretation but it does not name cases.

In short, there is no litigation history contained within the Plan text. For project‑specific litigation exposure or appellate decisions interpreting the Plan, search the Land and Environment Court, state administrative tribunal records and commercial legal databases for decisions citing the Kempsey Local Environmental Plan 2013 and the clauses of interest.

This Plan contains a number of traps for the unwary. These are concrete technical and procedural features that commonly lead to delay, extra cost, or refused applications.

Reliance on maps. Many critical rules are map‑driven: zoning, minimum lot size, height limits, FSR, heritage conservation areas, koala management areas, acid sulfate soils classes and other overlays (clauses 1.7, 2.2, 4.1(2), 4.3(2), 4.4(2), clause 7.1(2), clause 7.4(2)). A mistaken assumption about a map or reliance on an outdated map can render an application non‑compliant. Practitioners should check the current Land Zoning Map, Lot Size Map and overlay maps on the NSW Planning Portal before advising clients.

Exempt/compliant pathways excluded in sensitive areas. Schedule 2 and Schedule 3 can allow development to proceed in a streamlined fashion, but clause 3.3 states that exempt or complying development must not be carried out on any “environmentally sensitive area for exempt or complying development”, a term that includes coastal waters, coastal wetlands, mapped high Aboriginal cultural significance and high biodiversity significance areas and land reserved under national parks and other Acts. Assuming an easy pathway without verifying overlay status is a frequent error.

Covenant suspension exceptions. Clause 1.9A suspends agreements or covenants to the extent necessary for Plan‑consistent development, but it excludes covenants imposed by Council, relevant Crown instruments under the Crown Land Management Act, conservation agreements, Trust agreements and planning agreements (clause 1.9A(2)). Developers should not assume a free pass over all private covenants; many public and conservation instruments remain in force.

Limitations on applying clause 4.6. The exceptions to development standards in clause 4.6 are powerful but limited. Clause 4.6(8) bars use of clause 4.6 to contravene development standards for complying development, standards arising from BASIX commitments, clause 5.4 (local controls such as bedroom limits for bed and breakfasts etc.), clause 5.5, 4.2C, 6.1, 6.2 or 7.9 (essential services). Attempting to rely on clause 4.6 to avoid these excluded standards will fail.

Heritage and Aboriginal consultation requirements. Clause 5.10 requires the consent authority to notify the Heritage Council or local Aboriginal communities in many circumstances and to take responses into account (clauses 5.10(7)-(9)). Failing to undertake the required consultation or to allow sufficient time for responses can invalidate approvals or delay decisions.

Savings and transitional rules. Clause 1.8A contains detailed savings for DAs made before commencements or amendments. A development application lodged before an amendment might be determined as if the amendment did not apply (clause 1.8A(1)-(3)). Misreading the temporal effect of amendments is a common client risk.

Specific parcel permissions. Schedule 1 creates concentrated benefits for particular landowners by permitting additional uses on identified lots (Schedule 1 clauses). Those permissions do not extend generally and are subject to conditions; clients must check schedule items rather than assume broad applicability.

Flood and special flood considerations. Clause 5.21 and 5.22 impose substantive compatibility and risk assessments in mapped flood planning areas and lands between the flood planning area and probable maximum flood. The consent authority must be satisfied of specific flood‑related matters (clause 5.21(2) and clause 5.22(3)); failure to address these in a DA can lead to refusal.

Airport airspace and noise controls. Clauses 7.7 and 7.8 require consultation with the relevant Commonwealth body where development penetrates limitation surfaces and impose noise design standards based on ANEF contours and AS 2021,2000 for developments likely to be affected by aircraft noise. Applicants near Kempsey Airport must allow time and cost for noise attenuation design and Commonwealth consultation.

Canal estate prohibition. Clause 2.9 prohibits canal estate development as defined, a specific prohibition that may block developments that involve canals, raising or excavation to create waterways. Don’t assume waterfront housing with canals is permissible.

Limits on subdividing where secondary dwellings exist. Clause 2.6(2) expressly forbids subdivision that separates secondary dwellings from the principal dwelling unless minimum lot sizes are met. That affects many rural and residential small‑lot plans.

Temporary use limits. Temporary use is capped at 52 days in any 12 month period unless it is a sales office for a new release area, which is an exception (clause 2.8). Promoters of events or pop‑ups must watch the limit.

Agriculture and intensive livestock thresholds. Clause 5.18 creates thresholds under which certain intensive livestock activities may proceed without consent, but with strict location restrictions (distance from dwellings, waterways and other farms). Those thresholds are technical and must be applied carefully.

These “gotchas” are concrete sources of cost, delay, or refusal because they either narrow approval pathways, introduce consultation requirements or attach hard map‑based constraints. Practitioners should run a mapping and overlay check early, confirm any parcel‑specific Schedule 1 rights, and identify required technical studies (heritage, flood, acid sulfate soils, noise, koala plans, aquaculture plans) at project scoping.

Practical, step‑by‑step compliance advice grounded in the Plan’s provisions.

1. Identify zoning and overlays at the earliest stage. Use the Land Zoning Map, Lot Size Map, Height of Buildings Map, Floor Space Ratio Map, Heritage Map and other overlay maps referenced in the Plan (clauses 1.7, 2.2, 4.1(2), 4.3(2), 4.4(2), clause 5.10 and Part 7). The Plan’s permissions and constraints are map‑specific.

2. Check the Land Use Table. Confirm whether the proposed use is permitted without consent, permitted with consent or prohibited in the relevant zone (clause 2.3 and the Land Use Table). If the use is prohibited, do not lodge a DA expecting consent.

3. Determine whether the proposal is exempt or complying. Consult Schedule 2 (exempt) and Schedule 3 (complying) and the environmental context. If the site is an “environmentally sensitive area for exempt or complying development” (clause 3.3), exempt/compliant pathways are not available. For complying development that contravenes standards, remember the limitations set by clause 4.6(8).

4. Identify mandatory technical studies. Based on overlays, determine whether the DA must include heritage assessments or a heritage management document (clause 5.10(5)-(6)), an acid sulfate soils management plan (clause 7.1(3)), flood and evacuation assessments per clause 5.21 and 5.22, koala plan compliance per clause 7.4(3), karst assessments under clause 7.5, and aquaculture site/operational compliance per clause 5.19 and Schedule 6.

5. Address infrastructure and services. Clause 7.9 requires demonstration that essential services (water, electricity, sewerage, stormwater, vehicular access) are available or that adequate arrangements exist. For urban release areas, certification of arrangements for designated State public infrastructure by the Director‑General is required before some subdivisions (clause 6.1).

6. Consider heritage and Aboriginal consultation obligations early. If the site contains heritage items or is within a heritage conservation area or an Aboriginal place of heritage significance, notify the Heritage Council or local Aboriginal communities as required and allow time for responses (clause 5.10(7)-(9)). Prepare heritage impact statements and management plans where requested (clause 5.10(5)-(6)).

7. For any proposed contravention of a development standard, prepare the clause 4.6 justification. Clause 4.6 requires a demonstration that compliance is unreasonable/unnecessary and that sufficient environmental planning grounds exist. The EP&A Regulation requires a supporting document for such applications (note under clause 4.6(3)). Keep a full record of the assessment for the consent authority (clause 4.6(4)).

8. Check for parcel‑specific Schedule 1 permissions. If the subject land is listed in Schedule 1, determine whether the additional permitted use applies and whether any Schedule conditions must be satisfied (Schedule 1 items 1-16).

9. Appraise timing and transitional rules. If a development application was lodged before a Plan amendment or forthcoming State policy, check clause 1.8A for savings and transitional treatment. Identify whether proposed amendments, such as Amendment No 33 referenced at clause 1.8A(3), affect the DA.

10. Consult Commonwealth or State bodies where required. For developments affecting the Kempsey Airport Limitation or Operations Surface seek the relevant Commonwealth body’s advice and allow for potential refusal if penetration is opposed (clause 7.7). For urban release subdivisions with State infrastructure implications arrange the Director‑General’s certification per clause 6.1.

11. Manage covenants and registered interests. If private covenants are relevant, consider clause 1.9A which may suspend certain covenants to enable Plan‑consistent development, but review the exceptions in clause 1.9A(2). Also check whether the land is subject to any public authority registered interests which the clause saves (clause 1.9A(3)).

12. Design to avoid excluded provisions. For matters explicitly excluded from clause 4.6, such as BASIX obligations, complying development standards and specified clauses including 5.4 and 7.9, ensure the design complies rather than seeking a variance (clause 4.6(8)).

13. Build the record. The consent authority must be satisfied on many threshold matters. Provide clear, site‑specific evidence and management strategies addressing environmental impacts, amenity effects, evacuation and flood safety, heritage conservation, biodiversity and agriculture compatibility as required by relevant clauses (for example 5.21, 5.10, 5.13, 7.5). Where the Plan authorises consent subject to conditions, prepare to accept covenant or condition obligations to prevent “double dipping” in FSR calculations (clause 4.5(9)-(10)).

14. Prepare for appeals and reviews. Because the Plan sets mandatory tests and the clause 4.6 flexibility requires careful reasoning, if a decision is adverse prepare for merits and judicial review processes with a clear record of the environmental planning grounds relied on and the public interest case.

Who decides and who pays. The Council decides most consents (clause 1.6). Applicants bear the direct costs of technical studies, management plans, heritage investigations, noise attenuation design, acquisition or infrastructure contributions where required and the administrative costs of the application. State and Commonwealth agencies may require additional steps in particular cases and are accountable to their own statutory review mechanisms.

Compliance risk management. Early mapping checks, a preliminary planning and environmental due diligence package, and early engagement with Council and any relevant State agency (Planning Secretary, Director‑General, Commonwealth aviation authority) will reduce implementation risk and avoid wasted application costs.

This compliance pathway is built from the Plan’s clauses: zoning and maps (clauses 1.7, 2.2); permitted/consent/prohibited uses (clause 2.3 and the Land Use Table); exempt/compliant tests (clauses 3.1-3.3 and Schedules 2-3); technical and overlay requirements (Part 4 and Part 7); and procedural requirements for certification, concurrence and records (clauses 4.6, 4.2D, 6.1, 5.10).