Most Malaysian condominiums have a security SOP. Very few have an emergency SOP. The difference between the two is not academic — it is the difference between a guard who verifies first and a guard who escorts first, and in a cardiac emergency that difference is measured in minutes.

In March 2026, a case in the Klang Valley drew national attention after community figure Kuan Chee Heng reported by Daily Express Malaysia that security personnel at a condominium had held emergency responders at the gate for roughly 45 minutes while waiting for clearance from a superior. The 50-year-old resident inside, believed to have suffered cardiac arrest, did not survive. Public reaction focused on the guards. The more useful question is the one almost nobody asked: who wrote the procedure they were following, and did it ever contemplate an emergency at all?

This article is about closing that gap — practically, at your own building, using tools your JMB or MC already has.

Why standard security SOPs fail in emergencies

A typical Malaysian guardhouse SOP is built around a single premise: nobody enters until entry is authorised. That premise is correct for contractors, agents, delivery riders, and strangers. It is written to prevent tailgating, unauthorised access, and liability.

The problem is that the same SOP is silent on what happens when the person at the gate is a paramedic, a Bomba crew, or a family member responding to a call for help. Faced with silence, a guard does the rational thing — he escalates. Escalation means a phone call. A phone call at 2am means a supervisor who may not answer. And the clock keeps running.

Three structural features make this worse in Malaysia specifically:

  1. Guards are usually outsourced. The security personnel at your gate are typically employees of a contracted security firm, not of your JMB/MC. They follow their employer's post orders. If the JMB/MC has never issued a written instruction that overrides those post orders in an emergency, the guard has no authority to deviate — and every incentive not to.

  2. High turnover means low institutional memory. A verbal briefing given to a guard in January does not survive a shift rotation in June. Only a written, posted, signed-off protocol survives turnover.

  3. The default is "say no first." When a guard is disciplined for letting the wrong person in but never disciplined for a delay, the incentive structure produces delay. That is a management design problem, not a character problem.

None of this is unique to any one building. It is the default state of most schemes that have not deliberately fixed it.

What the law actually says (and does not say)

The Strata Management Act 2013 (Act 757) governs how strata schemes in Peninsular Malaysia and Labuan are managed — the powers and duties of Joint Management Bodies and Management Corporations, the making and enforcement of by-laws, and dispute resolution through the Strata Management Tribunal.

What Act 757 does not do is prescribe an emergency access procedure for your gate. There is no statutory template. That is not a loophole to complain about; it is a mandate. The Act gives your JMB/MC the power to make additional by-laws and to direct the management of common property. Emergency access sits squarely inside that power.

Two consequences follow:

  • You do not need to wait for a law change. A JMB/MC can adopt an emergency access protocol as a management resolution today, without amending by-laws at all, because it concerns the operational management of common property rather than the creation of a new obligation on proprietors.

  • If you want it to bind future committees, put it in the by-laws. Additional by-laws require a special resolution at a general meeting and must be lodged with the Commissioner of Buildings (COB) to take effect and bind all proprietors, tenants and occupiers. That is the durable route.

Both routes are legitimate. Start with the resolution because it is fast; pursue the by-law because it is permanent.

The eight clauses a written emergency access protocol should contain

Below is a working skeleton. Adapt the wording with your building manager and, for the by-law route, with a strata practitioner.

1. Definition of an emergency. Define it narrowly enough to be usable and broadly enough to be safe. A workable formulation: any situation where an ambulance, fire, police, or civil defence vehicle presents at the gate; or where a caller reports fire, medical collapse, entrapment, flood, gas leak, or structural failure.

2. The override clause. The single most important sentence in the document. Something to the effect of: In a defined emergency, the guard on duty is authorised — and required — to grant immediate access without waiting for approval from any supervisor, the management office, or the resident. Without this sentence, everything else is decoration.

3. Escort, do not obstruct. Access is granted immediately; verification happens in parallel, not before. The recommended practice is for one guard to escort responders directly to the unit or incident location while a second maintains gate control. This preserves security for the rest of the community without trading a life for it.

4. Lift priority and access. Nominate which lift is placed on emergency service, who holds the key or override, and where that key lives. A crew that gets through the gate in 30 seconds and then waits four minutes for a service lift has gained nothing.

5. Wayfinding pack at the guardhouse. A laminated block layout, unit numbering logic, hydrant and riser locations, and the location of any AED. Responders arriving at an unfamiliar 40-storey scheme lose real time to navigation.

6. Notification chain — after, not before. Sequence it explicitly: grant access → escort → then notify the building manager, the emergency contact on file for that unit, and the security supervisor. Notification is a downstream obligation, never a precondition.

7. Emergency contact register. Maintain a current next-of-kin or emergency contact for each occupied unit. This is the clause most schemes get wrong, because it collides with data protection duties — see the section below.

8. Indemnity and drill schedule. State that a guard acting in good faith under this protocol will not be subject to disciplinary action for granting access. Then schedule a drill — twice a year, with the security contractor, timed and minuted. An untested protocol is a hypothesis.

The AED question

The same March 2026 case renewed calls for automated external defibrillators to be standard in Malaysian residential buildings, alongside trained personnel. There is currently no blanket statutory requirement for residential schemes to install one.

If your committee is considering it, three practical points:

  • Cost sits at the lower end of most sinking fund line items, but the recurring costs — pad and battery replacement, and recertified training for guards and volunteer residents — are the part committees forget to budget.

  • An AED without trained users is a liability, not an asset. Budget the training in the same resolution.

  • Placement matters more than purchase. Guardhouse and main lobby beat management office, which is locked outside working hours.

Raise it as a specific budget line at the AGM rather than a general suggestion. Specific line items get voted on; general suggestions get noted.

Emergency contacts and the PDPA problem

Collecting next-of-kin details for every unit means your JMB/MC is now processing personal data — and, depending on what is recorded, potentially health-related information that falls into a more sensitive category under Malaysia's Personal Data Protection Act 2010 as amended by the Personal Data Protection (Amendment) Act 2024.

That is not a reason to skip the register. It is a reason to build it properly:

  • Collect the minimum viable field set — name, relationship, one contact number. Resist the urge to collect medical conditions unless the resident volunteers them and consents in writing.

  • Issue a short written notice explaining what is collected, why, who can access it, and how long it is kept.

  • Restrict access. The register should be reachable by the duty guard in an emergency and by nobody else casually.

  • Have a review cycle. Stale emergency contacts are the norm; annual re-confirmation at renewal or AGM time fixes it cheaply.

We cover the guardhouse data question in more depth in our companion piece on visitor logbooks and the PDPA.

How to actually get this passed

Committees do not reject emergency protocols. They defer them. Beat deferral with specificity:

  1. Bring a draft, not a topic. A one-page draft protocol tabled as a written motion is far harder to defer than "we should look into emergency access."

  2. Table it as an AGM or EGM agenda item in writing, within the notice period your scheme requires, so it must be minuted.

  3. Attach a cost line. Most of this costs nothing except printing and two drills a year. Say so in the motion — cost is the usual objection and it evaporates when quantified.

  4. Ask for a named owner. A protocol with no assigned committee member and no review date will not survive twelve months.

  5. Request a minuted response. If the committee declines, the minutes record that it was raised. That matters.

The takeaway

Security and emergency response are two different systems that happen to share a gate. Most Malaysian schemes have built the first and assumed the second. The starting point costs almost nothing: one page, signed off by your JMB/MC, posted at the guardhouse, and drilled twice a year. Everything else — faster resident notification, a current emergency contact register, cleaner records of who is on the premises — builds on top of that page, and works better once it exists.

If your building does not have that page, the next AGM is where you get it.

FAQ

Is a condominium legally required to let an ambulance in immediately? There is no provision in the Strata Management Act 2013 that sets out a specific gate procedure for emergency vehicles. The duty sits with the JMB/MC to manage common property responsibly, which is why a written internal protocol matters — the Act empowers the management body to create one but does not write it for them.

Can a guard be blamed for a delay? Guards typically follow the post orders issued by their employer, the contracted security firm. Where no emergency override exists in those orders, the gap is at the level of the JMB/MC and the security contract, not the individual on shift.

Does an emergency access protocol need a special resolution? Not if it is adopted as an operational management resolution. If you want it embedded as an additional by-law binding all proprietors, tenants and occupiers, that requires a special resolution at a general meeting and lodgement with the Commissioner of Buildings.

Are AEDs compulsory in Malaysian condominiums? There is no blanket statutory requirement for residential strata schemes. Installation is a decision for the JMB/MC, usually funded through the maintenance account or sinking fund and approved at a general meeting.

Who should hold the emergency contact register? Access should be limited to the duty guard and the building manager, with a written privacy notice given to residents and a documented retention period, consistent with obligations under the PDPA as amended in 2024.

This article is general information for Malaysian strata residents and management bodies, not legal advice. Verify current provisions against the gazetted text of the Strata Management Act 2013 and consult your Commissioner of Buildings or a qualified strata practitioner for any live matter.

Sources

Last reviewed: 31 July 2026.