Define the work the software must support Choose access-control software by testing the tasks your staff must perform: approving access, issuing credentials, setting schedules, removing former users, investigating door events and recovering from faults. A feature list is useful only when it describes the proposed controllers, readers, software version and licenses. Start with a door

An access-control reader collects a credential and communicates with the controller or supported management architecture. Selecting one requires more than matching its appearance to a door. Check credential technology, secure configuration, interface, environment, mounting and the user’s entry workflow. Separate credential technology from the reader interface The card or phone-to-reader exchange is different from the

An on-premises access-control system places management software and data under a locally managed infrastructure model. The application may run on a physical or virtual server; controllers at the openings may retain their own rules and event records. The exact architecture must be documented rather than inferred from the term “on-premises.” When to evaluate local management

Facial authentication can be one part of a commercial access-control design, but it needs a clear purpose, an appropriate privacy process and a tested alternative for people who cannot or do not use it. Evaluate the complete workflow rather than treating “AI” or “touchless” as evidence of accuracy, security or compliance. Define the authentication task