Building Approvals

Why approvals stall even when the application looks complete.

Approval delays are often blamed on missing information, workload or applicant quality.

But when applications circulate between teams, requests repeat and no single point of authority holds the decision, the issue is usually deeper.

The system is absorbing effort — but not converting it into a clear, timely decision.

Building Approvals · Problem 01
Two systems. Two authorities.
Nobody owns the gap between them.
Elapsed—
CouncilDA ✓
Planning conditions attached:
Setbacks & heightFaçade treatmentRoad wideningStormwaterVegetation bufferOperational works
Certifier — NCC & Building Act
Council-written — DA conditions
1
BA
Lodged
Certifier
2
NCC &
Building Act
Certifier
3
DA Conditions
Check
Council-written
4
Certifier
Decision
Certifier
 
BA lodged — Day 1
IR — NCC non-compliance — Day 12
Revised & resubmitted — Day 24
IR — DA condition conflict — Day 31
Resubmitted — Day 52
Both layers cleared — Day 58
Awaiting certifier decision…
Council wrote the DA conditions. The certifier checks them — but can't change them.
When they conflict with the NCC, the applicant negotiates both.
Nobody has authority to resolve it. The clock keeps running.
↻ REPLAY
You are likely seeing this if

Approvals are moving — but decisions are not resolving

  • Applications progress through stages but stall before a clear decision is reached
  • The same information is requested more than once at different points in the process
  • Different teams interpret requirements differently, creating rework and inconsistency
  • Adding staff or introducing new systems has not improved approval timeframes
  • Escalations are increasing as pressure builds in the approvals pipeline
  • Decisions are revisited late in the process, even when the application appears complete
These are not isolated issues. They indicate a system that is processing activity — but not consistently producing decisions.
What is actually happening

Approvals are not stalling in assessment. They are stalling in decision structure.

Most approvals environments are designed to gather information, not to resolve decisions.

As applications move between teams, each function adds input — but no single structure ensures those inputs are resolved into a clear, accountable decision.

The result is not a lack of effort. It is a system that cannot convert activity into outcome.

Information is collected across multiple teams
↓
Interpretation varies and requirements are applied inconsistently
↓
No single point of authority resolves the decision
↓
Applications circulate, repeat and stall

Until the decision structure is clear — who decides, based on what evidence, and at what point — approvals will continue to absorb effort without producing consistent outcomes.

Where the Delay Actually Enters

Assessment capacity is absorbed

Teams repeatedly review, clarify and reassess the same application because uncertainty was not resolved earlier in the pathway.

Escalation pressure increases

As applications remain unresolved, political pressure, applicant frustration and internal escalation begin to grow across the pipeline.

Decision velocity declines

The approvals system becomes increasingly occupied managing unresolved applications instead of progressing new decisions efficiently.

What this pattern costs
Most organisations measure application volume and approval timeframes. Few measure the cumulative operational cost of unresolved decisions moving repeatedly through the system.
  • If 25% of applications require multiple reassessment cycles
  • and each reassessment absorbs additional review hours across planning, engineering and compliance teams
  • the approvals system gradually reallocates capacity away from decision-making and into rework management
In a council processing 200 applications annually, a 25% rework rate absorbs over 1,000 assessment hours into reassessment each year. At $100k+ per planner, that is not a process inefficiency — it is a six-figure cost hidden inside normal operations.
Over time, this creates a compounding effect. New applications enter a system already carrying unresolved assessment load, increasing review complexity, slowing response times and creating further escalation pressure.
The visible delay is usually only the surface symptom. The larger cost is the gradual loss of effective assessment capacity across the approvals environment.
This pattern appears consistently across approvals environments where authority, evidence thresholds and escalation pathways remain fragmented between teams. Applications continue moving operationally, but decision resolution slows as uncertainty circulates repeatedly through the system.
The application keeps moving.
The decision does not.
What Most Organisations Try First

Why normal process improvements do not resolve approval delays

What XD Thinking™ Changes

What becomes possible when decision structure is clarified earlier

Adding more assessment staff

Increases processing capacity temporarily, but unresolved decision structures continue generating reassessment and escalation cycles.

Decision authority becomes explicit

Applications no longer circulate indefinitely between teams because responsibility for decision resolution is clearly defined.

Implementing new workflow systems

Improves visibility of applications moving through the process, but does not resolve conflicting interpretation or unclear authority.

Exit criteria are consistently applied

Review stages progress against defined evidence thresholds rather than subjective interpretation between departments.

Tightening compliance requirements

Often increases review complexity and information requests without improving decision clarity or accountability.

Escalation occurs before bottlenecks form

Complex or conflicting applications are surfaced earlier instead of accumulating unresolved pressure deep in the approvals pipeline.

Introducing approval time targets

Creates pressure on the system without resolving why applications continue circulating between teams in the first place.

Assessment capacity is preserved

Teams spend less time reprocessing uncertainty and more time progressing clear, accountable decisions.

These approaches improve activity management. They do not resolve how decisions are structured across the approvals pathway.

This is not about accelerating every approval. It is about reducing the structural friction that prevents decisions from resolving consistently.

Test this against a current approval. If applications are moving but decisions are not resolving, the next step is to test where authority, evidence or escalation is breaking down in a live approval pathway. Run a Decision Discovery Session or Check Your Building Approvals Risk A 5-minute building approvals stress test. Results shown on screen.