glossary Glossary 6 min read

Planning and Design Code (SA)

SA's single statewide planning instrument replaced 72 council Development Plans on 19 March 2021. Zones, subzones, overlays, TNVs in one document under PDI Act.

Ask Chalkline about this →

The Planning and Design Code (the Code) is South Australia’s single state-wide planning instrument, replacing all 72 separate council Development Plans on 19 March 2021. The Code is governed by the Planning, Development and Infrastructure Act 2016 (SA) and consolidates zones, subzones, overlays, and Technical and Numeric Variations (TNVs) into one statewide document. The current version is 2026.1, issued 15 January 2026. SA is one of three Australian jurisdictions (with NT and ACT) that uses a single statewide planning instrument rather than per-council schemes. Verified per PDI Act 2016 (SA) (2026-05-23).

Why SA went statewide:

Before 19 March 2021After 19 March 2021
72 council Development Plans, each with its own format and provisionsSingle statewide Planning and Design Code
Significant inconsistency across LGAsCommon rules applied with TNV calibration for local conditions
Each council interpreted and amended their plan independentlyStatewide review and amendment
Permitting varied by councilCommon assessment categories statewide

The 2021 consolidation was a major reform; older industry knowledge of “the [council name] Development Plan” no longer applies, it’s all the Code now.

Code structure:

ComponentContent
ZonesGeographic zoning (Residential, Employment, Open Space, Rural, etc.)
SubzonesLocal-area refinement within zones
OverlaysTopic-specific overlays (Heritage, Bushfire, Flood, Significant Trees)
Technical and Numeric Variations (TNVs)Council-level calibration of zone provisions (setbacks, heights, etc.), the SA equivalent of council-specific tweaks
General provisionsStatewide rules applying everywhere
DefinitionsCommon terminology

Key zones (residential focus):

ZoneDescription
ResidentialStandard residential
TownshipCountry town residential
Rural LivingLarger residential lots in rural settings
Suburban Activity CentreMixed-use suburban
Urban RenewalStrategic redevelopment
Hills NeighbourhoodHills residential
Hills ConservationSensitive hills with environmental controls

Plus commercial, industrial, recreation, open space, conservation, and others.

Technical and Numeric Variations (TNVs):

TNVs are how the Code adapts to local council conditions while maintaining a statewide framework. They specify:

  • Setbacks (front, side, rear).
  • Building heights.
  • Site coverage.
  • Density.
  • Specific zone-level rules.

Two parcels in the same statewide zone but in different councils may have different TNV-set setback requirements. The TNVs are visible on the PlanSA portal alongside the zone provisions.

Overlays:

Common overlayWhat it does
Heritage AdjacencyAdjacent to a state-heritage place; design controls apply
Heritage PlaceState or local heritage item; significant constraints
BushfireBAL-prone area; AS 3959 requirements
FloodFlood-prone land; floor levels
Hazards Acid Sulfate SoilsCoastal sites; site investigation required
Hazards SalinitySalinity risk; building design implications
Significant TreesTree retention controls
Native VegetationCleared-vegetation controls
Contaminated LandSite contamination remediation requirements
CoastalCoastal exposure

Reading the Code for a project:

  1. Open PlanSA online portal.
  2. Search the property to identify zone, subzone, overlays, and TNV-calibrated values.
  3. Read the zone provisions in the Code.
  4. Apply any subzone refinements.
  5. Check each overlay that applies.
  6. Apply the TNV values for the council’s local controls.
  7. Identify the assessment category for the proposed development.
  8. Lodge through PlanSA.

Assessment categories (from PDI Act):

CategoryPathway
AcceptedNo DA needed
Code Assessed Deemed-to-SatisfyDA against DTS criteria; routine
Code Assessed Performance AssessedDA against Performance Outcomes; merit + notification
RestrictedHigh-impact; State Planning Commission

(Each is covered in their own glossary entries.)

Version control:

The Code is regularly updated, typically twice per year. Version naming: YYYY.N (e.g. 2026.1 = first 2026 release, 2026.2 = second). Always check the current version when designing; provisions may have changed between draft date and lodgement.

VersionReleased
2026.115 January 2026
2025.2August 2025
2025.1January 2025
2024.2August 2024
2024.1January 2024
2023.2August 2023
2023.1January 2023
2022.2August 2022
2022.1January 2022
2021.119 March 2021 (initial Code commencement)

Common defects:

  • Reading an outdated Code version: design template from a 2024 build may not match the current Code.
  • Missing TNVs: zone provisions alone insufficient; TNV-specific setbacks etc. drive the design.
  • Overlay ignored: an overlay (heritage, bushfire, flood) applies but builder hasn’t read its provisions.
  • Wrong zone applied: searching by address gives the zone; assumption from neighbouring lot can be wrong.
  • Reading the old council Development Plan: superseded since 19 March 2021.

Cross-state equivalents:

StateEquivalent statewide framework
SAPlanning and Design Code (this) under PDI Act 2016
NTNT Planning Scheme 2020 under Planning Act 1999
TASTasmanian Planning Scheme (TPS) under LUPAA 1993
ACTTerritory Plan under Planning Act 2023
NSW, VIC, QLD, WAPer-council schemes

Builder takeaway:

  • For SA residential, the Code is the single source. Use PlanSA as the portal.
  • Always check the current Code version at the start of design.
  • TNVs are the most-missed element; they’re where council-level calibration sits.
  • Engage an SA-experienced planner for projects with multiple overlays or Performance Assessed categorisation.

Also known as: SA Planning Code; The Code (within SA); statewide Code; PDC.

Category: Approvals & DA.

See also


Last updated: 2026-05-23. Verified: 2026-05-23. Quarterly review for currency.