Low-Voltage Field Reference • Technical term
Request to Exit (REX) in Access Control: Function and Documentation
Request to exit is the system input or initiating function used to register or permit egress activity. Its role is not identical on every door: it may record an event, shunt a door contact, command an unlock, or participate in a code-required release arrangement.
Direct answer
what is request to exit in access control: the practical answer
Request to exit is the system input or initiating function used to register or permit egress activity. Its role is not identical on every door: it may record an event, shunt a door contact, command an unlock, or participate in a code-required release arrangement.
For a working contractor, the value of this definition is its ability to translate field language into a verifiable design decision. Use the sequence meaning → project consequence → evidence → acceptance. The label alone never proves compatibility, compliance or performance.
What this changes in the design package
Request to Exit (REX) in Access Control: Function and Documentation should change at least one controlled project record. On a floor plan, identify the physical location or route affected by door locking arrangement and adopted egress requirements. On the riser or signal-flow drawing, show how the selected equipment, pathway, power and communications relationships support the intended outcome. In the schedule, preserve the exact data needed to buy, configure, install and test the system.
Plan
Show the device, route, zone or interface in context. Use stable IDs rather than relying on a symbol alone, and flag any assumption that can change quantity or performance.
Riser or schematic
Show origin, destination, intervening equipment, shared infrastructure and interface responsibility. A diagram should expose relationships the floor plan cannot show clearly.
Schedule
Record listed hardware function, sensor or push-button type, controller sequence and fire alarm and power-loss interfaces where they can be reviewed and revised without redrawing the entire plan.
Proposal
State the verified design basis, named allowances, exclusions, owner/IT/electrical dependencies, testing method and the event that triggers a change order.
Field method
A repeatable definition workflow
Start by deciding what the term must communicate on this project. Then connect the definition to a selected device, a measurable setting, a drawing note and an acceptance result.
- 1. write the door sequence before wiring.
- 2. test normal and emergency egress states.
- 3. confirm direct-release paths where required.
- 4. record events and reset behavior.
After the final step, repeat the original operating scenario. A correction is not complete until the system passes the required function, the drawing and schedule match the installed condition, and the handoff record identifies what changed.
Decision and evidence table
| Question | Evidence to collect | Where to record it | Acceptance signal |
|---|---|---|---|
| What controls door locking arrangement? | write the door sequence before wiring; use exact model, reading, setting, photo or log evidence. | door sequence of operations, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls adopted egress requirements? | test normal and emergency egress states; use exact model, reading, setting, photo or log evidence. | REX wiring detail, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls listed hardware function? | confirm direct-release paths where required; use exact model, reading, setting, photo or log evidence. | egress interface matrix, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls sensor or push-button type? | record events and reset behavior; use exact model, reading, setting, photo or log evidence. | acceptance test script, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
Keep evidence close to the decision it supports. A screenshot without an equipment ID, a cable test without the cable identifier, or a code note without edition and jurisdiction is difficult to audit later.
Technical deep dive
Six controls that make request to exit defensible
1. door locking arrangement
preserve door locking arrangement before the team commits REX sensor to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to write the door sequence before wiring. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for using software REX as a substitute for required direct release, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the door sequence of operations. Tie it to request to exit and REX sensor with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
2. adopted egress requirements
establish adopted egress requirements before the team commits door contact shunt to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to test normal and emergency egress states. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for omitting fire alarm interface responsibility, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the REX wiring detail. Tie it to request to exit and door contact shunt with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
3. listed hardware function
measure listed hardware function before the team commits access controlled egress to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to confirm direct-release paths where required. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for not defining door-contact shunt timing, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the egress interface matrix. Tie it to request to exit and access controlled egress with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
4. sensor or push-button type
trace sensor or push-button type before the team commits maglock release to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to record events and reset behavior. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for testing only credential entry, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the acceptance test script. Tie it to request to exit and maglock release with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
5. controller sequence
reconcile controller sequence before the team commits door event sequence to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to write the door sequence before wiring. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for using software REX as a substitute for required direct release, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the door sequence of operations. Tie it to request to exit and door event sequence with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
6. fire alarm and power-loss interfaces
challenge fire alarm and power-loss interfaces before the team commits request to exit to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to test normal and emergency egress states. Compare the evidence with the intended access control outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for omitting fire alarm interface responsibility, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the REX wiring detail. Tie it to request to exit and request to exit with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
Field-capture worksheet
Before leaving the site, collect enough evidence that another qualified person can reconstruct the decision. Start with the site, floor, room and stable asset ID. Record the date, technician and current drawing revision. Photograph the overall context before taking close-ups, and place a readable label or reference in the image when practical.
- Identity
- Exact manufacturer, model, firmware or listing, terminal names, cable ID, panel/port/zone/door address, and the related plan symbol.
- Observed state
- What the user reported, what the technician reproduced, timestamps, LEDs or messages, logs, settings and whether the condition is continuous or intermittent.
- Measured state
- Applicable voltage, current, resistance, optical level, cable result, protocol status, signal format or environmental condition, including the instrument and test boundary.
- Change control
- The one change made, authorization, before/after evidence, temporary workaround, regression checks and any effect on other devices or shared infrastructure.
For this topic, call out door locking arrangement, listed hardware function and controller sequence. Use the vocabulary request to exit, REX sensor, door contact shunt consistently so the field note, drawing, schedule and proposal can be found together.
Worked field example
From an uncertain condition to a controlled record
A design-build contractor receives a report involving request to exit. The available plan shows a symbol, but it does not identify door locking arrangement, adopted egress requirements or listed hardware function. Instead of pricing or repairing from the incomplete symbol, the team opens a single issue record and assigns the affected equipment, cable or location a stable ID.
The technician collects the current settings, model information, photos and measured state. The designer compares that evidence with the selected equipment documentation and the current authoritative sources listed below. The estimator separates verified scope from allowances. The project manager records who owns any external dependency, such as an electrical circuit, network policy, door hardware condition, AHJ decision or owner-furnished device.
The corrected package includes the door sequence of operations, REX wiring detail and egress interface matrix. The team then repeats the operating test under the same conditions that produced the original question. That closed loop turns REX sensor and door contact shunt from search terms into traceable project decisions instead of isolated notes.
Common failure modes—and why they happen
Failure 01
using software REX as a substitute for required direct release
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 02
omitting fire alarm interface responsibility
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 03
not defining door-contact shunt timing
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 04
testing only credential entry
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
When a failure involves regulated life safety, egress, listing, energized work, public-safety radio, or code interpretation, stop at the boundary of your authorization. Escalate to the responsible qualified party and preserve the condition and evidence.
Minimum contractor deliverables
A useful answer survives the handoff from design to estimating, proposal, installation and closeout. At minimum, create the following:
- door sequence of operations.
- REX wiring detail.
- egress interface matrix.
- acceptance test script.
Each deliverable should show the project, revision, author, review status and the identity of the system element it controls. If a value is not verified, label it as an assumption, allowance, pending submittal or owner/AHJ decision. Do not let a blank field become an accidental commitment.
How to carry the answer into scope and proposal language
Describe the outcome first: what the customer will receive, where it applies and how it will be tested. Then name the basis used for request to exit, including the controlling drawing revision and selected equipment data. Include the labor and documentation needed to produce door sequence of operations and REX wiring detail.
Separate dependencies explicitly. Examples include usable owner drawings, accessible ceilings, working branch power, network addressing and policy, compatible owner equipment, door hardware readiness, permits, shutdown windows, AHJ review and access to occupied areas. If one of those facts is unknown, write an allowance or qualification and define how the price changes when the fact is confirmed.
Finish with acceptance: identify who witnesses the test, what evidence is retained and which result constitutes completion. This makes the page commercially useful without turning it into a product pitch.
Commissioning, handoff and future service
Commissioning should prove the designed function, not simply show that equipment turns on. Run the accepted scenario, an expected failure or trouble state, recovery, and any interface that crosses to network, electrical, fire alarm, door hardware, controls or owner systems. Save results against stable IDs and the approved revision.
At handoff, give the owner the door sequence of operations, REX wiring detail, final configuration, approved substitutions, warranties and the contact path for unresolved external responsibilities. Remove default credentials and temporary access where applicable. Explain which changes can invalidate the result—for example a new firmware release, equipment replacement, changed speaker tap, moved camera, added cable, revised AHJ direction or modified switch policy.
Future service begins by comparing the current condition with this accepted baseline. If the record is missing, recreate it before making broad changes. That discipline reduces repeated troubleshooting, protects proposal scope, and lets the next technician distinguish a design issue from a later operational change.
Frequently asked questions
What should I verify first?
Start with door locking arrangement and adopted egress requirements. Establish the exact product, project location and current system state before applying a diagram or changing configuration.
Can I use this page as a construction detail?
Use it as an editorial planning and verification aid. Convert it into a project detail only after reconciling the manufacturer instructions, adopted requirements, approved submittals and responsible professional or AHJ direction.
What belongs in the closeout package?
Include door sequence of operations, REX wiring detail, egress interface matrix, acceptance test script, plus test evidence, deviations, final settings and the identity of the person or authority that accepted the result.
What should I read next?
Continue with Access-Control Composite Cable Color Guide: How to Document Conductors Safely, Door Strike Power and Dry-Contact Relay Wiring Diagram, Access Reader Beeps but Door Will Not Unlock: Diagnostic Decision Tree, OSDP Reader Offline: Address, Polarity, Power and Secure Channel Checks and the Access Control design software resource.
Authoritative references and how to use them
These links are starting points for current primary-source information. Confirm the current edition, product revision, publication status, jurisdiction and applicability. Accessed for this release on 2026-08-08.
- 2024 IBC means of egress — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- Security Industry Association OSDP — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- UL Standards and Engagement — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.