When we speak with landowners at the early planning stage, one of the most common points of confusion is the difference between resource consent and building consent. They are not interchangeable, and in many residential projects you may need both. In simple terms, resource consent is usually about whether you are allowed to use or develop the land in a particular way under planning rules, while building consent is about whether the proposed building work complies with the Building Code.
For landowners in Auckland and Christchurch, that distinction matters. A project can look straightforward on paper and still run into delays if site coverage, setbacks, earthworks, stormwater, access, subdivision, or servicing issues have not been worked through before the building consent stage. In our experience, the fastest projects are rarely the ones that rush drawings to council first. They are the ones that resolve planning, servicing, and buildability issues in the right order.
If you are still shaping a subdivision or housing project, our land development team typically starts by reviewing the site constraints, likely planning pathway, infrastructure needs, and build sequence before detailed delivery begins.
What is resource consent?
Resource consent sits within New Zealand’s planning framework under the Resource Management Act 1991. In practice, it is the approval that may be needed when your proposed land use, subdivision, earthworks, servicing, or development does not fit within the applicable district or regional planning rules as a permitted activity.
For residential landowners, resource consent questions often arise when a project involves:
- subdividing land
- building more dwellings than zoning rules readily allow
- breaching recession planes, height limits, yards, site coverage, or landscaped area controls
- substantial earthworks or retaining
- stormwater or wastewater constraints
- vehicle crossing, access, or manoeuvring issues
- development near sensitive features, flood-prone areas, or other overlays
We usually explain resource consent as the planning permission side of a project. It addresses the effect of the proposal on the site and surrounding environment, not the technical building detail needed to construct it safely.
What is building consent?
Building consent sits under the Building Act 2004 and is administered through the building control system. Councils grant building consent when they are satisfied on reasonable grounds that the proposed work will comply with the Building Code. The application normally requires plans, specifications, and supporting technical information showing how the building work will meet code requirements.
For most new homes, terraced housing, major alterations, foundations, drainage, retaining structures, and structural work, building consent is a core part of the process. Building consent is also linked to inspections during construction and to final sign-off through the code compliance certificate process once the work is complete.
Even where some work may be exempt from building consent, we still advise landowners not to assume that means the project is free of planning or compliance obligations. Some low-risk work can be exempt from building consent and still require resource consent, depending on the planning rules applying to the site.
Where projects move from concept into delivery, our project management approach typically focuses on consent sequencing, consultant coordination, and documentation quality so the build team is not solving preventable approval issues on site.
Resource consent vs building consent: key differences
| Issue | Resource Consent | Building Consent |
|---|---|---|
| Main purpose | Assesses whether the land use, subdivision, or development is allowed under planning rules | Assesses whether the building work complies with the Building Code |
| Main legislation | Resource Management Act 1991 | Building Act 2004 |
| Main focus | Environmental effects, planning rules, site use, infrastructure, and development impacts | Structural safety, durability, fire safety, moisture control, drainage, energy efficiency, and other code requirements |
| Typical examples | Subdivision, land use breaches, earthworks, access, stormwater, servicing, overlays | New homes, additions, structural alterations, foundations, drainage, retaining requiring consent |
| Who usually assesses it | Council planning and specialist teams | Building consent authority within council |
| When it matters most | Before finalising what can be developed on the land | Before construction starts and throughout inspections/sign-off |
| End result | Consent decision with conditions if granted | Approved consent documents, inspections, then code compliance certificate if completed properly |
Do you need one, both, or neither?
There is no safe one-size-fits-all answer, but these are the broad scenarios we usually work through with landowners:
You may need resource consent only
This often happens where the key issue is subdivision, land use approval, or another planning matter before any immediate building work is undertaken. For example, a landowner may need approval to reconfigure titles or establish a development pattern before lodging detailed build documentation.
You may need building consent only
This is more likely where the proposed building work fits planning rules as a permitted activity, but still involves construction that requires technical approval under the Building Act. A compliant standalone home on a straightforward site is often closer to this pathway, although site-specific constraints still need checking.
You may need both resource consent and building consent
This is very common in residential development. Multi-unit housing, terraced homes, constrained sites, retaining, earthworks, and serviced subdivisions often trigger both planning approval and building approval. In our experience, many of the cost overruns on small-to-medium residential developments come from underestimating how often both systems intersect.
You may need neither in limited cases
Some low-risk work may be exempt from building consent, and some minor work may also be permitted under planning rules. But this is where landowners can make expensive assumptions. Exempt building work must still comply with the Building Code, and planning rules can still apply even if a building consent is not required.
Why the approval sequence matters
One of the most practical issues is timing. We generally advise landowners to confirm the planning pathway early, because resource consent can shape the design envelope, site layout, access arrangement, stormwater response, retaining strategy, and servicing approach that later flow into the building consent package.
In plain terms, building consent should not be treated as a way to solve unresolved planning problems. If the project design changes after resource consent conditions are set, or if the planning issues were not properly identified at the start, the building documentation often needs rework. That can affect consultant fees, procurement timing, and construction start dates.
For buildable residential projects, we often coordinate the planning, design, and delivery path alongside our main contractor role so there is alignment between what is approved, what is priced, and what can realistically be built on site.
Common mistakes we see landowners make
- Assuming one consent covers everything. A granted resource consent does not replace building consent, and a building consent does not override planning rules.
- Starting design too deeply before checking the site rules. This often leads to redesign once setbacks, earthworks thresholds, infrastructure limitations, or overlay issues emerge.
- Underestimating servicing and civil constraints. On development sites, stormwater, wastewater, access, retaining, and levels can become the real approval bottlenecks.
- Believing exempt building work means no further review is needed. Exempt work can still have Building Code obligations and can still create planning issues.
- Leaving documentation coordination too late. Poor alignment between planner, surveyor, architect, engineer, and builder is a common source of RFIs, redesign, and delays.
We also see a recurring real-world issue in practitioner discussions: landowners often focus on the house design first because it feels tangible, while the less visible site and compliance work gets deferred. In practice, the hidden items such as drainage paths, retaining interfaces, legal boundaries, easements, or consent conditions are often what determine whether a project runs smoothly.
Practical takeaway for landowners
If you own or are buying land for development, the most useful starting question is not “Which consent is easier?” It is “What approvals does this specific site and proposal trigger, and in what order?”
Our practical rule of thumb is:
- check the planning controls and likely resource consent triggers first
- confirm site servicing, levels, access, and civil feasibility early
- develop the design around realistic consent pathways, not assumptions
- prepare the building consent package only once the planning framework is clear enough to avoid rework
- treat final sign-off as part of the project from day one, not an afterthought
For landowners in Auckland and Christchurch, this usually means getting the right people involved early enough to connect planning, design, civil, and construction decisions before money is committed in the wrong place. In our experience, that early coordination is where a large share of project risk can be removed.
References
Author / Editorial Team
This article was produced by our internal Cypress Construction editorial team in collaboration with our land development, construction, and project delivery specialists. We write from the perspective of practitioners working across residential villas, terraced housing, standalone homes, and development projects in New Zealand. Our process combines operational experience, project coordination insight, and review of current public guidance so our articles reflect how approval pathways affect real delivery decisions on the ground.
