A booking-based access code can make self check-in easier, but the useful work happens around the code: confirming the right booking, setting the access period, communicating clearly and handling changes.
For a holiday let or serviced apartment, treat smart access as a guest journey and an operational responsibility. Airbnb’s self-check-in guidance provides context for independent arrivals. The actual lock, connection and access rules still need to fit your property.
Define the access window
Agree when guest access begins and ends. Use the property’s local timezone and make the same times visible in booking information and guest messages. Include how early check-in or late checkout is approved rather than leaving exceptions to informal messages.
An example policy could be “from the approved check-in time until the approved checkout time”. That wording is not a device specification: the selected lock and integration must support and correctly apply the policy.
Separate guest access from team access
Guests, cleaners and maintenance providers may need access at different times. Decide who can authorise each type and who checks that access is removed when it is no longer required. Avoid treating one shared code as the answer to every visit.
Keep the operational record clear enough for the responsible person to understand what is scheduled. Do not publish access codes in public signage, web pages or general marketing examples. Share guest instructions through the agreed private communication route.
Test booking changes, not just a normal arrival
Before relying on an automation, work through a short set of example bookings:
- A normal stay with the agreed arrival and departure times.
- A changed check-in date before the guest arrives.
- A cancelled booking.
- An approved extension or late checkout.
- A booking that has missing or inconsistent information.
- A situation where the platform or device connection is unavailable.
For each case, record the expected access state, guest communication and staff action. Confirm who reviews failures or exceptions. A successful first code does not demonstrate how all those cases will behave.
Agree the fallback before it is needed
Ask the lock supplier and installer about the device’s power, connection requirements and supported fallback arrangements. Identify who can help a guest locally and how they will receive the relevant task.
Use the manufacturer’s instructions for maintenance and access recovery. Do not assume that every smart lock works offline, uses the same battery arrangement or supports the same booking platforms. Any change to a door or lock should be assessed for that installation’s requirements by the appropriate provider.
Make the physical arrival clear
A valid code is only useful if the guest finds the correct entrance. Check the property number, parking directions and instructions for any shared areas. A simple property identification sign or wayfinding notice can support the digital instructions.
Keep the instructions short and ordered. Tell the guest which door to use and which action comes next, using the actual device’s approved guidance. Review photos or messages when the entrance changes.
Connect checkout to the next tasks
The end of a guest access window is one part of property turnaround. Cleaning, laundry, maintenance checks and readiness confirmation still need owners and status updates. Link those responsibilities to the stay without assuming that a departed guest means the room is already ready.
Our changeover checklist helps organise that handover. Signaki’s Guest Experience service brings booking-based smart access and property tasks into a connected workflow, with device compatibility and local arrangements confirmed during setup.
Tell us about your current booking system and properties to discuss the right scope.