DA conditions · Town planners

DA Conditions for Town Planners: Tracking Obligations Across Projects

A planning consultant rarely runs one development at a time. When you carry ten or twenty live approvals, the risk is not understanding any single condition, it is keeping sight of every obligation across every project at once. Structured condition tracking gives town planners that one view.

Town planners and planning consultants sit closest to the development approval, so they usually own the condition schedule that comes with it. On a single project that is manageable. The problem is scale: a busy consultancy runs many approvals in parallel, each with its own conditions, its own referral agencies, and its own timeline to plan sealing. Tracking obligations across that whole portfolio, not just within one file, is where the real risk and the real time cost sit.

What a DA condition schedule asks of a planner

In Queensland, development approval conditions come from two sources, and both flow to the town planner to manage. The assessment manager, usually the local council, decides the application and imposes conditions under the Planning Act 2016. Where an application is referred, a referral agency can direct the assessment manager to impose stated conditions, or give advice, under the same Act. So a single approval can carry conditions authored by several bodies, all of which the planner has to interpret and track to completion.

Those conditions are not open-ended. Under section 65 of the Planning Act 2016, a lawful development condition must be relevant to, but not an unreasonable imposition on, the development, or else be reasonably required in relation to it. That test is useful to a planner reviewing a schedule: it frames which conditions are properly grounded and which may be worth querying with council early, before effort is spent satisfying a condition in a way that later needs redoing.

Conditions also span the life of the project. Some are satisfied at the design stage, some during construction, and some only at completion once works are certified. A planner holding several projects has to know, at any moment, which conditions on which projects are due, outstanding, or blocked on an external party.

Where multi-project tracking breaks down

The failure mode for consultants is rarely a misread condition. It is a condition on project C that slipped while the team was heads-down on projects A and B. When each project's conditions live in a separate spreadsheet or inbox, there is no single place that answers the question a principal actually needs answered: across everything we are running, what is outstanding, what is at risk, and what needs action this week?

• No portfolio view. Condition status is trapped inside individual project files, so nobody can see the whole book of work at once. Problems surface project by project, usually late.
• External lead times invisible. Referral agency and utility sign-offs carry lead times that are easy to miss when they sit inside one project among many. Requested late, they become the critical path.
• Handover gaps. When a planner leaves or a project moves between staff, the informal knowledge of where each condition stands often leaves with them.

Time saved across the portfolio

The time saving for a consultancy comes from managing conditions once, in a structured record, rather than reconstructing status across scattered files every time a project nears plan sealing. When every condition is captured, assigned, and updated as evidence arrives, preparing for sealing on any given project is a collation exercise, not an investigation.

A shared record also lets a principal triage across projects: the conditions with long external lead times get actioned first, wherever they sit, so no single approval stalls the pipeline. See managing DA conditions across a project for the per-project discipline this builds on.

Risk reduced for the consultant

For a planning consultant, a missed condition is a professional exposure as much as a project delay. The client's settlement timeline, and the consultancy's standing with that client, both turn on conditions being satisfied and the plan being sealed on schedule. The more projects a firm runs, the greater the chance that an obligation on one of them is overlooked.

Structured tracking reduces that exposure by making the compliance position of every project explicit and current. Nothing depends on one person remembering the state of one file. See DA conditions management for property developers for how the same visibility serves the client side of the relationship.

How PlanEase supports a planning practice

PlanEase gives town planners a structured record of conditions across every project they run: extracted from each approval, assigned to a responsible party, and updated with evidence as it is collected. Instead of a spreadsheet per project, a consultancy gets one view of every obligation and its status, from approval through to plan sealing.

That portfolio-level visibility is what a firm running many concurrent DAs actually needs. It keeps every project's conditions current, surfaces what is outstanding before it becomes urgent, and holds the compliance record through staff changes and long project timelines.

For town planners, the challenge with DA conditions is breadth, not depth. Any one condition is understandable; keeping every obligation across every live approval in view is the hard part. A structured, portfolio-wide record of conditions is what lets a consultancy move projects to plan sealing on time and carry less risk across the whole book of work.