Why trees can become a deal breaker

Tree constraints usually show up in one of three ways.

1) The tree is legally protected

Councils often protect certain trees through local laws, planning controls, overlays, or permit conditions. That can mean:

• You cannot remove the tree without approval
• You can build, but only if the tree can be retained and protected
• Offsets or replacement planting requirements apply



If your design relies on removing a protected tree, approval risk goes up fast.

2) The design impacts are too high to mitigate

Even when removal is technically possible, councils can still push back if the impacts are considered unreasonable, especially when:

• Works sit inside the Tree Protection Zone (TPZ) or Structural Root Zone (SRZ)
• Excavation, level changes, or service trenching will damage roots
• Construction access, spoil, or storage will compact soil near the tree
• Retention is proposed, but protection measures are weak or unrealistic

This is where an arboricultural impact assessment is often required to support the design and document how impacts will be managed.

3) The tree has broader planning value

Some trees matter beyond the site boundary, for example:

• Neighbourhood character and streetscape value
• Habitat value and biodiversity considerations
• Heritage context and amenity impacts
• Visual screening and privacy outcomes



In these cases, the conversation is not just “can we remove it”, it is “should we remove it”, and “what is the net planning outcome”.

The most common scenarios where trees stall approvals

Building footprint clashes with retention requirements

This is the classic one. A footprint that works on paper ends up conflicting with TPZ or SRZ requirements once the tree is properly assessed and mapped.

Key outcome: Fewer redesigns after council feedback.

Driveways, crossovers, and access routes damage root zones

Access is often the hidden problem, especially where you need:

• A wider driveway for turning circles
• A new crossover location
• Construction vehicle access along a side boundary



Key outcome: Less back and forth with council about access impacts.

Services and drainage run through critical root areas

Water, sewer, stormwater, gas, and electrical can trigger major impacts if they require trenching through root zones.



Key outcome: Cleaner service alignment decisions before you lodge.

Trees near boundaries affect more than one property

If a tree sits close to the boundary, your works can create impacts that become a neighbour issue, particularly where:

• The tree belongs to the neighbour
• The tree is jointly impacted by both sites
• Root systems extend well into your site

Key outcome: Fewer objections caused by unclear tree impacts.

What councils usually want to see

Most councils are looking for clarity, not fluff. They want to understand the tree constraints and the plan to manage them.

Clear tree data and retention intent

Typically this includes:



• Species and condition notes
• Size measurements and location details
• A clear retention or removal recommendation
• A plan showing TPZ, and where relevant, SRZ

A defensible impact pathway

A strong pathway usually includes:

• What is being built and where
• What impacts occur, and why
• What design changes reduce impacts
• What protection measures will be installed
• What monitoring or sign-off is needed during works

Construction stage protection and compliance

If trees are being retained, councils often expect site controls that are specific and enforceable, such as:

• Tree protection fencing locations and timing
• No go zones for storage, washout, and parking
• Approved access routes
• Supervision points and inspection stages



This is also where a risk lens can matter, particularly if a retained tree sits near new targets like a driveway, playground, or building. A tree risk assessment can help separate amenity concerns from safety concerns.

A simple step by step to reduce approval risk

Step 1: Identify tree constraints before design is locked in

Do this early, ideally before you finalise:



• Footprint and setbacks
• Driveway and crossover location
• Retaining walls and level changes
• Pool, outbuildings, and service alignments

Step 2: Get the right report for the planning question

Different situations call for different levels of assessment. If council is concerned about development impacts, an impact assessment is usually the right tool, not a basic opinion letter.

Step 3: Design around retention where possible

Practical design moves that often help:



• Shift the building line away from root zones
• Reduce excavation near trees, or use piering where appropriate
• Re-route services to minimise trenching
• Use permeable surfaces or bridging solutions where feasible

Step 4: Make the protection plan buildable

If protection measures are unrealistic, council will not trust the retention promise. Plans must match how the site will actually be built.

Step 5: Align documentation, drawings, and wording

Common rejection triggers include mismatches between:

• Plans that show retention, but reports that imply removal
• Reports that assume methods not shown on the drawings
• Conditions that conflict with buildability

Quick examples of how trees change approvals

Example 1: “Small” changes that unlock approval

A minor footprint shift and revised driveway alignment can move key works outside sensitive root areas, turning a high risk retention claim into a realistic one.

Example 2: When removal becomes the sticking point

If a protected tree is central to the site and the project depends on removing it, the approval outcome can hinge on whether the planning controls allow removal at all, and whether the justification is strong enough.

Example 3: When risk becomes part of the decision

Where a retained tree is already in poor condition, or sits near high use areas, councils may require risk assessment and management conditions before consenting to retention.

Common mistakes

• Leaving tree assessment until after the architect drawings are finalised
• Treating TPZ and SRZ as “guides” rather than constraints that shape the design
• Assuming “we’ll protect it” is enough without clear, site specific measures
• Forgetting driveways, access, and services are often the biggest impacts
• Submitting inconsistent documents, or drawings that do not match the report
• Trying to argue removal without addressing planning value and alternatives

Quick checklist and next steps

Use this before lodging, or before a pre-lodgement meeting.

• Confirm which trees are protected and what approvals are needed
• Map tree constraints against the footprint, access, and services
• Decide which trees are retained and why
• Choose the right level of arborist reporting for the council question
• Ensure protection measures are realistic for the build program
• Check report wording matches the drawings, and vice versa



If you want a general overview of the permit process in Victoria, the Victorian Government guide is a useful starting point: Guidance for applying for a planning permit.

FAQs

Can council refuse my DA because of a tree?

Yes. Refusal risk increases when a tree is protected, when impacts are high and not properly addressed, or when the application does not show a realistic retention and protection pathway.

Do I always need an arborist report for a development application?

Not always, but it is common when trees are protected, close to proposed works, or likely to be impacted by excavation, access, retaining walls, or services. If council asks for it, the report needs to match the planning question, not just describe the tree.

What is the difference between TPZ and SRZ?

TPZ is a broader protection area around a tree that guides how close works should be. SRZ focuses on the structural roots that help keep the tree stable. Both can affect where you can build, dig, and run services, especially in tight sites.

Can I build inside the TPZ if I use special construction methods?

Sometimes. It depends on the tree, the type of works, and whether impacts can be reduced to an acceptable level with clear methods and a buildable protection plan. Councils generally want specific details, not broad statements.

What if the tree is on my neighbour’s property but roots extend onto mine?

Your works can still impact the tree. That can trigger council conditions and neighbour objections, especially if excavation or trenching is proposed near the boundary. It is usually best to identify and document these impacts early.

When should I involve an arborist?

Before the design is locked in. Early input can prevent avoidable footprint clashes, rework, and delays caused by late changes to access, services, and retention assumptions.

Wrap-up

Trees become approval problems when protections apply, impacts are not properly managed, or the design ignores root zone constraints. The fastest path is usually early assessment, design alignment, and a protection approach that can actually be delivered on site.



Enquire
Send your site address, plans, and timing, and we will advise what report pathway fits your approval stage.

You can reach the team via the contact page.