Keyless check-in that works when you are not there

Short-let hospitality has a specific structural problem: a stranger arrives at a property when you are not there, and needs to get in. Every solution to that involves a trade between convenience, security and the awkward reality that keys physically exist and can be copied, lost or simply not returned.

Keyless entry solves it properly, and it introduces its own failure modes that are worth understanding before a guest is standing in the rain at eleven at night.

What is actually wrong with keys

A key cannot be revoked. If a guest keeps it, or copies it, you have no way to know and no remedy short of changing the lock. Over a year of lettings that risk accumulates quietly.

Key handover is also the single most common operational friction in short lets. Meeting guests requires someone to be available at a time the guest chooses and frequently changes. Key safes work but concentrate the risk into one code that tends never to be changed. And late arrivals, delayed flights and missed trains turn a handover into an evening of phone calls.

The options, honestly compared

Key safe with a rotating code

The pragmatic entry point, and better than it sounds if the code genuinely rotates per booking. Cheap, requires no power or network, works when everything else fails, and the physical key inside remains the ultimate fallback.

Its weakness is discipline: a code that is not changed between guests is a permanent code known to everyone who has ever stayed. If you use one, changing it every turnover has to be part of the cleaning routine, not an intention.

Smart lock with per-booking codes

The standard answer for good reason. Each guest gets their own code, valid only for their stay, expiring automatically. You can see when it was used. No handover, no meeting, no key to lose.

Requirements to get right: battery management, a mechanical override, and codes that expire without anybody having to remember to remove them.

Smart lock integrated with the booking system

The version that scales. Codes are generated and expired automatically from the reservation, so nobody is issuing them by hand. Worth it above roughly three properties, or one property with frequent turnover.

App-only entry

We would avoid it as the sole method. It depends on the guest having a working phone, a charged battery, a data connection, having downloaded something, and Bluetooth behaving. Any one of those failing produces a locked-out guest and a phone call. As an option alongside a code, fine.

The details that prevent lockouts

Batteries

Replace them on a schedule rather than on a warning. Most smart locks warn at fifteen per cent, and lock batteries fall off a cliff in cold weather. Change them at every deep clean or every six months, whichever comes first, and keep spares in the property.

Code timing

Make codes valid from a few hours before check-in and until a few hours after check-out. Guests arrive early and leave late, and a code that expires at ten sharp generates a support call from someone standing outside with luggage.

Code delivery

Send it more than once and in more than one place: in the booking message, again the day before, and in whatever guide you provide. A code sent once, three weeks in advance, will not be found.

Cleaners and maintenance

Give them their own permanent or recurring credentials, not the guest code. Then the access log distinguishes a cleaner from a guest, which matters if something goes missing.

Auto-lock, carefully

Auto-locking after a delay is sensible, and it should trigger from the door contact reporting closed rather than from a timer. A lock that engages while the door is resting against the frame achieves nothing, and one that locks a guest out while they carry bags to the car creates a complaint.

Hotels: the same problem at a different scale

Small hotels and guest houses face the same handover friction with more rooms and a reception desk that may not be staffed overnight. The differences worth noting are three.

Room locks are commercial hardware. A hotel door is used far more heavily than a holiday flat door, and consumer locks will not survive it. Hospitality lock systems are a different product category, generally card or fob based, with a central management system and a portable programmer.

Central management is the point. With twenty rooms, per-room apps are unworkable. What you want is one system that issues a credential at check-in, expires it at check-out, and logs use per room.

The building entrance and the room are separate problems. Late arrivals need to get through the front door as well as their own, which usually means a code or credential on the main entrance with its own expiry.

What the access log is genuinely for

Two legitimate uses. Confirming that a guest arrived, which is useful when someone claims they could not get in. And confirming that the cleaner attended before the next arrival, which resolves a surprising proportion of turnover disputes.

What it is not for is monitoring guests' movements. The times a guest comes and goes are their business, and a host who volunteers that they noticed a guest returned at three in the morning has crossed a line that will appear in a review. Look at the log when there is a specific reason.

Multiple properties and multi-unit buildings

Above a few properties, three things change. Manual code issuing stops being viable, so booking integration becomes necessary rather than optional. Standardising on one lock model across the portfolio saves an enormous amount of support effort, spares and staff confusion. And if properties sit in a shared building, the communal entrance is usually not yours to change — which means guests need both a building entry method and an apartment code, and the building one is frequently the harder problem. Talk to the building manager early; some buildings prohibit short lets outright, and that is a conversation to have before installing anything.

Legal and platform requirements

Two things worth checking rather than assuming.

Local short-let rules vary enormously and change frequently. Several cities require registration, limit letting nights, or impose specific requirements on access and safety. Some require a physical key handover or a named local contact. Check the current position for your city rather than relying on what was true two years ago.

Fire regulations apply to the lock. Any door on an escape route must open freely from the inside without a code, a key or power. A smart lock that requires anything to exit is not acceptable, and for a property let to the public this may be inspected. Check the specific model's inside operation before buying.

A setup that works

1. A smart lock with per-booking codes, a mechanical key cylinder retained, and a key safe as backup.
2. Codes generated from the booking where possible, valid from three hours before to three hours after.
3. Separate recurring credentials for cleaners and maintenance.
4. A door contact, so auto-lock triggers on the door actually being closed.
5. Battery replacement at every deep clean, with spares in the property.
6. The code sent three times, and a phone number that a locked-out guest can actually reach.

The last item is the one people skip. Every access system fails occasionally, and the difference between a bad review and a good one is usually how quickly someone answers the phone.