How Long Does Development Approval Really Take in South Australia?

How Long Does Development Approval Really Take in South Australia?

General information for South Australian landowners and small developers only. This is not planning, legal or financial advice, and nothing here is a prediction of how long any particular application will take. Route questions about the assessment pathway, notification and referral triggers on a specific site to a planning consultant; questions about a live application, its verification status and fees to the relevant council and PlanSA; contract deadlines, due diligence periods and settlement terms to an SA property lawyer or conveyancer; and questions about carrying a longer hold to your own accountant or finance broker. Statutory timeframes and arrangements change over time, so confirm the current position for your own application before relying on anything here.

The answer everyone already has

Ask how long a development application takes in South Australia and you will get a number. A neighbour who subdivided quotes theirs. An agent quotes one that keeps the contract moving. A forum thread averages its replies into consensus. The figures differ, but they share a shape: a single tidy duration, delivered with confidence, attached to no particular application.

The folk number exists for an understandable reason. People compress what they lived through into one figure, because a figure is easier to hand over than a story about referral agencies and notification. But look at what it actually is: one case, remembered selectively, from an application whose profile you do not know. You do not know which pathway it was assessed under, whether it was referred to an agency, whether it was publicly notified, whether the authority came back with questions partway through — or even what the person is counting. Lodgement to decision is one period. First phone call to titles in hand is a much longer one, and people quote both as if they were the same thing.

It is worth being clear about what this piece is and is not. It is not a walkthrough of the stages — those are set out separately in how the DA process works in South Australia. And it is not a comparison of council areas, because a council's name is not a timeline; the reputational shortcut fails for the same reason the folk number does. This piece is about a narrower habit: treating a duration as a fact you can look up, when it is actually an estimate you have to build.

What a timeline is actually built from

A timeline is assembled from the features of your application, and most of the assembly happens before anyone starts assessing anything.

The first feature is the pathway. Which assessment pathway your proposal falls into is determined by the relevant authority against the Planning and Design Code — it is not something you choose, and not something this article can tell you. What your own planning consultant can do is advise you, before you lodge, which pathway your proposal is likely to attract on your site, because the pathway carries much of the timetable with it.

The second and third features are referrals and notification. Whether an external agency must be asked for its view, and whether neighbours must be told, are triggered by facts about the proposal and the land read against the Code. Your planning consultant can usually anticipate both from the title and the scheme; the authority determines them in fact.

The fourth feature is completeness at the door. Before assessment begins, an application goes through verification — the stage in which the authority establishes that what you have lodged is a complete, correctly constituted application. Verification is its own stage with its own logic, covered in what the verification stage actually does, and it matters here for one reason: time spent being verified is part of your wait whether or not it is part of any measured assessment period. An owner who counts from the day the documents went in, and an authority whose clock starts later, are both right — about different periods.

Keep those features in view and the folk number's problem becomes structural. Two applications can sit in the same suburb, involve the same kind of proposal, and still carry different pathways, different referral triggers and different notification outcomes. They were never going to take the same time, and no single figure could have been right for both.

Why a single number cannot be right

Suppose, though, that you could hold the profile constant — same pathway, same triggers, same completeness. Comparable applications would still not finish in identical times. Assessment involves people, workloads, holiday periods, agencies responding early or late, panels meeting on their own schedules. Across many comparable cases, durations do not land on a point. They form a spread: a cluster where most cases finish, and tails where the unlucky ones sit.

That spread is not noise around a true answer. It is the answer. A point estimate — the average, or worse, the memorable anecdote — throws away exactly the information an owner needs, which is not "what is typical" but "how wrong could this go, and what would make it go that way".

The distinction is not academic, because you make different decisions with a range than with a point. A point invites you to calibrate everything to it: the settlement terms you accept, the finance you arrange, the date you promise a builder or a buyer. When the point turns out to have been the optimistic edge of a spread, every one of those commitments is now wrong together, and each unit of extra wait has a carrying cost — rates, interest, insurance and forgone alternatives, worked through in what a delay actually costs to hold. A range invites a different posture: commitments sized to the cluster, contingencies sized to the tail, and a clear-eyed view of which features of your own application push it toward one end or the other.

An anecdote samples one case. Evidence samples many, and tells you where yours is likely to sit and why. That is the whole argument, and everything else here is its application.

The request for information deserves its own scenario

Of everything that widens the spread, one variable stands apart: whether the assessing authority comes back with a request for further information during assessment.

Note the wording. A request for further information is not verification wearing a different name. Verification is the completeness check at lodgement — is this a properly constituted application. A request for information arrives later, during assessment, when the authority decides it needs more material to determine the application. Conflating the two leads owners to assume that surviving verification means the questions are over. It does not; the stages are different instruments doing different work.

Here is the difficulty for anyone building a timeline: on lodgement day, you cannot know whether a request will come. And here is the statistical mistake almost everyone makes with that uncertainty: they blend it into an average. The blended figure is true of no application at all — too long for the file that sails through, too short for the file that stops while the applicant commissions the report the authority asked for.

The honest treatment is to split the scenarios and plan both. One timeline if no request comes; a distinctly longer one if it does; and a view, formed with your planning consultant, of which features of your application make a request more or less likely and what could be prepared in advance to blunt it. That last part matters because the request scenario is the portion of the timeline your preparation actually influences — assessment speed is not in your hands, but the completeness and anticipation of your material largely is. How requests arise, what they tend to ask for and how owners respond well is its own subject, taken up properly in the deep dive on requests for further information; for planning purposes, it is enough to hold it as a separate scenario rather than a hidden average.

From a guess to an estimate

So what does it look like to do this properly — to replace the folk number with something an owner can actually plan against?

It looks like matching. Take the profile of your application — the likely pathway, the referral and notification triggers your consultant expects, the proposal type, the kind of site — and set it against delivered, comparable cases rather than against everything ever lodged. In research we co-authored on South Australian planning applications, the pattern that mattered was exactly this one: applications with similar profiles cluster together, and the features that separate the clusters are mostly knowable before lodgement. The useful output is not a promise. It is a range with a reason attached — where cases like yours have landed, how wide the tails ran, and which of your features sit on the risky side.

Honest matching also means being open about thinness. Sometimes the set of closely comparable cases is small, and the right response is to widen the comparison deliberately — relaxing one feature at a time — and to say so, rather than quoting a confident figure from a quiet corner of the data. An estimate that discloses its basis can be interrogated and improved. A confident number with no basis can only be believed or not.

And an estimate has a boundary it should state plainly. The relevant authority determines your application on its merits; no reading of historical cases guarantees an approval or a timeframe, and anyone offering that guarantee is selling something other than evidence. What the evidence supports is narrower and more useful: a defensible view of the range, the scenarios and the levers, formed before you commit money to a schedule.

Putting a range on your own application

If you want that done systematically, this is what our approval timeline assessment report exists for. It takes the profile of your proposed application, matches it against comparable historical cases, and returns an evidence-based assessment — stated as ranges and scenarios, with the request-for-information case held separately, and with its basis disclosed so your own advisers can test it. It is an assessment built from historical cases, not a guarantee of any approval or timeframe, and it does not replace the planning consultant who advises you on your pathway and triggers. You can read what it covers at the approval timeline report. A report answers a question; running the approval itself is a different engagement, described at development approval and planning pathway. And if it would help to talk through whether your situation warrants one, start a conversation with us — a conversation is a practical way to work out whether the comparable set is deep enough to be worth your money.