Hospitality technology guide
The door lock is the first piece of hotel technology a guest touches and the one the operations team relies on most. When the lock system and the guest room management system (GRMS) share information, the room can react to the guest arriving, leaving or asking not to be disturbed — and the hotel gets a clearer picture of every room without extra hardware.
What “lock integration” means in a hotel
Most hotels run two separate systems at the guest room door. The lock system — VingCard and Saflok are the two names hotel teams in our region meet most often — issues keys, controls who may open which door and keeps an audit trail of openings. The guest room management system controls the room environment: HVAC set points, lighting scenes, occupancy logic and room status for housekeeping and engineering.
A lock interface is the link between the two. Depending on the lock platform and the hardware installed, it can pass door events and key information into the GRMS, receive room status back, or both. The goal is simple: one system should not have to guess what the other already knows.
It is worth separating three things that are often bundled together in proposals:
- The PMS–lock interface, which lets the front desk encode keys from the property management system at check-in. Almost every hotel has this.
- The lock–GRMS interface, which shares door and key events with the room controls. This is the integration this guide is about.
- The PMS–GRMS interface, which tells the room controls whether a room is sold, vacant or checked out so that energy strategies can follow the reservation.
The best results come when all three are planned together, because each one fills a gap the others leave.
Why connect the door lock to the guest room management system?
Energy that follows the guest
Occupancy sensing on its own can be fooled: a guest asleep and still, or a room with the curtains drawn, may look empty to a motion sensor. Door events give the GRMS a reliable anchor. A door that opens and closes, followed by movement inside, confirms that someone has entered; a door that opens and closes with no movement afterwards suggests the room has been left. Combined with the PMS status, the GRMS can move a sold-but-empty room to a moderate set point and an unsold room to a deeper setback, then bring it back to comfort before the guest returns.
This is the same logic behind the energy management work we describe on our automation and control systems page: the room should save energy when nobody needs it, without the guest ever feeling the system working.
Room status the whole team can trust
When door and key events reach the GRMS, the engineering and housekeeping dashboards can show more than “occupied” or “vacant”. Teams can see whether a room was entered by a guest key or a staff key, whether Do Not Disturb or Make Up Room is active, and whether a door has been left ajar. Housekeeping can plan rounds around rooms that are genuinely empty, and engineering can respond to a door-ajar or low-battery alert before a guest reports it.
Security and accountability
The lock system already keeps an audit trail. Sharing selected events with the GRMS and the wider building systems makes those events useful in real time — for example, flagging a door held open on a guest floor at night, or highlighting staff entries into a room that has requested privacy. Access rules themselves stay in the lock system; the integration adds visibility, not a second place to manage permissions.
A smoother guest experience
Guests rarely notice integration when it works. They notice when it does not: a room that is cold on arrival, lights that switch off while they are inside, or a cleaner knocking despite the privacy indicator. Linking the lock and the room controls removes many of these small frictions. Welcome scenes, arrival comfort and privacy handling all become more dependable when the GRMS knows exactly when the door was opened and by whom.
How the integration works in practice
Online and offline locks
Lock systems fall broadly into two families. Offline (standalone) locks store their rules on the lock and the key; events are collected when staff read the lock with a programming device. Online locks are connected through a wireless network or gateway and can report events and receive updates as they happen. Real-time integration with the GRMS generally needs online locks, or a GRMS-side door contact and room controller that can sense the door independently.
Many properties mix the two: online locks on guest room doors and offline locks on back-of-house areas. A good design states clearly which doors report into the GRMS and which do not, so nobody expects data the hardware cannot provide.
The events that matter
Not every lock event needs to reach the room controls. The useful set is usually small:
- Door opened and door closed, with the key type (guest, staff, master, emergency).
- Door left ajar beyond a set time.
- Privacy or Do Not Disturb status set on the lock, where the lock supports it.
- Low battery and lock fault alarms for engineering.
- Key validity changes at check-in and check-out, if the lock platform can share them.
Agreeing this list early keeps the interface simple to test and keeps network traffic and alarm noise under control.
Where the logic lives
The lock system remains the authority for access; the GRMS remains the authority for comfort and room status; the PMS remains the authority for the reservation. The integration should move information between them without duplicating decisions. In the hotels we have worked on, a central server for guest services is usually where these interfaces meet, giving the operations team one place to monitor rooms, while each underlying system keeps its own responsibilities.
VingCard and Saflok in Titan BT references
Lock interfaces appear throughout our hospitality references. Several examples on this site describe both brands working alongside energy management and a central guest services server:
- Raffles Istanbul — e527 energy management with a VingCard lock interface, a BACnet interface to the hotel’s other automation systems and the central server for monitoring.
- Asia Marriott Istanbul — energy management, guest services and a Saflok lock interface for keyless room access.
- Kempinski Bodrum — e527 energy management, a Saflok lock interface and a central server for guest services.
- Swissôtel Bosphorus — e527 and Modeva energy management, lighting management and a VingCard lock interface connected through the central server.
The common thread is not the brand of lock but the way it is connected: the lock, the room controls and the guest services platform are planned as one room system. You can browse more examples on our references page.
What to put in the specification
Lock integration problems usually start in the specification, not on site. These points help owners, consultants and operators get a design that works on opening day:
- Name the lock platform and model range early. Integration options depend on the lock family, the firmware and whether the locks are online. Leaving the choice open until late construction often removes options.
- Define the event list. Write down which door and key events the GRMS should receive and what each one should trigger. Keep it short and testable.
- Decide where privacy status is set. Do Not Disturb can live on the lock, on a room panel or on both. Decide which one is the source of truth so the two never disagree.
- Plan the network. Online locks and room controllers need wireless coverage or gateways in every corridor. Coordinate these with the hotel’s network infrastructure rather than adding a separate network late in the project.
- Agree the PMS interfaces at the same time. The PMS–lock and PMS–GRMS interfaces affect the same check-in and check-out events. Testing them together avoids rooms that are “checked out” in one system and “occupied” in another.
- Set alarm ownership. Decide who receives door-ajar, battery and fault alarms — engineering, security or the front desk — and how they are acknowledged.
- Include retrofit realities. In existing hotels, check door preparation, battery access and whether a door contact is needed for the GRMS when the lock cannot report online.
- Write the commissioning test. Define a room-by-room test: open with a guest key, open with a staff key, leave the door ajar, set privacy, check out. Every room should pass before handover.
Retrofit or new build: what changes
In a new build, the lock, GRMS and network can be designed together, so the cleanest option is usually online locks reporting through the room controller or a shared gateway. In a renovation, the existing locks may be offline or out of support. Options then include upgrading lock electronics to an online version, adding a door contact to the GRMS room controller so the room can still react to the door, or phasing the upgrade floor by floor while the hotel stays open. The right answer depends on the condition of the doors, the remaining life of the lock system and how much disruption the hotel can accept.
Either way, the guest should not see the difference. Corridors, doors and room panels should look and behave consistently, and staff should use one set of procedures across old and new floors.
Common mistakes to avoid
- Treating the lock as a separate package. When the lock is procured on its own, the integration often becomes a change order with limited options.
- Sending every event everywhere. Too many events create alarm fatigue and make faults harder to find. Share what the GRMS can act on.
- Two sources of truth for privacy. If the lock and the room panel can both set Do Not Disturb without syncing, housekeeping will receive mixed signals.
- Skipping the room-by-room test. A single mis-addressed room controller can link one room’s door to another room’s HVAC. Only a full test catches it.
- No plan for battery management. Online locks report battery levels; make sure someone owns the alerts and the replacement routine.
Planning a lock and GRMS project
Lock integration is a small part of a hotel project that guests feel every day. It works best when the lock platform, the guest room management system, the PMS interfaces and the network are planned as one room system from the start. If you are preparing a new hotel, renovating guest floors or reviewing an existing installation, our hospitality systems team can help you define the scope and the interfaces. For the wider GRMS decision, see our guide to comparing hotel GRMS and guest room controls, and for in-room services see hotel TV and guest services.
Contact Titan BT to discuss your property, the lock platform you use and what you want the room to do when the door opens.