How to Report an Issue (And Actually Get It Fixed)
How to Report an Issue (And Actually Get It Fixed)
“I told the MO 3 weeks ago and nothing happened.”
This is the most common frustration in any condo. The problem is rarely malice — it’s usually a broken feedback loop. Here’s how to fix it.
The Current System vs. The Ideal
Current:
You: "The lift is broken" (in WhatsApp group, at 11pm)
Security: "Noted, will inform MO."
[ 3 days pass ]
You: "Is the lift fixed yet?" (no response)
You: "Hello??"
[ frustration builds ]Ideal:
You: File issue via official channel (email, form, app)
MO: "Issue #123 logged. Estimated resolution: 2 days."
MO: "Issue #123 resolved. Lift technician confirmed repair. Please verify."
You: "Confirmed fixed."How to File an Effective Report
Step 1: Use the Right Channel
| Urgency | Channel | Example |
|---|---|---|
| 🔴 Emergency | Call Security (03-7660 4754) | Fire, burst pipe, medical, lift entrapment |
| 🟡 Urgent | Call MO (03-7660 4752) | No water, power outage, stuck lift |
| 🟢 Normal | Email MO | Noise complaint, facility issue, general inquiry |
| 🔵 Informational | WhatsApp group | ”Pool is very crowded today” — not a complaint |
Step 2: Give Complete Information
A good report answers 5 questions:
- What — exactly what’s wrong? (“Lift B1 is not stopping at Level 3”)
- Where — precise location (“Block B7, Lobby level, Lift #2”)
- When — when did you notice it? (“Since this morning, ~8am”)
- Who — your unit number (so MO can follow up if needed)
- Evidence — photo or video if applicable
Bad: “Lift broken” Good: “Lift #2 in Block B7 is skipping Level 3. Passengers press Level 3 but lift goes to Level 5 instead. Happened at 8:15am today. Our unit: B7-12.”
Step 3: Get a Reference Number
Ask for a reference number for your report. This turns a vague conversation into a trackable issue.
If the MO doesn’t have a formal system:
- Request: “Can I get a reference number for this report?”
- Track it yourself: note the date, time, and who you spoke to
Step 4: Follow Up (The Right Way)
| Timeframe | Follow-up |
|---|---|
| 24 hours | No follow-up needed (unless emergency) |
| 3 days | If no response: “Checking status on Issue #123 reported on [date]“ |
| 1 week | Escalate to JMB if no progress |
| 2 weeks | Escalate to AGM or COB if unresolved |
Tip: If you’re sending follow-ups, always reference your original report number and date. “Following up on Issue #123 (reported May 20) — the lift is still malfunctioning.”
What the MO Does After You Report
Your Report → MO logs it → Assigns to vendor or in-house team
↓
Vendor dispatched to inspect
↓
Vendor reports diagnosis & ETA
↓
Repair completed
↓
MO closes the ticket
↓
You're notified (if system allows)If the system works well: You get updates at each step. If it doesn’t: The ticket sits in someone’s email until you follow up. The fix: A proper tracking system (even a spreadsheet) turns complaints into trackable items.
When to Escalate
| If… | Escalate to |
|---|---|
| MO doesn’t acknowledge within 24 hours | MO again (follow up) |
| No action after 1 week | JMB representative |
| Same issue keeps recurring | AGM — propose a formal maintenance contract review |
| Issue involves structural or legal matter | JMB + COB |
| Emergency not handled properly | JMB + COB |
The Root Cause
Most “the MO never fixed it” problems are actually:
- Report got lost — WhatsApp message buried, email not answered
- No tracking system — MO doesn’t have a way to manage 1,120 units’ complaints
- Vendor delay — MO contacted the vendor, vendor didn’t come
- Parts needed — lift part takes 2 weeks to arrive, resident wasn’t told
- Budget issue — repair costs exceed available funds, needs JMB approval
The wiki can’t solve all these problems. But it can make the process visible enough that residents understand WHY things take time — and can help push for better systems.