PlanSA's ePlanning platform is routinely updated to introduce new functionality, enhance the customer experience and address technical issues.
After each update, changes are documented as release notes and published on PlanSA.
PlanSA components
PlanSA's ePlanning platform is made up of different online components:
- PlanSA portal website
- Development Application Processing (DAP) system
- Online Planning and Design Code
- South Australian Property and Planning Atlas (SAPPA)
- Council Financial Report Service
PlanSA is committed to ensuring its ePlanning system is responsive to the needs of its customers.
To view or to check on the status of a current enhancement project, visit the PlanSA system enhancements.
System updates are made fortnightly. After each update, system enhancements are documented as Release Notes and published on PlanSA.
Requests for system enhancements can be submitted to the PlanSA service desk via PlanSA@sa.gov.au.
2025
PlanSA portal
| Features | |
|---|---|
Code amendment submission form | PlanSA is currently developing a new code amendment dashboard which will allow proponents to lodge and track the progress of code amendments. Changes to the Website Submission Form have been made to support the development of the dashboard. The changes to the website provide a new user interface to submit a Proposal to Initiate a Code Amendment, including:
The form to request a change to the code remains unchanged and can be found on the Code Amendment website page. |
PowerBI
| Fixes | |
|---|---|
PowerBI - Practice direction dashboard | The Practice Direction 9 table has been updated to include all inspections in the total count (except rectifications). This fixes an error where monthly totals were incorrect. The Building Works Inspected column in the Practice Direction 8 Table has been renamed to Building Work Completion Inspection. |
DAP
| Features | |
|---|---|
Custom contact email for building occupation/ completion | The Council/SPC user defined email address for building notifications will appear on the Decision Notification Form's Building Occupation/Completion section. |
Rectification decision comment field visibility | The rectification decision comment detail is now visible on the Building Notification screen for the Relevant Authority and Accredited Professional (Building Certifier). This enhancement improves the efficiency and accuracy of the rectification process by providing critical feedback to authorised personnel while maintaining confidentiality. |
Building Notification enhancements | An email notification is sent to the applicant when building consent is granted and building indemnity insurance has not yet been provided. The email advises that indemnity insurance must be provided in DAP prior to the notice of building works commencing. An applicant is required to enter a reason where they did not enter into a domestic work contract and are not exempt from holding insurance. |
Planning consent “on hold” feature | The system now allows a Planning Consent to be placed on hold after the consultation process has closed. |
| Fixes | |
Development application – application contacts | Adding or modifying an application contact (i.e. applicant, primary contact, invoice contact, or land owner), changing the contact style (e.g. individual to business), or selecting contact style 'Council' no longer resets the selected contact type. |
Development application – document date distributed | For contacts requiring postal correspondence. The entered ‘Date Distributed’ for a selected document is now saved when the document is updated. |
Development application council contacts | When 'council' is an application contact (applicant, invoice contact, primary contact, or land owner) the contact's name field now displays the name of the council in the following places:
|
Edit consent elements – purpose of the development now available | When editing planning consent elements from the application summary page, the purpose of development checkbox is now available when council is the applicant and/or land owner. |
Electronic lodgement fee – council development is not revenue raising | The Electronic Lodgement Fee (ELF) no longer automatically defaults for the second consent when the applicant and/or land owner is council and development is not revenue-raising as determined on assessing the first consent. |
Withdraw application – referral body notified | The referral body is now informed when a development application with a state government agency agreement (pre-lodgement agreement) is withdrawn. |
DAP
| Feature | |
|---|---|
Construction Industry Training Fund (CITF) threshold change | Effective 1 January 2025 development approvals issues after this date, the CITF levy payable by the project owner is now calculated on the estimated project value of building or construction works greater than $100,000. Development applications with a building consent under assessment on or after 1 January 2025 the new threshold (works greater than $100,000) applies. To ensure that applicants have easy access to necessary information and maintain compliance with CITF levy requirements, the following enhancements have been made.
Visit About Levies | Construction Industry Training Board for more information. Latest version |
