Deemed-to-Satisfy or Performance-Assessed: What You Give Up by Designing Inside the Envelope

Deemed-to-Satisfy or Performance-Assessed: What You Give Up by Designing Inside the Envelope

General information for South Australian landowners only. This is not legal, planning or financial advice, and nothing here is an opinion about your site or your drawings. Route questions about which pathway a proposal would run through, which criteria apply to it and whether a departure is workable to a qualified planning consultant; questions about appeal rights, statutory timeframes and deemed consent notices to an SA planning and administrative law lawyer; questions about what a departure is worth in money to your own valuer, quantity surveyor or selling agent; and questions about what the Planning and Design Code currently says for your land to your council and PlanSA. Legislation, the Code and council delegations change, so confirm the live position before you rely on anything here.

The pathway is settled in the drawings, not on the form

You are at concept design, and the decisions in front of you look like design decisions. A setback. A wall height. A driveway location. A boundary wall.

Each is also a decision about how the application will later be assessed. By the time the drawing set is fixed, the pathway has largely been settled with it — not by a box anyone ticks, but by whether what has been drawn answers every prescriptive criterion the Planning and Design Code attaches to that class of development in that zone. City of Adelaide describes the pathway this way: "Deemed-to-Satisfy Development: includes classes of development that are contemplated in a Zone. DTS classes of development are listed in Table 2 of a Zone and which also provides prescriptive criteria to satisfy" (source: City of Adelaide — Development application process). The same page describes the alternative: "Performance Assessed Development: are often more complex and involve a merits-based assessment against the Planning & Design Code. These applications can sometimes require public notification and/or an agency referral."

One word in that quote needs care. The pathways the Code works with are deemed-to-satisfy, performance assessed, restricted and impact assessed. "Merits" in the South Australian system otherwise refers to a merits appeal in the Environment, Resources and Development Court, not to an assessment pathway.

That page is explicit that it sets out only the most common pathways. The fuller list runs wider: the SA Law Handbook sets out exempt development, accepted development, code assessed development — where the deemed-to-satisfy and performance assessed split sits — and "Impact Assessed Development, comprising: Restricted development (set out in Planning and Design Code); Impact Assessed development (set out by regulations); Impact Assessed development (declared by Minister)" (source: SA Law Handbook — Categories of Development). This article is only about the trade inside code assessed development. Whether a proposal is code assessed at all — rather than restricted in that zone, or impact assessed — is determined by the relevant authority, and that is a different question from failing a criterion within Table 2.

One caveat before that source does more work below: it is a secondary summary, its footer dates it as last revised in March 2021, and it names the provisions behind it (PDI Act sections 105, 106, 107 and 125, and regulation 53). Treat it as a map, and confirm the live position with your council and PlanSA.

Which pathway a given design would run through is determined by the relevant authority on the facts of that proposal, and working that out before drawings harden is what a planning consultant is engaged for. A general article cannot put your project on one side of that line. The sequence from lodgement to approval is set out separately in the SA development approval process; what follows is only about the trade inside it.

What staying inside the envelope buys

The deemed-to-satisfy pathway is built for proposals the Code already contemplates. The Handbook puts the assessment simply: "Deemed-to-satisfy development applications are assessed against the provisions of the Planning and Design Code by an Accredited Professional or an Assessment Manager," and, in the same subsection, "There are no public notification requirements for Deemed-to-satisfy developments" (source: SA Law Handbook — Categories of Development).

Two things bound that subsection. Its example — a detached house in a residential zone being "fast tracked" — is an illustration, not a rule that any particular house qualifies. And it stops there: it does not say a relevant authority loses the ability to refuse, and this article does not claim it. What it describes is narrower and still valuable: a smaller cast of decision-makers, and no step in which neighbours are notified. That missing step is most of what an owner is buying. Whether it is missing on a given application depends on how that application is categorised, which the relevant authority determines against the current Code — so it is one to confirm for your own proposal rather than to assume from the pathway name.

What leaving the envelope switches on

Where a proposal is not assessed as deemed-to-satisfy, different machinery is engaged — not as a penalty, but because the Code no longer has a tick-box answer for what has been drawn.

On the Handbook's account of performance assessed development: "Unless an exemption is provided under the Planning and Design Code or Practice Direction from the Minister, notification of performance assessed development applications must be given to adjacent land owners. A notice or sign outlining the development must be displayed on the land" (source: SA Law Handbook — Categories of Development). Note the opening clause: exemptions exist, and whether one covers a particular class in a particular zone is something to check in the Code rather than assume in either direction.

The same subsection lists what extends the assessment period, and the triggers are named ones rather than a general penalty for complexity: where the relevant authority is the State Planning Commission or an Assessment Panel; where the application is referred to an agency for comment; and where public notification is required. Departing from a deemed-to-satisfy criterion does not by itself extend anything — it can put a proposal in reach of those triggers, and that is the connection worth understanding at concept stage. Which authority would hold the file is a separate question, dealt with in delegated officer or assessment panel.

The room to argue is narrower than "argue it on merit" suggests

This is the part owners most often misprice. Performance assessed buys the ability to make a case — but against a defined set of policies, not against planning good sense at large.

That boundary was tested. Before a recent Code amendment, the rule of interpretation ended at "no other policies are applicable." In Geber Super P/L v Barossa CAP [2023] SASC 154, Justice Blue said: "It would be a bizarre result if a panel or other relevant authority were precluded from having regard to a provision of the Code that was objectively relevant merely because the computer had not produced that provision on an enquiry of the planning database" (source: Norman Waterhouse — Assessment Amendments to the Planning and Design Code).

The Assessment Improvements Code Amendment answered that in a particular direction. Norman Waterhouse reproduces the amended rule in two paragraphs. The first is the one an owner most needs — the old exclusion, retained and tightened, the added words being "to the assessment of the application": "The policies specified in Table 3 constitute the policies applicable to the particular class of development within the zone to the exclusion of all other policies within the Code, and no other policies are applicable to the assessment of the application." The Amendment then adds: "In interpreting the policies specified in Table 3 the relevant authority may, in assessing an application, consider other similar code provisions (beyond those produced from Table 3) for contextual purposes only. Where policies, outside of those returned by Table 3, are considered (for contextual purposes to interpret the applicable policies) they cannot form the reasons as to whether consent should be granted (or refused) for an application."

So the picture is two-sided: a relevant authority can look beyond Table 3, but only to interpret what is in it, and what sits outside cannot become a reason for the decision either way. The practical question at concept design is therefore not "can we argue for this" in the abstract. It is: which Table 3 policies would be produced for this class in this zone, and does the case for the departure live inside them? That is for your planning consultant, working from the Code as it applies to your land.

Design standards, and provision for automated decisions

Two changes are worth knowing before assuming this trade works as it did a few years ago.

The first is design standards. Norman Waterhouse reports that the Statutes Amendment (Planning, Infrastructure and Other Matters) Act 2025 introduces section 106(1a) of the PDI Act: "If a design standard applies in relation to a proposed development, the development may be assessed as deemed-to-satisfy development under this section provided that planning consent in respect of the development is granted subject to conditions requiring the development to be consistent with the design standard" (source: Norman Waterhouse — Amendments to the PDI Act). The boundary on that article matters: it says the majority of the Part 5 amendments "have recently commenced by proclamation" while expressly flagging others — the land division certificate change in section 138(1a) and Local Area Plans in section 245A — as not yet commenced. So "the Act is in force" is too blunt to build on. Whether a design standard applies to a particular development, and what that would mean for its pathway, is for the relevant authority and your planning consultant.

The second is easy to overstate. The same source reports that the Amending Act "introduces the ability to use equipment, computers or other electronic devices of an approved class (Approved System) to make specified decisions under the Act" — future tense on the page, which does not say the section has commenced or that any class has been approved. It also records that any act or determination of such a system "will have been taken to have been done by the Chief Executive as the relevant authority", and that "an authorised person may still act, make or substitute their own decision, instead of relying on the Approved System."

What to settle before the drawings harden

The honest answer to "which pathway will my design go through" is that it depends. The useful version is a short list to go and find out, each with an owner:

• Which class in Table 2 the proposal would be lodged under, and the full set of prescriptive criteria that class carries. Your planning consultant, working from the Code for your land.
• Which criteria the design currently sits closest to the edge of. Your designer and planning consultant together. In practice the trade often turns on a small number of criteria rather than the whole set; which ones, for this design, is what they can identify from the Code.
• What the departure is worth. Yours to decide, on figures from your own valuer, quantity surveyor or selling agent. A departure that carries a commercial outcome is a different decision from one that exists because nobody checked.
• Which Table 3 policies would be produced for that class in that zone — because after the amendment above, those are the policies the reasons must come from.
• Whether the class is exempted from notification by the Code or a Practice Direction if it goes performance assessed, and which of the named extension triggers could come into play.
• Whether a design standard is in the picture, given section 106(1a).

Ask those before the drawings are fixed and the trade is a decision; ask them after and it is a discovery. What gets checked when an application first arrives is covered in the verification stage, and if a decision does not land where you wanted, what to do after a refusal is worked from the file you built at concept stage.

Where a development manager sits in this

Cyberate PM does not assess applications, determine pathways or advise on planning law. We coordinate the owner's own professionals and sequence the work so the pathway question gets asked while it is still a design question — bringing the planning consultant into concept design rather than after it, and keeping the record a later assessment or appeal will be run from.

Predictability is genuinely worth something. Whether the alternative in fact brings notification, a referral or a longer road depends on the named triggers above and on whether an exemption applies to that class in that zone — which is why it belongs with your planning consultant before the drawings are fixed. What makes this a decision rather than an accident is knowing you are making it, at concept design, while changing a line on a drawing is still cheap.