When apartment building security stops working: notes from a busy month

cadogan1 on August 21, 2026

Apartment building security tends to get attention twice. Once when it is set up, and once when something goes badly enough that residents start emailing the Committee. In between it is usually invisible, which is the point, but also part of the problem. When invisible security stops working, no one notices until the incidents pile up.

We have spent the last few weeks working through two very different security situations at two Auckland buildings. Both taught the same underlying lesson. The model matters less than whether the model is actually being delivered, checked, and adjusted when the building’s circumstances change.

Apartment building security: a slow escalation

The first situation started as a noise complaint between neighbours. Talking it through with the resident surfaced a bigger pattern. Groups of high school students were entering the building most weekday afternoons, riding the lifts for entertainment, gathering in stairwells and car parks, occasionally smelling of drugs. Residents were feeling intimidated. Some told us they had stopped speaking up in lifts when students got in with them.

The initial response covered the obvious moves. A notice to residents. Direct conversations with individuals we could identify. Contact with the schools. A report to Police, who attended once. Behaviour improved briefly, then returned and escalated. On one afternoon there were two separate groups using drugs in stairwells at the same time as students loitering in the car park, lift lobby, and lifts.

At that point we brought in a static guard, weekday afternoons, initially for two weeks. Daily activity reports showed students being encountered on almost every shift and leaving without argument when asked. Resident complaints dropped significantly within the first week. There was still the occasional incident, a lingering smell of drugs on one day, a suspicious item found and photographed on a stairwell on another, but the pattern of intimidation was broken.

The lessons from that one.

Residents will tolerate a surprising amount before they formally complain. By the time you hear about it, it has usually been going on for weeks. A single noise complaint is often the visible tip of something larger, so it is worth asking a few open questions rather than treating each report in isolation.

Police attendance is a one off tool, not a plan. In our experience, Police will show up when called and will disperse a group, but they do not have the resource to establish a presence at a private building. Anything requiring a repeat presence has to come from somewhere else.

A visible, uniformed adult in the right place at the right time is remarkably effective against opportunistic antisocial behaviour. The students were not there to cause serious harm. They were there because the building was easy and unsupervised. Removing the unsupervised part removed most of the reason to be there.

Two weeks is often enough to reset the pattern, but only if you review honestly at the mid point and are willing to extend if the outcome has not landed. We ran a mid point review with the approver and confirmed the guard was achieving what was intended before letting the second week run.

Pattern two: a model that stopped delivering

The second situation was a mixed use building that had moved earlier in the year from a static on site guard, running 86 hours a week, to a mobile patrol model. Four short patrols a day at randomised times within set windows. On paper the change was reasonable. Static guards are expensive, and mobile patrols cover more ground for less money.

What surfaced over a few weeks was that the delivery did not match the promise. A tenant reported an unauthorised person on site during a patrol window, but the person was still there well after the patrol was supposed to have happened. The activity report for the next day showed no logged checks for two of the four scheduled windows. A separate call to the security firm’s after hours line went unresolved and, oddly, ended with the operator asking for payment.

We escalated all three points to the provider, who ran an internal investigation and confirmed a mixed picture. One of the missed patrols was a logging error. The guard could not sign in to the site’s run sheet and recorded the visit against the wrong site. The earlier missed patrol, however, was genuinely missed. The call handling issue was escalated to their CEO.

A few days later another incident occurred. An individual on site through the middle of the day, moved on only after a tenant approached them directly. The tenant asked the Committee to consider switching providers and gave a five day deadline. The security firm’s own report of the same incident told a fuller story. Their guard had already approached the individual, who was cooperative and packing up to leave, when the tenant arrived and became verbally aggressive, which is what actually escalated things.

Both accounts were partly true. Neither on its own was the whole picture.

The lessons from that one.

Daily activity reports are worth reading, not just filing. Two consecutive days of gaps in the same patrol windows should trigger a question the same week, not the next month. Small anomalies compound.

When residents or tenants report an incident, get the security provider’s incident report of the same event before drawing conclusions. In this case the two accounts differed in ways that changed the recommended response entirely. From “the provider is not showing up” to “the provider is showing up, but the reporting infrastructure and the tenant provider relationship need work.”

Residents intervening directly is a signal that the reporting path is not clear enough. If a tenant felt the only option was to confront an individual themselves, then either they did not know who to call, or they had tried and it had not worked. Either way, that is fixable, with clearer signage, a tenant facing contact card, or a shorter escalation path, and it should be fixed before the next incident.

Cost is a legitimate reason to change a security model, but the model needs to survive contact with reality. Mobile patrols work well in some buildings and poorly in others. The variables that matter are things like how visible the building is from the street, how many entry points there are, whether there is a concierge or facilities presence during the day, and whether the tenant mix creates predictable friction points. When those variables change, the model should be reviewed.

What we take from both

A few things transfer between the two situations, and probably to most others.

Security is only as good as the feedback loop around it. If the Committee does not see incident data regularly, and the residents do not have an obvious path to report things, and the provider does not get told when something goes wrong, then whatever is happening on the ground drifts away from what was agreed at the AGM.

The right model depends on the building, not the industry. A retail adjacent mixed use tower has different needs from a residential only block near a school, and both change over time. It is normal to move between static, mobile, and hybrid arrangements as circumstances evolve. What matters is that the move is deliberate.

When behaviour escalates, act sooner than feels comfortable. Bringing in a short term static guard for two weeks is a small cost compared with the reputational and wellbeing cost of a building where residents feel unsafe.

Get the full picture before making the call. Every incident has at least two accounts, and often the useful decision emerges from comparing them rather than from either one on its own.

And finally, this is the least glamorous point but the most important one. The boring administrative work is what makes security actually work. Activity reports read, incidents logged, tenants briefed, mid point reviews held, providers held to their contracts. None of it is interesting. All of it is what stops the next incident from being worse than the last one.

Fusiotherm (Fusio) Leaks in Apartment Buildings: A Practical Guide for Body Corporate Committees

cadogan1 on May 15, 2026

Cadogan Building Management | Auckland building management & body corporate specialists

If your apartment building has had a burst pipe, a stained ceiling in a lower-level unit, or a stubborn damp patch that keeps coming back, you may already be familiar with the term Fusiotherm. Fusiotherm leaks — known informally as Fusio leaks — have become one of the most common and most expensive plumbing problems in New Zealand apartment buildings built between roughly 1998 and 2015. For body corporate committees, the question is rarely whether a Fusio failure will affect your building; it is when, where, and how prepared you are to respond.

This guide explains what Fusiotherm is, why it fails, what the warning signs look like, and — most importantly — the practical steps your committee can take to protect owners, manage cost, and stop a single leak becoming a building-wide crisis.

What is Fusiotherm pipe?

Fusiotherm (sometimes called Fusio, Fusion, or aquatherm green pipe) is a polypropylene random copolymer — PP-R — plumbing system manufactured by the German company aquatherm. It became popular in New Zealand apartment construction from the late 1990s because it is lightweight, corrosion-resistant, and uses heat-fused joints instead of soldered or threaded connections. Marketed with a 50-year design life, it was widely specified for hot and cold water reticulation in multi-unit buildings.

In practice, a significant number of those installations are failing well inside 20 years — sometimes inside 10. The result is leaking risers, branch lines bursting inside walls, and repair bills that can run from tens of thousands of dollars for a localised failure into the millions for a full repipe.

Why are Fusio pipes failing?

There is no single cause, which is part of what makes Fusiotherm leaks so difficult to manage. The contributing factors most commonly identified by plumbing engineers and insurers include:

Manufacturing variation in certain batches of pipe and fittings imported in the 2000s.
UV exposure on site during construction, which degrades PP-R before it is ever installed.
Over-tightening or poor welding technique at heat-fused joints — the most common single failure point.
Long-term chemical attack from chlorinated water supplies, which makes the pipe brittle over time.
Higher operating temperatures and pressures than the system was originally designed for, especially on hot-water lines.

Most leaks occur at fittings rather than mid-run, and hot-water lines fail earlier than cold. Once one fitting has gone in your building, others installed in the same period — by the same plumber, from the same batch — are statistically more likely to follow.

Signs your building has a Fusiotherm problem

Committees should treat any of the following as a prompt to investigate seriously:

Repeated leaks in the same riser, stack, or stairwell — even if each one is small.
Water staining on ceilings of lower-level units after rain has been ruled out.
A drop in hot-water pressure or unexplained increases in the building’s water bill.
Damp or musty smells in cupboards housing risers or hot-water cylinders.
Insurance excess increases, exclusions, or insurer requests for a plumbing condition report at renewal.

Who pays — common property or unit owner?

Under the Unit Titles Act 2010, pipework that serves more than one unit — risers, mains, and the reticulation inside common walls — is almost always common property and therefore a body corporate responsibility. Pipe within a single unit, downstream of the isolation valve, is generally the owner’s. The boundary is rarely as clean as it sounds, which is why a careful site-specific assessment matters before liability is allocated.

Insurance is the other half of the picture. Most body corporate policies will cover resultant damage from a sudden leak (the soaked carpet, the ruined gib) but not the cost of the failed pipe itself, and increasingly not the cost of investigation. Insurers are watching Fusiotherm claims closely; some are now requiring evidence of a maintenance plan before they will renew.

Practical steps for your body corporate committee

The committees that come through a Fusiotherm problem in the best shape are the ones that treat the first leak as a system warning, not an isolated event. The following steps are in the order we recommend tackling them.

1. Don’t just patch and forget.

A single fitting failure in a Fusio system is almost never isolated. Record every leak — location, date, what failed, and which plumber attended — and start building a map of the building’s plumbing history.

2. Commission a plumbing condition assessment.

Engage a plumber or building services engineer with specific Fusiotherm experience to inspect accessible pipework, identify the installation period and likely batch, and grade the system’s remaining service life.

3. Update your Long-Term Maintenance Plan (LTMP).

Your LTMP must reflect the real risk. If a full repipe is realistic within 10 years, the plan and the long-term maintenance fund need to show that — and owners need to see it coming, not be ambushed by a special levy.

4. Talk to your insurer early.

Don’t wait for renewal. Tell your broker what you know, ask what evidence they want, and find out whether a documented maintenance and inspection regime will preserve your cover and excess.

5. Decide the right strategy: patch, partial repipe, or full repipe.

Each has a place. Patching buys time on a low-risk system. Partial repipes (hot lines first, or one riser at a time) spread cost. Full repipes are disruptive and expensive but end the problem. A specialist should help you model the cost over 5, 10 and 15 years before you commit.

6. Get multiple specialist quotes — and check experience.

Repiping an occupied apartment building is specialist work. Ask for references from comparable jobs, make sure quotes are like-for-like on access, reinstatement, and warranty, and avoid contractors whose only experience is single-house plumbing.

7. Communicate with owners early and often.

Nothing damages a committee’s mandate faster than owners learning about a major levy from a rumour. Use the AGM, written updates, and an owners’ meeting before any vote on funding.

8. Plan how the work will be funded.

Options include drawing on the long-term maintenance fund, a one-off special levy, staged levies, or, for larger schemes, body corporate financing. Each has tax and disclosure implications — get advice before you choose.

9. Mitigate damage while you decide.

Install leak-detection sensors at risers and under hot-water cylinders, check that isolation valves actually work, and make sure every unit has clear instructions for shutting off water in an emergency.

10. Engage a building manager who has done this before.

Fusiotherm projects sit at the intersection of plumbing, insurance, owner relations, and statutory compliance. A building manager who has run repipes before will save your committee thousands in avoided mistakes and many hours of volunteer time.

When to act

The temptation, especially when budgets are tight, is to wait for the next leak before doing anything. With Fusiotherm, that is almost always the most expensive strategy. The cost of investigation, planning, and a phased repipe done on your timetable is reliably lower than the cost of emergency callouts, insurance excesses, and damage to lower-level units done on the building’s timetable. If you have had even one significant Fusio failure, your committee should be commissioning a condition assessment this financial year.