The honest answer is sometimes. A protected tree is not permanently untouchable, but removing one is a consent process rather than a booking, and it needs a genuine case behind it. Council is not looking to be persuaded that the tree is inconvenient; it is looking for evidence that removal is justified.
This article covers what makes a tree protected in the first place, which grounds carry weight and which do not, what an application involves, and the alternatives that frequently solve the underlying problem without needing consent at all. As always, confirm the current position for your address with Auckland Council — this is general guidance, not legal advice.
What makes a tree protected
Protection comes from several directions, and a single tree can be caught by more than one at the same time.
- Scheduled notable trees. Individual trees listed by Auckland Council for their size, age, rarity, historical association or landscape value. Being on the schedule is not always apparent from the tree itself.
- Significant Ecological Areas. Vegetation within an SEA is protected as part of the ecosystem rather than as an individual specimen. Large parts of the western suburbs sit inside or adjacent to these.
- Kauri. Protected in their own right, with additional obligations arising from dieback management.
- Consent notices and covenants. Conditions attached to a subdivision or an earlier resource consent, recorded on the title and binding on whoever owns the property now.
- Reserves and public land. Trees on council land, or overhanging it, are not the adjoining owner’s to remove.
- Riparian and coastal margins. Vegetation near streams, wetlands and the coast carries protections aimed at stability and water quality.
Grounds that carry weight
Applications succeed when they demonstrate that removal is necessary rather than merely desirable. In practice, the arguments that land well are the ones supported by evidence a third party can verify.
Tree health is the strongest. A tree that is dead, dying, or so structurally compromised that it cannot be made safe by pruning has an obvious case, and an arborist report documenting decay, cavities, root damage or significant lean is the evidence that makes it.
Genuine safety risk is the next. Not a general unease about a large tree, but a specific, articulable hazard — a failure point above an occupied building, a compromised root plate on a slope above a driveway, a history of limb failure.
Actual damage that cannot be resolved another way also counts. Roots lifting a foundation or blocking a main drain, where root pruning or a barrier would not solve it or would destabilise the tree.
And removal necessary to enable a consented development, where the tree cannot reasonably be designed around and appropriate mitigation is offered.
Grounds that generally do not
It saves time to know which arguments are unlikely to succeed on their own.
Leaf and fruit drop, sap, bird mess and blocked gutters are maintenance issues rather than justifications. They are the normal consequence of having a mature tree, and council treats them that way.
Blocking a view is not a ground for removing a protected tree in New Zealand. There is no general right to a view, and this is one of the most common reasons applications fail.
Shading a lawn, a vegetable garden or solar panels is similarly weak on its own, though it may form part of a wider case if combined with something more substantive.
A general worry that a big tree might fall is understandable but not evidence. If you genuinely believe the tree is unsafe, the answer is an arborist assessment that either documents the hazard — giving you a real case — or reassures you that the tree is sound.
Wanting to build something where the tree stands is not enough by itself either. Council will usually expect to see that the design has genuinely attempted to accommodate the tree.
What the application involves
A resource consent application to remove a protected tree generally needs an arborist report at its core. That report identifies the species, size and condition, assesses structure and health, sets out the reason removal is proposed, and considers whether anything short of removal would resolve the issue.
Where the tree has ecological or amenity value, council may also want input from an ecologist or landscape architect. On a site within an SEA that is common rather than exceptional.
Mitigation is usually part of the picture. Replacement planting — often more than one tree for the one removed, sometimes of a specified species and size — is a frequent condition, and offering it upfront strengthens an application.
Costs to expect are the council application fee, the arborist report, any specialist reports required, and then the removal itself. Timeframes vary widely with complexity and how contested the application is. Start earlier than you think you need to, particularly if a settlement date or a build programme depends on it.
Alternatives worth exploring first
A surprising proportion of protected-tree enquiries turn out to have a solution that is not removal, and those solutions are cheaper, faster and far more likely to be approved.
Crown reduction brings the overall size down while keeping the tree. On a tree that has simply outgrown its position this often resolves the actual complaint. Note that reduction of a protected tree may still need consent, but it is a much easier application than removal.
Crown thinning reduces wind loading by letting air through the canopy, which addresses the "it might come down" concern directly and improves light beneath.
Crown lifting clears the lower canopy off a roof, a driveway or a path — usually the cheapest intervention available and frequently the one that solves the problem.
Deadwooding removes the parts most likely to fall without touching the living structure at all.
And targeted engineering solutions — root barriers, a redesigned drainage run, a repositioned foundation — sometimes cost less than the consent process would, and leave you with the tree.
It is worth having an arborist assess the tree with these options explicitly on the table, rather than asking only whether removal is possible. A report that says "removal is not justified, but a twenty per cent crown reduction would resolve the safety concern" is a better outcome than a refused application, and it is a great deal quicker than appealing one.
Kauri, which is a category of its own
If the protected tree in question is a kauri, expect a more involved process. These trees carry protection beyond the ordinary, and dieback management adds requirements on top of the consent question.
The disease itself does not automatically justify removal. Infected kauri can stand for years, and a tree in early decline still provides habitat, shade and — on a steep western section — root structure holding soil in place. Council will generally want to see that removal is about safety rather than about the diagnosis.
Any work near kauri, consented or not, should be carried out with proper hygiene: gear cleaned between properties, soil kept on site, machinery and foot traffic kept off the root zone, which extends well past the canopy edge. A contractor who is casual about this is a risk both to the tree and to your neighbours’ trees.
If you are dealing with a kauri, our dedicated kauri dieback page covers symptoms, hygiene practice and when removal genuinely becomes the right call.
The consequences of proceeding without consent
Removing a protected tree without consent is an offence under the Resource Management Act, with penalties available that substantially exceed the cost of the tree work. Auckland Council does investigate and has prosecuted, particularly where kauri and scheduled trees are involved.
Liability rests with the landowner. A contractor who assures you it will be fine is not the person who receives the enforcement notice — you are. If a contractor is willing to proceed without you having checked, treat that as information about the contractor.
Enforcement can also require remediation: replacement planting at your cost, sometimes at a scale well beyond what was removed. And an enforcement history attached to a property is the sort of thing that surfaces during due diligence at sale, and can complicate future consent applications on the same site.
The twenty minutes it takes to check with council is the cheapest part of the entire exercise.
Where to start
Begin by confirming the tree’s status. Auckland Council’s property search and GIS viewer will show ecological overlays and scheduled trees, and your title will show any consent notices or covenants. If the answer is not clear, ask council directly and get the response in writing.
Then get an arborist assessment. Even where removal is what you want, the report is what the application rests on — and it may identify a reduction or a structural prune that solves the problem without a removal consent at all.
Our arborists work throughout West Auckland, including plenty of properties within ecological overlays and kauri country. We can assess the tree, tell you honestly whether a removal case exists, prepare the supporting report where it does, and carry out the work to any conditions council attaches.
To arrange an assessment, call 09 886 0500 or send through your address and a few photos.