Wi-Fi Access Tied to Check-in and Check-out: Internet in Step with the Guest Stay

In short: what is Wi-Fi access tied to check-in and check-out?

Wi-Fi access tied to check-in and check-out means that a hotel guest's right to internet access is automatically synchronised with their stay. When the guest checks in at reception, Wi-Fi access becomes available; it remains valid throughout the stay; and when check-out is completed or the departure date arrives, it ends according to the rules set by the hotel. This setup requires reliable, up-to-date data exchange between the property management system (PMS) and the hotspot system.

Why Wi-Fi in step with the stay?

In the traditional approach, Wi-Fi access is independent of the stay. Reception gives each guest a code, or the whole hotel uses the same password. In that case:

• Guests who have checked out can keep connecting in front of the hotel, in the car park or at a nearby café.
• When a guest's stay is extended, the code expires and the guest has to come to reception for a new one.
• Code durations are calculated manually, leading to errors and inconsistencies.
• Access records do not match stay information.

In a setup that is in step with the stay, the Wi-Fi entitlement is created, updated and ended together with the guest's hotel record. This approach has four main benefits:

1. Guest experience: The guest authenticates only once for the whole stay and does not need to return to reception for extensions or room changes.
2. Operational efficiency: Reception does not perform separate Wi-Fi tasks; generating codes, setting durations and closing access are automated.
3. Security: People whose stay has ended are prevented from using the network, which remains open only to actual guests.
4. Consistent records: Access records align with stay periods, which simplifies technical investigations and regulatory processes.

How does it work technically?

Wi-Fi synchronised with the stay can be built with two main methods:

Query-based method

When the guest enters their room number and surname on the portal, the hotspot system sends an instant query to the PMS. The PMS returns whether the stay is active and the departure date. The hotspot sets the session duration according to this departure date. To detect check-out, the hotspot can periodically re-query the PMS about active sessions.

Event-based method

The PMS sends a notification (webhook or interface message) to the hotspot system the moment events such as check-in, check-out, a room change or a stay extension occur. The hotspot opens, updates or closes access based on this notification. This method gives more immediate results but requires the PMS to support such notifications.

Many projects use both methods together: a query at login, followed by event notifications and periodic checks.

Scenarios that must be designed

Real hotel operations are far more complex than "checked in – stayed – checked out". The following scenarios should be defined one by one at the start of the project:

Early arrival

The guest arrives in the morning, but the room will be ready in the afternoon. Because check-in has not been completed, the PMS may not show an active stay. Possible solutions:

• Limited access before check-in for guests whose reservation is for that day.
• Short-term guest access for the lobby (one-click or voucher).
• Making the stay active early through a pre-check-in process.

Late departure and waiting for a transfer

The guest has checked out but the airport transfer is a few hours later. If internet access is cut off during this time, guest satisfaction suffers. Possible solutions:

• A grace period after check-out (for example two hours).
• Short-term access valid in the lobby and common areas.
• Automatic extension of access for guests who pay for late check-out.

Stay extension

When a guest extends their stay by two days, the departure date in the PMS changes. The hotspot session must detect this change and extend automatically. Event-based notifications or periodic synchronisation solve this scenario.

Early departure

When a guest leaves earlier than planned, access should close together with check-out. In a query-based setup, this is caught by periodic checks of active sessions.

Room change

When a guest moves to another room, sessions opened with the old room number must either be transferred to the new record or closed, with the guest logging in again with the new details. Otherwise there may be a conflict with the device limit of the new guest who moves into the old room.

Cancellation and no-show

For records that were checked in but later cancelled, access must be ended immediately.

Same-day departure and arrival

A new guest may move in during the afternoon to a room vacated that morning. The previous guest's sessions must be completely closed for the new guest to connect without problems.

Long stays

For guests staying for weeks or months (long-term stays, staff accommodation, serviced apartments), session durations, device management and periodic re-authentication policies should be assessed separately.

Example timeline: one guest's stay

To see how synchronised Wi-Fi works in practice, let's follow a four-night stay step by step:

• Day 1, 11:00: The guest arrives early; the room is not ready yet. Because the reservation is for that day, they use two hours of short-term access in the lobby.
• Day 1, 14:00: Check-in is completed and the stay becomes active in the PMS. The guest connects in the room with room number and surname; access opens and remains valid until the departure date.
• Day 2: The guest also connects a laptop and a tablet. The per-room device limit applies.
• Day 3: The guest wants to move to a room with a view. Reception records the room change in the PMS; the hotspot transfers the old sessions to the new room record, and the old room is cleared for the next guest.
• Day 4: The guest extends the stay by one night. The departure date in the PMS is updated, and the hotspot session is automatically extended by a day.
• Day 6, 12:00: Check-out is completed. The two-hour grace period defined by the hotel begins, and the guest keeps using the internet in the lobby while waiting for the transfer.
• Day 6, 14:00: The grace period ends and all sessions close. Access records match the stay period exactly.

Throughout this process the guest authenticated only once, and reception did not perform a single additional Wi-Fi task.

Paid packages and posting to the folio

Some hotels offer high-speed premium packages alongside free basic access. In a setup integrated with the stay, when the guest buys a premium package on the portal, the package price can be added to the room folio in the PMS and collected at check-out with other charges. This feature depends on whether the PMS accepts folio postings from external systems and on the scope of the integration. For paid packages, clearly showing pricing and terms of use on the portal prevents payment disputes with guests.

What happens during a connection outage?

The connection between the PMS and the hotspot may be interrupted for many reasons: server maintenance, network failure, a licensing issue or a software update. Behaviour for this situation should be defined in advance:

• Existing sessions: Sessions active during the outage should continue according to the last known departure date.
• New logins: When the PMS cannot be reached, an alternative method (a voucher from reception, temporary SMS verification) should take over for new guests.
• Synchronisation: When the connection is restored, check-in and check-out events that occurred during the outage should be transferred to the hotspot system.
• Alerting: The technical team should be notified automatically of the integration outage.

Operating procedures

However well the automation is designed, reception staff need to be able to perform some manual actions:

• Viewing a specific guest's sessions in the panel and closing them manually when needed.
• Reviewing a daily report of sessions still open after check-out.
• Defining exceptional access for early arrival or late departure.
• An alternative procedure to apply when the integration is not working.
• Steps to check when a guest says "I can't connect" (surname spelling, room number, device limit, stay status).

These procedures should be written down and always included in training for new seasonal staff. Recording every manual intervention by reception in the panel, along with who made it and when, is also important for internal audit and any later investigation.

Reporting and control

Regular checks should be made to ensure that the check-in/check-out integration is working correctly:

• Daily check: Are there guests who have checked out but still have active sessions?
• Weekly check: Are there recurring problems in the integration error logs?
• Monthly check: How are Wi-Fi-related guest complaints and the number of reception interventions changing?

Checklist

Common mistakes

Frequently asked questions