Guide resource
Request To Exit explains a decision that can materially affect security, safety and administration. Use it to prepare for a site assessment, then have the final design checked against the building, door and operational requirements.
Separate exit detection from emergency release
A request-to-exit input tells the access system that an authorised exit is occurring, often to release a lock or suppress a forced-door alarm. It is not automatically an emergency door-release device. A motion sensor, push button, lock switch and break-glass unit can have different purposes and wiring paths.
Choose the device around the exit behaviour
A handle or lock-mounted switch can closely represent intentional use of the door. A push button requires a person to find and operate it. A motion detector can support touch-free flow but may trigger from nearby movement, reflections or activity through glass. High-security and public exits may need additional or different approved arrangements.
Consider accessibility, mounting, signage, tailgating risk and whether the person must unlock the door before reaching the detector’s field.
Document the release and alarm-suppression path
State whether REX directly interrupts lock power, requests release through a controller, suppresses a forced-door event, or performs more than one function. Define activation time, door-held timing and the response to a stuck or disconnected input. Required safe egress must not rely on an unsuitable software path.
Test ordinary, hurried and abnormal exits
Approach at different speeds and angles, operate the door during busy flow, remain near a motion detector, and test a person with limited reach or mobility. Verify that exit is reliable without creating nuisance unlocks, and confirm alarms behave correctly when the door opens without REX.
Review nuisance activation and changed surroundings
A REX device that worked at commissioning can behave differently after furniture, partitions, signs or door operators change. Review activation patterns when the entrance layout changes or nuisance unlocks appear. For motion devices, observe the detection field in real use; for buttons and lock switches, confirm physical condition, accessibility and reliable return after operation.
Request To Exit questions
What decision should the request to exit guide support?
For Request To Exit, use it to record the relevant door, user, administration and failure requirements before equipment is selected. It is a planning aid, not a universal compliance certificate.
Does the request to exit guidance apply to every opening?
For Request To Exit, no. Door construction, traffic, egress, fire significance, accessibility, environment and other building systems can change the appropriate design.
What site information is needed for request to exit?
For Request To Exit, provide numbered doors, photographs or plans, user groups, operating hours, credential preferences, interfaces, known building constraints and expected changes.
Who should review a decision based on request to exit?
For Request To Exit, the client and security designer should review it, with IT, building, fire, electrical, privacy or specialist contractors involved where their responsibilities are affected.
What should be tested after applying request to exit?
For Request To Exit, test authorised and denied use, normal exit, physical closure, monitoring, relevant power or communications conditions and any integration from original event to operator outcome.
Discuss your access-control requirements
Share the door locations, approximate user numbers, site plans or photos, integrations and expected growth. Serious Security can prepare an itemised proposal after the requirements and site conditions are assessed.
Request an itemised access-control quote Sydney: (02) 8734 3250 Melbourne: (03) 8513 0799
