EDQ Development Approvals and Conditions Compliance

What an EDQ development approval is

Economic Development Queensland is the State Government body responsible for planning and development in declared Priority Development Areas. Within a PDA, development applications are assessed and determined under the Economic Development Act 2012 rather than the Planning Act 2016, which is the framework that governs ordinary council development approvals across Queensland.

PDA development applications are decided by the Minister for Economic Development Queensland (MEDQ). A decision to grant a PDA development approval comes with conditions attached, in the same way a council DA does — covering matters such as infrastructure, engineering, easements, contributions, landscaping and operational works. The legal source is different, but the practical reality for a project team is familiar: a long schedule of conditions that all have to be satisfied and evidenced before the project can progress.

Whether a particular site falls inside a PDA is a threshold question worth confirming early, because it determines which assessment pathway, which planning instrument, and which decision-maker apply to the whole project.

Why EDQ conditions are easy to mismanage

PDA projects are often large, staged and long-running — exactly the conditions under which condition tracking tends to break down. The risk is compounded by the fact that the approval framework is unfamiliar to many teams who spend most of their time working under the Planning Act with councils.

• A different statutory framework. Because the approval is issued under the Economic Development Act rather than the Planning Act, the terminology, the decision notice format and the process steps differ from a council DA. Teams that assume the two are identical can miss requirements that are specific to the PDA pathway.
• Conditions buried in a long decision notice. EDQ approvals, like council DAs, can carry dozens of conditions issued as a PDF. Tracking them informally — in spreadsheets, emails, or from memory — is where items get lost.
• Fragmented evidence. Engineering sign-offs, infrastructure agreements, bonds and receipts accumulate across consultants, shared drives and individual inboxes over the life of a staged PDA project.
• Unclear ownership across stages. On multi-stage PDA developments, responsibility for each condition is rarely written down in one place, so work gets duplicated or conditions get overlooked between stages.

A structured approach to EDQ condition tracking

The fix is the same discipline that works for council DAs: treat conditions as a live schedule that runs across the whole project rather than a document you revisit at the end. Conditions should be extracted and categorised as soon as the EDQ approval is issued, ownership assigned for each one, and compliance evidence collected as it becomes available.

This matters more, not less, on PDA projects, because their scale and duration mean the team composition often changes before the work is finished. A single source of truth for the condition schedule protects the project against knowledge walking out the door.

Time saved

Most of the time lost on PDA projects is spent reconstructing the picture — re-reading the decision notice, chasing consultants for the latest sign-off, and working out what is actually outstanding before a stage can proceed. When conditions, owners and evidence sit in one structured schedule, that reconstruction work largely disappears.

Teams can see at a glance what is done, what is outstanding and what has been submitted, so each stage moves forward without the stop-start delays caused by hunting for information.

Risk reduced

The biggest risk on any approval — council or EDQ — is a condition that nobody realised was outstanding until settlement, finance or registration depended on it. Late-stage discovery turns a manageable item into a costly delay.

Tracking each EDQ condition against a named owner, with evidence attached, makes responsibility explicit and surfaces gaps early — while there is still time to act, rather than at the point of pressure. Clear ownership also removes the ambiguity that lets conditions fall between consultants.

How it works in practice

Planease is built for managing development approval conditions from issue through to plan registration, and the workflow is the same whether the approval came from a council under the Planning Act or from EDQ under the Economic Development Act.

• — Extract and structure conditions from the EDQ decision notice
• — Assign responsibility for each condition to a team member or consultant
• — Attach compliance evidence directly to individual conditions
• — Track progress across every stage of a long-running PDA project
• — Reach plan sealing and registration with confidence nothing has been missed

For context on how the more common council pathway compares, see our guidance on managing DA conditions across a project and the council-specific requirements set out on our Brisbane City Council DA conditions and Moreton Bay City Council DA conditions pages.

Frequently asked questions