![\"\"](\"https:\/\/www.timeteccloud.com\/blog\/wp-content\/uploads\/2026\/09\/What-a-JMB-can-do-about-unapproved-renovation-1024x355.png\")
<\/figure><\/div>\n\n\nThe powers are real, and they are by-law powers. The management body can demand the application that was never submitted, issue a breach notice, and impose the prescribed charge \u2014 capped at RM200 per breach unless the community has passed and filed additional by-laws setting its own. It can refuse access to contractors who were never registered. It can require reinstatement where the work breaches a by-law, and recover the cost of repairing damage to common property. Where the owner refuses, it can bring a claim to the Strata Management Tribunal.<\/p>\n\n\n\n
That last route matters more here than in most disputes. The owner is known, identifiable, and bound by the by-laws, so unlike a community trying to act against an unknown party, the Tribunal is genuinely available.<\/p>\n\n\n\n
What is yours, and what belongs to the local authority<\/h3>\n\n\n\n
Two limits get misread, in opposite directions.<\/p>\n\n\n\n
The first is entry. Committees often assume they cannot go in. They can \u2014 the prescribed by-laws require a parcel owner to permit the management and its agents to enter at reasonable times on reasonable notice, and immediately in an emergency, and refusing entry is itself a breach. Where the complaint involves cracks or a leak in the unit below, the inter-floor leakage procedure in the 2015 Regulations gives the committee a route with its own timelines: written notice, inspection, a certificate identifying the cause and the responsible party, and referral to the Commissioner of Buildings if the finding is disputed. Refusing that inspection carries consequences well beyond a by-law fine.<\/p>\n\n\n\n
What a right of entry is not is a right to force a door. If the owner refuses, the committee escalates rather than improvises \u2014 and arrives at the COB or the Tribunal with a documented refusal, which is evidence in itself.<\/p>\n\n\n\n
The second limit is demolition, and here committees overestimate themselves. The JMB cannot order structural work undone, and cannot cut water or electricity to force compliance. Once the work touches structure, the facade, or anything beyond the parcel boundary, the authority that matters sits with the local authority under the Street, Drainage and Building Act 1974. The committee’s role there is to refer, with documentation. A referral carrying dated entry records, photographs, an inspection certificate, and the absence of any approved application moves. A referral carrying complaint letters does not.<\/p>\n\n\n\n
Inspection tells you what. It cannot tell you who, or when<\/h3>\n\n\n\n
This is where most cases actually fail. Entry gets the committee a look at finished work \u2014 tiles down, ceiling closed, a wall that may or may not have been load-bearing. It does not establish when the work started, which contractors did it, how long they were on site, or what scope was ever approved. Those facts happened on common property weeks earlier, in front of a guardhouse, and either they were recorded or they are gone.<\/p>\n\n\n\n
The questions a Tribunal or a PBT officer will ask are all of that second kind:<\/p>\n\n\n\n
- \n
- Does an application exist at all, and what scope did it approve?<\/li>\n\n\n\n
- Which contractors entered, under what purpose, on which dates?<\/li>\n\n\n\n
- Did work continue past the approved date range, or outside permitted hours?<\/li>\n\n\n\n
- When did neighbours first report it, and was that report recorded at the time?<\/li>\n\n\n\n
- Was the by-law communicated to the owner, and did he acknowledge it?<\/li>\n<\/ul>\n\n\n\n
Most committees can answer these from memory. Memory is worth the same on both sides of a dispute.<\/p>\n\n\n\n
The record decides the outcome<\/h3>\n\n\n\n
![\"\"](\"https:\/\/www.timeteccloud.com\/blog\/wp-content\/uploads\/2026\/09\/E-form-with-space-683x1024.png\")
<\/figure>\nEvery answer above is a by-product of processing renovations normally rather than an investigation mounted after the fact. In iNeighbour<\/a>, the renovation application runs as an E-Form carrying scope, contractor list, date range and multi-level approval, with an In Progress status for work that is underway rather than prematurely closed. The contractor visitor flow enforces that approval at the gate \u2014 named contractors, within approved dates, with an acknowledgement step before entry \u2014 so an unregistered worker walking in becomes a dated fact rather than a guard’s impression. Live Activity monitoring shows who is on site now and flags arrivals outside the permitted window.<\/p>\n\n\n\n
The approved drawing and permit sit on the unit’s own document record alongside its notes and activity log, so three committees from now, when a leak appears below and the owner says it was always like that, the file still answers what was approved. Notices carry view and acknowledgement timestamps, which converts “we informed him” into something a Tribunal can read. Renovation deposits run through the same unit account in E-Billing, so withholding one against reinstatement is a billing record rather than an argument.<\/p>\n\n\n\n
None of this is exotic \u2014 it is the ordinary operation of a renovation process that happens to leave evidence behind, which is the point we made in managing renovation contractors in residential developments<\/a>. The committee that never built that process is the one now arguing from complaint letters.<\/p>\n<\/div><\/div>\n\n\n\n