Photo: SiteLogic editorial imageplanning
The Parking Overlay: Clause 45.09 and council-set rates
A Parking Overlay lets a council replace the standard Clause 52.06 car parking table with its own local rates or a cash-in-lieu contribution. This piece explains how the override works and what it does to a yield assumption.
Most feasibility models default to the parking table in Clause 52.06 without checking whether a Parking Overlay sits over the site. That is a reasonable starting assumption everywhere the overlay does not apply, and a wrong one everywhere it does. Where a council has adopted a Parking Overlay, its schedule can set a different rate entirely, or replace physical spaces with a cash contribution, and the standard table stops being the number that governs the site.
The provision
VPP Clause 45.09 (Parking Overlay) exists so a council can respond to local car parking conditions with rates tailored to a precinct or the whole municipality, rather than relying on the state-standard table alone. A schedule to the clause can identify areas or uses where local rates apply instead of the general requirement, specify a financial contribution that may be collected in place of providing physical spaces, and set out when that contribution must be paid and how it is indexed over time.
The general parking clause anticipates this override directly. Clause 52.06 (car parking) sets out the standard rate table and requirements that apply to most new uses and developments, but its own operative text recognises that a schedule to Clause 45.09 can specify a different car parking requirement or a different reduction pathway for the area it covers. The Parking Overlay is not an additional layer on top of the standard rate. Where it applies, it is the rate.
What applies
A schedule to Clause 45.09 typically does one or more of three things. It can set a local car parking rate that is lower or higher than the Clause 52.06 table for a defined use and area, reflecting factors such as proximity to public transport, an activity centre parking strategy, or heritage character where additional on-site parking would damage the streetscape. It can allow, or require, a financial contribution in lieu of providing a proportion of the required spaces on site, with the schedule stating the amount per space, the indexation method and the payment trigger. And it can identify a precinct where shared or public parking arrangements are intended to substitute for individual on-site provision, often tied to a separate parking plan or strategy the council has adopted for that area.
Which of these applies, and to what use, sits entirely in the schedule for the specific council and precinct. Two adjoining municipalities can run very different Parking Overlay settings, and a single municipality can run different schedules for different activity centres. There is no default Parking Overlay rate to memorise; the schedule is the only reliable source.
Planning Victoria's practice note on the Parking Overlay explains the intent behind the tool: to let councils align parking supply with actual local demand and transport patterns, rather than applying a single state-wide formula uniformly across areas with very different access to public transport and different urban character. That intent matters when reading a schedule, because the decision guidelines usually ask the responsible authority to weigh the same considerations, transport accessibility, character impact and demonstrated local demand, that justified the schedule's rates in the first place.
How to model it
The following figures are illustrative. They demonstrate the method and will vary by site, council and timing. Take a 20-dwelling apartment scheme where the standard Clause 52.06 table would require 30 car spaces, but the site sits inside a Parking Overlay precinct whose schedule sets a lower local rate equivalent to 20 spaces, with a cash-in-lieu contribution of $10,000 per space available for any shortfall the applicant chooses not to build. If the design provides 18 on-site spaces and pays the contribution for the remaining two, the direct cost is $20,000, but the design has also freed the floor area that ten additional basement spaces would otherwise have consumed. Depending on the site's basement economics, that reallocated area can be worth considerably more than the contribution itself, which is the actual commercial reason a Parking Overlay changes a yield assumption rather than simply changing a cost line.
Building a feasibility for a site with a Parking Overlay starts with reading the schedule before assuming the Clause 52.06 table applies. Identify whether the schedule sets a different rate, allows a cash-in-lieu substitution, or does both for different parts of the requirement. Where a contribution is available, treat the basement or podium area that a reduced physical rate frees up as a design variable in its own right, because in constrained inner and middle-ring sites the value of that reclaimed floor area often exceeds the contribution paid to free it up. Carry the contribution's indexation across the expected build programme the same way a development contribution under Clause 45.06 would be carried, since these are also typically indexed annually. Finally, do not assume a lower local rate is automatically achievable without a permit condition confirming it applies to the specific use proposed, since some schedules limit the reduced rate to particular uses or hours of operation.
What to check before exchange
Read the specific schedule to Clause 45.09 for the site's precinct in full, rather than relying on a summary from an agent or a previous feasibility. Confirm which use category the proposed development falls into, since parking rates in both Clause 52.06 and Parking Overlay schedules are use-specific, and a change in the mix of uses on a mixed-use site can shift which rate table actually governs each component. Confirm the current cash-in-lieu rate and its indexation and payment trigger directly with council rather than from an older schedule extract, since these figures move on the same kind of annual cycle as other development contribution mechanisms.
Check whether the schedule ties the reduced rate to a condition, such as a car share membership, a travel plan, or a cap on resident parking permits, since those conditions carry their own ongoing compliance obligations that outlast the permit stage. Finally, confirm whether the Parking Overlay sits alongside other overlays affecting the same site, such as a heritage or design and development overlay, because a rate reduction intended to protect streetscape character can come with its own design constraints that need to be resolved together, not sequentially.
Interaction with activity centre parking strategies
Parking Overlays are frequently adopted as the implementation mechanism for a broader activity centre parking strategy or precinct structure plan, rather than as a standalone council decision. Where that is the case, the overlay schedule should be read together with the adopted strategy document it implements, because the strategy often explains the reasoning behind a particular rate or contribution figure and can flag future reviews that would change the settings again. A schedule adopted to support a specific precinct plan can also be narrower in its area of application than the activity centre boundary itself, so checking the overlay map against the title, not just the strategy document, remains the reliable way to confirm whether the local rate actually applies to the site in question.
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-schemes.app.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.