Does Building Consent Check for Land Covenants in NZ?

Short answer: no. Building consent checks compliance with the Building Code and the district plan — that's a public regulatory approval, run by council, under the Building Act. It does not check, and has no jurisdiction to check, private covenants registered on the title. You can hold a fully consented, fully built, code-compliant structure and still be in breach of a covenant — and the consequence isn't a council notice. It's a civil claim from whoever the covenant benefits, and it can surface after the job is finished and paid for.

This article explains why council consent and covenant compliance are two separate approvals that never substitute for each other, why council doesn't check covenants as a matter of jurisdiction rather than oversight, who actually holds the power to enforce one, and what happens if you build in breach — plus the one sequencing change that avoids all of it.

Two approvals, two different questions

Building consent answers one question: does this structure comply with the Building Code, and does it meet what the district plan requires for the zone it's in? It's processed by a building consent authority against a statutory checklist.

A covenant answers a different question entirely: did someone with a private interest in the land — a subdivision developer, a neighbour, a body corporate, an original vendor — register a contractual restriction on the title, and does the design comply with it? Covenants are private law. They run with the land under general property and land transfer mechanics, not the Building Act, not the district plan, and not anything council administers.

Two separate legal regimes, checked by two separate parties, for two separate reasons. Council consent was never designed to stand in for covenant compliance, and it doesn't.

Why council doesn't check — jurisdiction, not oversight

Nothing in the Building Act tells a building consent authority to search the title for private covenants, read the registered instrument, or assess whether the plans breach it. Even if a processing officer happens to glance at a title for an unrelated reason and notices a covenant, acting on it isn't part of their statutory role. It's outside what they're authorised or resourced to enforce.

That matters because it means covenants don't get missed by accident — they were never in scope. The trap is that a smooth, thorough-feeling consent process can look like everything was checked, when what was actually checked was the Building Code and the district plan. The title's private restrictions were never on that list.

What an approved consent actually protects you from

An approved building consent protects against council issuing a notice to fix, declining code compliance, or flagging a Building Code issue — the standard building-project risks. It says nothing about whether a party who benefits from a covenant will come after the finished structure. Those are unrelated questions with unrelated answer sheets.

Who can actually enforce a covenant

Not council — it has no standing here. The party who benefits from the covenant enforces it, and depending on how the instrument was set up, that's usually one of:

The original developer or subdivider. Many new-subdivision covenants exist specifically so the developer can hold a consistent look across the whole site, and developers commonly keep enforcement rights for years after the last section sells.

A neighbouring landowner, where the covenant was registered for their direct benefit — a height limit protecting their view or light is a common example.

A body corporate or incorporated society, common on newer developments set up specifically to hold and enforce the covenants on behalf of all the owners.

Whoever holds the benefit doesn't need council to act. They enforce through the ordinary civil courts, under the terms of the covenant itself — a process that runs entirely separately from anything council does or doesn't sign off on.

What happens if you build in breach

This is the part that makes a covenant breach worse than a consent problem: there's no council process that fixes it after the fact. If a consented, completed structure breaches a covenant, the covenant holder can seek an injunction, damages, or both. In practice that can mean:

Modification or demolition. Being ordered to modify or fully demolish what was built — at cost to whoever built it or whoever owns it, regardless of a valid code compliance certificate.

Damages. Payable to the covenant holder.

Legal costs. On top of the cost of the fix itself.

A normal consent problem usually has a path: amend the consent, apply for a waiver, negotiate the condition with the processing officer. A covenant breach doesn't have an equivalent administrative fix. It's civil enforcement, and by the time it surfaces, the structure is usually already standing and the client has usually already paid.

The sequencing point

Because an approved consent gives no assurance either way, the only way to actually know is to read the title before pricing or designing — not after consent is lodged, and not after the CCC comes through.

1. Order the current Record of Title and check for registered covenants before the design is finalised, not once it's already drawn.

2. If one exists, get the instrument itself — not just the fact that it's noted on the title — and read exactly what it restricts: materials, height, use, colour, structures.

3. Identify who holds the benefit: developer, neighbour, or body corporate, and whether they're still active and contactable. Some developer covenants become practically difficult to enforce once the developer has wound up, but don't assume that without confirming it — get advice.

4. If the brief conflicts with the covenant, get that resolved in writing — a variation, waiver, or removal — before design work goes further, not after the client has signed off on plans that can't be built as drawn.

5. Treat building consent approval as answering a different question. It is not evidence the covenant question has been settled, and it shouldn't be read as one.

We can tell you what's registered against a title. We can't tell you whether a specific covenant would be read to prohibit a specific design, whether it's still enforceable, or whether a particular developer or body corporate would grant a variation — that's a question for your client's lawyer.

This article explains the legal difference between building consent and a registered land covenant, and what can happen if a consented build breaches one. It isn't legal advice. For whether a specific covenant restricts a specific design, or how to seek a variation or waiver, check with your client's lawyer or the covenant holder directly.