Have an upcoming project? Get in touch with us

Fill in your details below and one of our staff members will be in touch. Alternatively, you can call your local BRS office directly via the contact details in the footer of this page.
  • This field is for validation purposes and should be left unchanged.

Coastal Planning

NSW development within coastal management areas must now address the primary coastal planning controls during lodgement of a development application.

In conjunction with State Environmental Planning Policy (Coastal Management) 2018 which addresses how coastal development must be assessed, the Coastal Management Act 2016 establishes the environmental planning framework for development within coastal areas.

Particularly relevant to beach front properties, the coastal planning controls aim to protect and enhance the social, cultural and economic environment within the following coastal management areas:

  • Coastal wetlands and littoral rainforests area — areas which display the characteristics of coastal wetlands or littoral rainforests that were previously protected by SEPP 14 and SEPP 26.
  • Coastal vulnerability area — areas subject to coastal hazards such as coastal erosion and tidal inundation.
  • Coastal environment area — areas that are characterised by natural coastal features such as beaches, rock platforms, coastal lakes and lagoons and undeveloped headlands. Marine and estuarine waters are also included.
  • Coastal use area — land adjacent to coastal waters, estuaries and coastal lakes and lagoons.

The following SEPP (Coastal Management) 2018 mapping service is now available for property owners to determine if coastal management controls must be addressed for their site.

Coastal DAs are required to address the objectives of the coastal planning legislation to identify compliance with strategic and statutory management controls. Typically, the Barker Ryan Stewart Town Planning team will liaise with Architects, Coastal Engineers, and the Council to determine site specific threats that need to be addressed prior to lodgement of a DA. This process can reduce costs associated with over engineering, streamline the approvals process and mitigate environmental or amenity impacts on surrounding development.

Following major storm events and significant coastal erosion to a beachfront property in Collaroy, Barker Ryan Stewart have recently secured development approval for significant upgrades to private property coastal protection works (seawall construction) on Sydney’s Northern Beaches.

The proposed works adopt best practice coastal engineering design to facilitate the seawall in accordance with the Northern Beaches Coastal Zone Management Plans and relevant local planning controls. In collaboration with additional sub consultants, Barker Ryan Stewart provided a comprehensive review of relevant coastal planning controls and engineering design to facilitate long term protection of private coastal property assets.

Barker Ryan Stewart’s Town Planners have also secured approval for alterations and additions to a beach front dwelling in MacMasters Beach incorporating additional building works seaward of the coastal building line.

In addition to large scale re-design of the existing premises, the DA addressed coastal hazard controls within the Gosford Development Control Plan 2013 to facilitate a cantilevered extension of the roofline over an existing ocean front entertaining area. Consent was also provided for construction of a secondary dwelling within the Coastal Environment and Coastal Use Areas as determined in SEPP (Coastal Management) 2018 online mapping.

Barker Ryan Stewart can assist with pre DA planning advice and feasibility of coastal development, preparation of DA documents to support lodgement with Council and project management of the DA process through to approval.

Visit our what we do page or contact us today for more information.

Get the latest industry updates and news

Signup for the Barker Ryan Stewart newsletter to get all the latest news and updates in the industry.
  • This field is for validation purposes and should be left unchanged.