Who we are

Auckland
Level 1, 326 New North Road
Kingsland
Auckland 1021
09 358 0140

Tauranga
07 571 1441

Christchurch
402/159 Hereford Street
Christchurch 8011
03 550 1550

Context is
Everything

Insights

Building Remediation: When the Rain Finds a Way — Responding to Unexpected Leaks in Large Complexes

Building Remediation: When the Rain Finds a Way — Responding to Unexpected Leaks in Large Complexes

It is the call every Body Corporate Chair dreads, and in an Auckland winter like this one, the phone rings more often. The rain sets in for days, and somewhere on the fourth floor a stain blooms across a ceiling, or water tracks down inside a window reveal that has been dry for fifteen years. The instinct is immediate: get someone up there, find the hole, seal it, make it stop. I understand that instinct completely. But in a large complex, a rushed patch is often the most expensive decision a committee will make all year, because it destroys the one thing the leak just gave you for free: evidence. Here is how to respond to an unexpected leak in a way that protects your building, your insurance position, and your owners’ equity.

Author: Craig Birch, Principal at Context Architects.

Outline

  • Why an unexpected leak is information, not just an emergency.
  • The first 48 hours: how to stabilise without destroying evidence.
  • Telling a one-off weather event apart from a systemic failure.
  • How a rushed repair can quietly prejudice your insurance cover.
  • Governance and liability: working out who actually owns the leak.
  • Building a “leak register” that protects you over the long term.
  • When to escalate from maintenance to diagnostic investigation.

Key Takeaways

  • A leak is a symptom; the failure is usually somewhere you cannot see.
  • Document and photograph before you repair, never after.
  • Panic-patching can void warranties and prejudice insurance claims.
  • Repeated “isolated” leaks are the signature of a systemic problem.
  • Liability between owners and common property is rarely as obvious as it looks.
  • Decision-grade evidence now prevents budget blowouts later.
  • Heavy-rain leaks are a diagnostic opportunity, not just a nuisance.

Introduction

New Zealand’s weather has a way of auditing our buildings. A still, dry month tells you nothing about how a façade performs. A sustained, wind-driven Auckland downpour tells you everything. That is why leaks so rarely arrive politely or one at a time. They cluster around weather events, appear in multiple units at once, and show up in places that seem to have no logical connection to where the water is actually getting in.

For committees governing large multi-unit developments, particularly the monolithic-clad stock built through the 1990s and 2000s, this seasonal pattern is not a coincidence. It is the building telling you something about how its weathertightness systems are ageing. The challenge is that the moment water appears inside someone’s home, the pressure to act fast becomes overwhelming. Residents are upset, carpets are wet, and everyone wants the problem gone by the weekend.

This is where good governance and bad governance part ways. Under the Unit Titles (Strengthening Body Corporate Governance and Other Matters) Amendment Act 2022, committees of large developments (10 or more units) are no longer simply maintaining a building; they are legislatively responsible for managing a multi-million-dollar asset over a 30-year horizon. An unexpected leak is the first frame of a much bigger picture, and how you respond in the first week determines whether you get to see that picture clearly, or whether you paint over it. This article is about responding well: stabilising the immediate problem, preserving the evidence, protecting your insurance and legal position, and knowing when a “wet patch” is genuinely a maintenance job versus the visible tip of a systemic failure..

Why a Leak Is Information, Not Just a Problem

The single most useful mindset shift a committee can make is to stop seeing a leak purely as damage and start seeing it as data. Water entering a building has travelled a path. It found a defect, exploited it under the specific pressure of wind-driven rain, and then tracked along framing, flashings, or services until it emerged somewhere you could see it. That path is a diagnostic trail, and it is at its most legible in the days immediately after the event.

The problem with the “seal it and move on” reflex is that it erases this trail. A bead of sealant over the visible entry point (which is almost never the actual entry point) does two things. It stops the water on this occasion, creating a false sense that the issue is resolved. And it traps moisture behind the repair, where decay continues unseen. This is the “masking effect” that has quietly converted minor timber damage into major structural rot in countless New Zealand buildings.

In a large complex, the stakes are higher still. A single leaking unit is rarely a single-unit problem. The same detail that failed on level four very likely exists on every other level. Treating the symptom in one apartment while ignoring the pattern across the building is how committees end up paying for scaffolding, consultants, and consents five times over a decade, rather than once for a comprehensive solution.

The First 48 Hours: Stabilise Without Destroying Evidence

There is a genuine tension here, and it is worth naming honestly. You do have a duty to protect the building and the affected residents, which sometimes means urgent action. But “urgent” and “permanent” are not the same thing. The goal in the first 48 hours is temporary, reversible stabilisation that stops further damage while keeping every option open.

Make it safe, not finished

Address the immediate hazards: isolate electrical fittings near water, contain and remove standing water, protect contents, and set up drying. A temporary over-cover or membrane to keep weather out is fine. A permanent re-clad or a sealed-over repair is not, at least not yet. The distinction is whether your action can be undone and inspected later without losing information.

Document obsessively, before you touch anything

This is the step committees skip and later regret. Photograph the staining, the water path, and the surrounding context. Note the date, the weather conditions, the wind direction, and which units are affected. If you can, take moisture readings and keep them. This record is what turns a vague “we had a leak” into the decision-grade evidence your advisors, insurers, and future committees will rely on.

Resist the single-trade fix

Calling one waterproofer to “have a look and sort it” feels efficient. In a multi-unit building, it is usually how the discovery gap opens up. A leak that presents as a window issue can originate in a cladding junction, a balcony membrane, or a roof penetration metres away. Until the path is understood, any repair is a guess, and a guess you have paid to make permanent.

One-Off Event or Systemic Signal? How to Tell the Difference

Not every leak signals a building-wide crisis. Sometimes a gust drives water past a tired seal that simply needs replacing. The skill is in distinguishing genuine isolated maintenance from the early warning of systemic failure, because the two demand completely different responses.

A few patterns separate them. A genuinely isolated issue tends to be a single, identifiable, accessible defect: a cracked sealant joint, a blocked scupper, a lifted flashing, with no history and no neighbours reporting the same thing. A systemic signal looks different. It recurs in the same place after each repair. It appears in multiple units sharing a common construction detail. It correlates tightly with heavy or wind-driven rain rather than constant exposure. And it often emerges far from where the water enters.

The most important word in your maintenance records is “again.” When a committee finds itself approving a third or fourth “isolated” repair to the same elevation, that is no longer a series of small problems. That is one large problem announcing itself in instalments. The honest response is to stop patching and commission a proper diagnosis of the system, not the symptom.

The Insurance Trap: How a Rushed Repair Can Cost You Cover

Insurance is where good intentions can quietly undermine a committee. In the current New Zealand market, insurers are effectively acting as regulators, scrutinising weathertightness and maintenance more closely than ever, and several common mistakes around leaks can prejudice cover.

First, repairing before documenting can weaken or invalidate a claim. If the evidence of the damage is gone, the claim becomes a matter of assertion rather than proof. Second, most policies distinguish between sudden, accidental damage (often claimable) and gradual deterioration or a maintenance defect (often excluded). How a leak is characterised, and how well it is evidenced, can determine which side of that line it falls on. Rushing a repair without understanding the cause forfeits your ability to make that case.

Third, and most seriously: once a defect is known, obligations follow. A committee that becomes aware of a weathertightness failure may have a duty to disclose it to insurers and owners, and continuing to patch around a known systemic defect rather than addressing it can affect both your cover and your governance liability. The safest path is also the most disciplined one. Document the event, notify your insurer and broker early, take temporary protective measures, and get the cause properly diagnosed before committing to permanent works.

Governance and Liability: Who Owns the Leak?

This matters because it determines who pays, who must act, and who can be held liable for inaction. A committee that tells an affected owner “that’s your problem” when the cause sits in a shared cladding system is not only likely to be wrong; it may be exposing itself to a claim. Equally, an owner who carries out their own “fix” that disturbs common property without authority creates a different set of problems.

In a unit title development, a leak immediately raises an awkward question: whose problem is it? The answer is rarely as obvious as the affected owner would like. Broadly, the Body Corporate is responsible for common property and the building’s structural and weathertightness elements, while individual owners are responsible for the interior of their own unit. But water does not respect those boundaries, and the entry point that damaged a unit’s ceiling is very often in common property.

The cleaner approach is to treat the diagnosis as a Body Corporate responsibility from the outset, precisely because the cause usually lies in shared elements, and to apportion cost only once the source is actually understood. Trying to settle the liability argument before you understand the failure is how committees end up in disputes that cost far more than the repair itself.

From Reactive Patch to Decision-Grade Evidence

The thread running through all of this is the same one that runs through every serious remediation decision: replace the anxiety of unknowns with the certainty of evidence. An unexpected leak, handled well, is not a setback. It is a free, weather-driven test of your building that hands you a starting point for understanding the asset as a whole.

Practically, that means building a simple discipline around leak events rather than treating each as a one-off crisis:

  • Keep a leak register. Record every event: date, location, affected units, weather conditions, photos, moisture readings, and what was done. Patterns only become visible when the data sits in one place.
  • Establish a digital baseline. For larger or recurring issues, an accurate 3D or as-built record of the building removes the information asymmetry that leads to disputes and variation claims later.
  • Separate triage from solution. The first decision is never “which builder do we use.” It is “do we understand the cause well enough to rule out systemic failure?”
  • Commission an evidence plan, not a build plan. Spend a small amount now on targeted investigation to reduce the much larger risk of the unknown later.

A committee that does this turns a wet ceiling into the first data point of a coherent asset strategy, rather than the first of many forgettable repair bills.

Frequently Asked Questions

What is a long-terA leak appeared in an apartment during heavy rain. Is it the owner’s problem or the Body Corporate’s?m maintenance plan and who needs one?

It depends on where the water is getting in. Generally the Body Corporate is responsible for common property and the building’s weathertightness envelope, while owners look after the interior of their unit. Because the entry point is very often in shared cladding, roofing, or flashings, the diagnosis is usually best treated as a Body Corporate responsibility, with cost apportioned once the true cause is established.

Should we claim on insurance for a single leak?

Notify your broker or insurer early regardless but document the event thoroughly first. Policies typically distinguish sudden accidental damage from gradual deterioration or maintenance defects, and how the leak is evidenced and characterised can affect whether it is covered. Repairing before recording the damage can weaken a legitimate claim.

How do we tell a one-off leak from a systemic failure?

Look for repetition and pattern. A one-off is usually a single, accessible defect with no history. A systemic issue recurs after repair, shows up in multiple units sharing the same construction detail, and correlates with wind-driven rain. If you are repairing the same area for the third or fourth time, treat it as systemic and commission a diagnosis."

What is the single most important thing to do the moment a leak appears?

Document it before you touch it. Photograph the damage and water path, record the date, weather and affected units, and take moisture readings if you can. Then stabilise temporarily to prevent further damage. Permanent repairs should wait until the cause is properly understood

Next Steps

If your complex is leaking this winter, make sure you come out of the wet season understanding your building better than you went in.

  • Start a leak register today. Capture every event in one place, with photos and dates, so patterns can surface.
  • Freeze permanent patching of recurring leaks. If an area has failed more than once, stop sealing over it and get the cause diagnosed.
  • Notify your insurer early and correctly. Document first, then engage your broker, so you protect rather than prejudice your cover.
  • Seek diagnosis-led advice. Look for independent advice focused on understanding the cause and your governance position, rather than a contractor rushing you toward a repair.

Handled this way, an unexpected leak stops being a recurring emergency and becomes the moment your committee took back control of the asset.

Need help? Contact us here for assistance from Craig.

Jump to the other blogs in this series here:

About the Author

 Craig Birch, Principal at Context Architects

Craig Birch is a specialist in navigating the complex intersection of building remediation and asset governance. With deep experience guiding Committees through the high-stakes environment of "leaky building" remediation and seismic strengthening, Craig understands that these projects are not just about construction - they are about financial survival and community consensus.

He works daily with Body Corporate Chairs and Asset Managers to move beyond the "patch and repair" cycle, advocating for data-led strategies that protect owner solvency and restore long-term asset value. Craig is passionate about replacing the anxiety of "unknowns" with the certainty of evidence, helping owner groups transform distressed liabilities back into resilient, insurable, and saleable homes.