Development approvals · Comparison

PDA Development Approval vs Council DA: What Is Different

If your site sits inside a Priority Development Area, your approval does not come from the council under the Planning Act. It comes from Economic Development Queensland under a different Act, a different assessment document, and a different statutory clock. Knowing which pathway applies changes who you deal with, what you are assessed against, and how you track conditions through to plan sealing.

The short answer

In Queensland, a PDA development approval is assessed and decided by Economic Development Queensland (EDQ) under the Economic Development Act 2012, while a standard council DA is assessed and decided by the local government under the Planning Act 2016. EDQ states plainly that in a Priority Development Area, development applications are assessed and decided under the Economic Development Act 2012. The two pathways share a similar shape (lodge, assess, decide, condition, comply), but the decision maker, the assessment benchmark, and the statutory timeframes are different.

This matters most for developers, surveyors and planners who work across both greenfield growth fronts and infill sites, because the same project instincts do not transfer cleanly. A condition schedule from EDQ reads differently, is enforced under a different Act, and is endorsed through a different compliance process than a council DA condition schedule.

Why the distinction matters (time and risk)

Getting the pathway wrong wastes time and creates real risk, because you can spend weeks preparing against the wrong benchmark or lodging with the wrong decision maker. If a site is inside a declared PDA, the council is generally not the assessment manager for that development, so an application prepared for the council planning scheme is aimed at the wrong target.

The risk is not only at lodgement. Conditions imposed by EDQ are satisfied and endorsed by EDQ, not the council, so a team that treats a PDA approval like a council DA can chase the wrong authority for sign-offs and discover the mismatch late, when the survey plan is ready and settlement pressure is building. For a plainer primer on the PDA concept itself, see our guide to what a Priority Development Area is.

The council pathway: Planning Act 2016

A standard council DA is assessed under the Planning Act 2016 and the Development Assessment Rules, which set the stages and timeframes every application must move through. Development is either code assessable (assessed against the planning scheme, generally no public notification) or impact assessable (a broader assessment that includes public notification and the right of any person to make a submission).

The decision period is defined by the Development Assessment Rules made under section 68 of the Planning Act 2016. Under those rules the assessment manager generally has 35 business days (or a further agreed period) to assess and decide an application, with that clock affected by information requests, referrals and public notification. Referral agencies such as the Department of Transport and Main Roads, Unitywater and Energex are engaged through the referral stage under the Planning Act 2016 and Planning Regulation 2017.

The PDA pathway: Economic Development Act 2012

A PDA development application is decided by the Minister for Economic Development Queensland (MEDQ), a power generally delegated to EDQ, and it is assessed against the development scheme for that PDA rather than the council planning scheme. EDQ confirms that all PDA development applications are assessed against the development scheme for the PDA, unless an interim land use plan is in place.

The statutory clock is also different. Under the Economic Development Act 2012 there is a 40 business day statutory timeframe to decide a PDA development application, and if public notification is required the application cannot be decided until that process is complete. Public notification is not automatic: a PDA development application is publicly notified if it does not comply with aspects of the development scheme or may affect the amenity or development potential of adjoining land, with a submission period of at least 20 business days. In some PDAs the MEDQ delegates assessment to the local council, which is why confirming the decision maker before lodging is a first, not last, step.

Conditions carry through differently too. EDQ operates a compliance assessment process where documents, plans and works required by a condition are endorsed by EDQ before works proceed, rather than certified purely against council standards. Our page on EDQ development approvals and conditions compliance walks through what that endorsement process means for a project team.

Time savings: knowing the pathway up front

The clearest time saving is confirming the decision maker and assessment benchmark before you prepare anything, because that single check tells you which Act, which document, and which authority your whole application is built around. A team that establishes on day one that a site is in a PDA prepares against the development scheme and the 40 business day EDQ pathway, instead of drafting against a council planning scheme and reworking it later.

Our own analysis of public registers shows how much routine assessment volume is moving through the system, which is where lost time compounds. PlanEase tracks development-application activity across Queensland councils plus EDQ.

Approximate figures from PlanEase's analysis of public registers, data updated 16 August 2026, subject to revision. Not official statistics.

The median above is the typical council decision time across the councils we track; it is not an average, and it is drawn from calendar-based public register data rather than the statutory business-day clocks described above. EDQ, as the state PDA authority, is counted by volume only in our data and does not report a decision-time figure, which is exactly why the post-approval stage is the part of the pipeline that goes unmeasured.

Risk reduction: managing two condition regimes cleanly

The biggest risk in working across both pathways is treating an EDQ condition schedule like a council one, because the authority that must endorse compliance is different and so is the enforcement Act. A maintenance bond, an engineering certificate or a plan endorsement that would satisfy a council may need EDQ endorsement instead, and confusing the two is a structural cause of late surprises at plan sealing.

Structured condition tracking removes that ambiguity by recording, for every condition, which Act it sits under, which authority endorses it, who is responsible, and what evidence is required. That is the same discipline that underpins good council DA delivery, covered in our guide to managing DA conditions across a project, and it applies equally to PDA approvals. For the plan sealing end of a PDA project specifically, see plan sealing in Priority Development Areas.

PDA vs council DA at a glance

• Decision maker. Council DA: the local government as assessment manager. PDA: the Minister for Economic Development Queensland, generally delegated to EDQ (occasionally delegated back to the council).
• Governing law. Council DA: Planning Act 2016 and Planning Regulation 2017. PDA: Economic Development Act 2012.
• Assessment benchmark. Council DA: the local planning scheme. PDA: the development scheme for that PDA (or an interim land use plan).
• Statutory clock. Council DA: the Development Assessment Rules decision period, generally 35 business days. PDA: a 40 business day timeframe under the Economic Development Act 2012.
• Public notification. Council DA: required for impact assessable development. PDA: only where the development scheme requires it, the proposal does not comply, or it may affect adjoining land, with a minimum 20 business day submission period.
• Compliance and conditions. Council DA: satisfied against council requirements and referral agency responses. PDA: satisfied through EDQ endorsement and compliance assessment.

The PDA versus council DA distinction is not a technicality: it sets the decision maker, the benchmark, the clock and the compliance process for the entire project. Confirming the pathway before you prepare, then tracking every condition against the correct Act and authority, is the clearest way to save time and cut the risk of discovering a mismatch when the plan is ready to seal.