When the System Goes Down at Checkin

There is a specific kind of quiet that falls over a front desk when the screen stops responding. You tap a key, then another, then you check the guest's face to see if they noticed yet. Behind you the arrivals are stacking up, the flight that landed an hour ago is now walking through the door in a group, and the one system that tells you who they are and where to put them has gone dark. I have felt that quiet on the overnight and on a busy afternoon, and I can tell you the outage itself is never the real problem. The real problem is whether you prepared for it before it happened.

A hotel PMS outage is one of the cleanest tests of a desk there is. Everything you normally do through the system, confirming a reservation, seeing which rooms are clean, cutting a key, posting a folio, has to happen another way, and it has to happen while a lobby full of tired travelers watches you figure it out. The good news is that the whole thing runs on a short list of habits and a little paper. The desks that panic are the ones that never built the backup. The desks that stay calm already had it in a drawer.

What actually breaks when the PMS dies

It helps to be precise about what you lose, because it is more than a slow computer. When the property management system goes down, the front desk loses its live picture of the whole house at once. You lose the arrivals list, so you no longer know who is expected. You lose room status, so you cannot see at a glance which rooms are clean and vacant and which are still being turned. You lose the folio, so charges are not posting. And on most properties you lose the key encoder, because the machine that cuts keys talks to the same system.

Put together, that is a desk flying blind. You cannot verify a reservation, you cannot safely assign a room, and you cannot let a guest into it. Each of those is solvable on paper, but only if you have the raw material to work from. That raw material is the thing you should be printing before you ever need it, and it is the single point this whole article turns on.

The one habit that saves the night

Print the arrivals report. Print it at the start of every shift, and print it again before any window you know carries risk, a big arrival block, a maintenance push, a stormy afternoon. A current paper copy of who is coming and what rooms are sold is the difference between a manageable outage and a stalled lobby. If the system dies with something on paper, you have your map. If it dies with nothing, you are reconstructing the night from memory in front of a growing line.

An outage does not test your system. It tests whether you printed the report while the system still worked.

Alongside the arrivals report, you want a known house count, an honest number of how many rooms you truly have available, and a sense of room status as of the last time the system was alive. The deeper mechanics of that paper backup, the registration cards, the key stock, the running sheets, are worth building out in full ahead of time, which is exactly what the manual checkin backup plan is for. Do that work on a slow morning, not during the crisis.

How do you check a guest in with no system?

Once the screen is dark and the arrivals report is in your hand, the process is slower but not complicated. It is a loop, and you run the same loop for every guest until the system returns.

1. Confirm the reservation on paperFind the guest on the printed arrivals report. This is your proof the room is theirs and at what rate.
2. Assign a room you can verifyPick a room you know is clean and vacant from your last-known status, never one you are guessing about. A guess is how you send a family into an occupied room.
3. Capture details and payment by handA registration card takes the name, contact, and a card authorization so nothing is lost when charges post later.
4. Issue a keyFrom a backup encoder if you have one, or from pre-cut stock, or by walking the guest up if it comes to that.
5. Log it on a running sheetWrite down every room the moment you assign it, so the next guest cannot be handed the same one.

That last step is the quiet hero of the whole process. Without the system watching for collisions, the only thing standing between two guests and the same room is your running sheet. Treat it like the truth, because for the length of the outage, it is. I keep the sheet in one place, in one hand, and I write on it before I hand over a single key, never after. The half-second it takes to log a room is the cheapest insurance you will buy all shift, and the one shortcut that seems to save time is the one that manufactures the double-sold room you will spend an hour untangling later.

Protect the house count above all

The single most damaging mistake during an outage is double-selling a room, because it turns a technical problem into a service failure with a real person standing in it. Every room you assign comes off your available count. Every walkin you accept, and you should be cautious about walkins while blind, has to be checked against what you truly have left. If you lose track of the count, you can talk yourself into selling a room that is not there, and now you are managing an oversell you created. Guard the number. When in doubt, undersell.

Keeping the line moving while you work slow

A manual checkin takes longer than a normal one, and there is no way around that. What you can control is how the wait feels. The first move is honesty. Tell arriving guests plainly that the system is briefly down, that checkin is a little slower right now, and that you appreciate their patience. Most people are remarkably understanding when you are straight with them. What they do not forgive is watching a desk fall apart in silence while they guess at what is wrong.

The second move is flow. If you have a second person, split the work: one running the manual checkin loop, one managing the line, answering questions, and keeping the room from getting tense. A stalled line is where an outage becomes a mood, and a whole lobby of frustrated guests is a much harder thing to recover than a slow one. Managing the room and not just the guest in front of you is a discipline of its own, and it carries straight over from the outage to any bad night, which is why it belongs with everything on keeping the lobby calm in a crisis.

The third move is pace. Slow and steady beats fast and frantic. A frantic desk makes errors, and an error during an outage, a double-sold room, a missed authorization, costs you far more time than the few seconds you saved rushing. Set a calm rhythm and hold it. The guests will match the pace you set, so set a good one.

What not to do while blind

There are a few reflexes worth naming, because they are the ones that turn a recoverable outage into a mess that follows you into the next shift.

Every row trades a few seconds now against an hour of untangling later, and the discipline is choosing the slower move on purpose.

The prepared desk versus the unprepared one

The same outage produces two completely different nights, and the fork is decided weeks earlier. It is worth seeing the contrast side by side, because it is the whole argument for the paper habit.

• The prepared desk pulls a fresh arrivals report and house count from the drawer, opens a running sheet, and runs the manual loop as a slightly slow hour. Reconciliation afterward is clean data entry.
• The unprepared desk has nothing on paper, so it reconstructs the night from memory in front of a growing line, guesses at room status, and hands out collisions. Reconciliation afterward is detective work.

When the system comes back

The outage is not over when the screen wakes up. Now you have a stack of registration cards and a running sheet full of assignments that the system knows nothing about, and your job is to reconcile them in before anything else goes out of sync. Work through the sheet room by room: check in each guest you handled manually, post the charges you captured, and confirm the room status matches what you actually did on the floor. Until that reconciliation is done, the system's picture of the house is wrong, and acting on a wrong picture is how you create the next problem.

This is also the moment the running sheet pays you back. A clean log turns reconciliation into steady data entry. A messy or missing one turns it into detective work, cross-checking keys and folios and hoping you did not miss a room. The care you took during the outage is repaid, or punished, right here.

It is also worth pulling in help before you reconcile if you can. An outage that started at the top of an arrival wave usually leaves a real backlog, and a second set of hands, a manager, a colleague coming on shift, makes the catch-up far faster and far less error-prone. Split the stack, have one person enter while another confirms room status against what actually happened on the floor, and check each other's work as you go. Reconciliation done carefully once beats reconciliation done fast and wrong, because a mistake entered into the system now becomes tomorrow's phantom room or missed charge.

Communication matters here too, in both directions. Housekeeping needs to know which rooms you handed out during the blind window so their board matches reality, and the incoming shift needs a clear handover of anything still unreconciled so they are not surprised by a folio that never posted. A quiet, thorough closeout is what keeps an outage from leaving a tail of small problems for days afterward. The system coming back is the halfway point, not the finish line.

An outage is fundamentally a service recovery situation with a technical cause, and the same order of operations applies: acknowledge the delay to the guest, own it without blaming the vendor, fix it with a steady manual process, and follow up so the record is clean. If you want the fuller frame around that, it lives in the service recovery field guide for the front desk. The tools change when the system dies, but the posture does not.

The outage is a preparation test in disguise

Here is what I have come to believe after enough dark screens: nobody rises to the occasion during a PMS outage. You fall back to the preparation you did before it. The desk with a fresh arrivals report, a known house count, registration cards in the drawer, and a running sheet ready to go handles an outage as a slow hour. The desk without those handles it as a crisis, because it is inventing the whole backup live while the lobby watches. Same outage, two completely different nights, and the only variable is what you did on a quiet morning weeks earlier.

So the real lesson of the system going down is not about the moment it goes down at all. It is about the small, unglamorous habit of printing the report and keeping the paper ready when everything is working fine and there is no reason to think you will need it. That habit feels like a waste right up until the one shift it saves you, and on that shift it is the whole difference between a desk that keeps its calm and one that loses the lobby. Build the backup before the night that needs it. The system will go down eventually. Whether that becomes a story you tell calmly is decided long before the screen ever freezes.