Check-in is the moment a booking turns into a stay — and the moment most things can go wrong. The train is late, the code does not work, the front door sticks. What takes two minutes on a good day costs an entire evening, an 11pm phone call and a review that drags your average down for months. Self check-in does not fix this on its own. It fixes it when three things are right: the hardware, the instructions, and the plan for when something fails.

Why check-in is the most expensive moment in operations

In-person handovers consume time you cannot schedule. A guest announced for 6pm arrives at 9:40pm — and someone has to stay available in between. With one unit that is manageable. From the third unit onwards arrivals collide regularly, and at that point check-in decides whether your operation scales or whether it owns your evenings.

The second, often overlooked point: self check-in is a selling argument. Late arrivals, air travellers and business guests actively filter for it. Offering only a 4pm-to-7pm window loses you bookings you will never even see.

The three ways into the apartment

  • Key safe. Cheap, no power, no internet, works during a blackout. The downside: the code can only be changed manually, and a box on the façade is not always permitted or welcome. For single properties and for getting started, still an honest solution.
  • Smart lock with keypad. The standard for professional operations: every guest gets their own code that activates at check-in and expires at check-out. No keys get lost, no handover needs coordinating.
  • In-person handover. Not abolished, but used deliberately: for long stays, for complex properties, or when the building genuinely needs an introduction. As a conscious choice it is powerful — as your only option it is a bottleneck.

Whichever route you take, check the building rules and, where relevant, the owners' association regulations before you modify anything on a shared door. Removing an installation after the fact costs more than agreeing on it beforehand.

Issuing codes properly

One fixed code for all guests is convenient and the single most common weak point in any operation. It spreads into chat histories, into old booking confirmations, and eventually to people who checked out long ago. The rule is: one code per booking, time-limited.

A validity window slightly more generous than your official times works well — say from three hours before check-in until midday on departure day. That absorbs early arrivals and slow departures without anyone having to intervene. Keep separate codes for cleaning, maintenance and owners as well. If a code is compromised, you want to know which one.

The instructions matter more than the hardware

Most failed check-ins do not fail at the lock, they fail at the description. "Second courtyard, staircase C" is unambiguous to you and meaningless to a guest from Madrid at 10pm in the rain.

What good instructions contain: a complete address including floor and apartment number, two or three photos of the actual route (building entrance, staircase, apartment door), the code on its own line so it can be copied, one sentence on how the lock behaves — whether a button must be pressed after the code or the handle turned — and the parking situation. Send it the day before arrival, not at the time of booking. Nobody ever finds a message from three months ago.

If you host international guests, the instructions belong in the guest's language. Automated multilingual guest communication — in our case through our own software, CENTCOM — is not a luxury for that reason; it is what prevents the late-night calls you would otherwise take.

The plan for when it fails

Technology fails. Batteries die, the stairwell wifi drops, a guest mistypes the code five times and the lock blocks. What matters is not whether this happens but how long it takes until someone is inside.

Three things should be in place: a physical spare key in a second, documented location; a phone number that is genuinely answered in the evening and that appears in the arrival message; and a fixed battery replacement cycle rather than reacting to low-battery warnings. Swapping batteries every six months costs a few euros. A locksmith on a Sunday evening costs many times that — plus the review.

What to measure

Two numbers are enough to start. How many arrivals trigger a question? And how many of those questions come in after 8pm? If more than one in ten arrivals generates a message, the cause is almost always the directions, not the guest. Watching that rate fall is the most honest measure that your check-in is genuinely automated — and not just designed to look that way.