Latest information
Updates
Follow material planning, development, infrastructure and property changes relevant to the Southern Thornlands Priority Development Area.
Filter the catalogue
Choose a section
All updates has its own main catalogue. Choosing a section opens a permanent, shareable section URL.
Chronological catalogue
Planning & Policy
Planning instruments, government policy and regulatory changes affecting Southern Thornlands.
6published updates
Proposed Southern Thornlands Development Scheme released for public notification
EDQ released the proposed Southern Thornlands PDA Development Scheme, opening public submissions from 3 August to 15 September 2026.
Read updateCouncil withdraws its Southern Thornlands planning scheme amendment
Redland City Council withdrew its earlier Southern Thornlands planning scheme amendment after the State became the planning authority for the new PDA.
Read updateSouthern Thornlands declared a Priority Development Area
The Queensland Government declared the 890-hectare Southern Thornlands PDA and brought an Interim Land Use Plan into effect.
Read updateSouthern Thornlands PDA declared and Interim Land Use Plan takes effect
The Southern Thornlands Priority Development Area was declared on 4 April 2025, bringing the Southern Thornlands PDA Interim Land Use Plan into effect.
Read updateShapingSEQ 2023 moves Southern Thornlands into the Urban Footprint
The final ShapingSEQ 2023 moved Southern Thornlands into the Urban Footprint and designated it as an SEQ development area subject to detailed planning controls.
Read updateSouthern Thornlands identified as a Potential Future Growth Area
ShapingSEQ 2017 identified Southern Thornlands as a Potential Future Growth Area, beginning a formal investigation pathway without approving urban development.
Read updateHow Updates work
The update explains what changed
Updates record material events and announcements. Current property, development, planning and infrastructure facts remain on the relevant records elsewhere on the website, so an update does not become a second copy of the underlying database information.