Photo: SiteLogic editorial imageplanning
The General Residential Zone and mandatory height controls
How the General Residential Zone's mandatory maximum height and garden area requirement bound a site's envelope, and why the schedule to the zone still needs checking.
What applies
The General Residential Zone, at Clause 32.08, is the default residential zone across most of established Melbourne and regional Victoria. Its purpose is to encourage a diversity of housing that meets the needs of different households, to allow moderate housing growth in locations offering good access to jobs, services and transport, and to support development that respects the preferred neighbourhood character of the area while still accommodating more change than the Neighbourhood Residential Zone is designed to absorb.
The clause carries two standards that matter most to a feasibility: a mandatory maximum building height, and a garden area requirement expressed as a percentage of the site that scales with lot size. The height is set as a default position in the zone that the schedule can vary for a particular council; the garden area percentage, by contrast, is a fixed statewide standard set in the clause that the schedule cannot adjust. The word "mandatory" is doing real work here: unlike some of the standards elsewhere in the residential zones that a permit can vary if the decision guidelines are satisfied, a mandatory height control cannot be exceeded by a permit at all. If the schedule and the mandatory standard say a building cannot go above a given height, no amount of design merit changes that outcome.
What applies to the envelope
Because the mandatory height control cannot be varied through the permit process, it functions as a hard ceiling on the built form rather than a starting point for negotiation. This is a different discipline to overlays or discretionary standards, where a well-argued design response can sometimes secure a variation. Confirm, before any concept design work begins, whether the height figure that applies to the specific site is the zone's default position or a figure the schedule has substituted, and treat whichever figure applies as fixed.
The garden area requirement operates alongside the height control and works against building footprint rather than building height. The table in the clause sets the percentage of the site that must be kept as garden area, increasing as lot size increases, but the percentages are a fixed statewide standard set in Clause 32.08-4 and, unlike the height control, are not variable by the schedule to the zone. Read together, the mandatory height and the garden area requirement effectively define a three-dimensional envelope for the site: how tall it can go, and how much of the ground plane must stay uncovered. A concept plan that satisfies one but not the other has not solved the site.
The decision guidelines direct the responsible authority to weigh housing diversity, the pattern and character of the surrounding area, and the site's relationship to nearby activity centres and transport, in addition to compliance with the mandatory and default numeric standards.
How to model it
Establish the mandatory height that applies to the specific address from the current schedule to the zone, and the garden area percentage from the lot-size table in the clause itself, before testing any massing options. Because the height control is mandatory rather than discretionary, there is no value in modelling a scenario above it on the assumption that a strong design argument might carry a variation. That argument does not exist for a mandatory standard.
The following figures are illustrative. They demonstrate the method and will vary by site, council and timing. Consider a 1,000 square metre GRZ lot where the applicable schedule holds the zone's default mandatory height, and the fixed garden area standard, on this lot size, requires roughly a third of the site to remain uncovered. A concept that tries to achieve a given number of townhouses might find that the garden area requirement, not the height limit, is what actually constrains the achievable footprint and therefore the yield. Modelling both constraints together, rather than treating height as the binding limit by default, is what prevents a scheme being redesigned late because the garden area sum was done last.
Where a site's schedule has increased the mandatory height above the zone's default, for example to reflect a location near an activity centre, model that higher figure conservatively until it has been confirmed directly against the current scheme, since schedules are amended and a superseded figure can overstate what is achievable.
What to check before exchange
Confirm the mandatory height and garden area figures that apply to the specific address directly from the current planning scheme, not from a previous due diligence report or a comparable site, because the height figure is schedule-specific while the garden area figure is a fixed statewide standard, and both are subject to amendment. Where the site is near the boundary of an activity centre or a different zone, confirm which schedule applies to the title itself.
Check for a Design and Development Overlay or a Neighbourhood Character Overlay layered over the GRZ, since either can impose additional height, setback or built form requirements on top of the zone's mandatory standard, and the more restrictive of the two controls will govern. Request written confirmation from the council of the current standards if the mapped schedule is ambiguous, particularly on sites that appear to sit within a recently amended precinct.
Interaction with other controls
The mandatory height control in the GRZ interacts directly with any Design and Development Overlay covering the same land, and where both apply, the more restrictive figure controls the outcome. It also interacts with Clause 55, the standard applied to development of two or more dwellings on a lot, which carries its own building height and site coverage considerations that must be read consistently with the zone's mandatory standard rather than as a separate, competing test.
Why two GRZ sites can differ
Because the mandatory height is schedule-variable, two lots carrying the same General Residential Zone label can support meaningfully different built forms. A council pursuing housing growth near a train station or an activity centre may use its schedule to lift the mandatory height for that precinct well above the zone's default figure, while holding the default elsewhere in the same municipality to protect established character areas. The zone name tells a buyer or a feasibility analyst that the site sits in the middle tier of the residential zone hierarchy. It does not tell them the actual height ceiling or footprint constraint, and treating the zone label as a proxy for those figures is a preventable error.
This is also where a comparison with the Neighbourhood Residential Zone is useful. Where the NRZ is built around protecting character and limiting growth as its default position, the GRZ's default position anticipates moderate change, and its schedule is more often used to increase capacity in well-located precincts than to wind it back. Neither pattern is guaranteed on any given site. That is exactly why the schedule check forms the substance of the assessment rather than a preliminary step to it.
Record keeping and review
Record the schedule figures relied on for a feasibility, and the date they were checked, in the project file, and re-confirm them immediately before lodging a permit application or exchanging on a contract. Schedules to the GRZ are amended as councils update housing strategies and structure plans, and a mandatory standard that applied when a site was first appraised can change before a permit is finalised.
Published by the SiteLogic Editorial desk. Every fact traces to a primary source. See our standards and corrections register.
Fact-checked: 19 July 2026 · Review by: 19 July 2027
Sources: planning-schemes.app.planning.vic.gov.au · planning.vic.gov.au
Was this useful? Try the tool this post is based on:
Pro on SiteLogic. Logi: up to 60 messages a day. Logi also stops at US$15 of model cost in a Melbourne calendar month. The Developer Comms Kit and unlimited saved projects. The Strategy Lab simulator runs without Pro. Saving a scenario needs a signed-in account. $60/month or $600/year, ex GST. First 3 months are $30/month, ex GST, on monthly Pro.