The Plan’s dominant organising concepts are zoning, mapped development standards, overlay constraints and site‑specific exceptions. Key concepts and how the Plan implements them:

• Zoning and Land Use Table (cl 2.1-2.3; Land Use Table): Zoning classes are listed (R, E, RU, MU, SP, RE, C, W). The Land Use Table paired with zone objectives specifies for each zone what is: permitted without consent, permitted with consent and prohibited. The consent authority must have regard to zone objectives when assessing applications (cl 2.3(2)). The Plan also allows additional permitted uses for particular mapped lots (cl 2.5; Schedule 1).
• Maps and spatial controls (cl 1.7; cl 2.2; numerous references): The Plan delegates many key standards to maps (Land Zoning Map, Lot Size Map, Height of Buildings Map, Floor Space Ratio Map, Terrestrial Biodiversity Map, Riparian Lands and Watercourses Map, Heritage Map, Sun Access Protection Map, Land Reservation Acquisition Map). The text alone does not determine permissibility without consulting the maps (cl 1.7(1) and cl 2.2).
• Development consent as gatekeeper: The Plan specifies many actions that require development consent (e.g., subdivision cl 2.6, demolition cl 2.7, development below mean high water mark cl 5.7, many local provisions in Part 7). Where development is exempt or complying, Schedules 2 and 3 and cl 3.1-3.2 set the conditions.
• Overlay‑style environmental and hazard controls (Part 7; cl 5.21-5.22): the Plan requires the consent authority to be satisfied of particular environmental/hazard outcomes for certain land (e.g., biodiversity cl 7.4, riparian cl 7.6, acid sulfate soils cl 7.1, flood planning cl 5.21). These are not mere matters for consideration but in many cases are threshold constraints to consent (e.g., cl 7.1(3) requires an acid sulfate soils management plan).
• Development standards and exceptions (Part 4): minimum lot sizes (cl 4.1 and related clauses 4.1AA-4.2D), building heights (cl 4.3), floor space ratios and their calculation (cl 4.4-4.5). Clause 4.6 provides the process for exceptions to development standards subject to demonstrating unreasonable or unnecessary compliance and recording the assessment.
• Local design and amenity controls (cl 7.12 design excellence; cl 7.20 sun/shadow protections for particular public places; cl 7.21 minimum building street frontage for tall buildings): the Plan embeds precise local urban design expectations as conditions for consent.
• Site‑specific permissions and caps: Schedule 1 contains parcel‑specific additional permitted uses (for example, permitted uses and floor area caps for specific lots, cl 1-23 of Schedule 1). The Plan therefore combines town‑wide rules with granular parcel exceptions.

The Plan makes clear that State environmental planning policies can prevail where specified by the Environmental Planning and Assessment Act (cl 1.9(1)). The Plan also excludes certain SEPPs or provisions if so listed (cl 1.9(2)), although the reproduced text here does not include the list content.

The Plan uses mandatory phrasing (“must not”, “must”) for threshold matters (e.g., cl 2.6(1) subdivision only with consent, cl 2.7 demolition only with consent, cl 4.3 height limits not to be exceeded; cl 5.21(2) flood planning prohibits consent unless satisfied). That language creates hard limits in many cases.

Finally, the Plan contains express transitional/savings and conflict rules: DAs made prior to commencement are to be determined under the previous instrument (cl 1.8A), and this Plan prevails over other local instruments for land to which it applies (cl 1.8 repeal provision and cl 6.4 where Part 6 prevails to extent of inconsistency).

The Plan affects multiple actor groups, and the instrument’s clauses identify or imply who pays, who decides and who must change behaviour:

• Landowners and developers: Their rights to subdivide, build, demolish, change use or operate specific uses are shaped by zones, maps and provisions. For example, subdivision is permitted only with development consent (cl 2.6), and minimum lot sizes, strata and community title rules limit subdivision outcomes (cl 4.1, 4.1AA, 4.2C). Site‑specific additional permitted uses in Schedule 1 confer explicit opportunities to particular landowners.
• The Council (consent authority): Identified as the consent authority for this Plan (cl 1.6). The Council decides development applications, must be satisfied about flood, heritage, biodiversity, design excellence and other requirements before granting consent (see cl 5.21, cl 5.10, cl 7.4, cl 7.12), and must keep records of assessments (cl 4.6(4)).
• The broader community and adjoining landowners: The Plan directs impacts on amenity and service provision. For instance, temporary events on public reserves and roads are permitted without development consent but subject to other approvals (cl 7.18), and provisions like cl 5.21 require that development not adversely affect evacuation routes or increase flood risk to other properties.
• Specific State agencies and authorities: Where federal or State interests are engaged the Plan requires consultation or identifies the relevant acquiring authority (cl 5.1, cl 7.9 regarding consultation with the relevant Commonwealth body for airspace penetration). Part 6 requires certification by the Director‑General for designated State infrastructure arrangements in urban release areas (cl 6.1(2)).
• Special interest economic actors: The Plan sets industry‑specific rules. Aquaculture operators face detailed site and operational controls in cl 5.19 and Schedule 6 (species selection, containment, discharge controls). Intensive livestock operations have threshold exemptions and locational constraints (cl 5.18(4)-(5)). Industrial and commercial operators face gross floor area caps in Zones E3 and MU1 (cl 7.14).
• Heritage and Aboriginal interests: The Plan requires consent for work affecting heritage items, archaeological sites or Aboriginal places (cl 5.10(2)-(9)), and mandates notification and consultation steps (cl 5.10(7)-(9)).
• Owners bound by private instruments: Clause 1.9A suspends covenants, agreements and similar instruments to the extent necessary to enable development under the Plan, but excludes covenants imposed by the Council and a defined list of conservation or statutory instruments (cl 1.9A(1)-(3)). This directly affects holders of private restrictive instruments.

Who pays and who benefits, as derived from the Plan:

• Concentrated beneficiaries: Schedule 1 additional permitted uses confer explicitly identifiable development opportunities to named land parcels. Those owners gain direct benefits when a use is permitted (e.g., retail, hospitality or tourist uses with defined floor area caps).
• Diffuse public costs and benefits: The Plan’s public aims (cl 1.2),heritage protection, biodiversity, flood resilience, urban amenity,are public goods that the wider community may receive benefits from, but which impose transaction, compliance and construction costs on applicants through required management plans, design obligations and infrastructure provision (see clls 5.10, 7.1, 6.1-6.3).
• Development‑cost impacts on private actors: Requirements for management plans (acid sulfate soils, heritage management documents, aquaculture operational plans), design excellence (cl 7.12) and infrastructure contributions/certifications (cl 6.1-6.3) increase the compliance costs developers must bear before obtaining consent.

Geographic focus: The Plan’s legal effect is map‑based; many controls rely on the Plan’s maps rather than only textual zoning (cl 1.7, cl 2.2), so affectedness varies parcel by parcel. Practitioners must therefore consult the Plan’s maps and schedules for parcel‑level outcomes.

The Plan creates a set of duties on the consent authority and obligations/rights for applicants and landowners. Key duties and rights include:

Duties of the consent authority (Council)

• To have regard to zone objectives when determining applications (cl 2.3(2)).
• To be satisfied of specific environmental, heritage, design and hazard matters before granting consent: e.g., biodiversity (cl 7.4(4)), riparian land (cl 7.6(4)), acid sulfate soils management plan requirement (cl 7.1(3)), flood planning (cl 5.21(2)), design excellence (cl 7.12(3)). Many of these are expressed as preconditions to consent.
• To consult specified bodies and notify Aboriginal communities for heritage matters where required (cl 5.10(7)-(9)).
• To keep a record of assessments made under cl 4.6(3) where an exception to a development standard is sought (cl 4.6(4)).
• To require preparation of local development control plans for certain areas and to rely on those DCPs where the Plan requires them before consent is granted (cl 6.3(2)-(3); cl 7.19(3) for a particular site).

Rights and constraints on landowners and applicants

• Right to carry out development that is permitted without consent, subject to the Plan’s exempt development standards (cl 3.1; Schedule 2), and subject to compliance with the Building Code of Australia and other statutory approvals (cl 3.1(3)(a)-(b)).
• Right to apply for development consent where development is permitted with consent, and for the consent authority to consider the application against the Plan’s provisions and relevant State policies (cl 2.3; cl 1.9).
• Subdivision rights are constrained: subdivision only with consent (cl 2.6(1)); special minimum lot size rules and exceptions apply (cl 4.1, 4.1AA, 4.1A, 4.1B, 4.2-4.2E).
• Entitlement to a complying development certificate for development meeting Schedule 3 conditions (cl 3.2), where the development is listed and meets the stated standards.
• Duty to prepare and provide specialist management plans where required: acid sulfate soils management plan (cl 7.1(3)); heritage management documents or heritage conservation management plans where requested (cl 5.10(5)-(6)); management strategies for eco‑tourist developments (cl 5.13(3)(k)).
• Where a development standard would be contravened, an applicant may seek consent under cl 4.6 but must demonstrate compliance with cl 4.6(3) (that compliance is unreasonable or unnecessary and there are sufficient environmental planning grounds), and the consent authority must record its assessment (cl 4.6(4)).

Specific duty‑right interactions that materially change practice:

• Suspension of covenants (cl 1.9A) alters the operation of private restrictions: parties relying on private covenants may find those covenants do not operate to prevent development authorised by the Plan, subject to enumerated exceptions (cl 1.9A(2)).
• Savings for pending DAs (cl 1.8A) preserve the application of earlier instruments to applications made before the Plan’s commencement.
• The Plan grants the consent authority the power to permit development that contravenes a development standard subject to the applicant meeting cl 4.6 tests, thereby providing a procedural path to variances while creating a recording duty on the authority (cl 4.6(3)-(4)).

Rights not established in the Plan

• The Plan does not itself create criminal sanctions or specify fines; enforcement mechanisms and penalties are matters dealt with under other statutes (the Plan repeatedly references the Act and other laws). The Plan creates consenting and assessment duties but does not contain a schedule of offences or penalties in the reproduced text.

The Plan sets procedural and substantive constraints but the reproduced text does not itself contain an explicit penalty schedule. The enforcement régime implied by the Plan must be read together with the Environmental Planning and Assessment Act and other statutes referenced. Specific enforcement design elements in the Plan:

• Consent authority role and discretion: The Plan designates the Council as the consent authority (cl 1.6). The Council’s functions include determining development applications, imposing conditions and requiring management plans or DCPs before consent (see cl 2.3, cl 5.10, cl 6.3). The authority to refuse consent is embedded throughout where mandatory conditions are not met (for example, cl 5.21 prohibits granting consent for development in a flood planning area unless the authority is satisfied of particular matters).
• Procedural preconditions and mandatory refusals: The Plan contains mandatory prohibitions and threshold constraints which function as hard enforcement levers. For instance, canal estate development is expressly prohibited (cl 2.9(1)), and cl 4.3 says the height of a building is not to exceed the maximum on the Height of Buildings Map. Where the Plan says “must not be granted” (e.g., cl 4.6(6) on exceptions for rural subdivisions), the consent authority must refuse consent in those circumstances.
• Conditions and management plans: The Plan allows the consent authority to impose conditions requiring covenants (cl 4.5(9)), heritage management works (cl 5.10(10)), or time‑limited consents (Schedule 1 cl 20 requires landscaping material supplies site to cease after 30 years). Non‑compliance with consent conditions will be enforced under the Act and associated regulatory mechanisms.
• Exempt/complying development enforcement: Schedules 2 and 3 set technical conditions for exempt and complying works. Exempt development is “without the need for development consent” (cl 3.1) but remains subject to other statutory approvals and controls; the Plan notes that such development is not exempt from licences or approval under other Acts (Schedule 2 note).
• Interaction with other enforcement regimes: The Plan regularly cross‑refers to other legislation where enforcement powers are located (e.g., Heritage Act 1977 for State heritage matters at cl 5.10, Rural Fires Act 1997 for bushfire hazard reduction works at cl 5.11). Where the Plan excludes or defers to other Acts (cl 1.9A(3) preserves public authority rights under registered instruments), enforcement of those instruments will follow their own statutory pathways.

What the Plan does not state in the reproduced text

• It does not set out the specific penalties, infringement notices or prosecution processes. Those are matters the Plan leaves to the Environmental Planning and Assessment Act and other statutes it references. Practitioners should consult the Act for the statutory enforcement powers, offences and penalties applicable to carrying out development without consent or breaching conditions.

Implementation enforcement risks and burdens

• Many clauses create subjective satisfaction tests (the consent authority “must be satisfied” about a range of matters under clls 5.21, 7.4, 7.6, 7.12 etc.). That discretion concentrates decision power in the Council and creates legal uncertainty for applicants, and correspondingly increases the administrative burden on the Council to document and justify decisions (the Plan explicitly requires record‑keeping in cl 4.6(4)).
• The Plan’s map‑reliant approach means errors or uncertainties in map interpretation can generate disputes and enforcement queries; the Plan requires maps to be public and maintained (cl 1.7(3)-(4)).

The Plan is explicitly framed as part of a statutory system and repeatedly cross‑references other laws, instruments and guidelines. Interaction mechanisms in the text:

• State environmental planning policies (SEPPs): The Plan is subject to SEPPs that prevail over it under section 3.28 of the Act (cl 1.9(1)). The Plan also contains cl 1.9(2) which, where specified, lists SEPPs or provisions that do not apply to the land the Plan covers (the reproduced text shows the clause but not the list).
• The Environmental Planning and Assessment Act and regulations: The Plan repeatedly refers to the Act (for example cl 1.6 situates the consent authority “subject to the Act”), and to the regulations for matters such as the requirement to accompany a contravention submission with a document under the EPA Regulation (cl 4.6 note). Many of the Plan’s assessment pathways are designed to operate within the Act’s DA, CDC and complying development regimes (cl 3.2(3) and notes).
• Building Code of Australia and BASIX: Exempt and complying development must meet Building Code deemed‑to‑satisfy provisions (cl 3.1(3)(a); cl 3.2(3)(b)). Clause 4.6(8)(b) excludes BASIX commitments and related standards from being varied under cl 4.6.
• Heritage Act 1977: The Plan defers to the Heritage Act for State heritage items and interim heritage orders (cl 3.1(3)(d) and multiple cross‑references in cl 5.10). The Plan prescribes notification to the Heritage Council and requires its response to be considered (cl 5.10(7), (9)).
• Fisheries, Biodiversity and Marine management laws: Clauses concerning aquaculture (cl 5.19, Schedule 6) require consistency with aquaculture industry development plans and the NSW Oyster Industry Sustainable Aquaculture Strategy. Environmentally sensitive area definitions cross‑refer to Biodiversity Conservation Act 2016, Fisheries Management Act 1994 and other Acts (cl 3.3).
• Local Government Act 1993: The Plan authorises classification or reclassification of public land consistent with the Local Government Act (cl 5.2 and Schedule 4) and refers to the definition of public place in that Act for floor space ratio calculations (cl 4.5(11)).
• Crown land and National Parks statutes: Clause 1.9A(2) preserves the effect of certain instruments (e.g., Crown Land Management Act 2016 instruments, conservation agreements under National Parks and Wildlife Act 1974) by excluding them from the clause that suspends covenants.
• External guidelines and manuals: Flood planning clauses require consideration of external guidance: the Considering Flooding in Land Use Planning Guideline and the Flood Risk Management Manual (cl 5.21(4)-(5), cl 5.22(4)-(5)).
• Other SEPPs: The Plan’s Land Use Table notes certain SEPPs that may be relevant (e.g., SEPP (Housing) 2021 and various State SEPPs referenced in the Land Use Table note).

Practical interface consequences:

• Applicants must thread the Plan’s requirements with State policies, the Building Code/BASIX and relevant specialist licences (e.g., fisheries or Crown land approvals). The Plan makes many consents contingent on satisfaction of external statutory regimes or guidelines (cl 5.19(3) for aquaculture, cl 7.1 referencing the Acid Sulfate Soils Manual).
• Where the Plan conflicts with or is inconsistent with an overriding SEPP, the SEPP will prevail (cl 1.9(1)), which can change permitted uses or development standards on particular sites.
• The Plan’s parcel‑specific additional uses (Schedule 1) create exemptions from zone constraints but those rights remain subject to other laws (e.g., building approvals, other statutory approvals).

The reproduced Plan text includes numerous marginal amendment notations. The Plan has been the subject of multiple legislative amendments reflected in the clause notes. The following is a source‑grounded, non‑exhaustive mapping of amendment entries as they appear in the provided text (references are the amendment citations embedded in the Plan):

• 2016 amendments: appear in many clauses (e.g., cl 1.9 amended 2016 (310) Sch 4.8; Schedule 1 and other parts amended 2016 (5), Sch 1 references). These 2016 entries reflect early post‑2013 modifications to the Plan.
• 2017 amendments: appear in the Land Use Table note (2017 (493), Sch 1.1) and Schedule 1 history (2017 (692)).
• 2018 amendments: multiple insertions and substitutions (for example, cl 4.2E was inserted 2018 (514), Sch 1 [2]; Schedule 1 history shows 2018 references; Schedule 6 references to aquaculture update in 2018 (27) and 2018 (514) appear in clauses).
• 2019 amendments: numerous and widespread. Examples in the text include Am 2019 (621), Sch 5 (savings/provisions and 1.9A amendments), 2019 (192), Sch 1 (multiple amendments to zones, exemptions, complying development), 2019 (137), Sch 6; 2019 (653), Sch 1 introduced or altered cl 4.4 and cl 7.20; 2019 (1), cl 4 amended Schedule 4.
• 2020 amendments: appear in cl 1.3 (Am 2020 (45), cl 5(1)) and cl 7.19 Subst 2020 (783), Sch 1.
• 2021 amendments: cl 4.4 amended 2021 (714), Sch 10.5; cl 7.12 amended 2021 (84), Sch 1[1]-[2]; Schedule 5 shows 2021 (84), Sch 1[3][4].
• 2022 amendments: widespread (Am 2022 (32), Sch 1[1], 2022 (314), 2022 (344), 2022 (829) Sch 1.6 has many targeted changes across the Plan including amendments indicated in cl 1.2, cl 2.1, cl 4.1AA, cl 4.1A, cl 4.1B, cl 4.2B, cl 4.2C, cl 4.6, cl 5.3, cl 7.12, cl 7.13, cl 7.14, cl 7.15-7.16, cl 7.17, cl 7.18 and others. The 2022 (829) set is cited heavily across many clauses as recent package amendments.
• 2023 amendments: appear in a number of technical insertions and substitutions (e.g., cl 4.1A substitution 2023 (124), Sch 1[1]; cl 5.21 and 5.22 were substantiated 2023 (609) and 2023 (554), and cl 7.7 repealed 2023 (435)). Other 2023 amendments include changes in Schedule 1 (2023 (124)) and Part 6 changes (2023 (554)).
• Other specific amendment citations appearing across the instrument: 2018 (406), 2018 (694), 2020 (783), 2022 (130), 2022 (567), 2022 (314) and multiple discrete amendment instruments cited in the clause notes.

What the Plan’s amendment notes show, without over‑claiming:

• The Plan has been actively updated across a sequence of amendment instruments (2016-2023 at least). The clause‑level notes record which statutory instruments made particular changes. The textual record supplied includes amendment citations for particular clauses; those citations identify when the Plan text was altered and by which amending instrument, as shown in the clause footnotes.

Limitations of this summary

• The reproduced text includes amendment markers but does not compile a consolidated amendment chronology. Users wishing to trace the complete legislative history should inspect the NSW legislation database for the Plan and each cited amending instrument listed in the clause notes (for example 2019 (621), 2022 (829), 2023 (609) and others referenced in clause notes).

The provided Plan text contains no judicial decisions, case law or litigation summaries. The Plan names no court judgments. Therefore, there is no litigation history recorded in the instrument as provided.

Practitioners seeking litigation history should:

• Search public law and planning case databases for proceedings that reference “Coffs Harbour Local Environmental Plan 2013” or relevant land parcels, DAs and consent decisions.
• Check administrative review outcomes (if any), Land and Environment Court decisions for judicial review or merits appeals, and any reported decisions that interpret specific Plan provisions (for example, disputes about the exercise of satisfaction/discretion under cl 5.21, cl 7.4 or cl 4.6).

Because the Plan vests broad discretionary assessment duties in the consent authority, common litigation themes to investigate (not contained in the Plan but typical in planning practice) are likely to include interpretation of “satisfied” tests, the scope of discretionary exceptions under cl 4.6, adequacy of heritage or biodiversity assessments, and correct application of mapped controls. The Plan itself does not provide examples or binding authorities.

This Plan contains multiple technical traps for practitioners and potential implementation risks. The following are specific, source‑grounded items to watch:

1. Maps are decisive, but not reproduced in the text

   • Many controls are map‑dependent: zoning (cl 2.2), lot size minimums (cl 4.1), heights (cl 4.3), FSR (cl 4.4), biodiversity overlays (cl 7.4), riparian land (cl 7.6), heritage areas (cl 5.10) and sun access areas (cl 7.20). Always consult the Plan’s maps (cl 1.7(1) and notes). Failing to reference the maps can lead to incorrect assumptions about permissibility.

2. Savings for pending applications and policy timing

   • Applications made before the Plan’s commencement are to be determined as if the Plan had not commenced (cl 1.8A(1)). A DA lodged before a relevant SEPP or amendment may therefore proceed under the prior instrument. Practitioners must check the DA lodgement date and the commencement dates of amendments.

3. Suspension of covenants (cl 1.9A)

   • Clause 1.9A suspends private covenants to the extent necessary to enable development under the Plan, but excludes covenants imposed by Council and several conservation instruments (cl 1.9A(2)). This can alter the enforceability of private restrictions and may surprise holders of third‑party rights. Also cl 1.9A(3) preserves public authority rights under registered instruments.

4. Exclusions and “not adopted” clauses

   • Several clauses are marked “[Not adopted]” (e.g., cl 5.5, cl 5.9, cl 5.14, cl 5.15, cl 5.23). Relying on their headings alone is hazardous; the operative text is absence. Confirm whether those topics are governed by other instruments or local policies.

5. The difference between “permitted without consent”, “exempt development” and “complying development”

   • Exempt and complying development have specific technical tests (cl 3.1-3.2 and Schedules 2-3) including compliance with Building Code provisions and other approvals. A use listed as “may be carried out without development consent” in the Land Use Table is nevertheless subject to Part 5 of the Act (note after cl 2.3) and other approvals. Confirm whether a proposal is truly exempt or whether a CDC is needed.

6. Clause 4.6 exceptions to development standards require documentary proof and a record

   • If an applicant seeks consent that contravenes a development standard, cl 4.6(3) requires demonstration that compliance is unreasonable or unnecessary, and cl 4.6(4) requires the consent authority to keep a record of its assessment. The EPA Regulation requires a supporting document to accompany the DA. This creates an evidentiary burden and a formal record that can be challenged.

7. Site‑specific caps and time limits in Schedule 1

   • Schedule 1 often contains precise caps (gross floor areas, heights, expiration dates). For instance, cl 20 of Schedule 1 requires a landscaping materials supply use to cease within 30 years and imposes removal obligations. These are hard constraints specific to parcels that can materially affect project economics.

8. Heritage and Aboriginal consultation thresholds

   • For archaeological sites not on the State Register the consent authority must notify the Heritage Council and consider its response within 28 days (cl 5.10(7)); for Aboriginal places the Plan requires notification of local Aboriginal communities and consideration of responses (cl 5.10(8)). Failure to observe these steps can invalidate consents or lead to judicial review.

9. Flood planning and climate change inputs

   • Clauses 5.21-5.22 require consideration of projected climate impacts and external guidelines (Considering Flooding in Land Use Planning Guideline and Flood Risk Management Manual). Applicants must integrate those external technical standards into designs and approvals.

10. Double‑dipping and FSR calculations

    • Clause 4.5 contains detailed rules to avoid “double dipping” in FSR calculations (subclauses (3)-(11)). A consent may require covenants that restrict creation of floor area on a particular lot (cl 4.5(9)-(10)). Practically, project finance and land assembly plans must account for these covenanting mechanisms.

11. Performance tests are numerous and subjective

    • Many clauses use “must be satisfied” or similar language (e.g., cl 5.21(2), cl 7.4(4), cl 7.12(3)). This gives Council broad judgement and increases the need for comprehensive evidence sets (heritage, biodiversity, flood, acoustics for airport noise, acid sulphate soils assessments).

12. Prohibitions that are not obvious: canal estates

    • Canal estate development is expressly prohibited (cl 2.9). The clause also contains a technical definition that captures filling/excavation in tidal/inundated contexts for residential development, so proponents of waterfront residential projects must be certain their proposal is not caught.

13. “Not specified” gaps

    • Clause 1.9(2) indicates some SEPPs do not apply but the reproduced text leaves that list blank. Confirm the full instrument text to identify which SEPP provisions are excluded.

14. Parcel specific heritage listings and conservation areas

    • Schedule 5 lists many heritage items and conservation areas. Proposals affecting those parcels face mandatory heritage assessment obligations (cl 5.10). Practitioners must check Schedule 5 entries against site titles.

A practical compliance roadmap grounded in the Plan text:

1. Start with maps and zone classification (cl 1.7; cl 2.2)

   • Identify the parcel on the Plan’s Land Zoning Map, Lot Size Map, Height of Buildings Map, Floor Space Ratio Map and any overlay maps (biodiversity, riparian, heritage, sun access). The Plan’s operative rules are map-dependent (see cl 1.7(1), cl 2.2 and numerous clauses referring to maps).

2. Check the Land Use Table and Schedule 1 (cl 2.3; Schedule 1)

   • Determine whether the proposed use is permitted without consent, permitted with consent or prohibited in the parcel’s zone. If the parcel is listed in Schedule 1, review the parcel‑specific additional permitted uses and limits (Schedule 1 clauses often contain caps and conditions).

3. Determine whether the development is exempt or complying (Part 3; Schedules 2-3)

   • If you are relying on exempt or complying development, confirm the proposal meets the technical requirements of Schedule 2 (exempt) or Schedule 3 (complying) and the Building Code of Australia (cl 3.1(3)(a) and cl 3.2(3)(b)). For complying development, check Part 2 conditions and the cross‑reference to State Policy (Schedule 3 note).

4. Where development consent is required, identify mandatory thresholds and prepare required supporting documentation

   • If triggers exist such as acid sulphate soils (cl 7.1(2)-(3)), heritage items or conservation areas (cl 5.10(2)-(6)), biodiversity (cl 7.4), riparian lands (cl 7.6) or flood planning (cl 5.21-5.22), prepare the relevant specialist management plans and assessments. The Plan makes submission of these documents a precondition to consent in many cases (e.g., cl 7.1(3) requires an acid sulfate soils management plan prepared in accordance with the Acid Sulfate Soils Manual).

5. For standards likely to be exceeded, prepare an exceptions case under cl 4.6

   • If a development standard (e.g., height or FSR) would be contravened, prepare the required document demonstrating that compliance is unreasonable or unnecessary and that there are sufficient environmental planning grounds (cl 4.6(3)). Remember the consent authority must record its assessment (cl 4.6(4)). The EPA Regulation requires the DA be accompanied by the applicant’s grounds document.

6. Check ancillary statutory approvals and SEPP interactions (cl 1.9; cl 3.1 notes)

   • Confirm whether any State environmental planning policies prevail (cl 1.9(1)) or whether other approvals/licences are needed (heritage, fisheries, Crown land licences). Exempt development remains subject to approvals or licences under other Acts (Schedule 2 note).

7. Prepare for design excellence and urban design obligations (cl 7.12; cl 6.3)

   • If the site lies within zones where design excellence is required (cl 7.12(2)), assemble urban design and architectural evidence demonstrating compliance with the Coffs Harbour DCP and the matters listed in cl 7.12(4). For urban release areas, expect a DCP and staging/infrastructure requirements (cl 6.3).

8. Mind location‑specific caps and constraints

   • For special zones like E3, MU1, W4, or for named parcels in Schedule 1, check gross floor area caps, use restrictions and site conditions (for example cl 7.14 caps business/office floor area in E3 and MU1; Schedule 1 contains parcel‑specific FSR and height caps).

9. Address ancillary matters in the DA package

   • Include calculations under cl 4.5 for FSR and site area, ensure no double counting of floor area (cl 4.5(4)-(11)), include covenants where consent will condition covenanting, and prepare flood, bushfire, fauna/flora, sewage, and services evidence where the Plan requires consideration (cl 7.11 essential services; cl 5.11 bush fire exemptions for Rural Fires Act authorized works).

10. For heritage or Aboriginal matters, follow notification and consultation steps (cl 5.10)

    • If the site involves an archaeological site or Aboriginal place, comply with the notification and consultation procedures and consider the possible need for a heritage management document or heritage conservation management plan (cl 5.10(5)-(6), (7)-(9)).

11. For public land, acquisitions and classifications follow Schedule 4 and cl 5.1-5.2

    • If the proposal involves public land or acquisition issues, consult the Land Reservation Acquisition Map and the table in cl 5.1 to identify the relevant acquiring authority and classification provisions in Schedule 4 (cl 5.2).

12. Expect conditions and possible covenanting

    • The consent authority may impose conditions that require covenants to prevent “double dipping” in floor area (cl 4.5(9)-(10)), time limits on uses (Schedule 1 cl 20), conservation obligations or management requirements (cl 5.10(10)).

13. Document outcomes and keep records

    • Because the Plan mandates consent authority record‑keeping for certain decisions (cl 4.6(4)) and frequently uses “satisfied” tests, ensure that assessment reports, technical evidence and decision records are thorough and defensible.

14. Consult maps, the Coffs Harbour DCP and external guidelines early

    • The Plan repeatedly refers to the Coffs Harbour DCP (cl 7.12(5)), the Considering Flooding guideline and the Flood Risk Management Manual (cl 5.21(4)-(5)), and various industry development plans for aquaculture (cl 5.19(5)). Incorporate these into project planning before lodgement.

If in doubt about the Plan’s effect on a particular parcel, the Plan’s operative wording makes clear that the maps and schedules are decisive and that the consent authority must be engaged early. The Plan’s many discretionary satisfaction points and map‑driven elements place an evidentiary and procedural burden on applicants; addressing those in advance reduces the risk of refusal or protracted conditions.