The Maintenance Request That Never Gets Fixed

The Leak That Keeps Coming Back

Unit 7. Third floor. The tap in the bathroom has been dripping since the previous tenant. The first complaint came in eleven months ago — a WhatsApp message to the property manager, who forwarded it to the plumber, who fixed it, apparently.

Six weeks later: another message. Dripping again.

The plumber came back. He fixed it again.

Three months later, new tenant, same unit. Same tap. Same drip. The new tenant reports it. The property manager, who handled the first two requests, is on leave. The stand-in doesn't know the history. The plumber is called for what everyone treats as a fresh issue.

By the time the tap is properly replaced — rather than temporarily patched — it has generated four maintenance requests, cost three times what a replacement would have, and contributed to one tenant choosing not to renew.

This is not a plumbing story. It's a data story.

Reactive Maintenance Is a Loop, Not a Process

Most property operations run on reactive maintenance: something breaks, someone reports it, someone fixes it, the file is closed. The problem is that "closed" usually just means the conversation ended — not that the underlying issue was resolved, documented, or connected to its history.

Without a structured maintenance record attached to the unit, every request is treated as an isolated event. The plumber who shows up doesn't know it's the fourth visit for the same problem. The property manager reviewing the month's costs doesn't see that unit 7 is consuming a disproportionate share of the maintenance budget. Nobody connects the dots because the dots are scattered across different WhatsApp threads, call logs, and half-remembered conversations.

The loop continues until someone gets frustrated enough to either escalate or leave.

What Unit-Level History Changes

When maintenance records are attached to the unit — not to a person's inbox — patterns become visible that were previously invisible.

A unit that generates five requests in a year is statistically different from one that generates one. The nature of those requests tells you something: recurring plumbing issues may indicate a structural problem; repeated electrical faults may signal wiring that needs inspection. A contractor who closes the same job four times without resolving it is costing you more than their invoice suggests.

None of this analysis is sophisticated. It just requires the data to exist in one place, linked correctly, and visible to whoever is making decisions.

The Tenant Retention Angle

Maintenance is the primary reason tenants don't renew, and the reason they cite online when they leave reviews.

Not rent increases. Maintenance.

Specifically: maintenance requests that go unanswered, that take too long, or that fix the symptom without addressing the cause. The third time a tenant reports the same issue, they've already mentally started looking elsewhere. By the fourth time, you've lost them — you just don't know it yet.

The economics are clear. Tenant turnover costs: void period, reletting fees, light refurbishment, administrative time. A single turnover typically costs more than a year of properly managed maintenance on that unit.

Reactive maintenance, run on informal systems, is not a cost-saving strategy. It's a tenant retention tax — paid irregularly, invisibly, and always at the worst possible moment.