Legal & Planning Advanced

Voluntary Planning Agreements NSW: A Developer's Negotiation Guide

How property developers use Voluntary Planning Agreements (VPAs) in NSW: when to offer one, negotiation leverage, costs, registration and state comparisons.

By Feasly Team
28 min read
11 June 2026
voluntary planning agreementplanning agreement nswdeveloper contributionsplanning proposal

A Voluntary Planning Agreement (VPA) often sits at the point where a New South Wales (NSW) deal either stacks up or quietly stops working. You have a site, you want more yield than the current controls allow, and the council suggests there might be a path through a planning proposal or a generous Development Application (DA), provided you “contribute” something to the community. What you contribute, how it is valued, when you hand it over and whether it binds the people who buy your finished lots are all questions that land directly on your margin. Get the structure wrong and a Voluntary Planning Agreement (VPA) can quietly absorb the entire uplift you were chasing.

Most of what is written about Voluntary Planning Agreements (VPAs) is aimed at councils or at lawyers, not at the person carrying the development risk. This guide takes the developer’s side of the table. It covers what a Voluntary Planning Agreement (VPA) is under the Environmental Planning and Assessment Act 1979 (EP&A Act), how it differs from the contributions you may already be paying, where your negotiating leverage actually sits, what the process and timing tend to look like, and how the obligations may affect your feasibility, your settlement program and your buyers. State-by-state notes are included at the end, because the equivalent mechanisms outside NSW behave differently and the trap is assuming they are the same.

What a Voluntary Planning Agreement actually is

A Voluntary Planning Agreement (VPA) is a written agreement, governed by Part 7 of the Environmental Planning and Assessment Act 1979 (EP&A Act), between a planning authority (usually a council, sometimes the Minister or a state agency) and a developer who has made, or proposes to make, a Development Application (DA) or a Complying Development Certificate (CDC), or who is seeking a change to an Environmental Planning Instrument (EPI) through a planning proposal. Under section 7.4(1) of the Environmental Planning and Assessment Act 1979 (EP&A Act), the developer agrees to provide land, monetary contributions or some other material public benefit, to be used or applied towards a public purpose.

The word “voluntary” is doing real work in that definition, and it is the single most important thing for a developer to understand. A Voluntary Planning Agreement (VPA) cannot be forced on you. It is a negotiated instrument, and as the next section explains, the legislation goes out of its way to stop a council from treating one as a precondition of approval. That said, in practice a Voluntary Planning Agreement (VPA) is most often the thing that makes an ambitious planning proposal or an out-of-the-ordinary Development Application (DA) deliverable, so the “voluntary” framing can feel academic when your project depends on the uplift. Understanding the difference between what the council can require and what it can only request is where the negotiation is won or lost.

The public purposes a Voluntary Planning Agreement (VPA) can fund

Section 7.4(2) of the Environmental Planning and Assessment Act 1979 (EP&A Act) describes a “public purpose” broadly. It includes, but is not limited to, providing or recouping the cost of public amenities or services, affordable housing, and transport or other infrastructure; funding the recurrent (ongoing) expenditure of those things; monitoring the planning impacts of development; and the conservation or enhancement of the natural environment. In practical developer terms, the contribution a council asks for under a Voluntary Planning Agreement (VPA) might be a cash payment, the dedication of a parcel of land for open space or a road widening, the construction of a public work such as a park or a stormwater asset (often called “works in kind”), the delivery of affordable housing dwellings, or a mix of these.

The breadth of that list is a double-edged feature. It gives you flexibility to offer something that genuinely suits your site, for example building a piece of public domain you were going to improve anyway, rather than writing a cheque. It also gives a council scope to ask for things that have little obvious connection to your project, which is exactly why the legislation and the supporting policy build in limits, discussed below.

How a VPA differs from section 7.11 and 7.12 contributions

If you have developed in NSW before, you have probably paid local infrastructure contributions under section 7.11 (formerly section 94) or a levy under section 7.12 (formerly section 94A) of the Environmental Planning and Assessment Act 1979 (EP&A Act). It is worth being precise about how a Voluntary Planning Agreement (VPA) differs, because the differences change your exposure. Our developer contributions and infrastructure levies guide covers the standard contributions mechanisms in detail; the summary below focuses on what sets a Voluntary Planning Agreement (VPA) apart.

The first and most consequential difference is nexus. A section 7.11 contribution must demonstrate a connection between the demand your development creates and the infrastructure the council spends the money on. Under section 7.4(4) of the Environmental Planning and Assessment Act 1979 (EP&A Act), a Voluntary Planning Agreement (VPA) does not require that nexus. Having no connection between your development and what the money is spent on does not, by itself, make the agreement invalid. The supporting policy tempers this by saying a Voluntary Planning Agreement (VPA) should not provide for public benefits that are “wholly unrelated” to the development, but the bar is plainly lower than the strict nexus test that governs section 7.11. For a developer, that means a Voluntary Planning Agreement (VPA) can be asked to carry obligations a standard contribution never could, which is both its flexibility and its risk.

The second difference is calculation. Section 7.11 contributions are calculated from the cost of the infrastructure identified in a contributions plan. A Voluntary Planning Agreement (VPA) is negotiated, so its value is whatever the parties land on. There is no published schedule that caps it, which is precisely why your negotiation strategy matters so much more here than it does when you are simply paying a levy off a rate.

The third difference is interaction. A Voluntary Planning Agreement (VPA) can be structured to operate instead of, or in addition to, section 7.11 contributions or a section 7.12 levy. Under sections 7.4(3A) and 7.4(5) of the Environmental Planning and Assessment Act 1979 (EP&A Act), a Voluntary Planning Agreement (VPA) cannot exclude the application of section 7.11 or section 7.12 unless the relevant consent authority or the Minister is a party to the agreement. Where the agreement does exclude them, the consent authority cannot then also impose a condition under those sections. This matters because you do not want to negotiate a generous Voluntary Planning Agreement (VPA) and then discover you are still being levied the standard contribution on top. Whether the agreement is in addition to, or in substitution for, the standard contributions is a term you negotiate explicitly, and section 7.4(3) of the Environmental Planning and Assessment Act 1979 (EP&A Act) requires the agreement to state which it is.

There is now a fourth interaction to watch. Since the Housing and Productivity Contribution (HPC) replaced the former Special Infrastructure Contribution (SIC) regime from 1 October 2023, with the Ministerial order updated on 1 July 2024, a Voluntary Planning Agreement (VPA) cannot exclude the application of the Housing and Productivity Contribution (HPC) without the approval of the Minister or the designated development corporation, under section 7.4(5A) of the Environmental Planning and Assessment Act 1979 (EP&A Act). The Housing and Productivity Contribution (HPC) applies to new residential, commercial and industrial development across Greater Sydney, the Lower Hunter, the Central Coast and the Illawarra-Shoalhaven, so for a great many NSW projects it now sits alongside whatever you negotiate locally. A reduction in the Housing and Productivity Contribution (HPC) may be available where a state or regional infrastructure contribution was already made before 1 October 2023 in relation to the land, including under a planning agreement, so the history of the site is worth checking during due diligence.

”Voluntary” is your leverage, not just a label

The most useful thing a developer can know about Voluntary Planning Agreements (VPAs) is that the Environmental Planning and Assessment Act 1979 (EP&A Act) actively protects the voluntary nature of the arrangement, and those protections are negotiating tools.

Under section 7.7 of the Environmental Planning and Assessment Act 1979 (EP&A Act), an Environmental Planning Instrument (EPI) cannot expressly require a planning agreement to be entered into before development consent is granted. A council cannot refuse to grant consent on the ground that you have not entered into a Voluntary Planning Agreement (VPA), or on the ground that you have not offered to. A council can only require a Voluntary Planning Agreement (VPA) as a condition of consent if you have made an offer, and then only in the terms of that offer. In other words, the obligation can only ever be one you have proposed.

Two further protections sit alongside that. Under section 7.4(9), a Voluntary Planning Agreement (VPA) cannot impose an obligation on a planning authority to grant consent or to make a change to an Environmental Planning Instrument (EPI). And under section 7.4(10), a Voluntary Planning Agreement (VPA) is void to the extent it would require or allow anything that breaches the Environmental Planning and Assessment Act 1979 (EP&A Act), an Environmental Planning Instrument (EPI) or a development consent. You cannot buy an approval, and the council cannot sell one. The supporting policy reinforces this from the council’s side: a development proposal must be assessed on its planning merits, public benefits offered under a Voluntary Planning Agreement (VPA) do not make otherwise unacceptable development acceptable, and benefits cannot be exchanged for a variation to a development standard. A variation under clause 4.6 of the Standard Instrument Local Environmental Plan (LEP) still has to be justified on planning grounds in its own right.

For a developer, the practical reading of all this is that a council that says “we will not support your proposal unless you sign a Voluntary Planning Agreement (VPA)” is overstating its position. The proposal has to be assessed on merit regardless. What the Voluntary Planning Agreement (VPA) genuinely does is let the council point to the public benefit when it explains why supporting your proposal is in the public interest. That is a real and legitimate function, and it is often what gets a marginal planning proposal across the line, but it is not the same as the council being able to demand a contribution. Knowing the difference lets you negotiate the scope and value of the offer rather than feeling cornered into accepting the council’s first number.

A note of realism balances that. The protections are strongest on paper and in the Land and Environment Court. In day-to-day practice, a council assessing a discretionary planning proposal has wide latitude, and a developer who is genuinely relying on council support has limited appetite for a fight. The point of understanding section 7.7 is not to pick a battle, it is to negotiate from an accurate sense of where the lines sit, so the contribution you offer is proportionate to the benefit you are actually receiving.

Where VPAs typically come up in a developer’s deal

A Voluntary Planning Agreement (VPA) tends to appear at one of two moments. The first is the planning proposal, where you are seeking to change the controls on your land, for example a rezoning or an increase in Floor Space Ratio (FSR) or height, through an amendment to the Local Environmental Plan (LEP). Because that change creates additional development capacity, councils frequently expect a public benefit to accompany it, and a Voluntary Planning Agreement (VPA) is the instrument that captures it. If you are early in a rezoning, our residential zoning regulations guide sets out how the zone and the controls drive your development capacity in the first place, which is the value the council will be looking at.

The second moment is the Development Application (DA), where you are applying for consent under the existing controls but seeking something that benefits from a negotiated outcome, perhaps a more ambitious built form, a staging arrangement, or a design that depends on works in the public domain. Our Development Application (DA) approval guide covers the consent process itself; the Voluntary Planning Agreement (VPA) is the side instrument that may run alongside it.

The policy guidance is explicit that, where possible, the Voluntary Planning Agreement (VPA) should be negotiated and exhibited at the same time as the related planning proposal or Development Application (DA), so the public can see the development and the public benefit together. For your program, that means the Voluntary Planning Agreement (VPA) negotiation is not a tidy-up at the end; it runs in parallel with the assessment and can become the critical path if it drags.

The value-capture trap, and why it protects you

A recurring tension in Voluntary Planning Agreements (VPAs) is value capture, the idea that a council should be able to claw back the land-value uplift that a rezoning creates. The NSW policy position is clear that value capture should not be the primary purpose of a Voluntary Planning Agreement (VPA). Councils are advised not to use a Voluntary Planning Agreement (VPA) simply to capture uplift, often expressed as a dollar figure per square metre of additional floor space or as a percentage of the increase in land value, because that creates the perception that planning decisions can be bought and sold.

This is genuinely useful to a developer. When a council frames its ask as “X per cent of your uplift”, that framing runs against the stated policy. It does not make the request unlawful, councils do still negotiate around the value created, but it gives you a principled basis to push back on a percentage-of-uplift demand and to refocus the conversation on specific, deliverable public benefits with a defensible cost. The associated policy principles, that a Voluntary Planning Agreement (VPA) should not be used for general revenue raising or to cover a council’s revenue shortfall, point the same way. Your strongest position in a negotiation is usually to offer to deliver a defined public work or land dedication with a transparent, independently verified cost, rather than to accept an open-ended monetary contribution pegged to your profit.

The process and timing, from a developer’s clock

Understanding the procedural steps matters because each one consumes time, and time on a development site is money. The indicative sequence a council follows, drawn from the NSW planning agreements practice note, runs roughly as follows, though the exact path varies by council and by deal.

It begins with an offer. There is no statutory definition of an “offer” under section 7.7(3) of the Environmental Planning and Assessment Act 1979 (EP&A Act), but the guidance is that it should be in writing, addressed to the council, signed by or on behalf of all parties other than the council, and detailed enough to cover the matters a Voluntary Planning Agreement (VPA) must contain plus anything the council’s own planning agreements policy requires. Because the obligation can only be in the terms of your offer, the offer is where you set the ceiling. Drafting it carefully, with advice, is one of the highest-leverage things you can do.

Negotiation follows, ideally running in parallel with the planning proposal or Development Application (DA) rather than after it. Then the agreement is drafted, usually by lawyers on both sides, and assessed by the council against its acceptability test. An explanatory note is prepared. The draft Voluntary Planning Agreement (VPA) and the explanatory note are then publicly exhibited for a minimum of 28 days, and the agreement cannot be entered into unless that exhibition has happened. After exhibition the council considers any submissions, may require changes (and may have to re-exhibit if the changes are material), reports the matter to an open council meeting, and then, if it resolves to proceed, the agreement is executed. Under section 203 of the Environmental Planning and Assessment Regulation 2021, the agreement is not entered into until it is signed by all relevant parties, and once executed it must be in writing, signed, and published on the NSW Planning Portal and the council’s website.

Realistically, on a planning proposal, the Voluntary Planning Agreement (VPA) negotiation, drafting, exhibition and execution can run for many months and sometimes longer than a year, and it can sit on the critical path between gateway determination and the making of the plan. For a developer, two implications follow. First, start the Voluntary Planning Agreement (VPA) conversation early, ideally at the pre-application stage, so it is not the thing holding up the rezoning. Second, build the negotiation and holding period into your feasibility, because the cost of carrying a site through an extended Voluntary Planning Agreement (VPA) process is real and is easy to under-estimate.

The explanatory note and the acceptability test

Two documents shape how your offer is received. The explanatory note is a plain-language summary of what the draft Voluntary Planning Agreement (VPA) does, how it delivers public benefit, why it is in the public interest, and when the obligations will be delivered. It is the document the public reads during exhibition, so it is worth making sure it presents your contribution accurately and fairly, because submissions are made off the back of it and the council must take those submissions into account.

The acceptability test is the council’s internal checklist. The NSW practice note frames it as five questions: whether the agreement is directed towards legitimate planning purposes identifiable in the statutory controls and adopted strategies; whether it delivers infrastructure or public benefits not wholly unrelated to the development; whether it produces outcomes that meet the general values and expectations of the public and protect the public interest; whether it provides a reasonable means of achieving the outcomes and securing the benefits; and whether it protects the community against adverse planning decisions. Individual councils add their own criteria in their planning agreements policy. Reading the relevant council’s policy before you frame your offer is sensible, because it tells you in advance how your contribution will be judged.

Costs, security and how the obligation is enforced

A Voluntary Planning Agreement (VPA) creates obligations that may run for years, so the council will want security that you will actually deliver. The common forms of security may include bonds or bank guarantees, registering the agreement on the title to the land so future owners are bound, a deed of guarantee from a related or parent company, or a combination. Each has a different cost and balance-sheet impact for a developer. A bank guarantee ties up facility capacity; registration on title constrains your dealings with the land; a parent-company guarantee exposes the wider group. These are negotiable terms, and the security package is part of the commercial deal, not an afterthought.

There are also transaction costs. A council may, and usually does, seek to recover the costs of negotiating, preparing and later administering and enforcing the agreement, and these can be written into the Voluntary Planning Agreement (VPA) itself. Where the contribution is works in kind, the council will often want an independent Quantity Surveyor (QS) to verify the cost of the works, and where land is being valued the parties may use independent valuations. Our quantity surveyor and cost estimation guide explains how a Quantity Surveyor (QS) substantiates construction cost, which is the same discipline that underpins a credible works-in-kind offer. Engaging your own Quantity Surveyor (QS) early, so your offer is grounded in a defensible number, tends to produce a better outcome than arguing valuations after the council has anchored on a figure.

Goods and Services Tax (GST) is a live issue

The Goods and Services Tax (GST) treatment of a Voluntary Planning Agreement (VPA) is not automatic and can change the real cost of the deal. The NSW guidance is direct that both parties to a planning agreement have a potential Goods and Services Tax (GST) liability and should obtain advice in every case on whether a Goods and Services Tax (GST) liability attaches. Whether a monetary contribution, a land dedication or a works-in-kind delivery is treated as consideration for a taxable supply is a question for your tax adviser on the specific facts, and the answer affects whether you are handing over a number gross or net of Goods and Services Tax (GST). It is an easy item to leave until execution and an expensive one to get wrong, so it belongs in the feasibility and in the heads of agreement, not at the signing table. The Australian Taxation Office (ATO) has published guidance on the Goods and Services Tax (GST) treatment of payments and supplies under planning agreements, and it is worth your adviser confirming the current position for your structure.

Registration on title, and what it means for your buyers

Under section 7.6 of the Environmental Planning and Assessment Act 1979 (EP&A Act), a Voluntary Planning Agreement (VPA) can be registered so that it runs with the land, but only if all parties with an interest in the land agree. Registration is the council’s preferred security in many cases because it binds future owners, which is exactly the point a developer needs to think carefully about.

If your project is a subdivision or a strata development where you will be selling completed lots, an obligation registered against the title can follow those lots to your purchasers unless the agreement is drafted so that the obligations are satisfied or released before, or on, the sale of each lot. A buyer’s solicitor doing due diligence will find a registered planning agreement, and an unsatisfied development obligation sitting on a residential lot can complicate or slow a sale, and may affect price. The practical drafting point is to negotiate clear release mechanisms: the obligation should be discharged, or the relevant lots released from the agreement, at the milestone where you have performed, so that the land you are selling is clean. This is a detail that a developer-focused lawyer will manage as a matter of course, and it is worth raising explicitly in negotiation rather than assuming the standard council template handles it in your favour. Engaging the right adviser early matters here; our property development lawyers guide covers when a planning or development specialist is the right call.

State Voluntary Planning Agreements

Not every Voluntary Planning Agreement (VPA) is with a council. A State Voluntary Planning Agreement is entered into with the Minister for Planning or a state agency, typically to fund state public infrastructure, and is more likely to arise on larger projects, state significant development, or sites within state-led precincts. The Department maintains a State Voluntary Planning Agreements register and a digital lodgement service through the NSW Planning Portal. The framework principles are the same as for local agreements, but the counterparty, the scale of the infrastructure and the internal approval pathway differ, so the negotiation tends to be more structured and the timeframes longer. If your project is large enough to attract state interest, treat the State Voluntary Planning Agreement as its own workstream with its own program.

How a VPA lands in your feasibility

A Voluntary Planning Agreement (VPA) is, in the end, a feasibility input, and the discipline that protects your margin is treating it like one from the start rather than as a planning footnote. Three things tend to catch developers out.

The first is timing of the cash or works. A monetary contribution payable on the issue of the first construction certificate hits your cash flow very differently from one payable on the issue of the first occupation certificate or staged across a multi-building program. Land dedication and works in kind have their own timing, often tied to milestones, and the carrying cost of delivering a public work early in a project can be significant. The agreement’s delivery schedule, which section 7.4(3) of the Environmental Planning and Assessment Act 1979 (EP&A Act) requires it to set out, is a number-by-number input to your cash-flow model, not a single line item.

The second is the value itself, which is negotiated rather than fixed. Because there is no published cap, the contribution can move materially during negotiation, and the difference between the council’s opening position and a defensible, benefit-based number can be the difference between a feasible and an unfeasible project. This is precisely the kind of variable worth stress-testing. Modelling the project across a range of contribution values, and seeing where the deal stops working, tells you how hard the number is worth fighting for and at what point you should walk. Feasly’s feasibility and sensitivity analysis tools let you run the contribution as a variable and see its effect on residual land value and project return, so you go into the negotiation knowing your walk-away figure rather than discovering it afterwards.

The third is the interaction with the contributions you are already paying. As noted above, unless the agreement says otherwise, a Voluntary Planning Agreement (VPA) sits on top of section 7.11 or section 7.12 contributions and, in much of the state, the Housing and Productivity Contribution (HPC) as well. Your feasibility needs to capture the full stack, the local contribution or levy, the Housing and Productivity Contribution (HPC) where it applies, and the Voluntary Planning Agreement (VPA), rather than treating the negotiated agreement as if it replaces everything else. Confirming, in the agreement, whether the Voluntary Planning Agreement (VPA) is in addition to or in substitution for the standard contributions is both a legal term and a feasibility number.

Negotiation strategy: a practical checklist for developers

Pulling the threads together, a few practical positions tend to serve developers well when a Voluntary Planning Agreement (VPA) is on the table.

Start early and in writing. Because the obligation can only be in the terms of your offer, the offer document is your most important lever. Frame it before the council frames it for you, and frame it around specific, deliverable benefits with transparent costs rather than an open-ended payment.

Anchor on works and land, not on a percentage of uplift. The policy is on your side here. A defined public work or land dedication, costed by your own Quantity Surveyor (QS) or valuer, is easier to defend, often delivers genuine value to the project’s setting, and resists the value-capture framing that a percentage-of-profit ask invites.

Pin down timing, security and release. Negotiate when the obligation is delivered, what security the council takes and, critically, how and when the obligation is released so it does not follow your sold lots. Each of these is a commercial term with a feasibility consequence.

Confirm the interaction with other contributions and the Goods and Services Tax (GST) position before you sign, not after. State clearly in the agreement whether it operates instead of or in addition to section 7.11 or section 7.12, deal with the Housing and Productivity Contribution (HPC) where it applies, and get tax advice on the Goods and Services Tax (GST) treatment of whatever you are providing.

Model the contribution as a variable. Run it across a range in your feasibility, find the value at which the deal stops working, and let that walk-away number, rather than the pressure of the moment, govern how hard you negotiate.

Read the council’s planning agreements policy. Each council publishes its own policy and acceptability criteria. Knowing how your offer will be judged before you make it is a cheap and large advantage.

How other states handle the same problem

The NSW Voluntary Planning Agreement (VPA) is one expression of a broader idea, the negotiated agreement that secures developer-provided public benefits or controls in connection with a planning approval. Every Australian jurisdiction has some version, but the mechanics, the names and the way the obligation binds the land differ, and assuming the NSW model applies elsewhere is a common and costly error. If you develop across state lines, treat each as its own regime.

Victoria

Victoria’s closest equivalent is the agreement under section 173 of the Planning and Environment Act 1987. A section 173 agreement is made between the responsible authority and a landowner to set out conditions or restrictions on the use or development of land, or to achieve other planning objectives. It can be, and frequently is, used to secure developer contributions as an alternative to a development contributions plan or an infrastructure contributions plan, as well as to lock in staging, design controls and ongoing obligations. A defining feature, and one a developer must plan around, is that a section 173 agreement is recorded on the title and binds future owners and occupiers, so as in NSW the release mechanics matter when you are selling completed lots. Removing or amending a section 173 agreement has its own statutory process, so they are not lightly undone.

Queensland

Queensland deals with negotiated developer obligations principally through infrastructure agreements under the Planning Act 2016. An infrastructure agreement can be used where development places additional demand on trunk infrastructure, and they are also used by local governments in circumstances where infrastructure charges are not levied in the ordinary way. The Planning Act 2016 also provides for agreements relating to infrastructure partnerships. The Queensland system sits within a more codified infrastructure-charging framework than the NSW negotiated model, so the negotiated agreement tends to fill defined gaps rather than being the primary contribution mechanism.

South Australia

South Australia operates under the Planning, Development and Infrastructure Act 2016, which provides for land management agreements and supports planning agreements through regulation. Land management agreements are registered against the title and bind the land, performing a similar securing-and-binding function to the NSW and Victorian instruments, and are commonly used to tie conditions or contributions to the land for the benefit of the relevant authority.

Western Australia, Tasmania, the ACT and the Northern Territory

The smaller jurisdictions generally achieve comparable outcomes through bilateral development or contribution arrangements and through conditions registered against title, rather than through a single named statutory “planning agreement” mirroring the NSW Voluntary Planning Agreement (VPA). In Western Australia, developer contribution arrangements are typically delivered through development contribution plans under the relevant state planning policy framework, supplemented by negotiated agreements on larger or non-standard projects. Tasmania, the Australian Capital Territory and the Northern Territory each address negotiated obligations within their own planning legislation, and where the regulatory position is broadly similar the mechanism tends to share the same core features: a voluntary or negotiated agreement, a defined public benefit, and some method of binding the obligation to the land or to the developer. As always, the detail is jurisdiction-specific, the thresholds and processes differ, and local advice is essential before you assume an NSW-style approach will transfer.

Common questions developers ask

A few questions come up often enough to be worth addressing directly, though the answer in any specific case depends on your site, your council and your structure.

Can a council force me into a Voluntary Planning Agreement (VPA)? No. The agreement is voluntary, an Environmental Planning Instrument (EPI) cannot require one as a precondition of consent, and a council cannot refuse consent on the ground that you have not offered one. A council can only require a Voluntary Planning Agreement (VPA) as a condition of consent if you have offered one, and only in the terms of your offer.

Does a Voluntary Planning Agreement (VPA) guarantee my approval? No. The agreement cannot oblige a council to grant consent or to change an Environmental Planning Instrument (EPI), and your proposal still has to be assessed on its planning merits. What the agreement can do is provide a public benefit the council can point to in finding that supporting your proposal is in the public interest.

Will the Voluntary Planning Agreement (VPA) replace my section 7.11 contributions? Only if the agreement says so and the consent authority is a party. Otherwise it sits in addition to your section 7.11 or section 7.12 obligations, and in much of NSW the Housing and Productivity Contribution (HPC) applies as well. Confirm the interaction in writing.

How long does the process take? It varies widely, but on a planning proposal the negotiation, drafting, the minimum 28-day exhibition, the consideration of submissions and execution commonly run for many months and can exceed a year. Start early and keep it off your critical path where you can.

Will the obligation bind the people who buy my lots? It can, if the agreement is registered on title under section 7.6 and the obligations are not released before sale. Negotiate clear release mechanisms so the lots you sell are clean.

The takeaway for developers

A Voluntary Planning Agreement (VPA) is one of the more negotiable instruments a NSW developer encounters, and that is exactly why it rewards preparation. The value is not fixed, the obligation can only be in the terms you offer, the policy framework limits naked value capture, and almost every consequential term, timing, security, release, the interaction with other contributions and the Goods and Services Tax (GST) treatment, is something you negotiate rather than accept. The developers who do well with Voluntary Planning Agreements (VPAs) are the ones who treat them as a commercial negotiation grounded in a feasibility model, frame their own offer first, anchor on deliverable benefits with defensible costs, and know their walk-away number before they sit down. Treated that way, a Voluntary Planning Agreement (VPA) is a tool for getting an ambitious project supported. Treated carelessly, it is where the uplift quietly disappears.

This guide is general information for property developers and is not legal, tax or financial advice. The application of the Environmental Planning and Assessment Act 1979 (EP&A Act), council policies, the Housing and Productivity Contribution (HPC) and Goods and Services Tax (GST) to your project depends on your specific circumstances, and the law and policy in this area continue to change. Obtain your own professional advice before acting.

Information Disclaimer

This guide is provided for general information only and should not be relied upon as accounting, legal, tax, or financial advice. Property development projects involve complex, case-specific issues, and you should always seek independent professional advice from a qualified accountant, lawyer, or other advisors before making decisions. This guide makes no representations or warranties about the accuracy, completeness, or suitability of this content and accepts no liability for any loss or damage arising from reliance on it. This material is intended as a general guide only, not as fact.

Get started today

Ready to ditch the
spreadsheets?

Join hundreds of Australian developers already using Feasly to run faster feasos with software built specifically for the Australian and New Zealand market.

Book Demo
Personal onboarding
Australian support
No commitment required