When the internet goes down: a front desk checklist for cloud-based hotels

A hotel internet outage plan is a written procedure for running the front desk on paper while the browser-based system is unreachable, then reconciling every manual record afterwards. It has three parts: preparation (a second line, nightly printed lists, pre-numbered forms), the outage itself (one log, one person in charge), and a clean catch-up.

The screen freezes halfway through a check-in. The guest is at the desk, the room is clean, the key is blank, and the system that holds the room, the rate and the bill cannot be reached. This article walks through what stops, what to prepare in advance, how to run the desk during the outage, and how to catch up afterwards without double postings or missing records.

What stops when the internet stops?#

In a browser-based system the screen is a window onto a server somewhere else, so with no connection the desk can neither read nor write. What stops is not one feature but the shared record of rooms, guests and money.

The room inventory is the first loss. The only place that says which room is free, which is occupied and which is out of order becomes unreadable, and the desk starts working from memory. Key card encoders are usually driven by the same system, so no connection means no new key unless the encoder has a standalone mode that someone has actually tested.

Posting stops at the moment of the charge. Room, restaurant, minibar and spa all write into the same guest bill, and none of them can be written. Rates and availability stop flowing to the channels, so the risk moves off the desk and onto the booking sites, where a room can still be sold while the hotel cannot see it. Night audit cannot close the business day, which delays the date-based reports and postings that follow it.

Compliance steps that run through the system pause, but the duty behind them does not. Identity notifications and fiscal documents still have to be produced for the stays that happened. What still works is the building, the rooms, the guests, the staff, a printer that does not need the network, and paper.

What should be ready before the connection drops?#

Preparation is cheap and boring, and it is the only part you control. Four things matter: a second connection, a nightly printed list, pre-numbered paper, and a named person for each job.

A second line from a different provider, ideally entering the building by a different physical path, is the first item. Add a charged mobile router as a third option, with a known data limit. Test the failover on a schedule: unplug the primary line at a quiet hour, time how long the backup takes, and write down which devices do not come back by themselves, usually the printer, the key encoder and the card terminal.

Print the in-house list at a fixed point every night, after the business day closes: arrivals, room numbers, departure dates, balances, groups, special requests and VIP notes. Print a fresh copy at every shift handover, the same way you would for any front desk shift handover checklist. Keep pre-numbered charge slips and registration forms at the desk, with a log of which numbers were issued to which staff member.

Put a contact sheet on paper: internet provider, IT provider, PMS vendor, channel manager, key card vendor, e-invoice integrator and accountant, with names and mobile numbers rather than a shared inbox. Name the roles in advance: who calls the provider, who owns the paper log, who decides to stop selling, and who speaks to guests.

During the outage: how do you check in a guest and take a payment?#

Run the desk from one numbered paper log and one person's decisions. The goal is not to look normal; it is to leave a record you can post once, correctly, when the system returns.

One log, one writer: every arrival, key, charge and message goes into a single numbered sequence with a time and initials. Two parallel notebooks are how double postings begin. Check-in means completing the paper registration form, assigning the room from the printed list, and marking it as taken on a paper floor plan so a second terminal does not sell it again.

If the encoder needs the system, switch to the mechanical or master key procedure and record every key handed out against a room and a name. Charges go on a pre-numbered slip with room, item, amount, time and initials, signed by the guest, with a copy given to the guest at the moment of the charge. For payments, use a card terminal on its own connection where you have one, and record cash on a separate cash sheet that references the slip number, not a running total.

Stop-sell deserves its own decision. With no visibility you can sell a room twice or sell it at a stale rate, so decide in advance whether the answer is to reduce availability through the channel manager, ask the provider to close channels, or accept the risk with a manual block, the same trade-off behind any stop sale decision. Tell in-house guests what is down: the guest app and the online offers will not answer, so the front desk is the channel, and a short written note saves repeated explanations.

Do identity notifications and invoices still have to go out?#

The connection is a tool, not the duty. Identity notifications and fiscal documents still have to be produced for the stays that happened, so record everything on paper at the moment of check-in and complete it when the system returns.

Capture at check-in the same identity data you would type into the system, following your normal KBS check-in routine, and note the actual time the guest arrived, because that is the fact you will need later. Timing is set by the authority and interpreted by your provider and your adviser; ask both in advance and write the answer into the procedure. Fiscal documents are issued through a licensed integrator, so if the integrator is unreachable, prepare the document and send it when it is back, and keep a person reviewing e-invoices before they go out.

Never skip, always record. The failure that hurts is not a late document but a missing one, or a stay with no identity record at all. Tell the accountant on the same day, with the paper slips in hand, so the documents are issued in the right period and nothing is reconstructed from memory weeks later. Paper forms carry personal data, so lock them, keep them only as long as your retention rule allows and destroy them on schedule.

How do you catch up afterwards without double postings?#

Catch-up is a reconciliation, not a typing exercise. Every paper slip should be posted once, against a reference, and then checked against what the system thinks happened.

Post from the slips in number order and write the slip number into the system's reference field, so a second person can see at a glance that it is already done. Then compare the paper log against the system's arrivals, departures and postings, looking for the two failure modes: a slip posted twice and a slip never posted.

Channels need the same treatment. List every reservation that arrived by phone or email during the outage, compare it with what the channels sold, and check for overbookings and for rates that were pushed stale. Room status matters too: housekeeping worked on paper, so confirm clean, occupied and out-of-order rooms before the next check-in wave rather than trusting the screen. If night audit did not close, close the business day in order instead of jumping dates, or the reports that follow will not line up.

Finish with a one-page incident note: when it started, when it ended, what was done on paper, what broke, what to change. It is the only way the checklist gets better.

What should you ask your PMS vendor about offline behavior?#

Ask before you sign, and ask again every year, because offline behavior is a product decision the vendor has already made, and it is worth asking directly.

Ask what the desk can see and do with no connection, and accept an honest "nothing, plan for paper" as a good answer. Ask whether the key card encoder works without the system, and ask for the standalone procedure in writing. Ask how manual entries get into the system and whether there is a reference field and a reconciliation report. Ask what happens to rates and availability on the channels when the system cannot be reached, and whether you can export the in-house list yourself at any time rather than waiting for a support ticket. Ask for the escalation path and response time written into the contract, and how planned maintenance is announced. Then ask the same questions of the channel manager and the e-invoice integrator, because the outage is shared across all three.

What to do next#

Print tonight's in-house list after the business day closes, then run an unplug test at a quiet hour and write down what stops and who does what. That single exercise, one page and fifteen minutes, tells you more about your hotel's outage readiness than any vendor document. From there, build the three phases into a written procedure: prepare the connection, the paper and the roles; run the outage from one numbered log with one decision-maker; then reconcile every slip once and check the channels and room status before the next check-in wave.