Knowing how to report an estate fault properly can be the difference between a problem being fixed quickly and disappearing inside hundreds of WhatsApp messages.
A message saying the light is bad or there is water somewhere forces management to start asking questions before anybody can act.
A useful report tells management exactly what is wrong, where it is, how serious it appears and what evidence is available.
Residents should not need to become maintenance experts. They just need to provide enough information for the right person to find and assess the problem.
What counts as an estate fault?
An estate fault is usually a problem affecting shared infrastructure, common areas or services managed by the estate.
Examples include:
- broken streetlights;
- blocked drains;
- leaking estate water pipes;
- damaged roads;
- broken gates;
- faulty boom barriers;
- damaged perimeter fencing;
- overflowing refuse points;
- failed borehole equipment;
- common-area electrical faults;
- broken playground equipment;
- damaged CCTV equipment;
- and faults in shared recreational facilities.
Not every problem inside your home belongs to estate management.
For example, a leaking kitchen tap inside your apartment may normally be a landlord, tenant or private maintenance matter.
A burst main water pipe supplying several streets is much more likely to be an estate issue.
If you are unsure, report it with enough information for management to determine responsibility.
For shared infrastructure, estates should already have an estate maintenance schedule identifying the equipment and areas they maintain.
What information should a fault report include?
A good fault report does not need to be long.
It needs to be specific.
Include these details:
What happened
Describe the problem plainly.
For example:
Streetlight is not coming on.
Water is flowing continuously from a pipe.
Drain is completely blocked.
Boom barrier is stuck open.
Exact location
Do not say near my street if you can be more precise.
Use something such as:
Streetlight opposite House 24, Palm Street.
Blocked drain beside the children's playground.
Water leak near the second gate.
Photo or video
A clear photo can often explain the problem faster than several paragraphs.
Take enough of the surrounding area to help management identify the location.
When you noticed it
This can help determine whether the problem is new or recurring.
How serious it appears
Mention if the problem is:
- creating a safety risk;
- blocking access;
- affecting several households;
- getting worse;
- or disrupting an essential service.
A useful report might say:
Streetlight opposite House 24 on Palm Street has been off since yesterday evening. Other lights on the street are working. Photo attached.
That gives management somewhere to start.
Compare it with:
Light no dey work.
Management now has to ask which light, where and since when.
For a specific lighting problem, see how to report a faulty estate streetlight.
Is the fault an emergency or a routine maintenance issue?
Not every problem should enter the normal maintenance queue.
Some situations require immediate action.
Examples may include:
- fire;
- exposed live electrical cables;
- serious flooding;
- major security breach;
- collapsed structure;
- dangerous fallen tree;
- severe water-main failure;
- gate failure creating an immediate security risk;
- or another situation threatening life or property.
In those circumstances, contact estate security or the relevant emergency response immediately.
Do not simply submit a maintenance report and assume somebody will see it in time.
A broken streetlight may be urgent for security reasons, but it is different from a fire.
A leaking pipe may need prompt repair, but it is different from rapidly rising floodwater threatening homes.
Residents should know the estate's emergency process before an emergency happens.
See the estate emergency response plan for what management should have in place.
Kompound, for example, separates normal issue reporting from emergency SOS. Its current SOS function sends an alert to estate security with the resident's location and identifies whether the emergency is medical, fire, security or panic.
That distinction matters.
Routine fault: report and track it.
Immediate danger: raise the alarm first.
How can residents avoid duplicate complaints?
Once a fault is reported, twenty residents should not need to report the same broken streetlight separately.
Duplicate reports create noise without necessarily making repairs faster.
The better system is for residents to be able to see that the problem has already been acknowledged.
For example:
Reported
Management has received it.
Assigned
Someone is responsible for investigating or repairing it.
In progress
Work has started.
Waiting for parts
The repair is temporarily delayed.
Resolved
The problem has been fixed.
Residents can then follow the existing issue rather than sending another message.
WhatsApp makes this difficult.
A blocked-drain report posted at 7:30 a.m. may be buried beneath:
birthday messages,
visitor questions,
security discussions,
advertisements,
and unrelated complaints
before the facility manager checks the group.
This is one reason serious maintenance reporting should not depend entirely on the community chat.
The group can still be useful for conversation.
The maintenance queue should remain separate.
What should management do after receiving a report?
Reporting is only half the process.
Management needs a workflow after the complaint arrives.
A useful sequence is:
1. Acknowledge it
The resident should know the report was received.
2. Assess the priority
A water leak affecting twenty houses should not sit behind repainting a clubhouse wall.
3. Assign responsibility
Send the issue to the caretaker, facility manager, electrician, plumber, security team or relevant contractor.
4. Inspect where necessary
Some problems cannot be properly diagnosed from a photograph.
5. Approve the repair
Obtain quotations or spending approval where required.
6. Update the status
If repair will take three days, residents should not have to guess what is happening.
7. Confirm completion
Close the issue only after the work has actually been completed.
Management should also preserve recurring fault information.
If the same borehole pump fails four times in six months, that is no longer just four separate repair jobs.
It may indicate a larger maintenance or replacement problem.
The same applies to repeatedly blocked drains or a gate motor that constantly fails.
These patterns should feed into the estate's future maintenance plan and budget.
For water-specific problems, see estate water supply management.
When should a resident escalate an unresolved fault?
Not every repair can happen immediately.
A contractor may need to inspect it.
Replacement parts may need to be sourced.
Management may need approval for major expenditure.
But residents should not be left without information indefinitely.
Escalation makes sense when:
- the fault creates a safety risk;
- the problem is becoming worse;
- an essential service remains unavailable;
- the report has received no acknowledgement;
- a promised repair date repeatedly passes;
- or the issue keeps being marked resolved when it is not.
Start with the normal management channel.
Reference the original report rather than starting the story again.
For example:
Issue 184, blocked drain beside House 12, was reported on Monday and is still overflowing. Could management please confirm the repair status?
That is more useful than:
Nobody in this estate ever does anything.
If repeated operational follow-up fails, the issue may need to go to the facility manager, EXCO or another appropriate level under the estate's complaint process.
Use the process in how to handle estate complaints where an ordinary maintenance request becomes a broader management complaint.
Residents should also distinguish between disagreement and maintenance.
A neighbour parking badly is not the same type of issue as a failed borehole pump.
Different problems need different workflows.
How does Kompound track estate faults?
Kompound turns issue reporting into a dedicated workflow instead of leaving faults inside the community chat.
Its current platform allows residents to report issues with a photo and location. Management receives open issues in one queue and residents can follow the status until the matter is resolved.
The current system specifically covers examples such as:
- broken streetlights;
- blocked drains;
- and damaged fencing.
The workflow is straightforward.
Resident reports the problem
They provide the fault details, photo and location.
Management sees it in the issue queue
Open problems are kept together instead of being scattered across chats.
The issue is handled
Management can prioritise and act on it.
Status remains visible
Residents can follow what is happening rather than repeatedly asking for updates.
The issue is closed when resolved
The estate retains a record of what happened.
Kompound describes the system as tracking issue reports through to resolution, and its current pricing confirms that issue reporting is included for residents without a separate resident fee.
The platform's current admin tools also include announcements and issues, giving management a common place to handle the operational side of estate problems.
For emergencies, the process remains separate.
SOS alerts stay active until handled, and security can acknowledge that it is responding.
This gives an estate two clear channels:
Something is broken
Report an issue.
Someone is in immediate danger
Raise an SOS.
That is much cleaner than putting both situations into the same WhatsApp group and hoping the right person happens to be online.
The best way to report an estate fault is therefore simple:
say exactly what happened,
give the exact location,
attach a useful photo,
state whether there is an immediate risk,
and use a system where you can see what happens next.
Residents should not have to chase a fault from person to person.
And management should not have to search through weeks of messages to remember what still needs fixing.