DA conditions · Tracking

DA Condition Tracking for Property Developers

A development approval hands you a schedule of conditions and a fixed set of deadlines you cannot see until it is too late. Condition tracking is how a developer keeps that schedule visible from the day of approval to the day the plan is sealed.

Most developers do not manage conditions line by line themselves; their consultants do. What a developer needs is tracking: a current, reliable view of which conditions are done, which are outstanding, who is responsible, and whether anything is drifting toward the critical path. That is a different problem from the day-to-day work of satisfying conditions, and it is the problem this page is about.

Tracking sounds simple until you have three active projects, each with its own DA carrying dozens of conditions, each spread across a planner, an engineer, a surveyor, and a certifier. The status lives in email threads, spreadsheets, and individual memories. No one owns the full picture, so the full picture only assembles itself at plan sealing, when there is no time left to fix what it reveals.

For the wider case for structured condition management, see DA conditions management for property developers. This page focuses specifically on the tracking layer: what it needs to do, and what it saves.

Why tracking is a developer problem, not just a consultant problem

Condition tracking is a developer problem because the consequences of an untracked condition land on the developer, not the consultant. A missed referral sign-off or an uncollected completion certificate does not shift a consultant's timeline; it shifts the settlement date, the finance drawdown period, and the holding cost. The exposure is financial and it sits with the party carrying the project.

In Queensland, that exposure has a specific shape. A survey plan cannot be registered with the Titles Registry until it is sealed by council, and it cannot be sealed until the development approval conditions are satisfied. Under the Planning Act 2016, plan sealing is the gate between an approved project and a titled, sellable lot. Any condition that is not tracked, and therefore not finished on time, holds that gate shut.

This is also where measurement runs out. PlanEase analysis of public Queensland council and Economic Development Queensland (PDA) development application registers over the rolling three months to 11 July 2026 covered ~7,870 development applications across 20 Queensland councils plus EDQ, with a median time to decision of about 24 days across the councils. The front of the pipeline, getting a decision, is measured and reasonably quick. The stage after it, tracking conditions through to plan sealing, is largely unmeasured on most projects, which is exactly why it is where time quietly disappears. See our Queensland development application insights for the measured side of that pipeline.

Approximate figures from PlanEase's analysis of public registers, subject to revision. Not official statistics.

What DA condition tracking needs to do

Effective DA condition tracking gives a developer a single, current view of every condition across every active project without having to chase consultants for updates. In practice, a tracking system for property developers needs to do a specific set of things:

• Hold every condition from the DA as a discrete, trackable item, not a buried PDF list
• Show a live status for each condition: not started, in progress, evidence held, satisfied
• Assign a responsible party to each condition so accountability is explicit
• Attach the evidence (certificates, receipts, referral approvals) to the condition it satisfies
• Surface the conditions with long external lead times early, before they become critical
• Roll up status across a portfolio, so a developer can see every project in one place

The distinction that matters for a developer is between doing the work and seeing the work. Consultants do the work. A tracking system lets the developer see it, in real time, across the portfolio, without waiting for a progress meeting. For the underlying discipline this supports, see managing DA conditions across a project.

Time savings: what tracking actually recovers

The time a tracking system saves is not the minutes spent updating a status; it is the weeks avoided at the end of the project. An outstanding matters cycle at plan sealing typically adds two to four weeks per round, and multiple rounds are common on projects where conditions were never tracked. Every one of those weeks is a week of extended finance and delayed settlement.

Tracking recovers that time by moving the discovery of problems forward. When the status of every condition is visible throughout the project, a stalled referral or a missing certificate surfaces months before plan sealing, while there is still slack in the program to fix it. The plan sealing application is then assembled from a record that was built as the project ran, not reconstructed under pressure at the end.

Across a portfolio, the saving compounds. A developer running several projects on a consistent tracking process stops rediscovering the same failure modes on each one, and stops absorbing the same avoidable delays project after project.

Risk reduction: visibility as the control

The risk that condition tracking controls is concentrated at the worst point in the project: settlement. Unconditional contracts, drawn finance, and purchasers with fixed move-in dates all depend on plan registration, which depends on plan sealing, which depends on conditions being satisfied. An untracked condition is a hidden path to a missed settlement.

Visibility is the control that reduces that risk. A developer who can see, at any point, which conditions are outstanding and who holds them can escalate early, before a slipping item becomes a critical-path failure. The risk is not eliminated, but it moves from invisible and late to visible and manageable.

For advisory firms and project managers running developments on behalf of clients, a shared tracking record is also a reporting asset: it replaces reconstructed status updates with a current, documented position that can be shared without a round of chasing.

Using PlanEase for DA condition tracking

PlanEase is built to be the tracking layer for developers and their teams. Conditions from the DA are extracted and structured as individual items, each with a status, a responsible party, and its own evidence attached as it is produced. Instead of assembling the compliance picture at the end, the developer watches it build across the project.

• Every condition tracked from DA approval through to plan sealing
• Current status visible without chasing consultants for updates
• Responsibility assigned by condition, so accountability is clear
• Evidence linked to conditions, ready for the plan sealing application
• Portfolio view across multiple projects and consultant teams

PlanEase is used by developers, town planners, and surveyors managing DA conditions on Queensland projects. For a category view of the tooling, see plan sealing software.

DA condition tracking is one of the highest-leverage things a developer can put in place, because it converts a hidden schedule of deadlines into a visible one. The conditions are fixed at approval, the responsible consultants are known, and the evidence required is generally predictable. Tracking all of it from day one, across every project, is the most direct path to faster plan sealing and more predictable settlements.