Back to Journal
Removing a restrictive covenant: the planning and title routesPhoto: SiteLogic editorial image

Planning Law

Removing a restrictive covenant: the planning and title routes

The routes available to vary or remove a restrictive covenant on a Victorian title, why each is difficult, and why the outcome always turns on the specific covenant and site.

·Written and fact-checked . Published .·6 min read

A restrictive covenant on title, commonly a single-dwelling covenant on an older subdivision, can be the single biggest constraint on a medium-density scheme, more binding in practice than the zoning itself. Removing or varying one is possible, but every available route is deliberately hard to use, and the outcome on any given title depends on facts this article cannot predict. Treat what follows as an explanation of how the routes work, not a forecast of how any specific covenant will resolve.

The provision

There is no single Victorian mechanism for removing a covenant. Three separate routes exist, and none of them is a formality. Practitioners looking at a site with a live restrictive covenant weigh a planning-scheme pathway, a general law application under the Property Law Act, and a negotiated release directly with the benefiting owners, and often need more than one of these to actually resolve a covenant that stands in the way of a development.

The planning-scheme route

Section 60 of the Planning and Environment Act 1987 governs how a responsible authority decides a permit application, and it is the provision practitioners point to when a permit for buildings and works would otherwise be inconsistent with a registered restrictive covenant. Broadly, the framework requires the decision maker to have regard to matters such as whether the people who benefit from the covenant have had the opportunity to be heard, and whether removing or varying the restriction would cause detriment to those beneficiaries or to the locality. Exactly how those matters are weighed on a given application, and what counts as sufficient detriment, is decided case by case on the facts in front of the decision maker, and is not something a general explanation can predict for a specific title.

It is important to separate the planning consequence from the title consequence. A permit obtained through this pathway resolves the planning question, whether the proposed use or development can proceed notwithstanding the covenant. It does not, by itself, remove the covenant from the title. The registered restriction can remain on the certificate of title even where a permit has been granted that authorises the inconsistent use or development, and that distinction is easy to miss and important to get right before relying on a permit as though it settles the title position.

The Property Law Act route

Section 84 of the Property Law Act 1958 is the general law mechanism, heard by the Supreme Court, for discharging or modifying a restriction on the use of land. This is a genuinely separate legal process from the planning system, run in a different jurisdiction on different criteria, and it is the route that actually removes or varies the covenant on title, rather than resolving a planning consequence around it. It is also, in practice, a more involved process than a planning application, because it requires identifying and giving notice to everyone with an interest in the covenant's continuation, and satisfying the Court on the statutory grounds for discharge or modification.

Negotiated release

The third route sits outside both statutory processes: a direct negotiated release or variation agreed with the owners who benefit from the covenant, then registered on title once agreed. Where the benefiting group is small and identifiable, for example a handful of neighbouring lots created under the same original subdivision, this can be the fastest and cheapest route, because it avoids both a planning permit process and a Court application. Where the benefiting group is large, historic, or difficult to identify with confidence, a negotiated release becomes impractical for the same reason the statutory processes exist, and a developer is pushed back toward the planning or general law route regardless.

In practice, a negotiated release is often pursued in parallel with one of the statutory routes rather than instead of it. A developer might approach the identifiable neighbouring beneficiaries early, while also lodging a permit application on the planning-scheme route, so that a favourable negotiated position can be used as supporting evidence of an absence of detriment if the matter proceeds to a contested decision. None of the three routes should be treated as mutually exclusive alternatives chosen at the outset. Which combination makes sense depends entirely on the specific title.

Why each route is hard

Each route is deliberately difficult because a restrictive covenant represents a property right held by other landowners, not merely a planning control that a government body can vary unilaterally. The planning-scheme route turns on how the decision maker weighs detriment and notice for a specific instrument on a specific title, which varies by the covenant's wording and by the interests actually affected. The Property Law Act route requires identifying the full class of people with a benefit under the covenant, which for an older subdivision covenant can be genuinely difficult to establish with confidence, and then satisfying the Court that discharge or modification is warranted. A negotiated release depends on the willingness of every relevant beneficiary to agree, which is not something a purchaser can assume in advance of actually approaching them.

Why this is fact-specific

None of these routes has a predictable outcome that can be described in general terms, and this article deliberately does not state what a tribunal or court will decide on a given covenant. The wording of the specific covenant, when and how it was created, who currently benefits from it, and the nature of the proposed development, all change the analysis. A covenant that has been successfully varied on a neighbouring lot is not a reliable precedent for a different title, even one created under the same original subdivision. Anyone assessing a site constrained by a restrictive covenant needs specific advice from a property lawyer who has reviewed the actual title, the covenant instrument, and the surrounding lots, before any acquisition or feasibility decision assumes the covenant can be removed or varied.

Timing and holding cost

Whichever route is realistically available, none of them resolves quickly. A Supreme Court application under the Property Law Act runs on the Court's own timetable and requires proper notice to everyone with an interest in the covenant, which takes time to establish and serve correctly. A planning-scheme application that turns on a contested covenant question can attract objections and a Tribunal review in its own right, adding the timing risk described elsewhere in this series to the covenant risk already on the table. A feasibility that assumes a covenant will be cleared within the same program as an ordinary permit application is very likely understating both the time and the professional fees the site will actually require before it can be built as intended.

What to check before exchange

Obtain a full title search and, where available, the original covenant instrument, rather than relying on a summary description from the vendor or agent. Identify, as far as the title record allows, who currently holds the benefit of the covenant, and whether that group is small and identifiable or broad and historic. Get a specific opinion from a property lawyer on which of the available routes is realistically open on the facts of that title, and treat any feasibility that assumes covenant removal as conditional on that advice, not as a settled input. Where a permit has already been obtained through the planning-scheme route, confirm separately whether the covenant itself has been removed from title, since the two are not the same outcome.


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: legislation.vic.gov.au · legislation.vic.gov.au

Our standards·

Share this article

Get new articles by email

Weekly digest of new articles. No spam. Unsubscribe any time.

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.

See Pro pricingFree tier stays free.