Most DA delays happen before
the application is even lodged.
Applicants submit without knowing whether their development is permissible, which controls apply, or which documents are required. The council finds out at the same time. Automated DA validation moves that discovery upstream — before submission, before the RFI cycle begins.
The DA Process Is Reactive by Design.
Development applications are lodged and then assessed. The council discovers whether an application is complete, permissible and compliant at the same time the applicant does — after submission. When something is missing or incorrect, a Request for Information is issued, the clock pauses and the resubmission cycle begins. In high-volume councils this cycle repeats across hundreds of applications simultaneously.
The underlying cause is not officer capability or applicant incompetence. It is that the validation step — checking permissibility, controls and document completeness — happens after lodgement rather than before it. Moving that step upstream changes the entire sequence.
Planning legislation · land use · permissibility
DAs sit under state planning legislation. They assess whether a use or development is permitted on a site, what planning controls apply, and whether the proposal meets those controls. Assessed by planning officers.
Building code · NCC · construction certification
BAs sit under building certification legislation. They assess whether a building design complies with the National Construction Code. Assessed by certifiers — often a different team or an external private certifier.
Both share the same structural failure — compliance checked after lodgement rather than before. The legislation differs. The sequencing problem is identical.
Applicants and councils discover the same problems at the same time.
The DA lodgement process is designed to receive applications and then assess them. There is no structured mechanism to validate permissibility, controls or document completeness before the statutory clock starts. Three failure patterns repeat across councils of every size and volume.
Permissibility unknown at the point of submission
Applicants frequently submit development applications without a clear, confirmed view of whether their proposed use is permitted on the site. Zoning, overlays and specific planning controls interact in ways that require interpretation. The council assessment team determines permissibility during the review — at which point the application is already in the queue and the statutory clock is running.
The consequence: Applications that should never have been lodged enter the assessment pipeline. Officer time is consumed on applications that cannot proceed. Applicants bear cost and delay before receiving a definitive answer.
Required documents identified during assessment
Each development type and site-specific planning control triggers a different set of required supporting documents — heritage reports, traffic impact assessments, ecological surveys, acoustic reports. These requirements are knowable before lodgement but are rarely systematically checked at that point. Officers identify missing documents during assessment and issue RFIs requesting them.
The consequence: The assessment clock pauses while applicants commission reports that should have been prepared before lodgement. Each missing document adds weeks. Multiple missing documents compound into months.
Planning controls interpreted differently each time
Floor space ratios, setbacks, height limits, car parking rates and heritage controls are applied to each application through officer interpretation. Where that interpretation varies between officers or between similar applications, applicants receive inconsistent feedback and councils accumulate exposure to challenge. Consistency requires codification — turning planning controls into structured, repeatable rules.
The consequence: Inconsistent interpretation generates applicant disputes, delays and reputational pressure on the planning team — even when individual decisions are defensible in isolation.
Automated DA validation restructures this sequence. Permissibility, applicable controls and required documents are confirmed before lodgement. By the time the statutory clock starts, the application is already complete.
When Validation Moves Before Lodgement
- ✓Permissibility confirmed before an application enters the assessment queue
- ✓Applicable planning controls identified automatically against site-specific zoning and overlays
- ✓Required supporting documents flagged before lodgement — not discovered during assessment
- ✓Planning controls applied consistently across applications — reducing interpretation variation and challenge exposure
- ✓RFI volume falls — assessment officers spend time on merit, not completeness and permissibility checks
- ✓Determination timelines shorten without legislative change, additional staff or system replacement
Common Misconceptions
-
✕A replacement for the council's assessment function
Planning merit, discretionary decisions and community consultation remain with the council. Automated validation handles permissibility and completeness — the upstream steps that currently consume officer time before merit assessment begins.
-
✕A new lodgement portal or system replacement
Urban Compass operates alongside existing council systems and lodgement platforms. It adds a pre-lodgement validation layer — it does not require replacing existing infrastructure.
-
✕Dependent on legislative change
Pre-lodgement DA validation operates within existing statutory frameworks. No legislative amendment is required to implement or pilot it.
-
✕Only for high-volume metropolitan councils
The RFI problem exists at every volume level. Regional and smaller councils often carry proportionally higher officer burden per application — pre-lodgement validation reduces that regardless of scale.
-
✕A tool only for applicants, not for councils
Urban Compass serves both sides. Applicants use it to prepare complete, compliant lodgements. Councils benefit from applications that arrive assessed against known requirements before the statutory clock starts.
They Are Three.
Development applications generate more volume and more complexity than any other approval type. Permissibility depends on overlapping GIS layers - zoning, flood, bushfire, heritage, environmental corridors, road setbacks - each maintained separately, each checked manually. The same problem hits three different groups in three different ways.
The assessment authority buried in pre-lodgement queries and incomplete applications
Before a DA is even lodged, planning officers spend significant time answering the same questions - what can I build here, what overlays apply, what documents are required. That query burden consumes assessment capacity before the clock even starts. When applications do arrive, manually checking permissibility across flood, bushfire, zoning, heritage and environmental overlays adds further delay before assessment begins. Urban Compass automates that overlay check - so questions are answered before they reach a planning officer, and lodgements arrive already permissible and document-complete.
- Councils processing high DA volumes with limited planning officer capacity
- Teams where pre-lodgement query volume is consuming assessment time
- Planning directors managing inconsistent permissibility interpretations across staff
- CIOs building the case for AI-supported assessment under the SEQ Digital Plan Priority 1.3
The applicant who needs to know what is possible before spending money on consultants
The largest single group of DA applicants is not large developers. It is families wanting to subdivide, small investors adding a secondary dwelling, local businesses changing use, and landowners trying to understand what their site permits before engaging an architect or town planner. Under the current system those questions can only be answered by booking a pre-lodgement meeting, waiting weeks, and then paying for professional advice - before knowing whether the project is even feasible. Urban Compass answers the permissibility and overlay question in minutes, before any consultant is engaged and before any money is committed to drawings.
- Owner-occupiers and small investors exploring what their site permits
- Landowners assessing development potential before sale or purchase
- Small business operators seeking to expand or change use
The planning consultant or developer lodging multiple DAs across multiple council schemes
Town planners, planning consultants, architects and developers lodging multiple DAs each month face the same manual overlay check on every project - repeated across different council planning schemes, each with different zone tables, overlay maps, and document requirements. A consultant lodging 20 DAs a month across four SEQ councils is currently doing that check manually every single time. Urban Compass configures each council's planning scheme once - GIS overlays, zone permissions, required supporting documents - and then runs the check in minutes across every project in that consultant's or developer's pipeline.
- Planning consultants and town planners lodging across multiple council areas
- Developers active across growth corridors needing consistent pre-lodgement certainty
- Architects and designers needing permissibility confirmation before investing in detailed design
DA volume is significantly higher than BA volume
Development applications cover a far broader range of activity than building approvals - from single-dwelling additions and small commercial changes through to large-scale subdivision and mixed-use development. The GIS overlay complexity (flood, bushfire, heritage, environmental, zoning) means each application type requires a different permissibility check across multiple datasets. That volume and complexity is precisely what makes automated pre-lodgement validation valuable across all three markets - not just for councils, but for every person and organisation that interacts with the development approvals system.
Urban Compass: AI-Powered DA Pre-Lodgement Validation
Urban Compass is an AI-powered town planning web application designed specifically for the Australian planning environment. It validates development feasibility, identifies applicable planning controls and flags required supporting documents before an application is lodged — so both the applicant and the council know what is needed before the statutory clock starts.
UrbanTech Plus works with Urban Compass to implement pre-lodgement DA validation for Australian councils — scoped to your planning scheme, configured to your applicable controls and piloted against your highest-RFI application types.
AI-driven evaluation of whether a proposed development is permitted on a specific site, assessed against zoning, overlays and planning scheme provisions.
Automatic identification of required supporting documents based on development type and site-specific planning controls — flagged before lodgement, not during assessment.
Structured, consistent interpretation of applicable controls including floor space ratios, setbacks, height limits, car parking rates and heritage requirements — applied the same way every time.
Built for the Australian planning environment — validated with councils and planning professionals.
Urban Compass was developed specifically for Australian statutory planning frameworks — not adapted from an overseas product. The platform has been developed in collaboration with town planning professionals and validated against real DA lodgement environments. Its approach mirrors the operational change UrbanTech Plus advocates: move the compliance and completeness check upstream, before the statutory clock starts, so the assessment team can focus on merit rather than information management. The platform is designed to serve both property owners preparing their own applications and town planners managing lodgements on behalf of clients.
Organisations that have engaged with Urban Compass include:
Source: Urban Compass Software · urbancompasssoftware.com
This work connects directly into:
DA and BA sit under different legislation but share the same structural problem
Councils managing both development and building approvals can address the sequencing failure in both streams. The governance argument is identical — the platform configuration differs to reflect the different legislative framework.
Low-readiness councils need the sequencing diagnosis before the platform
Where a council's approval delays are driven by governance ambiguity rather than completeness failures, the right starting point is a structured diagnostic that identifies the sequencing cause before any platform work begins.
What a DA Validation Pilot Typically Involves
A pilot engagement configures Urban Compass against one development type in your council area - typically medium-density residential or a high-RFI commercial category. It validates the platform against your planning scheme and recent lodgements, measures the reduction in incomplete or non-permissible submissions, and produces a clear evidence base for broader deployment.
No existing system is replaced. No legislative change is required. The pilot runs alongside your current assessment process.
Fee and timeframe are indicative. Scope is confirmed through the governance diagnostic and results call before any commitment is made. All engagements are fixed-fee with defined outputs.Is Your DA Process Ready to Be Automated?
Eight questions. Under two minutes. Your result identifies whether your council is positioned to implement pre-lodgement DA validation — and what needs to be in place first.
1 · Do you know your current RFI rate — the proportion of DAs that receive a request for further information before assessment can proceed?
2 · Can you identify which development types or application categories generate the most avoidable RFIs in your council?
3 · Are your planning scheme provisions — zoning, overlays, local controls — documented in a structured, consistent format that could be used to configure automated rules?
4 · Does your council have a clear, documented list of required supporting documents for each development type — or is this primarily held in officer knowledge?
5 · Is there executive support for implementing a pre-lodgement validation approach within your current planning framework?
6 · Have applicants, councillors or ministers raised approval timeframes as a performance concern in the past 12 months?
7 · Does your council currently offer any structured pre-lodgement service that confirms permissibility and document requirements before formal submission?
8 · Has your council identified lodgement completeness and permissibility — rather than assessment complexity — as a primary driver of DA determination delay?
Your council has real DA challenges but the planning scheme documentation and governance foundations for automated validation are not yet fully in place. The right starting point is a structured conversation to map the lodgement gap and identify which development types offer the clearest pilot opportunity.
Discuss Your SituationYour council has the beginnings of the documentation and political appetite needed for pre-lodgement DA validation. A scoping conversation can identify which development type generates the most avoidable RFIs and what a 90-day pilot would look like in your environment.
Discuss Your SituationThe documentation, executive appetite and problem awareness are in place. The next step is identifying the highest-RFI development type, scoping the planning controls to be configured, and designing a pilot that produces a measurable first-submission improvement within a single quarter.
Discuss Your SituationThe DA lodgement gap is a sequencing problem.
It has a sequencing fix.
Most councils respond to DA delay pressure by adding planners, simplifying forms or improving applicant communication. These address the symptom. Moving permissibility assessment, controls identification and document completeness checks upstream — before lodgement, before the statutory clock starts — addresses the cause.
Urban Compass was built specifically for the Australian planning environment. It is validated against real council lodgement workflows and designed to serve both the applicant preparing the submission and the council receiving it. A pilot targeting your highest-RFI development type can be scoped and measured within a single quarter.
Evidence base: Urban Compass Software · urbancompasssoftware.com · NSW Planning System Reform Bill 2025