How to Stop Parkade Exit Doors From Being Propped Open in Vancouver Strata Buildings

First define which door event matters

The phrase ‘door alarm’ can describe several different events. For a busy strata parkade, these events are not interchangeable. A system intended to catch a propped-open door should not create an unnecessary alarm every time a resident exits normally.

A door-position contact reports whether the door is open or closed. By itself, it cannot establish why the door opened. Forced-door logic requires coordination with the access-control controller, approved releases and request-to-exit devices.

Use separate layers for local deterrence and remote reporting

A useful design often separates three jobs: detect that the door has remained open beyond a configured grace period, sound a warning at the opening and send useful information to an authorized responder. Those outcomes can work together, but they do not necessarily come from one device.

A purpose-built door-prop alarm can provide the immediate local warning. A compatible alarm or access-control platform can provide app notifications, event history or both. The proposal should identify which equipment performs each function and whether both layers use the same contact or separate contacts.

How a delayed local door-prop alarm works

A door-prop alarm monitors the door position and starts a timer when the opening is used. Normal passage can occur without an alarm if the door closes before the timer expires. If it stays open beyond the selected time, the sounder calls attention to the condition at the door.

One example is the Detex EAX-300. Its installation instructions list field-selectable door-open times of 1, 15, 30 or 45 seconds, or 1, 2 or 4 minutes, with a 15-second default. The same instructions state that an alarm caused by the door remaining open is silenced and rearmed when the door closes. Detex lists the integral sounder at approximately 100 dB.

That behaviour should not be assumed for every exit-alarm product. Some devices alarm immediately, offer different timing choices or require a key reset. The selected model and programmed sequence should appear in the written scope.

Remote notifications are a separate design decision

If council, a caretaker or building staff need phone alerts, a compatible door contact can be connected to an alarm or access-control platform. For example, Ajax documents that a compatible wired opening contact connected through its MultiTransmitter can create an opening alarm and a restoration event when the contact returns to normal, depending on system settings.

The standalone Detex EAX-300 documentation does not identify an app-notification feature or a general alarm-output relay. Remote reporting therefore needs its own compatible equipment and communications path.

A connected layer also does not automatically wait for the same grace period as the local door-prop alarm. It may report as soon as the door opens. If the required outcome is ‘notify us only after the door has remained open for 30 seconds,’ the timer logic must be confirmed for the exact controller, integration and programming.

Define and test the complete event sequence

The intended sequence should be written into the proposal and demonstrated at turnover. Council should see normal passage, a held-open condition, closure and rearming, as well as the available power, communications and trouble behaviours.

1. A resident opens the parkade exit from the secure side and the door-position contact changes state.
2. The local door-prop timer begins without delaying or preventing egress.
3. If the resident passes through and the door closes within the approved time, the local timer resets without sounding.
4. If an object or a hardware problem prevents closure, the local alarm activates after the selected grace period.
5. On a device designed for closure reset, removing the obstruction and closing the door silences and rearms the local alarm.
6. A separate connected system records and sends only the opening, restoration or held-open events included in its tested configuration.
7. The designated responder checks the door and records any repair or security follow-up required.

Choose the grace period for the actual opening

There is no universal delay that fits every strata building. A useful setting allows ordinary egress, including residents who need more time, without allowing the door to remain unsecured unnecessarily.

If a door is slow to close because of a mechanical defect, extending the timer is not the real repair. Check the closer, hinges, frame alignment, latch and environmental conditions first.

• Observe normal resident traffic and the time genuinely required for passage.
• Account for accessibility needs and the door’s approved operating sequence.
• Review door size, closer speed, latch behaviour and seasonal conditions.
• Identify legitimate delivery or maintenance use and how it will be managed.
• Confirm the timing choices actually supported by the proposed equipment.
• Record the final setting and retest it after any door-hardware adjustment.

Compare a local alarm with a connected layer

The right proposal can include one or both layers. This comparison explains the roles; final behaviour depends on the selected equipment, wiring, programming, power and communications.

Preserve safe egress and repair the door itself

A security door-held-open alarm must not obstruct, lock or delay a required exit. It can monitor and sound while still allowing immediate egress. Any work involving panic hardware, electromagnetic locks, door closers, latching, fire separations or fire-alarm interfaces needs review appropriate to the actual opening.

The City of Vancouver advises building owners to keep exit routes clear and ensure fire doors are not blocked or wedged open. The security objective is to detect and discourage door propping without compromising safe egress.

Before adding electronics, confirm that the door closes and latches reliably. An alarm can report a condition; it cannot correct a worn hinge, poor alignment, inadequate closer or damaged latch.

Give every alert an owner and a response

An app notification is not the same as professional monitoring, and neither is useful without a defined response. Council should identify who receives daytime and after-hours events, how quickly the condition should be checked and when a repair contractor, security provider or emergency service should be contacted under the property’s approved procedures.

If the design uses self-notifications, its effectiveness depends on an authorized person seeing and acting on them. If it reports to a monitoring station, agree on the signal type, call list and response instructions before commissioning. Vancouver properties should also confirm whether the connected design falls within the City’s security-alarm permit requirements.

• State which event starts the local timer and the available delay settings.
• Document what sounds, what resets it and how authorized service work is handled.
• Name the people or service receiving each remote event.
• Explain what continues during power, internet or cellular outages.
• Assign recurring tests for contacts, sounders, batteries and notifications.
• Record the response for a propped door, recurring hardware fault and suspected unauthorized entry.

Plan the opening, not just the alarm

WeTech Security Solutions plans access control, alarm systems and gate and parkade security for strata, condo, apartment and commercial properties in Vancouver and across the Lower Mainland.

The assessment begins with the real opening: door and frame, closer, latch, contact, existing wiring, access-control sequence, power, communications and the people who will manage the result. If a parkade exit is repeatedly being left open, note the location, when it happens, how long it remains open and which security systems are nearby. A site visit can then distinguish a local door-prop alarm, connected notification, door-hardware repair or coordinated combination.