The guest lost the keys. A spare set is not yet a plan.

It's 11:10 pm. The guest calls: we can't find the keys, they may have fallen out while we were out.

A spare set may solve the immediate emergency. But it isn't a plan yet. It only works if someone knows where it is, can reach the property and is able to deliver it within a reasonable time.

A real plan for lost keys needs to answer more precise questions first:

• how the guest gets back in;
• who has to step in;
• what information the guest receives;
• which codes can actually be shared;
• what happens to the lost key;
• when access needs to be changed;
• how any related costs are handled.

The point isn't just having a copy. It's designing the whole path before it's needed.

The biggest cost is uncertainty

The material value of a key can be small. The operational impact can be much larger: guests standing outside, tense phone calls, waits, late-night trips, language barriers, no way to reach the right person, worries that the lost key could be traced back to the property.

In that moment the guest mostly needs to know what to do. A clear procedure doesn't remove the incident, but it stops every decision from being made under pressure.

First distinction: keyless access, or a key kept inside a box?

Not every coded access works the same way.

Coded lock or keypad

When the guest enters directly with a PIN and never holds a physical key, the risk of losing the set is greatly reduced.

Other issues can still occur: a mistyped code, a flat battery, a keypad fault, a PIN not yet active, a jammed door or lock, an unreachable phone. A backup procedure is still needed.

When the system supports it, a different code for each stay improves access control compared to a PIN shared for months across many guests. This is explored further in <a href="/blog/door-code-for-each-stay-guest-trust">why to use a different door code for each stay</a>.

Lockbox holding a physical key

A combination box doesn't necessarily prevent losing the key. If the guest opens the box, takes the key and carries it around, that key can still be lost.

A lockbox can still be useful in two ways: as a regular delivery system, or as a controlled place to store an emergency backup. The two uses shouldn't be confused.

The backup should reduce dependence on one single person

If the property uses physical keys, a spare set remains useful. What matters is deciding in advance where it lives, who can authorise its use, who knows the code, how it's collected, when it's put back and when the combination should be changed.

A key safe can reduce the need for the owner to reach the property in person. It should still be installed in an allowed spot, be sufficiently protected, be checked regularly, be genuinely accessible to the authorised guest and, where possible, be kept separate from any obvious sign of which unit it belongs to.

Before installing anything, it's prudent to check building rules, the property's own conditions and any regulations that apply to the address.

The code for the emergency backup shouldn't be published in the general guide or handed out to every guest in advance. It should only be shared when the agreed procedure is triggered.

A different case is when the lockbox is the regular entry system: there the code naturally has to be delivered to the authorised guest, through an appropriate channel and time window.

Instructions should say what to do, not reveal how to enter

There's no need to describe the whole security architecture in the guest guide. A simple pointer is enough.

Lost the keys or can't get in? Contact the property on this number or through this channel. We'll walk you through the procedure set up for your stay.

The wording has to reflect the service that is actually available. You shouldn't write "we always answer, even at night" unless there really is round-the-clock coverage.

It's better to communicate precisely the hours of the main contact, the number to use, an alternative channel, the out-of-hours procedure, any local backup and realistic response times. Reassurance is only useful when it matches a real setup.

The plan continues after the guest is back inside

Handing over the spare doesn't always close the incident. Once access is restored it's worth considering where the key may have been lost, whether it carries labels or references to the property, whether it opens only the unit or also the building door, garage and common areas, whether the cylinder should be swapped, whether a digital code should be deactivated, whether the lockbox combination should be changed and when to restore the backup.

Not every lost key automatically requires replacing the lock. But the decision shouldn't be improvised.

The property should also have a clear policy on any costs. It's better to state upfront, transparently and in line with the rules that apply: the possible cost of duplication, a technician visit, replacing the cylinder when needed, and losing special keys, remotes or badges.

A penalty decided after the fact easily leads to disputes. A rule known before check-in is easier to handle, and always needs to be assessed against the platform's own terms.

A minimal plan when using physical keys

A basic setup can include a main set handed to the guest, a spare kept in a controlled place, a person who can authorise its use, contact instructions accessible from a phone, a procedure for changing combinations or locks, and a transparent rule about any costs.

The backup doesn't need to be right by the door. It should sit at the point that best balances security, accessibility and how the property is actually run. For some properties that's an authorised lockbox; for others, a local collaborator, a reception, an appointed neighbour or a service partner.

A minimal plan when using codes

Digital access should include a stay-specific code when the system supports it, a validity window aligned with arrival and departure, a check before arrival, an alternative procedure in case of failure, a reachable contact and deactivation of the code at the end of the intended period.

The fact that there is no physical key to lose doesn't mean access can't fail. A plan B is still needed.

Where StayFast fits into the flow

In StayFast the split between public information and information reserved to the stay is essential.

In the public guide

The public guide can carry the channel to use when something goes wrong, the assistance hours, general instructions, non-sensitive pointers and the procedure to follow if the guest can't get in.

It shouldn't carry door PINs, codes for an emergency box, unit credentials or any information that would allow physical access to the property.

In the personal Stay Hub

On the Fast plan, the Stay Hub can tie information to a specific recognised stay. Sensitive unit data, when configured, is shown only to the correct stay, during the useful window of the stay, within the access window in place and on the recognised device.

If the guest forgets a PIN that has already been made available, they can look it up in their own Stay Hub while the access window is open. That reduces the need to rewrite codes inside messages, without turning the public guide into a store of sensitive information.

Contact and Concierge shouldn't replace access controls

When the direct contact channel is active, the guest can write to the property through the intended path. The request can arrive linked to the stay, making it easier to see who is writing, for which booking, which unit is involved and which phase of the stay they're in.

The Concierge AI can help with non-sensitive procedural questions, based only on information confirmed by the property. It can explain, for example, where to find the Arrival section, which number to call, what the agreed procedure is and what the assistance hours are.

It shouldn't share door PINs, backup codes or other access credentials on its own.

The guide is especially useful when the owner isn't there

For remote hosts, the guide doesn't replace the operational contact. It does, however, stop the guest from starting from scratch: they can already know which channel to use, who to contact, what information to have ready, what not to try and which path is going to be triggered.

It's one of the cases where the guide really becomes a form of organised presence. It's the same principle explored in <a href="/blog/absent-host-guest-guide-is-your-presence">The host who isn't there: why the guest guide is your presence</a>.

A quick check before the next stay

To pressure-test the plan, just imagine the scenario: it's 11:10 pm, the guest is standing outside the door, I can't reach the property. Then run through:

• does the guest know who to contact?
• is the number correct?
• does someone actually answer at that hour?
• is there an alternative?
• is the backup accessible?
• has the box been tested recently?
• is the code still the one on file?
• is the digital PIN active?
• is it clear what to do the next day?
• have the financial consequences already been defined?

Every uncertain answer points to a part of the plan that still needs work.

The spare set is a tool, not the strategy

A backup can save the evening. The strategy is broader: reduce the risk, separate public information from sensitive codes, provide alternative access, communicate a realistic path, act on security after a loss and avoid improvised decisions and costs.

Lost keys can't always be prevented. The confusion that follows, however, can be reduced well before the guest picks up the phone.