Modern stainless-steel elevator interior with blue accent lighting and a floor-selection panel with embedded card reader
Solutions

Elevator floor control: the lift only answers the floors your credential allows

Floor-restricted selection from lobby to landing, coordinated turnstile and fire-service rules, passenger and service separation, and integration scoped to the actual controller.

In a tall building the elevator is itself an access boundary: once someone is inside a lift, uncontrolled floor buttons deliver them to tenant suites, hotel guest floors or plant levels that the lobby turnstile was meant to protect. Elevator floor control binds the call panel and floor selection to the credential, so a visitor reaches only the hosted floor, an office tenant reaches their leased floors, and service lifts follow separate schedules. Because lift behaviour depends on the specific elevator controller and the life-safety system, every integration — which floors a credential releases, how common and service lifts differ, and what happens during a fire recall — is confirmed in writing against the actual equipment rather than assumed from a brand name. The office solution covers tenant floors, the hotel solution covers guest lifts, and the multifamily solution covers residential cores.

Key facts

Elevator floor control at a glance

Floor selectionCredentials release only authorized floors at the lobby and landing call panels
Lobby coordinationTurnstile, lift and stair access follow one rule so a denied floor cannot be reached another way
Visitor logicHosted visitors receive the destination floor for the visit window and no other selection
Service liftsGoods, housekeeping and fire-service movement follow separate schedules from passenger lifts
Life safetyFire recall and firefighter control always override credential logic per the approved design
Integration scopeCompatibility is verified against the actual lift controller and agreed in writing
BOM shapeLobby and cab readers, controller interface, turnstile coordination and commissioning scope
Answer unit

Open floor buttons with lobby security, or credential-linked destination control?

Multi-tenant and high-rise buildings specify floor-restricted selection; low-rise single-tenant buildings may rely on stair and floor-door control.

DimensionOpen lift buttonsCredential-linked floor control
Tenant floorsAnyone in the lift reaches any floorOnly leased floors selectable per credential
VisitorsEscorted or unsupervised roamingDestination floor issued for the visit
Service trafficService moves share passenger liftsSeparate goods and housekeeping schedules
Fire eventsManual response assumptionsAutomatic recall with firefighter override intact
Bypass riskStairs defeat the lift restrictionTurnstile, lift and stairs coordinated as one boundary
Typical fitLow-rise single-tenant sitesHigh-rise hotels, offices and residences
Door fitment

Door types and lock-body match

The lobby call panel is the primary control; landing panels, stair cores and the service lift must be coordinated or floor control is bypassed.

OpeningTypical doorLock approach
Lobby call panelMain lift lobby destination panelCredential releases authorized floors before the car is called
Turnstile / lobbyBarrier between street and lift hallCoordinated so only authenticated passengers reach panels
Landing panelFloor call panels on tenant levelsRestricted to the floor’s occupants and authorized cross-floor roles
Guest / visitor liftHotel or event passenger liftsRoom- or host-linked single-floor selection during the stay or visit
Service liftGoods and housekeeping carShift and vendor schedules separate from passengers
Stair / bypass coreFire stairs and inter-floor doorsControlled so stairs cannot bypass the lift floor policy
Typical configuration

Example BOM shape for a high-rise core

This example illustrates a typical configuration, not a specific customer project. Lift count, controller model and tenant mix drive the list.

ComponentTypical logicNotes
Lobby and cab scopeCall-panel and in-car floor readersCredential-linked selection for passenger lifts
Controller interfaceIntegration with the actual lift controllerFloor mapping and fallback agreed in writing before build
Boundary coordinationTurnstile, landing and stair-core alignmentNo uncontrolled path to a restricted floor
Life-safety scopeFire recall and firefighter overrideVerified against the authority-approved sequence
CommissioningFloor-by-floor test with all tenant profilesIncluding visitors, service traffic and a fire-recall test
Deployment workflow

How an elevator control program rolls out

  1. Equipment and floor auditLift controller models, floor tenancy, service lifts and stair paths are surveyed before any commitment.
  2. Pilot coreOne lift group runs tenant, visitor, service and fire-recall scenarios end to end.
  3. Building rolloutLift groups and coordinated cores commission floor by floor around occupancy.
  4. Staff adoptionSecurity and concierge rehearse visitor floors, moves and emergency response.
  5. Assurance handoverFloor matrix, life-safety sign-off, fallback procedure and service contract are documented.
FAQ

Elevator floor control: common questions

How does the lift know which floors a passenger may reach?

The credential presented at the lobby call panel — card, code or mobile credential — carries the person’s authorized floor groups, and the destination-control system enables only those floor selections before calling a car; in-car readers can reinforce the rule where the building requires it. A visitor’s temporary credential carries just the hosted floor for the visit window, while service and housekeeping credentials select service levels on their schedules. The floor matrix is built from the tenancy and room list and maintained when leases change. The pilot core tests the full matrix, including a passenger attempting an unauthorized floor, so the rejection behaviour is confirmed rather than presumed compatible with the installed lift.

Does it integrate with our existing elevator controller?

Floor control interfaces vary considerably by lift manufacturer, controller generation and whether destination hardware already exists, so compatibility is verified against the specific controller model and firmware rather than a brand claim, and the integration points — floor mapping, common versus restricted floors, service lifts and failure fallback — are agreed in writing before build. Some buildings require an additional floor-control interface module installed by the lift vendor, which affects both scope and commissioning. A survey of the machine room and controller documentation is the first step. Where an integration cannot be certified, the fallback design uses controlled stair and floor doors rather than promising lift behaviour the equipment cannot deliver.

How are visitors and service traffic kept to the right floors?

Visitors receive a credential that selects only the destination floor tied to their host and visit, often from a turnstile or concierge station, so a guest cannot explore other tenant floors; hotel guests similarly reach their room floor and amenities during the stay. Goods, housekeeping and waste movement use a separate service-lift schedule tied to shifts and work orders rather than sharing passenger cars. Mixed-use buildings additionally separate residential, hotel and office populations across lift banks where the core design allows. Every population is included in the commissioning matrix, since a restriction that works for tenants but not deliveries creates a daily workaround that erodes the whole system.

What happens during a fire or elevator emergency?

Credential restrictions never obstruct the life-safety sequence: on fire recall the lifts return as designed, firefighter control remains exclusively with responders, and evacuation stairs and exit paths open according to the authority-approved design regardless of access groups. The floor-control integration is tested to confirm it does not interfere with recall or emergency power behaviour, and occupants with mobility needs follow the building’s documented evacuation plan. Stair cores that are controlled for normal security release appropriately in an emergency. The pilot includes a witnessed fire-recall test with the lift maintainer, because an unverified assumption about override priority is the single most dangerous failure in vertical access control.

How is an elevator floor-control BOM and MOQ scoped?

The BOM covers lobby and in-car readers, the lift-controller interface, any required floor-control module, turnstile and stair-core coordination, life-safety commissioning and spares, with MOQ and lead time confirmed in writing per quotation. Buildings pilot one lift group across tenant, visitor, service and fire scenarios before extending to the full core. Send the lift brand and controller model, floor-by-floor tenancy, service-lift layout and machine-room access, and the quote maps each line to verified integration scope rather than generic hardware.

Let the lift answer only the floors that belong to the passenger

Send the lift controller model, floor tenancy and service-lift layout — receive an integration-scoped BOM with written MOQ and lead-time terms.

Discuss your project (RFQ)Project configurations

Last updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team

Your Cart
Your experience on this site will be improved by allowing cookies Cookie Policy
Chat on WhatsApp