A development proposal can look straightforward on paper yet take very different approval paths. In Queensland, code versus impact assessment is one of the first issues to settle because it affects your application strategy, likely timeframe, notification requirements and exposure to objections.
For a new dwelling, subdivision, childcare centre, industrial use or commercial project, the assessment category is usually set by the relevant planning scheme. It is not something an applicant can simply select because one pathway appears faster. Getting this point right early helps avoid buying a site, designing a project or lodging an application on assumptions that do not hold up under council assessment.
What assessment categories mean in practice
Queensland planning schemes identify whether development is accepted (ie. exempt), accepted subject to requirements, assessable or prohibited. Assessable development is generally assessed as either code assessment or impact assessment. The applicable zone, overlays, neighbourhood plan, use definition and scale of the proposal all matter.
Code assessment is generally used where a proposed development is anticipated by the planning scheme, provided it can demonstrate compliance with the relevant assessment benchmarks. Impact assessment is generally used where a development may have broader planning consequences, is not clearly anticipated in that location, or needs a wider assessment of its effects.
Neither category guarantees an approval or a refusal. A well-prepared impact assessable proposal may be appropriate and approvable. Equally, a code assessable application can still receive information requests, require design changes, be delayed by technical matters or be refused if it does not adequately address the applicable assessment benchmarks.
The practical difference is the scope of assessment and the level of project risk that must be managed before lodgement.
Code versus impact assessment: the key differences
Code assessment has a defined framework
For code assessment, council assesses the proposal against the assessment benchmarks identified in the planning scheme and other applicable planning instruments. These may include zoning provisions, development codes, overlay codes, parking requirements, built form controls, landscaping, servicing, flooding, traffic and environmental standards.
The focus is typically clear: can the proposal comply with the relevant requirements, or can an acceptable planning outcome be demonstrated where a prescribed standard is not met? This still requires proper planning evidence. A minor shortfall in setbacks, site cover, car parking or landscaping may need a considered response rather than a simple assertion that the outcome is acceptable.
Code assessable applications are not subject to public notification. That removes the formal submission period and submitter appeal rights that apply to impact assessment. It can make the process more contained, but neighbouring owners may still become aware of a proposal through other channels, particularly on visible or sensitive sites.
Impact assessment allows a broader assessment
Impact assessment considers the relevant assessment benchmarks and any other relevant matters. This broader scope gives council more discretion and gives the applicant more room to make a case for a development that does not sit neatly within the expected outcome of the planning scheme.
That flexibility comes with added work. The planning report and supporting technical reports must explain why the use, scale, design and location are suitable. It may need to address need, economic benefit, housing choice, site constraints, amenity, traffic, servicing, environmental effects and compatibility with the surrounding area. The right supporting consultants can be critical, depending on the site and proposal.
Impact assessable applications require public notification after the application reaches that stage. The applicant must complete the notification correctly, including public notices and signs, and provide the required evidence to council. Members of the public may make properly made submissions. Those submitters have appeal rights if council approves the application, which is why a realistic approval strategy considers community response from the outset.
Why the category can change the project decision
For landowners and developers, the assessment pathway can influence whether a site is worth pursuing at all. A code assessable use may offer a more predictable route, but only if the site can satisfy the full range of applicable controls. A site can be code assessable for the proposed use yet still carry difficult flood, heritage, ecological, character, access or infrastructure constraints.
An impact assessable proposal may offer a valuable development opportunity where the planning scheme does not expressly anticipate the use. However, it needs more than a promising commercial idea. The proposal must be supported by a credible planning rationale, a design that responds to legitimate impacts and enough allowance in the programme and budget for notification, council review and possible appeal risk.
This is particularly relevant for proposals such as higher-density housing in lower-density areas, non-residential uses near homes, larger subdivisions, specialised accommodation, intensive land uses and projects on constrained land. The planning scheme may support the broader intent, but the details of location, scale and interface will determine whether the case is persuasive.
Do not rely on the zone alone
A common mistake is to check the zoning map, see that a use is generally contemplated, and assume the approval route is settled. Planning schemes are more detailed than that. Tables of assessment may distinguish between uses based on site area, gross floor area, building height, number of dwellings, proximity to sensitive land uses or a mapped overlay.
For example, a small-scale use may be code assessable in a particular zone while a larger version of the same use is impact assessable. A subdivision may be assessed differently depending on lot sizes, road access, infrastructure availability or environmental constraints. A proposal that looks like a standard development can also trigger additional assessment through flood, bushfire, airport, heritage, biodiversity or character overlays.
Definitions matter as well. The planning scheme definition that best describes the proposed activity may not be the label commonly used in marketing material or on a building design. Misclassifying the use can lead to the wrong assessment pathway, incomplete documentation and avoidable delays.
A better approach before you commit
The strongest projects start with targeted due diligence, not with a set of plans prepared in isolation. Before committing to a purchase, finalising a design or signing a building contract, confirm the development potential against the current planning controls.
A useful desktop assessment should identify the likely use definition, zoning, overlays, level of assessment, relevant codes, referral triggers and obvious technical constraints. It should also flag whether the proposal has a reasonable prospect of using a fast-track pathway, where available, or whether it needs a fuller impact assessment strategy.
For code assessment, the work should test compliance early. If a design cannot meet setbacks, height, car parking, site cover, drainage or access requirements, it is better to know before lodging. Sometimes a practical redesign resolves the issue, however this can result in reduced yield so this exercise needs to be done during the due diligence phase. In other cases, a carefully justified alternative solution is possible. It depends on the wording of the code, the site context and the scale of the departure from the prescribed standard(s).
For impact assessment, early strategy is even more valuable. The proposal should be shaped around the planning case before the formal application is prepared. That may mean reducing bulk near a boundary, improving acoustic treatment, changing access arrangements, staging development or providing stronger evidence of need and community benefit. These are not just cosmetic changes. They can be the difference between a proposal that appears speculative and one that gives council a sound basis to support an approval.
Timing, objections and approval risk
Clients often ask which pathway is faster. Code assessment is commonly more streamlined because it has a defined assessment scope and no public notification stage. But speed depends on the quality of the application, characteristics of the development proposal, council workload, the need for referral agency input and whether further information is requested.
Impact assessment has a longer statutory process because notification is required and the assessment criteria is broader. It may also require more specialist reporting. That does not mean it should be avoided at all costs. If impact assessment is the correct category, attempting to force a proposal into a code pathway is unlikely to save time or money. It usually creates a more expensive problem later.
The best way to reduce delay is to lodge a complete, coordinated application that anticipates the real planning issues. Council officers need enough information to assess the proposal confidently. Neighbours need clear material to assess and contemplate during public notification. Decision-makers need an evidence-based planning case, not vague assurances that impacts will be managed.
When to obtain planning advice
Obtain advice before you rely on a real estate agent’s description of development potential, particularly where the purchase price assumes subdivision yield, extra dwellings, a commercial use or redevelopment beyond the existing development approval or lawful use rights. A brief planning review can identify whether the opportunity is code assessable, impact assessable, accepted development subject to requirements or simply not supported at all by the applicable Planning Scheme/City Plan.
For existing projects, advice is equally useful when council issues an information request or when a design change moves the proposal outside the original assessment assumptions. The right response is rarely a generic letter. It should address the relevant statutory provisions, planning scheme outcomes and site-specific facts.
At Consult Planning, we help Queensland clients assess the pathway early, prepare clear development applications and manage the process through to a decision. The aim is practical: reduce surprises, protect the project programme and give council a properly supported basis to approve the application.
Before the plans are locked in or the contract goes unconditional, take the time to confirm what the planning scheme actually requires. A clear answer on the assessment pathway can protect a significant investment and point the project in the right direction from day one.
