Resource Consent New Zealand: Developer's Guide to the Process

For most New Zealanders engaging with the planning system, resource consent looks like a single piece of paperwork on the path to a renovation or a fence that breaches a boundary rule. For property developers, it is the gating event that determines whether a site is buildable at all, how long it will be held before construction, and how exposed the feasibility is to neighbours, councils, iwi authorities and the Environment Court. Most of the top-ranking resource consent content in New Zealand is written for homeowners, or for a generic mixed audience, and skips the developer-specific machinery that drives programme and feasibility risk.

This guide focuses on what a property developer may need to know about resource consent under the Resource Management Act 1991 (RMA): the activity classifications, the four consent pathways, when a proposal is non-notified, limited notified or publicly notified, the Assessment of Environmental Effects (AEE), statutory timeframes, conditions, lapsing, appeals, the Fast-track Approvals Act 2024 (FTAA), and the planned replacement of the Resource Management Act 1991 (RMA) by a Planning Act and a Natural Environment Act. References are to New Zealand legislation and council guidance throughout, with all dollar amounts in New Zealand dollars (NZD).

What resource consent actually is

Resource consent is the formal approval issued by a local authority for an activity that is not permitted as of right under a district plan, regional plan or national environmental standard. It is the consenting tool of the Resource Management Act 1991 (RMA), which has governed land use and environmental management in New Zealand since 1991 and continues to do so in 2026 while replacement legislation is debated in Parliament.

It sits alongside, but is separate from, the building consent process. A building consent confirms a proposed structure complies with the New Zealand Building Code and is issued under the Building Act 2004. A resource consent confirms the activity itself is acceptable from a land use, subdivision or environmental effects perspective. A developer commonly needs both, and on a complex site may need several resource consents under different chapters of the same plan before a single building consent is touched. The Building Performance guide to resource consent sets out the formal distinction.

For a developer, the question is rarely “do I need resource consent” in the abstract. It is “which activity classifications does my proposal trigger, how is the application going to be notified, how long is that going to take, and what is the cost of holding the site through to a decision.”

Activity classifications: the six-step ladder

The RMA classifies every activity into one of six categories. Where a proposal sits on this ladder determines whether consent is needed, how the council assesses it, and how much discretion the decision-maker has.

The Quality Planning guidance on rule structures summarises the six classes and the way they typically interact in a district plan.

A permitted activity does not need consent. It is described in the RMA, in regulations such as a national environmental standard, or in the relevant district or regional plan as permitted, and complies with any conditions specified for that activity. Permitted-activity development still needs to comply with the building code and may still need a building consent, but the council has no discretion to refuse the activity itself.

A controlled activity requires consent, but the council must grant it. Discretion is limited to imposing conditions on specified matters set out in the plan. This is the friendliest end of the consenting spectrum for a developer. Once a proposal is correctly classified as controlled, the question becomes what conditions the council will impose, not whether the activity will be allowed.

A restricted discretionary activity requires consent and the council can decline. Importantly, the council’s discretion is restricted to the matters specifically listed in the plan, regulation or national environmental standard for that activity. A common pattern for moderate breaches of bulk and location standards.

A discretionary activity requires consent and the council has full discretion to grant, decline, or impose conditions, having regard to the matters in section 104 of the Resource Management Act 1991 (RMA). Most non-trivial development applications sit here.

A non-complying activity also requires consent, but the application has to pass the gateway test in section 104D of the Resource Management Act 1991 (RMA) before it can even be considered on its merits. Either the adverse effects on the environment must be no more than minor, or the activity must not be contrary to the objectives and policies of the relevant plan. Failing both gates means the application is refused without further substantive assessment.

A prohibited activity cannot be consented at all. The only path forward is a plan change to re-classify the activity.

For a developer working up a feasibility, the activity classification is not a footnote. It is one of the largest single drivers of consenting risk, time and cost. A scheme that pencils as a restricted discretionary application is a different proposition to the same scheme on a slightly different site triggering a non-complying classification. The threshold-of-effects test for non-complying activities adds a meaningful refusal risk that needs to be priced into the feasibility, not assumed away.

The four consent pathways

Resource consent is a single statutory concept, but in practice a developer will be dealing with one or more of four distinct pathways, each processed slightly differently:

A land use consent is required for activities that breach district plan rules (height, site coverage, setback, density, parking and similar). Land use consents are processed by the territorial authority (a city or district council) and are the most common form of resource consent on a development site. The Auckland Council overview of consent types sets out the categories most developers will see in a metropolitan plan.

A subdivision consent is required to divide land into new lots, create unit titles, or adjust boundaries. Section 11 of the Resource Management Act 1991 (RMA) prohibits subdivision unless it is expressly allowed by a rule in a plan or by a resource consent. That is the inverse of the position for land use, where activities are permitted unless restricted. Subdivisions require a licensed cadastral surveyor to prepare the scheme plan and need certification under sections 223 and 224 of the Resource Management Act 1991 (RMA) before titles can be issued by Land Information New Zealand (LINZ).

A discharge consent is required for activities that discharge contaminants to air, water or land, including stormwater discharges on development sites. These are processed by the regional council (in Auckland, by Auckland Council in its dual unitary role).

Water permits and coastal permits are required for taking, damming, diverting or using water, or for activities in the coastal marine area. Most urban developers will not need water or coastal permits, but waterfront, riparian or rural-zoned projects often will.

A complex urban project may need three or four of these at once: a land use consent for the building bulk and height breaches, a subdivision consent to create titles, a discharge consent for stormwater, and an associated permitted-activity earthworks pathway under the relevant national environmental standard. Each runs to its own track and timetable, though they are typically bundled into a single application package for processing.

Notification: the most important developer decision

The single most consequential split in the resource consent regime is whether a proposal is processed as non-notified, limited notified or publicly notified. The same proposal on the same site can carry very different timing, cost and risk profiles depending on which side of the line it falls.

Sections 95 to 95G of the Resource Management Act 1991 (RMA) set out the notification framework. The Quality Planning summary of section 95A and section 95B explains the council’s decision tree.

A non-notified consent is processed without public input. Either the proposal is assessed as having no more than minor effects on the wider environment and no affected persons, or all affected persons have provided written approval. Non-notified consents must be processed within 20 working days of acceptance.

A limited notified consent is served on a defined list of affected persons, typically immediate neighbours or others whose interests are more than minor. Those persons have a 20-working-day window to lodge submissions. The council then makes a decision, with or without a hearing.

A publicly notified consent is advertised to the world. Anyone may make a submission, and the application is effectively open to the entire submitter ecosystem (resident associations, environmental groups, commercial competitors with a planning lawyer on retainer). Public notification is the slowest and most expensive end of the spectrum.

The notification determination is made under sections 95A and 95B of the Resource Management Act 1991 (RMA) within 20 working days after the application is first lodged. The council assesses whether adverse effects on the wider environment are more than minor (public notification trigger), or whether any affected persons would experience more than minor adverse effects (limited notification trigger).

The strategic question: written approvals

For a developer, the practical question is rarely “will this be publicly notified”. Most well-designed mid-scale residential and mixed-use proposals can be steered into non-notified territory. The question is whether to invest in obtaining written approvals from neighbours and other affected persons before lodgement.

A person who has given written approval under section 95E of the Resource Management Act 1991 (RMA) is not an affected person for notification purposes and need not be notified. The Environment Guide on written approvals sets out the formalities. Securing written approvals from the small group of neighbours who would otherwise be served with a limited notified application can collapse the consent timeline from months to weeks and remove the submission risk entirely.

The cost of obtaining written approvals is typically a handful of letters, site visits and, in some cases, minor design changes negotiated with neighbours (a setback adjustment here, a screen planting commitment there). The benefit is a non-notified pathway with a hard 20-working-day clock. For a developer holding a site at 8% blended cost of capital, every month saved at the consenting stage compounds straight into project return. The arithmetic on this is rarely close. If written approvals are obtainable, the time and money spent securing them is almost always returned several times over.

Where neighbours refuse to engage or use the approval process to extract uncommercial concessions, the application proceeds to limited notification, the submission window opens, and the consent timeline lengthens by several months in the median case.

The Assessment of Environmental Effects (AEE)

Every resource consent application must be accompanied by an Assessment of Environmental Effects (AEE) under section 88 of the Resource Management Act 1991 (RMA). The AEE is the document that the council reads, the submitters argue against, and the commissioner ultimately weighs. It is also the document that determines whether the application is even accepted for processing.

Schedule 4 of the Resource Management Act 1991 (RMA) prescribes what the AEE must address. The Ministry for the Environment guide to section 88 and Schedule 4 is the authoritative reference. Clause 7 of Schedule 4 lists the effects that must be assessed, including:

• Effects on those in the neighbourhood and, where relevant, the wider community, including social, economic and cultural effects.
• Physical effects on the locality, including landscape and visual amenity effects.
• Effects on ecosystems, including plants, animals and physical habitat disturbance.
• Effects of the use, development or protection of natural and physical resources of the area.
• Discharge effects, where relevant.
• Effects on traffic, infrastructure capacity and amenity.
• Effects on cultural and historic heritage values.

The detail required in the AEE is meant to be proportional to the scale and significance of the proposed effects. A two-lot subdivision in an established residential area does not warrant the same document as a 200-unit apartment proposal in a transport-corridor zone. In practice, council planning teams have well-developed views on what they expect to see, and an AEE that under-shoots their expectations will trigger a section 92 request for further information (covered below) before the application is accepted for processing, burning calendar time before the statutory clock has even started.

For a developer, the AEE is the document that ties the consultant team together. The planner writes the document but draws on the architect’s design, the traffic engineer’s report, the acoustic engineer’s modelling, the landscape architect’s visual assessment, the contamination consultant’s site investigation, the cultural impact assessment (where required) and the stormwater engineer’s catchment analysis. Coordinating that team and budget realistically for the AEE work is one of the most under-priced inputs in early-stage feasibility models.

Pre-application: when to invest

Most councils now offer a formal pre-application meeting service. The Auckland Council pre-application guidance page and the Wellington City Council equivalent are typical of the larger metropolitan councils. Smaller territorial authorities offer a similar service in less formalised ways, often through a duty planner.

The pre-application meeting is paid for at a deposit rate that varies by council, with actuals invoiced against the deposit. A planner and a development engineer sit on the council side, with relevant specialists (heritage, urban design, transport, stormwater) joining as needed. The developer’s team presents the concept design, identifies the likely consent triggers, and asks the council to indicate what it will need in the AEE.

For a developer, the pre-application meeting is rarely a wasted investment. It surfaces the council’s likely concerns early, allows the design to evolve before plans are documented to a level of detail that makes them expensive to change, and creates a relationship with the planning officer who will likely be the case manager when the application is lodged. On larger or more contentious projects, two or three pre-application meetings staged through the design development phase are not unusual.

What pre-application advice does not do is bind the council. The advice is non-binding and the same council can take a different view at processing. The value is in surfacing issues, not in extracting commitments.

The statutory timeframe and the section 92 clock-stop

For a non-notified application, the statutory processing timeframe is 20 working days from acceptance. For a limited notified application, the timeframe extends with the submission and decision steps. For a publicly notified application, the typical end-to-end timeline is six to twelve months and longer where a hearing is held and appealed.

The Quality Planning summary of consent timeframes sets out the statutory clock at each stage:

• The notification determination is made within 20 working days of lodgement under section 95(2)(b) of the Resource Management Act 1991 (RMA), or 10 working days for fast-track applications under section 95(2)(a) of the Resource Management Act 1991 (RMA).
• For non-notified applications, the substantive decision is also made within 20 working days.
• For limited notified or publicly notified applications, the submission period is 20 working days.
• If a hearing is held, the decision is issued within 15 working days of the hearing closing under section 115(2) of the Resource Management Act 1991 (RMA). If no hearing is held on a notified application, the decision is issued within 20 working days of the close of submissions.

These statutory timeframes are routinely extended in practice for two reasons. First, councils may give themselves an “extension” of up to twice the statutory timeframe in special circumstances under section 37 of the Resource Management Act 1991 (RMA). Second, the clock stops when the council requests further information.

Section 92 requests for further information

Section 92 of the Resource Management Act 1991 (RMA) allows the council to request further information at any reasonable time before the hearing or before the decision is issued. The applicant must respond within 15 working days of the request, either by providing the information, refusing to provide it, or agreeing to commission an external report.

Critically, the processing clock stops when a section 92 request is made before notification, and only restarts when the response is received. The Quality Planning summary of section 92 explains the clock-stopping rules in detail.

The consequence for a developer is that a “20 working day” non-notified consent can easily stretch to 12 weeks or more in practice if multiple section 92 requests are issued and responses take time to assemble. The risk is structurally lower where the AEE has been thoroughly prepared, where pre-application engagement has surfaced the council’s concerns in advance, and where the technical reports have been peer-reviewed before lodgement.

For feasibility purposes, a planning programme that assumes the statutory 20 working days literally is almost always too optimistic. A working assumption of 8 to 14 weeks for a moderately complex non-notified application, and 6 to 12 months for a limited or publicly notified application, is closer to the market median.

Decision-making criteria: section 104

When the council comes to make a substantive decision, it is required to consider the matters in section 104 of the Resource Management Act 1991 (RMA). The Quality Planning summary of section 104 sets out the framework.

Section 104 requires the council to have regard to:

• Any actual and potential effects on the environment of allowing the activity.
• Any relevant provisions of national environmental standards, national policy statements, regional policy statements, regional plans and the relevant district plan or proposed plan.
• Any other matter the consent authority considers relevant and reasonably necessary to determine the application.

Subject to Part 2 of the Resource Management Act 1991 (RMA), case law has generally held that section 104 does not elevate any of the listed matters to a primary status. The relative weight given to each is a matter for the decision-maker. For non-complying activities, section 104D adds the gateway test (no more than minor effects, or not contrary to plan objectives and policies) before the section 104 assessment is even reached.

For a developer, this is the decision-making framework that determines whether the conditions attached to a granted consent are reasonable, whether the council’s reasons for declining a consent are appealable, and whether an Environment Court appeal has prospects.

Conditions, lapsing and the 2025 duration amendment

A granted resource consent comes with conditions. Conditions can require landscaping, infrastructure upgrades, stormwater controls, monitoring, financial bonds, infrastructure contributions, and timing constraints on staging. They are imposed under section 108 of the Resource Management Act 1991 (RMA) and must be tied back to actual or potential effects identified during the assessment.

Conditions matter enormously to feasibility. A condition requiring a $500,000 upgrade to a council stormwater outfall, or a contribution to a local park reserve at a five-figure-per-lot rate, can move a project from feasible to marginal. Reviewing draft conditions before they are finalised and negotiating proportionate alternatives is one of the most leveraged hours a developer’s planner spends on a project.

Lapsing

Once granted, a consent will lapse if not given effect to within the period specified in the consent. If no period is specified, section 125 of the Resource Management Act 1991 (RMA) defaults the lapse period to 5 years for most consents and 3 years for coastal permits for aquaculture activities. “Given effect to” generally means physical works on the ground consistent with the consent, typically the start of construction.

An extension of the lapse period can be sought under section 125 of the Resource Management Act 1991 (RMA), with the council required to consider whether substantial progress has been made towards giving effect to the consent and whether the applicant has obtained approvals from persons adversely affected by the extension. The extension is discretionary, not a right, and is often refused where the planning context has shifted in the intervening years.

The 2025 duration of consents amendment

In 2025, the Government introduced the Resource Management (Duration of Consents) Amendment Bill 2025 as an interim measure to prevent consents from expiring during the transition to the replacement legislation. Under the amendment, current resource consents due to expire before the end of 2027 are proposed to be automatically extended until 31 December 2027.

For a developer holding a consent through the transition period, the amendment removes some of the lapsing risk that would otherwise apply, but it does not extend consents indefinitely and does not change the underlying section 125 framework for consents granted after the amendment takes effect. Confirming the current state of the amendment with a planning lawyer before relying on it is sensible.

Section 127: changing conditions after grant

A consent holder can apply under section 127 of the Resource Management Act 1991 (RMA) to change or cancel conditions of a granted consent. The application is treated in the same way as a fresh resource consent application for a discretionary activity, with the council assessing the scope of the change and the consequential effects.

Where the proposed variation would result in a fundamentally different activity or one with materially different effects, the council can require a fresh application rather than a section 127 variation. The line between a permissible variation and a requirement for a new application is fact-specific and is one of the more litigated areas of consent administration.

For a developer, section 127 is the tool for accommodating design changes between consent grant and construction start: substituting one material for another where the original condition was prescriptive, varying a stormwater control regime where the engineering has been refined, or adjusting a staging condition where market conditions have moved. Used early and judiciously, it can save a project from a costly re-consent.

Appeals to the Environment Court

A resource consent decision can be appealed to the Environment Court of New Zealand within 15 working days of receiving the decision. The 15-working-day deadline is strict, and a late appeal requires the Environment Court to grant a waiver of time.

The right of appeal varies by notification status. Applicants and submitters on notified applications have full appeal rights. For non-notified consents, appeal rights are typically limited to specific procedural challenges rather than a merits review.

The filing fee is $600 at lodgement. Costs from there scale rapidly: counsel, expert witnesses, hearing time and (in many cases) the prospect of a cost award against the unsuccessful party are all significant. The Environment Guide on lodging appeals sets out the procedural requirements in detail.

For a developer, the Environment Court is a strategic backstop, not a routine step. Most consent disputes are better resolved at the hearing stage through pre-hearing meetings and section 36A mediation. By the time a matter reaches the Environment Court, the project programme has already absorbed many months of delay and the cost of the appeal is rarely justified by the expected value of the consent.

The Fast-track Approvals Act 2024

In December 2024, the New Zealand Parliament enacted the Fast-track Approvals Act 2024 (FTAA), a permanent alternative consenting pathway for projects with significant regional or national benefit. A new applications process opened on 7 February 2025, administered by the Environmental Protection Authority (EPA) and the Ministry for the Environment.

The Fast-track Approvals Act 2024 (FTAA) consolidates multiple approval regimes (resource consents under the Resource Management Act 1991 (RMA), notices of requirement, certificates of compliance, certain conservation approvals, and aquaculture decisions) into a single integrated process. A project that would otherwise need consents from multiple regulators can be packaged into a single Fast-track Approvals Act 2024 (FTAA) substantive application, with the decision made by an expert panel rather than a council hearing commissioner.

There are two pathways under the Act:

A listed project is named in Schedule 2 of the Fast-track Approvals Act 2024 (FTAA), having been identified by the Government as automatically eligible for the substantive process. Projects in this category proceed directly to substantive application without a referral step.

A referred project is a project not listed in Schedule 2 that is referred into the Fast-track Approvals Act 2024 (FTAA) by the joint Minister of Infrastructure, Minister for Regional Development and Minister for Resources. Referral applications are assessed against criteria including the project’s regional or national significance.

For property developers, the Fast-track Approvals Act 2024 (FTAA) is most relevant for large-scale housing, mixed-use, infrastructure-led and brownfield projects where the scale of the proposal justifies the application cost and the integrated approval pathway. Smaller residential development projects will typically remain in the conventional Resource Management Act 1991 (RMA) consenting stream. The economics of choosing between the two are project-specific and should be tested against an integrated planning programme before commitment.

Auckland in particular: AUP, MDRS withdrawal, PC78 and PC120

For developers operating in Auckland, the consenting landscape has been unusually volatile in 2025. The Auckland Unitary Plan (AUP) sets out the residential zoning framework, with the principal zones for medium-density urban development being Mixed Housing Urban (MHU) and Terrace Housing and Apartment Buildings (THAB). The Auckland Unitary Plan chapter on Mixed Housing Urban and the associated THAB chapter set out the height, density and bulk and location standards for each zone.

The Medium Density Residential Standards (MDRS), introduced through the Enabling Housing Supply Act 2021 amendments to the Resource Management Act 1991 (RMA), required tier 1 councils to permit up to three dwellings of up to three storeys on most residential sites without resource consent. From August 2025, the Government introduced legislation giving Auckland Council the option to withdraw Plan Change 78 (PC78), which had implemented the Medium Density Residential Standards (MDRS) into the Auckland Unitary Plan (AUP).

On 9 October 2025, Auckland Council partially withdrew Plan Change 78 (PC78), removing the Medium Density Residential Standards (MDRS) as a permitted activity across most Auckland residential zones. Development standards reverted to the underlying Auckland Unitary Plan (AUP) provisions. The council notified its replacement plan change, Plan Change 120 (PC120), on 3 November 2025. Submissions on Plan Change 120 (PC120) closed on 19 December 2025.

Plan Change 120 (PC120) is structured to direct intensification towards well-located and lower-hazard areas, with stronger controls on flood-prone and coastal-erosion-prone sites. The detail will evolve through the submission, hearing and decision stages, with a likely operative date sometime in 2026.

For a developer with active Auckland projects, the practical consequences are material. Schemes that relied on the Medium Density Residential Standards (MDRS) as a permitted-activity pathway and lodged before 9 October 2025 may still proceed under that framework (subject to transitional provisions and the Certificate of Compliance route). Schemes that had not lodged by that date are typically back into the Auckland Unitary Plan (AUP) zone rules and will need resource consent for the three-storey, three-dwelling outcomes that were previously permitted.

The reset is one of the most significant single planning events affecting Auckland development feasibilities in the current decade. Reworking yield assumptions and consenting programmes on Auckland sites in light of the Plan Change 78 (PC78) withdrawal is essential, not optional.

The RMA replacement: Planning Act and Natural Environment Act

The Resource Management Act 1991 (RMA) is being replaced. The Government released the Planning Bill and the Natural Environment Bill on 9 December 2025. Both Bills had their first reading on 16 December 2025, and submissions closed on 13 February 2026. Enactment is targeted for mid-2026, with the replacement legislation expected to fully commence in stages thereafter.

The philosophical change is one of separation. Under the Resource Management Act 1991 (RMA), urban development and environmental protection have been weighed together in a single decision-making framework. Under the new system, the Planning Act will focus on land use planning and enabling urban growth and infrastructure, while the Natural Environment Act will focus on environmental protection, with the two functions managed through parallel but distinct decision-making frameworks.

For property developers, the replacement is being framed as enabling rather than restrictive, a deliberate move away from what Government commentary has described as a culture of “no” under the Resource Management Act 1991 (RMA). The detail will determine whether that framing holds. The transition period through 2026 and 2027 will see a period of overlap where:

• Existing resource consents granted under the Resource Management Act 1991 (RMA) remain valid and enforceable.
• Active applications continue under the Resource Management Act 1991 (RMA) until the new legislation takes effect.
• District plans, regional plans and the Auckland Unitary Plan (AUP) continue to apply.
• The Fast-track Approvals Act 2024 (FTAA) sits separately and continues operating.

The transition is the most significant planning reform in a generation and warrants close monitoring through 2026. Decisions about whether to lodge under the Resource Management Act 1991 (RMA) or wait for the new framework will become a strategic question for some projects, particularly those that are well-positioned under either regime but might gain materially under one over the other.

Iwi engagement and cultural impact assessments

Section 36A of the Resource Management Act 1991 (RMA) expressly removes any general duty on applicants to consult before lodging a resource consent application. In practice, iwi consultation is not optional on most development projects.

Where a proposal affects sites of significance to mana whenua, sits within a statutory acknowledgement area, or triggers cultural impact assessment requirements in the relevant district plan, engaging with the relevant iwi authority is functionally a prerequisite. The Auckland Council guide to engaging with mana whenua sets out the typical process in a metropolitan context, including the use of an iwi engagement portal to identify which iwi authorities to contact.

A cultural impact assessment (CIA) is commissioned from the relevant iwi authority and forms part of the AEE where required. Timing, cost and scope are negotiated directly with the iwi authority, and timeframes can range from a few weeks for straightforward sites to several months for sites of significant cultural value or where multiple iwi authorities have overlapping interests.

For a developer, allocating sufficient programme and budget for iwi engagement at the feasibility stage is one of the harder-to-quantify but increasingly important inputs. Under-resourcing it is one of the more common causes of section 92 requests, notification escalations and submission-stage opposition.

Cost ranges: what to budget

Resource consent costs vary widely by council, project complexity and consultant scope. Indicative ranges based on current council guidance and consultant rates:

The Auckland Council schedule of consent fees and deposits is the source-of-truth reference for the Auckland market, and the equivalent Wellington City Council resource consent fees schedule covers the Wellington region.

Notably, all council fees in New Zealand operate on a deposit-and-actuals basis. The deposit is paid at lodgement and the council invoices any costs in excess of the deposit at hourly rates ranging from $100 to $300+ per hour depending on the specialist and the council. For complex consents, actuals frequently exceed the deposit by a meaningful multiple. Budgeting the deposit alone is a common feasibility error.

Development contributions, infrastructure growth charges and reserve contributions sit separately to consent fees and can run into six figures per development. The Auckland Council Infrastructure Growth Charge for the metropolitan area is currently around $12,320 per residential equivalent unit, payable separately from resource consent and building consent fees.

What to budget for in feasibility

The feasibility implications of the consenting framework break down into three main lines:

Hard consenting costs (council fees, consultant fees and specialist reports) are the visible line items and the ones most commonly captured in feasibility templates. The cost ranges above are the starting point.

Holding cost during the consent period is the larger but less visible cost. A site held for nine months while a limited notified consent is processed, with finance costs running at (say) 9% blended cost of capital on a $5 million site value, costs the project around $340,000 in holding cost alone. A six-month delay from a contested public notification adds another $225,000. These numbers swamp the hard consenting costs on most projects.

Conditions and contributions crystallise at consent grant and can range from incidental to project-redefining. Stormwater upgrades, infrastructure contributions, financial bonds, traffic-engineering works and reserve contributions each need to be tested through sensitivity analysis. Modelling the impact of consent conditions on residual land value using a tool like Feasly’s feasibility software can quickly surface which conditions are deal-changing and which are absorbable.

Common developer mistakes

Patterns the more experienced consenting planners and lawyers consistently flag:

Treating the statutory 20 working days as a real programme assumption. It is the floor, not the median. A working assumption that builds in 8 to 14 weeks for a moderately complex non-notified application is closer to the market reality and protects against finance-cost overruns when the timeline slips.

Skipping pre-application engagement on the basis of cost. A few thousand dollars in pre-application fees is one of the highest-return spends in the entire consenting process. The information the council surfaces in pre-application typically shapes the AEE in ways that pay back many times over.

Under-budgeting the AEE. Most over-shooting on consenting cost comes from underestimating the consultant team needed to produce a credible AEE for the project’s scale. A 200-unit apartment scheme needs more than a basic AEE template, and the cost of trying to do it on a low-rise residential consent budget is a series of section 92 requests, notification escalations and avoidable opposition.

Ignoring written approvals as a tool. Many developers default to a limited notification pathway when written approvals from a manageable set of neighbours would have collapsed the consent into the non-notified stream. The time and cost of obtaining approvals is, in most cases, dramatically less than the time and cost of running a limited notified process.

Forgetting the lapse date. Five years feels like a long time when a consent is granted. It is not, particularly when finance, presales and construction sequencing have to fit inside the window. Tracking the lapse date in the project register and applying for an extension well before expiry is a small administrative discipline that prevents a costly re-consent.

Treating the Resource Management Act 1991 (RMA) replacement as a 2027 problem. Decisions made on current projects in 2026 may interact with the transitional provisions of the new legislation. Watching the Planning Bill and Natural Environment Bill through enactment, and stress-testing current projects against likely transition arrangements, is sensible.

Where this leaves a developer

The New Zealand resource consent regime is administratively dense, statutorily detailed and currently in transition. For a property developer, the consenting workstream is one of the largest single drivers of programme, cost and risk on most projects, and one of the most leveraged places to invest in early professional advice and pre-application engagement.

The framework that may be in place from 2027 onwards under the Planning Act and Natural Environment Act will reshape the surface of the regime, but the underlying disciplines of activity classification, effects assessment, neighbour engagement and council relationships are unlikely to change. A developer who understands the section 95 notification tests, who invests appropriately in the AEE, and who treats consenting programme assumptions with the rigour they deserve is generally well-positioned regardless of the legislative envelope.

The detail will differ from site to site. The discipline of working through the framework (what activity class, what notification pathway, what conditions, what holding cost) is universal.