Ask any trustee what the single biggest source of resident complaints is, and it's rarely the levy increase or the parking rules. It's maintenance: the pothole that's been "getting fixed" for three months, the broken gate motor nobody logged, the pool pump repair that the caretaker mentioned verbally to one board member and nobody else heard about. Not because boards don't care, but because most schemes are still running maintenance through channels that were never built for it: a shared inbox, a WhatsApp group, a notice board.

Here's why that breaks down as a scheme grows, and what a proper maintenance tracking system actually needs to do.

Why the WhatsApp group stops working

A community WhatsApp group is a great tool for "the gate is stuck, does anyone else's fob work?" It's a poor tool for maintenance management, for reasons that become obvious the moment a scheme passes about 40 or 50 units:

Nothing is a record. A message in a group chat isn't a maintenance request with a status, an owner, and a resolution date. It's a message that scrolls away under the next twenty messages about parking. Six months later, when an owner asks "didn't I report this ages ago?", there's no way to check.

Nobody owns it. When a resident posts "the irrigation is flooding the driveway" into a group of 200 people, the diffusion of responsibility is total. Everyone assumes someone else is handling it. Often nobody is.

There's no audit trail for the board. If an insurance claim, a CSOS dispute, or an angry owner at the AGM asks "when was this reported and what did the board do about it," a scrollback through a group chat isn't a defensible answer.

It doesn't scale past a handful of active issues. One or two requests a week, fine. A scheme running a dozen open maintenance items across landscaping, plumbing, electrical, and security has no way to see the whole picture in a chat interface, and the board ends up managing by memory.

Email has the same core problem in a different shape: requests land in one person's inbox, that person goes on leave, and the request sits unread for two weeks.

What proper maintenance tracking actually requires

A maintenance system that works for a community scheme needs to do a handful of specific things well:

Structured logging with photos and location. A resident should be able to report an issue from their phone, attach a photo, and specify where in the scheme it is, in under a minute. The easier this is, the more likely people actually use the system instead of falling back to WhatsApp out of habit.

Visible status, automatically. The resident who reported the leak should know, without asking, whether it's been seen, assigned, or resolved. Automatic status-change notifications remove the single biggest source of "did anyone even see this?" frustration, and they remove the board's job of manually updating every resident who asks.

A single view for the board. Trustees need to see every open request across the whole scheme, not the fraction that happens to be in their own inbox or that they remember from a chat thread. That single view is what turns "we're on top of maintenance" from a feeling into something demonstrably true.

A closed loop. Every request needs an end state: resolved, with a note on what was done. Without that, boards lose the ability to answer basic questions later, like whether a particular type of fault keeps recurring and might point to a bigger underlying problem (the same geyser failing three times in a year is a signal, not three unrelated maintenance tickets).

A record that survives handovers. Committees turn over. A trustee who resigns shouldn't take institutional knowledge of "what's still outstanding" with them. A proper system means the next committee inherits a clean, complete picture on day one instead of starting from zero.

The trust dividend

There's a second-order benefit that's easy to underestimate: residents who can see their maintenance request move through a visible status, logged, in progress, resolved, trust the board more, even when the fix takes a while. Most complaints about "the board doesn't do anything" aren't actually about speed. They're about silence. A resident who reported a broken gate three weeks ago and has heard nothing feels ignored, even if the board ordered the part on day one. A resident who can see "parts ordered, ETA next week" feels informed, and informed residents are dramatically less likely to escalate to angry AGM questions or CSOS complaints.

That's not a soft, nice-to-have benefit. Trustee time spent managing angry residents is trustee time not spent on the actual maintenance backlog, and burnt-out volunteer trustees are one of the more common reasons committees struggle to find people willing to stand for election.

What this looks like in Votera

Votera's maintenance module lets residents log requests with photos and location directly from their phone. Every status change, logged, assigned, in progress, resolved, triggers an automatic notification to the resident who reported it, so nobody is left wondering whether anyone saw their message. Board members get a single dashboard showing every open request across the scheme, with the ability to track, update, and close each one, and a resolved history that persists through committee handovers.

Because it sits inside the same platform as the vendor and service-provider compliance tracking, a maintenance request that needs a contractor can be matched directly against approved, compliant service providers, rather than the board having to remember which plumber has an up-to-date insurance certificate on file.

A quick self-assessment

If any of the following sound familiar, it's worth reconsidering how your scheme handles maintenance:

Residents report issues through more than one channel (WhatsApp, email, verbally to the caretaker) with no single source of truth.
Nobody can say, off the top of their head, how many maintenance items are currently open.
Residents regularly ask "did anyone see my message?"
A new trustee joining the committee has no clear record of outstanding maintenance work.
The board has been asked to produce a maintenance history for an insurance claim or CSOS matter and struggled to compile one.

None of these are failures of the people involved. They're the predictable result of running an operational process through tools built for casual conversation. The fix isn't more diligence from volunteer trustees who are already stretched thin. It's a system that does the tracking, the notifying, and the record-keeping automatically, so diligence isn't the only thing standing between a resident's report and a resolved issue.

Votera is an HOA and body corporate management platform built for South African community schemes, covering maintenance, governance, vendor compliance, and resident communication in one dashboard. See how maintenance tracking works or start a free 30-day trial.