Hotel Smart Lock Guest Access Management
Hotel smart lock guest access management is the written operating loop that moves a guest keycard through four gates — encode, issue, recover, revoke — on the property management system and hotel PC software that sits behind every hotel RFID door lock, so that a room opens for the right guest on the right dates and stops opening for that guest the moment they no longer have a right to be in the room. The question this playbook answers is not "how does a hotel lock work" but "how does a hotel run its guest access correctly across a multi-year lifecycle, across multiple shifts, across housekeeping and maintenance and emergency exceptions, so that access stays correct after the launch hype fades". This is the access-management spine; the check-in and check-out ceremonies that wrap around it are siblings (Hotel Smart Lock Check-In Workflow, /blog/hotel-smart-lock-check-out-workflow), and the architectural choices that determine which software tool actually sits in front of the lock are siblings too (/blog/hotel-smart-lock-system-architecture).
This document is written as an SOP — numbered protocols, IF-THEN rules, exception handling, and time budgets. Run it as-is, or adapt the cadences, but run something. Guest keycards have a richer failure surface than guest names on a paper ledger: cards are lost, left in the room after check-out, cloned by social-engineering, returned by past guests, handed to a third party at the desk, demagnetised by a phone, broken by a hotel laundry cycle, and quietly reissued by an overworked night auditor who forgot to check the guest out properly. The counterweight to that surface is a written rhythm with named owners, named entry/exit gates, and named consequences when gates are skipped.
Two honest disclosures before the protocols start:
- Per-model capability is a product-page item. Whether a specific hotel lock in this hotel-lock category reads Mifare 1 @ 13.56 MHz at 0–5 cm, holds 1,000 audit/event records, supports master cards, staff cards, floor cards, building cards and emergency cards, integrates directly with a PMS layer, and exposes a mechanical-key bypass, is a fact about that model. This playbook tells you what to do once you have decided that capability is present. Confirm it on the product page for every shortlisted SKU before you encode the first card.
- Guest cards are not the only credential. Every realistic hotel deployment pairs the guest keycard with at least one non-guest lane — staff cards for housekeeping and maintenance, master cards for managers, emergency mechanical key for first responders, and increasingly mobile or PIN credentials for guests who arrive without their card. The protocols below assume that fallback is in place; for the staff side see Hotel Smart Lock Staff Card Management, for the lost-card recovery side see Hotel Smart Lock Lost Card Management.
Protocol 0: Scope, Vocabulary, and Boundaries
Before the cadence starts, fix the vocabulary so every later protocol is executable by someone other than you.
| Term | Working definition for this playbook | Boundary |
|---|---|---|
| Guest card | A RFID Mifare 1 @ 13.56 MHz keycard (catalog-frequency band — check the model’s published specification for the deployed SKU) that opens one or more guest-room doors during a defined stay window | Distinct from staff card, master card, floor card, building card, emergency card, mechanical key |
| Hotel PC software | The on-site Windows application (or equivalent) that encodes cards, holds the lock database, and writes to each lock via handheld encoder or networked encoder; this catalog's hotel-lock lines list "multilingual management software" and "standalone or centralized database modes" among supported capabilities | One distinct from the cloud PMS the property uses for subscription or loyalty |
| PMS (Property Management System) | The reservation, billing and check-in/check-out system that the front desk runs; the handshake between PMS and hotel PC software is the integration boundary this playbook treats as a handoff | The PMS layer itself is bought separately; whether and how it talks to the login platform is per-model |
| Encoder | The handheld or networked device that physically writes the card; sits on the front desk or at the housekeeping supervisor station | One encoder per property for small hotels; one per floor or per cluster for larger properties |
| Lock database | The list of locks the software knows about, with each lock's room number, building, floor, door type, cardholders and audit events | Stored in hotel PC software; uploaded to locks via encoder or via wired/wireless sync — confirm on the platform |
| Stay window | The check-in date/time to check-out date/time during which the card is authorised to open the assigned room(s) | Defined by the reservation in the PMS; mirror of the reservation's check-out time, not the guest's actual departure |
| Master card | A card that opens every guest room in a defined scope (property-wide, building-wide, floor-wide) — used by managers, supervisors and authorised contractors | Distinct from staff card (which is one-hotelier's daily or shift access) |
| Staff card | A card issued to a named employee, with a clear role (housekeeping, maintenance, room service) and a clear time window (shift hours, weekdays only) | See Hotel Smart Lock Staff Card Management |
| Emergency card | A card held in a sealed envelope in the manager's safe or behind the front desk, used to admit first responders under written policy | Almost never used in normal operations; un-seal events get logged |
| Mechanical key | The non-electronic cylinder key that opens the lock when electronics fail or battery dies — usually a 5-pin cylinder on hotel-line locks; check the model’s published specification | Stored sealed in the front desk safe; usage triggers a written log entry |
| Audit log | The record of which card opened which door at what time; held in the lock and pulled by hotel PC software at defined intervals | Capability and depth are model-specific; check the model’s published specification |
| Revocation | The act of removing a card from the active list so it can no longer open any door — the single most consequential action in this playbook | Revocation is what separates a keycard system from a metal keycard lock |
Three explicit non-goals this playbook will not redo:
- Architectural choices about standalone vs centralized vs networked lock management. Whether the property uses standalone mode, centralized database mode, or networked mode is a decision covered in Hotel Smart Lock System Architecture. This playbook assumes that decision has been taken and writes the access loop against whatever the chosen mode supports — check the model’s published specification.
- Check-in and check-out ceremony design. The front-desk workflow that wraps around this access loop — ID check, deposit, room assignment, keycard handover, express check-out, late check-out — is dissected in Hotel Smart Lock Check-In Workflow and Hotel Smart Lock Check-Out Workflow. This article assumes the check-in/out ceremony has already decided which room the guest is in and on which dates, and writes the access loop that delivers the room keycard to the guest.
- Cardholder storage capacity, audit retention, PMS layer coverage, and multi-property scope. The catalogue publishes the Mifare 1 @ 13.56 MHz read band, 0–5 cm read distance, and audit/event-record depth up to 1,000 on the SLK-9936S hotel lock (a documented first-party data point). Per-model audit depth, per-lock cardholder capacity, and PMS-integration depth are not asserted as catalog capability here — check the model’s published specification for every shortlisted SKU before you commit.
The catalog reality is worth writing down once, plainly: this site exposes 79 published models across 10 categories, with 24 models in the hotel-lock category. Hotel-line locks in this catalog expose RFID Mifare card reading as the primary credential medium, paired on most models with mechanical-key bypass and audit-log retrieval. Some lines (SLK-9905A as one example) expose a hidden reader; others (SLK-9936S, SLK-9936G, SLK-9951TH, SLK-9962S) expose the more standard panel-mount Mifare reader. The hotel PC software these lines pair with is multilingual, runs in standalone or centralized database mode, and is positioned for 1–5 star hotels. Whatever your project — confirm the specific lock and the specific software you are buying supports the card types, card volumes, audit depths, and PMS-integration depth that your property will actually demand.
Protocol 1: The Four Gates (Entry Criteria → Active Card)
Guest keycard management is a four-gate loop. Skipping a gate is the single most common cause of "the door opened for the wrong guest / did not open for the right guest / opened for a guest who had already left" incidents. Each gate has an entry condition, an exit condition, and a named owner. No gate is optional; if a gate cannot be completed, the card is not issued and the request is escalated (Protocol 6).
Gate 1.1 — Encode
| Field | Entry criterion (must be true to start the gate) | Exit criterion (must be true to leave the gate) | Owner |
|---|---|---|---|
| Reservation exists | A confirmed reservation exists in the PMS with a room number, a check-in date, and a check-out date | The reservation is reachable from hotel PC software; the room number exists in the lock database | Front desk manager |
| Card stock | Blank RFID Mifare 1 cards are available at the encoder station, with a defined restock type | The card physically encodes without error | Front desk / housekeeping supervisor |
| Lock database | The lock database in hotel PC software has the assigned room registered with its floor, building, and door type | Room is searchable in the encode interface | IT / hotel PC software administrator |
| Encoder live | The encoder is connected to the hotel PC software and reports a healthy card-read test on a known-good card | Encoder passes a self-test or a known-good card test before the guest arrives | Front desk shift lead |
| Stay window defined | The reservation's check-in and check-out date/time are mirrored into hotel PC software | Stay window dates appear correctly in the encode interface | Front desk manager |
IF-THEN rules
- IF the reservation is in the PMS but not yet visible in hotel PC software → STOP. Either the PMS-to-hotel-PC handshake failed (escalate to IT) or the room is not yet mapped in the lock database (escalate to hotel PC software administrator). Do not encode blind.
- IF the encoder fails its self-test or fails to write a known-good card → STOP. Swap encoder, swap USB cable, swap card stock. Do not attempt to encode the guest's card against a known-bad encoder.
- IF the lock database does not contain the assigned room → STOP. Adding a room to the lock database is a separate protocol (see /blog/hotel-smart-lock-room-assignment). Do not improvise at the encoder.
- IF the reservation has open balances, unverified ID, or pending deposits → STOP. The encode gate is not the place to chase payment. Defer encode until the reservation clears the front-desk ceremony.
Gate 1.2 — Issue
| Field | Entry criterion | Exit criterion | Owner |
|---|---|---|---|
| Card encoded | The card has been successfully written with the room, the stay window, and any assigned common-area authorisations | Card opens the assigned room at the door reader; first open can be logged | Front desk agent |
| Guest identity confirmed | The guest's name on the card matches the guest's name on the PMS reservation, and ID has been checked per property policy | Identity match is logged in the PMS at the issue moment | Front desk agent |
| Guest briefed | The guest has been told the stay window, told how to use the card at the door, and told what to do if the card fails | Briefing is acknowledged in writing or on the PMS issue record | Front desk agent |
| Card sleeve | The card is in a sleeve that names the room number, the hold, the check-out date, and the property's lost-card hotline | Sleeve matches the identification card | Front desk agent |
IF-THEN rules
- IF the card does not open the assigned room on the first test → STOP. Treat as a Gate 1.1 failure (encoder, lock, or card). Do not hand the card to the guest.
- IF the guest's name does not match the reservation → STOP. Resolve the identity mismatch before issuing. Do not hand the card to someone other than the named guest.
- IF the guest is not the reservation holder but a designated check-in proxy (corporate booker, family member, travel agent) → follow the property's proxy-authorisation policy before issuing. Document the proxy in the PMS at the issue moment.
- IF the guest requests additional cards (children, partners, travel group) → block release against the property's additional-card policy. Most properties cap additional guest cards at 1–2 per registered guest; confirm the property's own policy.
Gate 1.3 — Recover
| Field | Entry criterion | Exit criterion | Owner |
|---|---|---|---|
| Issue event | A guest card was issued at Gate 1.2 and is now either lost, broken, demagnetised, suspected-cloned, or simply not returned at check-out | The original card is treated as compromised; a fresh card is encoded if the guest still has access rights; the old card is queued for revocation | Front desk / duty manager |
| Guest still has access rights | The guest's reservation is still active (not checked out, not cancelled, not blacklisted) | Recovery proceeds if access rights remain; otherwise skip to revocation | Front desk manager |
| Recovery reason logged | The reason for recovery is recorded — lost, broken, demagnetised, suspected-cloned, never returned | Log entry exists in the PMS or hotel PC software at the recovery moment | Front desk agent |
| Old card flagged for next revocation pass | The original card's identifier is queued for the next revocation pass | Flag is in the revocation queue | Front desk agent |
IF-THEN rules
- IF the card is reported lost outside business hours → run the recovery protocol at the night auditor's station, not by improvising at the encoder. Treat every lost card as a security event, not a customer-service event.
- IF the card is suspected-cloned (same card identifier seen at two distant doors within an impossibly short window) → escalate immediately. Treat the entire property as potentially exposed; trigger an audit-log pull and a property-wide card re-issue decision (Protocol 6).
- IF the guest checks out without returning the card → the card is treated as lost + at the moment of check-out. Revocation runs at check-out. No card-re-issue variant.
Gate 1.4 — Revoke
| Field | Entry criterion | Exit criterion | Owner |
|---|---|---|---|
| Revocation trigger exists | One of: reservation checked out; reservation cancelled; guest blacklisted; staff or contractor relationship ended; card reported lost; card suspected-cloned; card holder no longer entitled (room reassignment, downgrade, eviction); audit anomaly detected | Revocation event is logged with reason | Front desk manager / hotel PC software administrator |
| Card identified | The card's identifier (the Mifare card ID or the hotel-issued card number) is known to hotel PC software | Card is selectable in the revocation interface | Hotel PC software administrator |
| Card removed from active list | The card's status in hotel PC software is set to revoked, with the revocation timestamp and reason | Revocation record exists; if the lock database is centralised, the change has propagated to the locks; if standalone, the next sync has captured the change | Hotel PC software administrator |
| Card blacklisted in the locks | Each lock the card was authorised to open has had the card identifier removed from its active list — confirmed by an audit-log pull from the affected locks | Audit log from each affected lock no longer accepts the old card | Hotel PC software administrator + duty manager |
IF-THEN rules
- IF the revocation trigger is a check-out → run revocation at the same transaction as the check-out. Do not defer to the night shift. Do not batch into a daily cron. The card is dead the moment the bill is settled.
- IF the revocation trigger is a suspected-clone → revoke the card and every card authorised to open the same doors in the same window, until the audit log clarifies which card was the real one. This is the only time the playbook authorises a "scorched earth" revocation.
- IF the revocation trigger is a guest dispute or a property eviction → revoke the card before the guest is informed. Disputes that involve a guest who still holds a working keycard escalate property-wide; never argue with a guest who can still open their room.
- IF the revocation trigger is an employee off-boarding → revoke the staff card at the off-boarding moment. Off-boarding events that drag the revocation out by hours have produced hardcases in the field; revoke first, argue later.
Protocol 2: Card Type Authorisation Map
Not every card on the property has the same authority. Conflating card types is the second most common cause of "the door opened for the wrong person" incidents after the four-gate skipping failure. The map below names the cards a property typically runs and the authority each card carries.
| Card type | Authority scope | Issued by | Authorisation source | Lifetime |
|---|---|---|---|---|
| Guest card (single room) | One assigned guest room, common areas the property has authorised for guests (gym, pool, breakfast room, business centre), during the reservation's stay window | Front desk agent | PMS reservation → hotel PC software encode | Stay window; revoked at check-out |
| Guest card (suite / multi-room) | Multiple assigned guest rooms (suite + parlour, adjoining rooms for families), common areas, during the stay window | Front desk manager | PMS reservation → hotel PC software encode | Stay window; revoked at check-out |
| Master card (property-wide) | Every guest room in the property | General manager | Sealed-authorisation log; hotel PC software encode under named master authority | Long-lived; replaced on a defined cycle (typically annually, or on master-card-holder change) |
| Master card (building-wide) | Every guest room in one named building | Building manager | Sealed-authorisation log | Long-lived |
| Floor card | Every guest room on one named floor | Floor supervisor | Sealed-authorisation log | Long-lived |
| Staff card (housekeeping) | Every guest room on the assigned floor + housekeeping closet, in a defined shift window | Housekeeping supervisor | Hotel PC software with role assignment | Active while employed; revoked at off-boarding |
| Staff card (maintenance) | Every guest room on the assigned floor + maintenance areas, in a defined shift window | Maintenance supervisor | Hotel PC software with role assignment | Active while employed; revoked at off-boarding |
| Staff card (room service / F&B) | Guest room assigned to a current in-house dining delivery + F&B back-of-house, in a defined shift window | F&B manager | Hotel PC software with role assignment | Active while employed; revoked at off-boarding |
| Emergency card | Every guest room in the property | Sealed envelope in the manager's safe; un-seal events logged | Sealed-authorisation log; un-seal triggers a written incident report | Long-lived; sealed envelope inspected quarterly |
| Mechanical key | Every guest room in the property's mechanical-key reach (typically every room whose lock carries the matching cylinder) | Sealed envelope in the manager's safe; un-seal events logged | Sealed-authorisation log; un-seal triggers a written incident report | Long-lived; key custody controlled by seal position |
| One-shot card (cleaning / inspection) | One named guest room, during a defined short window (e.g., 30 minutes for inspection) | Housekeeping supervisor or duty manager | Hotel PC software with timed-pass window | Hours; revoked automatically at window end |
IF-THEN rules
- IF a card type is not on the above table → the card is either not supported by the deployed lock and software, or it is an unauthorised internal designation. STOP. Do not improvise a card type at the encoder.
- IF the authority scope is ambiguous (e.g., a "floor card" that is also expected to open the breakfast room) → resolve the ambiguity against the property's written access policy. Do not improvise at the encoder.
- IF a card is needed that does not exist in the table (e.g., contractor card, vendor card) → either define a new card type in the property's access policy and document it, or refuse the request. "Just one card, won't be long" is the most common root cause of a security incident.
- IF multiple staff cards of the same role are needed (e.g., three housekeepers for one floor) → issue three separate cards, each named to its holder. Do not issue one card shared across three people.
Protocol 3: Encoding Workstation Discipline
The encoder station is the bottleneck of the access loop. Most failed access events trace back to a workstation that is in poor physical state, has stale lock database, or has a card stock that has degraded. This protocol defines the daily, weekly and monthly discipline.
Daily (every shift)
| Check | Action | Owner | Time budget |
|---|---|---|---|
| Encoder self-test | Run the encoder's self-test or read a known-good test card | Front desk shift lead | 60 seconds |
| Card stock check | Inspect the card stock for visible damage, demagnetisation, or expired stock | Front desk shift lead | 60 seconds |
| Lock database freshness | Open hotel PC software and confirm the lock database timestamp is current (today or last sync) | Front desk shift lead | 60 seconds |
| Emergency envelope | Confirm the emergency card and mechanical-key envelopes are sealed and accounted for | Front desk shift lead | 30 seconds |
| Revocation queue | Open the revocation queue and confirm there are no pending revocations older than 24 hours | Front desk manager | 5 minutes |
| Audit log pull trigger | Confirm the audit-log pull trigger has run for the past 24 hours and the audit log is being captured | Hotel PC software administrator | 5 minutes |
Weekly (every Monday morning)
| Check | Action | Owner | Time budget |
|---|---|---|---|
| Encoder cable and connector inspection | Visual inspection of USB cable, card-stock contact pins, encoder housing | Hotel PC / IT | 10 minutes |
| Card stock restock | Replenish card stock against a defined par level | Housekeeping supervisor + front desk manager | 15 minutes |
| Lock database integrity | Run hotel PC software's database integrity check; reconcile any drift between software lock list and physical lock list | Hotel PC software administrator | 30 minutes |
| Master card use log | Pull the master card use log for the past week; reconcile every entry against a written justification | General manager | 15 minutes |
| Emergency envelope inspection | Inspect emergency envelope for tamper evidence; log inspection timestamp | General manager | 5 minutes |
| Mechanical key custody log | Inspect the mechanical-key safe for tamper evidence; reconcile every lock appearance with a written justification | General manager | 10 minutes |
| Staff card reconciliation | Pull the active staff card list; reconcile against the HR active-employee roster | Hotel PC software administrator + HR | 30 minutes |
Monthly (first business day of the month)
| Check | Action | Owner | Time budget |
|---|---|---|---|
| Encoder firmware version | Confirm encoder firmware is on the supported version; coordinate with vendor if upgrade is needed | IT | 30 minutes |
| Hotel PC software version | Confirm software is on the supported version; coordinate with vendor if upgrade is needed | IT | 30 minutes |
| PMS handshake test | Test the PMS-to-hotel-PC handshake with a synthetic reservation; confirm the reservation propagates to the lock database | IT + front desk manager | 30 minutes |
| Audit log retention check | Confirm audit log retention is within policy; export and archive the past month's audit log per property policy | Hotel PC software administrator | 30 minutes |
| Card stock expiry check | Inspect card stock for expiry dates; remove expired stock from rotation | Housekeeping supervisor | 15 minutes |
| One-shot card review | Pull the past month's one-shot card list; reconcile every entry against a written justification | Duty manager | 15 minutes |
| Card issuance volume vs card stock | Reconcile card issuance volume against card stock consumption; investigate any drift above 10% | Front desk manager | 15 minutes |
| Fail-mode review | Open Protocol 7's fail-mode log for the past month; identify any patterns | General manager | 30 minutes |
IF-THEN rules
- IF any daily check fails → STOP card issuance until the failure is resolved. Do not issue cards against a known-bad encoder or known-stale lock database.
- IF any weekly check is missed twice in a row → escalate to general manager. Each weekly check is a unique per-shift owner signal that no leader can absorb for them.
- IF any monthly check is missed → the property's PMS-to-lock software is exposed at the integration boundary. Escalate to general manager; flag for /request-a-quote conversation with the manufacturer about whether a managed-service or annual-maintenance contract is appropriate.
Protocol 4: Stay-Window Discipline
The stay window is the second most consequential variable in the access loop, after the four gates themselves. Stay windows that are too tight strand guests outside their rooms at the moment of early check-in; stay windows that are too loose let guests into rooms after they have checked out. The discipline below sets the boundaries.
| Stay window state | Authoritative start | Authoritative end | Card validity | Action at the encoder |
|---|---|---|---|---|
| Standard reservation | PMS check-in date at the property's standard check-in time (typically 14:00 or 15:00) | PMS check-out date at the property's standard check-out time (typically 11:00 or 12:00) | Valid from authoritative start to authoritative end | Encode with start = standard check-in time; end = standard check-out time |
| Early check-in (room available) | PMS early-arrival flag set by front desk | PMS check-out date at standard time | Valid from early-arrival flag time | Encode with start = early-arrival flag time |
| Late check-out (room available) | PMS check-in date at standard time | PMS late-checkout flag set by front desk | Valid until late-checkout flag time | Encode with end = late-checkout flag time |
| Extension (mid-stay) | Current card end-time | PMS extension flag set by front desk | Replace existing card with one valid until extension flag time | Re-encode fresh card; revoke old card at the same transaction |
| Same-day reservation | PMS check-in date at standard time | PMS check-out date at standard time | Valid for the stay window | Encode with start = standard check-in time |
| Walk-in (no PMS reservation) | Manual entry in hotel PC software at front desk's action | Manual entry at front desk's action (typically standard check-out time on the day of arrival unless extended) | Valid until manual end entry | Encode with manual start and end; reconcile the manual entry against the PMS as soon as a reservation is created |
| No-show reservation | PMS no-show scheduled flag at standard check-out time | Card never encoded or revoked at the moment the flag fires | Revoke before encoding or revoke immediately | Do not encode; if already encoded (early arrival), revoke at the flag |
IF-THEN rules
- IF the PMS check-in time is in the past and the card has not been encoded → flag for the property's late-arrival policy (typically a manual check-in with the same stay window).
- IF the PMS check-out time is approaching and the card has not been revoked → trigger Protocol 1.4 (Revocation) at the standard check-out time, not at the moment the guest's bill is settled.
- IF a guest requests an early check-in and the room is not yet ready → do not encode against a "ready at 10:00" promise. Encode when the room is actually ready; the card's stay-window start becomes the actual readiness time, not the requested time.
- IF a guest requests a late check-out and the next guest is arriving the same day → do not encode a late check-out. Negotiate luggage storage and a separate check-in time for the arriving guest; the new guest's stay window takes priority.
- IF the PMS-to-hotel-PC handshake fails during a stay-window update → fall back to manual entry in hotel PC software; reconcile against the PMS at the next handshake restore.
Protocol 5: Audit-Log Discipline
The audit log is the only record of what actually happened at the door. Card-encoded events are the guests' authority; audit-log events are the doors' truth. The two must agree. When they disagree, the audit log wins.
| Audit-log event | What it tells you | When to pull | Who pulls |
|---|---|---|---|
| Card open | A guest card opened a named room at a timestamp | At check-out; daily; on incident | Hotel PC software administrator |
| Card denied | A card attempted to open a named room and was refused at a timestamp | At incident; daily summary | Hotel PC software administrator |
| Mechanical key open | A mechanical key was used at a named room at a timestamp | At every use | Front desk manager |
| Master card open | A master card opened a named room at a timestamp | At every use | Hotel PC software administrator |
| Staff card open | A staff card opened a named room at a timestamp | Daily summary; at incident | Hotel PC software administrator |
| Battery low | A lock reported battery low | Daily | Hotel PC software administrator |
| Tamper alert | A lock reported a tamper event | At every alert | Hotel PC software administrator + duty manager |
| Lock offline | A lock dropped out of the network (if networked mode is in use) | At every alert | IT |
IF-THEN rules
- IF a card-open event is logged for a card that has been revoked → escalation. The lock database has not propagated the revocation. Run Protocol 1.4 again, with the affected lock as the unit of work.
- IF a card denied event spikes for one room in a short window → potential probing or social engineering. Escalate to duty manager; pull the audit log for the room for the past 24 hours.
- IF a mechanical-key open event is logged without a corresponding un-seal event in the sealed-authorisation log → escalation. Mechanical key custody has been broken.
- IF a master card open event is logged without a corresponding written justification in the master card use log → escalation. Master card use is undocumented.
- IF a tamper alert fires → the lock is potentially under attack. Treat as a security event, not a maintenance ticket. Trigger Protocol 6.
Protocol 6: Exception and Incident Handling
Things will go wrong. The question is not whether, but how the property responds. The exceptions below cover the predictable failure modes and the rare but consequential incidents.
| Exception | First action | Escalation | Recovery after |
|---|---|---|---|
| Card lost (single, during stay) | Encode a replacement at Gate 1.2; queue the lost card at Gate 1.3; revoke at Gate 1.4 within the same shift | Duty manager if guest disputes card was returned | After repair, the recovery is logged; no property-wide impact |
| Card lost (same guest, multiple offices) | Encode the full incident to Protocol 1.3 with a wide-angle scope; revoke at Gate 1.4 every card the guest may have used; pull audit log for the past 24 hours | General manager + property security | Audit log determines whether the property's wider card fleet is exposed |
| Card suspected-cloned | Treat as a property-wide incident; revoke at Gate 1.4 every card authorised to open the affected doors in the affected window; pull audit log from every affected lock | General manager + property security + manufacturer support (if audit log shows cloned patterns) | Audit log determines the cloned scope; re-issue all cards authorised in the affected window |
| Guest dispute / eviction | Revoke at Gate 1.4 before the guest is informed; pull audit log for the past 24 hours for the disputed room | General manager + property security + legal | Audit log is the property's evidence; re-issue cards only on the general manager's written authorisation |
| Lock electronics fail | Issue a mechanical-key from the sealed envelope; log the un-seal; replace the lock's batteries or the lock | Maintenance supervisor + hotel PC software administrator | Mechanical-key use is logged; the lock is restored or replaced per Protocol 7 |
| Lock mechanical fail | Block the lock; arrange alternate accommodation for the affected guest; replace the lock | Maintenance supervisor + duty manager | The replacement lock enters the lock database at the moment of install; every active card is re-issued |
| PMS-to-hotel-PC handshake fails | Fall back to manual entry in hotel PC software; reconcile against the PMS at the next handshake restore | IT + hotel PC software administrator | Manual entry is logged; reconciliation is logged |
| Encoder fails | Swap encoder; swap USB cable; swap card stock; if no encoder is available, fall back to a second encoder station or to a neighbouring property | IT + hotel PC software administrator | Encoder is restored or replaced per Protocol 7 |
| Hotel PC software fails | Fall back to a second station; if no second station, fall back to manual key issuance with a written log; reconcile at software restore | IT + hotel PC software administrator | Manual issuance is logged; reconciliation is logged |
| Battery low event | Replace the lock's batteries at the next shift change; verify battery replacement against a written log | Maintenance supervisor | Battery replacement is logged; the audit log records the replacement |
| Tamper alert | Treat as a security event; dispatch property security; pull audit log from the affected lock | General manager + property security + local law enforcement if physical evidence supports it | Tamper is investigated; lock is restored or replaced |
| Guest leaves card in room after check-out | Treat as lost + at the moment of check-out; revoke at Gate 1.4 within the same shift; physical recovery happens at the next housekeeping visit | Front desk shift lead | After rotation, the card is physically recovered and destroyed; the revocation is already logged |
IF-THEN rules
- IF the exception is a guest dispute → never argue with a guest who still holds a working keycard. Revoke first.
- IF the exception is a suspected clone → never assume a single guest is the only victim. Pull the audit log first; revoke second; notify the third.
- IF the exception is a tamper alert → never reset the lock without preserving the audit log. The audit log is the evidence.
- IF the exception is a PMS handshake fail → never assume the manual fallback is correct without reconciliation at handshake restore.
Protocol 7: Illustrative Project Scenario
Consider a 120-room property in a mid-tier city — three floors of 40 rooms each, mix of standard rooms and suites, on-site restaurant, gym and small meeting room. The property runs the SLK-9936S hotel smart door lock on every guest room (catalog-positioned for 1–5 star hotels, RFID Mifare 1 @ 13.56 MHz read band, mechanical-key bypass, multilingual hotel PC software, standalone or centralized database mode — check the model’s published specification for every deployed SKU). The property uses a mainstream PMS for reservations and billing; the PMS-to-hotel-PC handshake is enabled at the property's PMS contract level (a project-specific handshake capability — confirm per property).
Day-zero deployment
| Phase | Action | Owner | Duration |
|---|---|---|---|
| Site survey | Accepted | Hotel GM | 1 day |
| Lock database build | Accepted | IT + hotel PC software administrator | 2 days |
| PMS-to-hotel-PC handshake test | Accepted | IT + PMS vendor | 1 week |
| Front desk training | Accepted | Front desk manager + hotel PC software vendor | 3 days |
| Housekeeping training | Accepted | Housekeeping supervisor + hotel PC software vendor | 1 day |
| Master card and emergency card issue | Accepted | General manager | 1 day |
| Pilot | Accepted | Duty manager + IT | 1 week (5 rooms on one floor) |
| Full rollout | Accepted | General manager + IT | 1 week (all 120 rooms) |
Steady-state cadence
| Cadence | Owner | Time budget per cycle |
|---|---|---|
| Daily encoder self-test | Front desk shift lead | 60 seconds |
| Daily revocation queue check | Front desk manager | 5 minutes |
| Daily audit log pull | Hotel PC software administrator | 30 minutes |
| Weekly lock database integrity | Hotel PC software administrator | 30 minutes |
| Weekly staff card reconciliation | Hotel PC software administrator + HR | 30 minutes |
| Monthly PMS handshake test | IT + front desk manager | 30 minutes |
| Monthly audit log retention archive | Hotel PC software administrator | 30 minutes |
Annual review
| Item | Owner | Time budget |
|---|---|---|
| Master card cycle | General manager | Annual; 1 day |
| Emergency card custody review | General manager | Annual; 1 day |
| Hotel PC software upgrade review | IT + hotel PC software vendor | Annual; 1 week |
| Encoder firmware upgrade review | IT + hotel PC software vendor | Annual; 1 day |
| Access policy review | General manager + duty managers | Annual; 1 day |
| PMS handshake upgrade review | IT + PMS vendor | Annual; 1 day |
The point of the scenario is not the specific hotel, the specific lock model, or the specific PMS. The point is the cadence — daily, weekly, monthly, annual — and the named owners for each cadence. A property that runs the cadence correctly will keep guest access correct across a multi-year lifecycle; a property that runs the cadence only when something goes wrong will run into the same exception every quarter.
Protocol 8: Common Failure Modes and Refusal Lines
The field has a small set of recurring failure modes. Naming them in advance is the cheapest insurance the playbook can buy.
| Failure mode | Symptom | Root cause | Refusal line |
|---|---|---|---|
| "Just give them a card" | Front desk agent encodes a card without a reservation match | Front desk pressure to resolve a customer interaction quickly | Refuse. Encode against the PMS, not against the agent's memory. |
| "It's just for ten minutes" | Front desk agent encodes a one-shot card for a contractor, no written authorisation | Contractor pressure to start work | Refuse. One-shot cards require a named requestor and a named justification. |
| "We forgot to revoke" | Guest checks out; card is not revoked until the night auditor catches it the next morning | Revocation not run at the check-out transaction | Refuse. Revocation runs at the same transaction as check-out. |
| "The card stock is fine" | Front desk agent encodes against visibly damaged card stock | Card stock not being rotated | Refuse. Card stock has a defined restock cycle; expired or damaged stock is removed from rotation. |
| "The audit log can wait" | Hotel PC software administrator defers the daily audit log pull | Workload pressure | Refuse. Audit log is the audit trail. Daily pull is non-negotiable. |
| "The mechanical key is in the safe" | Mechanical key is unsealed without an unseal event log | Front desk pressure to admit a guest whose card has failed | Refuse. Mechanical-key un-seal is a logged event. Use the sealed envelope protocol, not improvisation. |
| "It's the same master card" | Master card is shared across multiple managers | Master card cycle has not been honoured | Refuse. Master cards are named. Shared master cards are an incident waiting to happen. |
| "We'll fix it tomorrow" | Encoder firmware, hotel PC software version, or PMS handshake test has drifted | No named owner for the monthly review | Refuse. Monthly review is non-negotiable. |
The refusal lines above are not optional. They are the discipline that separates a hotel that runs a guest access loop from a hotel that runs an exception waiting list.
Confirmed Boundaries and Open Questions
A short list of what this playbook does and does not claim.
| Claim | Confirmed by | Open question |
|---|---|---|
| Hotel locks in this catalog support RFID Mifare 1 @ 13.56 MHz reading | Catalog spec block (SLK-9936S first-party data — check the model’s published specification) | Which specific SKU in your shortlisted set supports which specific band and read distance |
| Hotel locks pair with multilingual hotel PC software running in standalone or centralized database mode | Catalog spec block (SLK-9936S first-party data — check the model’s published specification) | Whether your property's PMS layer, multi-property scope, and audit retention requirement fit the software's documented capability |
| Card-based access on hotel lines is a catalog capability | Catalog position (24 hotel-lock models) | Which specific model supports which card-type authority (master, staff, one-shot, emergency) at the lock level |
| Mechanical-key bypass exists on hotel lines | Catalog spec block (5-pin cylinder — check the model’s published specification) | Whether the mechanical-key cylinder on each lock matches the property's existing master-key system or requires a separate keying plan |
| Audit-log depth up to 1,000 events on the SLK-9936S | Catalog spec block (product-page-documented — check the model’s published specification) | Audit depth on the specific SKU in your shortlisted set |
| Battery operating cycles above 15,000 on 4 × AA on the SLK-9936S | Catalog spec block (product-page-documented — check the model’s published specification) | Battery operating cycles on the specific SKU in your shortlisted set |
| PMS integration with hotel PC software | Project-specific handshake capability (not asserted as catalog capability) | Whether the PMS your property uses is on the hotel PC software's supported integration list, and at what handshake depth |
| Cardholder capacity, PMS layer coverage, multi-property scope | Project-specific (not asserted as catalog capability) | The specific numbers for your property's lock database size, audit retention policy, and portfolio growth plan |
The boundaries above are the playbook's discipline: claim what the catalog confirms, name what is per-model and must be confirmed on the product page, and refuse what is project-specific and must be answered at the quote.
Closing Recommendation
A hotel that runs the four-gate loop correctly — encode against the PMS, issue to the named guest, recover the lost or damaged card without improvisation, revoke at the same transaction as check-out — and runs the workstation discipline daily, weekly and monthly, will keep guest access correct across a multi-year lifecycle. A hotel that tries to improvise any one of the four gates at the encoder will run into the same exception every quarter.
For the project-specific numbers — per-model cardholder capacity, audit depth, PMS handshake depth, multi-property scope, hotel PC software version, encoder fleet sizing, master card cycle policy, emergency envelope cycle policy, and access-policy review cadence — the answers come from a single conversation: a project brief sent via /request-a-quote, with the property's room count, PMS layer, audit retention policy, and access-policy regime currently in writing. The hotel-lock category page (/hotel-lock) is the entry point for the catalog; the SLK-9936S hotel smart door lock (Keypad Hotel Smart Door Lock) is the documented first-party data point for the spec block referenced throughout this playbook. Confirm per-model capability on the product page before you encode the first card.

