Clause 52.37 Canopy Trees: what it actually weighs, and where applications come unstuck

Amendment VC289 introduced Clause 52.37 into every Victorian planning scheme on 15 September 2025. It creates a planning permit trigger to remove, destroy or lop a canopy tree in most residential zones. If you prepare or assess applications on residential land, it changes what you need to consider before a footprint is developed.

The headline most coverage leads with is "you now need a permit to remove a tree." True, but that's not the part that decides your application. What decides it is the narrow list Clause 52.37 lets the Responsible Authority (Council) consider, and the trap is the boundary canopy tree, which loses the exemptions a regular canopy tree gets.

What counts as a canopy tree

A canopy tree under the clause has all three of: a height of more than 5 metres, a trunk circumference of more than 0.5 metres measured at 1.4 metres above ground, and a canopy diameter of at least 4 metres (Clause 52.37-1). If a tree doesn't meet one of these criteria, it isn't caught by 52.37, though it may still be caught by an overlay.

The clause draws a second line that catches people out. A boundary canopy tree is one where any part of its trunk sits within 6 metres of the narrowest street frontage, or within 4.5 metres of the rear boundary (Clause 52.37-1). It's treated differently from a regular canopy tree, and the difference matters because the exemptions don't apply to it.

Where the permit trigger bites

The clause applies in the Mixed Use, Township, Residential Growth, General Residential, Neighbourhood Residential, and Housing Choice and Transport zones (Clause 52.37-2). Low-Density Residential, Commercial, or Industrial Zones are out.

For regular canopy trees, two exemptions do most of the work (Clause 52.37-2). A canopy tree on a site already developed with an existing dwelling is exempt. And a canopy tree assessed under Clause 54, 55, 57 or 58 as part of a development application is exempt from a separate 52.37 permit, provided it isn't removed before the permit issues.

Boundary canopy trees get neither exemption. On a standard single-dwelling site, removing or lopping a boundary canopy tree still triggers an application under 52.37. This is the trap. A designer who assumes "existing dwelling, so we're exempt" is wrong the moment the tree sits inside a boundary buffer. The State guide spells this out: on a lot with an existing dwelling, a permit is still required to remove a canopy tree within the 6-metre front and 4.5-metre rear buffers.

The practical move is the one a couple of planning firms have already worked out: get the feature survey to show trunk position and canopy spread, then overlay the front and rear buffers before driveways and the building footprint are set. Do it early, and you design around the trigger. Do it late, and you're applying for a permit you could have avoided.

The decision guidelines are deliberately narrow

This changes how a 52.37 application is argued. When the Council assesses an application under this clause, it is exempt from the Clause 65 decision guidelines and from parts of section 60 of the Planning and Environment Act 1987 (Clause 52.37-4). The state guide puts it plainly: Council "must only consider the decision guidelines contained in clause 52.37 and cannot consider other matters such as state policies, Municipal Planning Strategy and local planning policies."

So neighbourhood character, broader local policy, the general "orderly planning" arguments a planner would normally weigh, Council can't bring those to bear on a 52.37 decision. The assessment is confined to the clause's own guidelines (Clause 52.37-7): canopy contribution and urban heat, the tree's health and stability, whether it's damaging a building, the design's effort to minimise impact on canopy trees, and replacement planting.

This removes some of the discretionary arguments the Council might use to refuse an application. It also means the case for removal has to be made squarely on the clause's terms, backed by a suitably qualified person's assessment of health and condition where that's the basis for removal (Clause 52.37-6), not on a wider planning narrative.

Canopy cover is now a design input with a target

Clause 52.37-3 sets a minimum canopy outcome, not just a removal trigger, and the requirement is shaped by site area. For sites up to 1,000 square metres the clause sets a number of canopy trees, not a percentage: one tree on lots of 100 square metres or less, rising through the bands to six trees on a 701 to 1,000 square metre site (Table 1). For sites above 1,000 square metres it switches to a canopy cover target of at least 20 per cent of the site area, lifted further by a formula where existing cover already exceeds 20 per cent.

The state guide describes the small-site bands as "approximately 10 per cent" canopy cover, but the operative requirement in the clause is the tree count in Table 1, so that's what a site should be designed to meet. The requirement can be met by retaining existing canopy trees, planting new ones, or a mix. A new canopy tree has to be a species and type that at maturity reaches a height of at least 6 metres and a canopy diameter of at least 4 metres (Clause 52.37-1), and it needs real growing room: a deep soil area of at least 12 square metres with a minimum dimension of 2.5 metres, or a planter of at least 12 cubic metres and 0.8 metres deep (Clause 52.37-3).

The effect is that canopy is now a design input with a target attached, the way deep soil or setbacks are. On many sites that means new planting has to be designed in, not added once the building footprint has covered the available ground.

It sits on top of the overlays, not instead of them

Clause 52.37 doesn't override or replace the overlays. The state guide is explicit: "Clause 52.37 does not override or limit the operation of other relevant planning provisions such as overlays and the bushfire requirements." A Vegetation Protection, Environmental Significance or Significant Landscape Overlay still applies in parallel, and local laws keep operating where they cover matters outside the clause.

That interaction is where most applications come unstuck, and it has its own piece: Clause 52.37 didn't switch off the overlays: how the tree controls now stack.

What this means for you

Clause 52.37 caught a large class of residential trees that previously fell only under local law, confined the Council's discretion to a narrow set of guidelines, and put a canopy target on the site. Getting the survey and the buffers sorted before the footprint is fixed is what keeps an application clean.