Code vs impact assessment in Queensland, explained

Whether your Queensland development application is code assessable or impact assessable is decided before you lodge anything — it is written into the council planning scheme's tables of assessment, zone by zone and use by use, under the framework of the Planning Act 2016. The difference is not procedural trivia: code assessment means no public notification, no submitter appeals, and assessment against fixed benchmarks; impact assessment means your neighbours are formally invited to object, objectors gain appeal rights, and council's discretion widens. Across the 1,011 zone-by-use assessment entries Casa Intelligence indexes from the eight SEQ planning schemes, 27% are accepted development (no application needed), 60% are code assessable, and 13% are impact assessable.

The short version

What decides the pathway. The categorising instrument — almost always the council planning scheme's tables of assessment, occasionally the Queensland Planning Regulation. Zone plus use plus scale, looked up in a table. Not council's mood, not your consultant's optimism.

What code assessment means. Assessed only against the relevant codes. No public notification. No submitter appeals. Must be approved to the extent it complies with the assessment benchmarks.

What impact assessment means. Public notification of at least 15 business days, anyone may lodge a submission, properly made submitters gain appeal rights, and council weighs the whole planning scheme and relevant matters — genuine discretion, genuine uncertainty.

Why it matters. Time, cost, and risk all step up at the impact threshold. In Brisbane, predominantly code assessable subdivision applications show a median of 55 days to decision across 16,593 decided applications; multiple-dwelling applications — larger, more complex, and more often impact assessable — show a median of 144 days across 8,258 (Casa Intelligence analysis; an illustrative contrast, not a controlled comparison).

What decides whether a DA is code or impact assessable?

Three inputs: the zone (and any precinct or neighbourhood/local plan overriding it), the proposed use as defined in the scheme, and thresholds — height, density, site area, GFA. The planning scheme's tables of assessment map each combination to a category: accepted, code assessable, or impact assessable.

The thresholds are where projects quietly change category. A multiple dwelling proposal might be code assessable at 2 storeys and impact assessable at 3; accepted on 800m² and code assessable on 600m². The same use can also flip category across a zone boundary — which is why two sites 200 metres apart can carry completely different application risk. A consistent example from our index: dual occupancy is code assessable in the standard residential zones of every one of the eight SEQ planning schemes, and impact assessable in the Rural zone of every one of them. The pattern is legible once you read the tables — the failure mode is not reading them until after the contract is signed.

What is the practical difference once you lodge?

Code assessment is a compliance exercise. Council assesses the application against the assessment benchmarks in the applicable codes — the zone code, overlay codes, development codes — and, under section 60 of the Planning Act 2016, must approve it to the extent it complies. Nobody outside the process is notified. No third party can appeal. The negotiation, if any, is technical: which benchmarks are met, and whether your alternative solutions hold up.

Impact assessment opens the doors. The application is publicly notified for at least 15 business days — a sign on the land, notices, the register. Anyone can lodge a submission, and council must consider them. Council assesses against the whole planning scheme and any other relevant matter, which gives it room to refuse a proposal that ticks individual boxes but jars with the intended character of an area — and room to approve one that does not tick every box. And every properly made submitter walks away holding appeal rights to the Planning and Environment Court, so even a granted approval can be dragged into litigation.

How much time and money does the pathway add?

The statutory floor moves first: impact assessment adds the notification period (15+ business days), the submission window, and the time to respond to whatever comes in. The commercial reality moves further. Submissions mean consultant time to answer; contentious applications mean pre-decision negotiation; and a submitter appeal means Planning and Environment Court timeframes measured in months to years, with legal and expert costs that routinely exceed the entire original application budget.

For calibration, the all-application medians across SEQ (Casa Intelligence analysis of decided applications, elapsed days lodgement to decision): Logan 28, Gold Coast 42, Sunshine Coast 50, Moreton Bay 51, Brisbane 52. Those blended figures are dominated by simple, code assessable and accepted-adjacent applications; the moment a project steps up in complexity or category, it leaves those medians behind — Brisbane multiple-dwelling applications run a 144-day median against the city's 52-day baseline.

Cost follows the same curve. On top of notification costs and response work, the deeper cost of impact assessment is risk-pricing: financiers and vendors both price approval uncertainty, and an impact assessable pathway weakens your position on both fronts. The full cost stack — fees, consultants, charges, and holding time — is laid out in what a development application really costs in South East Queensland.

None of which makes impact assessment fatal. Approval rates across our SEQ dataset remain high overall, and well-prepared impact applications succeed constantly. What changes is variance: code assessment fails or succeeds on technical grounds you can largely verify in advance; impact assessment adds actors and discretion you cannot fully control. Developers do not fear impact assessment because refusal is likely — they fear it because certainty evaporates.

Performance outcomes vs acceptable outcomes: what happens when you cannot tick the box?

Inside every code, the benchmarks come in pairs. The performance outcome (PO) states what must be achieved — say, that a building's height and bulk respect the streetscape and neighbouring amenity. The acceptable outcome (AO) is one pre-approved way to achieve it — say, 8.5 metres and two storeys. Meet the AO and that benchmark is settled, no argument available.

Miss the AO and you are not refused — you are arguing. In code assessment you can propose a performance solution: a demonstration that your design achieves the PO by another route. A 9.2-metre building on a sloping site might cast less shadow than a compliant 8.5-metre building on flat ground; a reduced setback might be offset by articulation and landscaping. Council must assess the argument against the PO, not simply insist on the AO.

Performance solutions are where good consultants earn their fee, and where weak applications die slowly. Every AO you miss becomes a mini-case you must win, an invitation for an information request, and a source of assessment time. The strategic rule of thumb: comply with the AOs wherever the yield cost is small, and spend your performance-solution arguments only where they buy something material. An application that misses six AOs for marginal gain is not brave; it is slow.

Can council actually refuse a code assessable application?

Yes — but only on narrow grounds, and the narrowness is the point. Under the Planning Act 2016, a code assessable application must be approved to the extent it complies with the assessment benchmarks, and can only be refused if non-compliance cannot be resolved through conditions or an acceptable performance solution. Council cannot refuse a compliant code application because neighbours are unhappy, because it dislikes the design, or because the area "has enough" of that use. That legal architecture is why refusal is rare across our SEQ dataset — of more than 272,000 decided applications we track across seven councils, the overwhelming majority were approved.

The honest flip side: "approved" is not "approved as drawn". Council's real leverage in code assessment is the information request and the conditions package. A technically weak application does not usually get refused; it gets slowed, amended, and conditioned until it complies. If your feasibility depends on a specific yield or layout, the risk to manage is not the refusal letter — it is the negotiation that erodes the scheme one benchmark at a time.

Where does accepted development fit in?

Below code assessment sits a third category that involves no application at all. Accepted development — 27% of the zone-use entries in our SEQ index — can proceed without a planning approval provided it meets any nominated requirements, typically the acceptable outcomes of a relevant code. A compliant secondary dwelling, a house in most residential zones, a small extension: these go straight to building approval and the planning system never sees them.

The boundary between accepted and code assessable is a design variable, exactly like the boundary between code and impact. Many small projects can be configured to stay accepted — and skipping the DA entirely is worth more than any amount of application efficiency. Our guide to granny flats and dual occupancy across SEQ shows this boundary in action, council by council.

Should you design to the threshold?

Usually, yes. Because categories flip on thresholds — storeys, height, site area, dwelling count — the pathway is partly a design choice. The classic SEQ trade: a three-storey scheme that triggers impact assessment versus a two-storey code assessable scheme with one fewer unit. The impact scheme carries more revenue on paper; the code scheme carries no notification, no submitter appeal risk, a faster decision, and cheaper finance. On thin-margin infill projects, the code assessable option wins that comparison more often than developers expect — and the time to run it is before the site contract goes unconditional, not after the architect has drawn the bigger scheme.

How do you find out which pathway applies to your site?

Definitively: read the tables of assessment for your zone and use in the current planning scheme, then check the overlays and any local plan that modifies them, then check the Planning Regulation for state-level triggers. That is a few hours of careful work if you know the scheme, and a genuine research project if you do not.

The fast version: a $150 Preliminary Planning Report for any SEQ address gives you the zone, overlays, the assessment pathway for your intended use, and comparable decided DAs — prepared by a qualified development professional (Master of Architecture), delivered in minutes. If you are comparing several sites, pathway alone is often the filter that removes half the list; our suburb DA statistics show how each area actually behaves. For the Brisbane-specific process end to end, see the complete guide to development applications in Brisbane.

Caveats

Assessment categories are set by the current version of each planning scheme and change when schemes are amended — verify against the live scheme before relying on any category, including figures quoted here. Our 1,011-entry index reflects the zone-use combinations we track, not every clause of every scheme. Historical decision statistics describe past outcomes and guarantee nothing about a future application. This is general information, not legal advice; for contested pathways or performance-solution strategy on high-stakes projects, engage a planning lawyer or your development team.