Commercial / In depth

Access Control Fundamentals: Follow the Door's Decisions

Understand credentials, readers, controllers, locks, exit signals, door contacts, and the difference between entry security and safe exit.

Electronic access control joins a permission decision with a physical opening. Presenting a credential, receiving an access-granted event, and actually opening a door are three different events. Learning that sequence helps beginners describe problems precisely. It also prevents a common mistake: treating every failure as a bad reader or assuming that a green light proves the entire door assembly performed correctly.

Recognize the main roles

PartWhat it contributes
CredentialA card, fob, mobile credential, or other approved identifier presented for an access decision.
ReaderReceives credential information in a supported format.
ControllerEvaluates configured permissions, such as the authorized door and schedule.
Locking hardwarePhysically controls entry according to the approved system design.
Request to exitA signal associated with intended exit; its exact purpose depends on the arrangement.
Door contactReports the monitored door-position condition, commonly open or closed.

These roles may occupy separate products or be combined within one device. The management software provides the administrative interface, while the location and timing of access decisions depend on the product architecture. Credential, reader, controller, and software compatibility must be established together. Schlage's reader-controller introduction explains the basic decision sequence and several ways products divide these responsibilities.

Keep exit monitoring separate from exit release

Request-to-exit, often abbreviated REX, RTE, or RX, does not name one universal operating method. A switch inside door hardware can report that someone operated the inside lever while mechanical hardware independently permits exit. In other approved arrangements, an exit-related device participates in releasing an electrical lock. You must identify which arrangement you are looking at.

A door-position contact provides different information. It reports position at its sensing point; that alone does not prove the latch is securely engaged. A system may compare position, authorized access, and exit signals when generating events or alarms. The exact logic is configuration dependent. Allegion's RX-switch explanation is a useful reference for understanding monitoring versus control.

Ask two separate power-failure questions

Fail safe commonly means the electrified locking function unlocks when power is removed. Fail secure commonly means it remains locked when power is removed. These terms often describe the entry or secure side of an opening. They do not, by themselves, tell you whether someone inside can leave.

Mechanical free egress means that the exit hardware permits departure mechanically, independently of an electronic access decision. Suitable hardware can therefore maintain fail-secure entry while allowing mechanical exit. Conversely, an arrangement that electrically restrains egress requires evaluation under the applicable provisions for that arrangement. Never approve a design from the words “fail safe” alone.

Power loss, fire-alarm response, and loss of network communication are different conditions. The required responses depend on the selected products, complete assembly, adopted code, and authority having jurisdiction. Allegion's fail-safe and fail-secure FAQ explains why these distinctions matter.

Build an expected-versus-observed worksheet

For supervised training, use a mock opening or an authorized demonstration system. Write the expected sequence before observing it. For example: an approved training credential is presented, the system records its decision, the hardware changes to its intended entry state, the door opens, and it returns to the documented condition after closing.

Record each observation in its own column. “Credential recognized” is evidence about one part of the sequence. “Door opened” is evidence about another. Add an uncertainty column: “No latch-status monitoring fitted” is more informative than assuming that a closed indication proves latching. Any planned fault-condition demonstration should use a supervisor-approved test procedure with responsibility for the opening established in advance.

Hypothetical case: the green-light complaint

At a fictional shared office, an employee reports that her badge receives a green indication but the door sometimes stays shut. The apprentice is tempted to order a new reader. Instead, the supervisor asks for a neutral description of the sequence and the conditions under which the complaint occurs.

The resulting note says the authorized system displayed an access-granted event, but entry was not achieved on two observed attempts. It records the door identifier, time, relevant environmental observations, and who witnessed the result. This does not diagnose a particular component. It gives the qualified technician a better starting point than “reader broken” and avoids altering a working configuration merely to see what happens.

Practice: interpret three observations

A training door uses documented mechanical free egress. Its entry hardware is specified as fail secure. A door contact reports closed, and the software shows an earlier access-granted event. Which observations establish that the door is currently latched? What should the apprentice say about exit during loss of lock power?

Model answer

Neither the earlier access decision nor the position indication alone proves current latch engagement. That requires an appropriate observation or fitted monitoring method within the approved verification procedure. The documented mechanical exit operation is the relevant basis for explaining egress during loss of lock power; the fail-secure label describes the entry function. The actual assembly must still be verified against its documentation.

Review before making a claim

  • Name the event you observed and the evidence supporting it.
  • Distinguish permission, hardware operation, position, and latching.
  • Identify whether REX monitors exit or participates in release.
  • Record entry behavior and exit behavior separately.
  • Use approved procedures for testing and escalate unexplained results.

Continue your learning

Sources & further reading

Reviewed September 19, 2026. Check the linked organizations for current requirements.