Hotel PMS Downtime:
How to Build a
Contingency Plan

The property management system is the centre of a hotel's operation. It knows who is in which room, who is arriving, who owes what, which rooms are clean and which key cards should open which doors. When it becomes unavailable — even for an hour — reception staff suddenly have no answers to the most basic questions.

Every PMS will go down at some point. Whether you run an on-premise system or a cloud platform such as Oracle OPERA Cloud, Mews or Protel, the question is not if but how well your team copes when it happens. This guide walks through the common causes of PMS downtime and gives you a step-by-step plan to keep the hotel running until normal service returns.

What Causes PMS Downtime?

"The PMS is down" can mean very different things. Diagnosing which one you are facing determines what you do next.

1. Internet outage

For a cloud PMS, losing the hotel's internet connection is effectively the same as losing the PMS. Leased line faults, roadworks cutting cables, and router or firewall failures are all common culprits. If you have only one connection, you have a single point of failure.

2. Cloud PMS vendor outage

Occasionally the problem is at the vendor's end — a platform incident, a failed update or a problem with their hosting provider. You cannot fix it yourself, so your plan needs to cover operating without the system and knowing who to contact for status updates.

3. Interface failures

Often the PMS itself is fine but an interface has failed: the link to the key-card encoder, the POS, the payment gateway, the call accounting system or the channel manager. The symptoms are partial — rooms can be checked in but keys will not encode, or restaurant bills do not post to rooms — and they are easy to misdiagnose.

4. Power failure

A power cut takes out on-premise servers, network switches, WiFi and front desk PCs at the same time. Without uninterruptible power supplies (UPS), even a brief interruption can corrupt databases or leave equipment needing a manual restart.

5. Ransomware and cyber attacks

A ransomware incident can make the PMS and every connected system unusable for days, not hours. It is the scenario where a downtime plan matters most — and where good, isolated backups make the difference between a bad week and a disaster. We cover the wider threat picture in our guide to cybersecurity threats facing UK hotels.

The Impact on Check-in and Checkout

Without a plan, PMS downtime quickly turns into a queue at reception. Staff cannot see which rooms are clean and vacant, cannot encode keys, cannot take payment against a folio and cannot produce bills. Departing guests may leave without settling, arriving guests may be given rooms that are already occupied, and charges from the bar and restaurant can be lost entirely. There is also a safety dimension: in an emergency, you need to know who is in the building.

Your Step-by-Step PMS Downtime Plan

Step 1: Produce offline reports every shift

The foundation of any downtime plan is information you already hold before the system fails. Schedule your PMS to print or export a set of reports at every shift change (or at least at the start of the night shift), and save copies to an encrypted local device as well as on paper:

• In-house guest list by room, with departure dates
• Today's and tomorrow's arrivals, including special requests and guarantee status
• Departures with current folio balances
• Room status / housekeeping report
• Guest ledger and deposits held
• Group and event lists for the next 48 hours
• An emergency evacuation (fire roll-call) list

These reports contain personal data, so store them securely and destroy old copies under your data protection policy.

Step 2: Prepare manual check-in packs

Keep a sealed downtime box at reception containing pre-printed registration cards, manual folio and charge sheets, a room-move log, a key-issue log, pens and a printed copy of the plan itself. Staff should never need to improvise forms while guests are waiting.

Do not include forms that ask for card numbers. Take payments on payment terminals instead, so card details are never written down — see our PCI DSS v4.0 guide for hotels for why this matters.

Step 3: Plan your key-card encoder fallback

Most hotel lock systems have their own management software alongside the PMS interface, and many can encode keys directly from that software when the PMS link is down. Find out now how your system behaves, make sure duty managers have their own credentials, and print short instructions for cutting a guest key, a duplicate key and a master key manually. If the lock server itself is on-premise, put it on a UPS.

Step 4: Add 4G/5G failover internet

For a cloud PMS, a backup internet connection is the most valuable investment you can make. A firewall or router with automatic failover to a 4G/5G connection (or a second fixed line from a different provider) keeps reception online when the primary line fails. Prioritise the failover link for operational traffic — PMS, payments, key system — rather than guest WiFi, which can quickly consume a mobile connection. Our network and WiFi solutions include designing this kind of resilient connectivity.

Step 5: Protect key equipment with UPS

Put a UPS on the core network switches, firewall, broadband/failover routers, any on-premise servers, the key-card encoder and at least one front desk PC and printer. The aim is to ride through short power cuts and allow a controlled shutdown in longer ones. UPS batteries wear out, so test and replace them on a schedule.

Step 6: Define roles and escalation

Decide in advance who declares "downtime mode", who calls IT support, who calls the PMS vendor, who manages the front desk queue and who updates the general manager. Write the escalation path down with names and phone numbers, and include out-of-hours contacts — outages rarely happen at 10am on a Tuesday.

Step 7: Keep vendor contacts and account details to hand

Keep a printed contact sheet with support numbers, your customer or site IDs, and contract references for your PMS vendor, internet provider, lock system supplier, payment provider, POS supplier and IT support partner. Note where each vendor publishes status updates.

Step 8: Script your guest communication

Give front desk staff a short, calm script so they are not improvising under pressure. For example:

Have a version ready for departing guests explaining how their bill will be finalised, and decide in advance what goodwill gesture, if any, managers can offer during long outages.

Step 9: Recover and reconcile

The outage is not over when the PMS comes back. Before returning to normal operation:

• Enter every manual check-in, checkout and room move into the PMS
• Post all manual charges from the bar, restaurant and other outlets
• Reconcile payment terminal totals against posted payments
• Check room status with housekeeping so no room is double-sold
• Confirm interfaces (keys, POS, payments, channel manager) are working and that availability has resynchronised with OTAs
• Securely file or destroy paper records and hold a short debrief

PMS Downtime Readiness Checklist

Print this table and keep it with your downtime box. Review it at least quarterly.

Testing Your Plan with Drills

A plan nobody has rehearsed will fail on the night. Build testing into the calendar:

• Tabletop exercise: walk the management team through a scenario — "the internet has failed at 6pm on a Friday with 40 arrivals" — and check who does what.
• Live front desk drill: during a quiet period, check in a test guest using only the downtime box, cut a key manually and reconcile afterwards.
• Failover test: unplug the primary internet connection (with your IT partner's agreement) and confirm the PMS and payments stay up.
• Restore test: for on-premise systems, prove that backups can actually be restored.

Include night staff and new starters, and update the plan after every drill or real incident.

Frequently Asked Questions

Does a cloud PMS remove the need for a downtime plan?

No. A cloud PMS removes the need to maintain your own server, but it depends completely on your internet connection and the vendor's platform. You still need offline reports, a backup internet connection and manual procedures.

How often should offline reports be printed?

At least once per shift, and always before the night shift starts, when support is thinnest. Many hotels also export copies automatically to an encrypted local device so they are available even if printers are down.

Can we issue key cards if the PMS is down?

In many cases, yes. Most lock systems can encode keys directly from their own software when the PMS interface is unavailable. Check how your system works, make sure the encoder is on a UPS, and train duty managers on the manual process.

How should we take payments during PMS downtime?

Use your payment terminals directly and record each transaction on a manual folio so it can be posted to the PMS later. Never write card numbers down. Make sure your terminals can operate independently of the PMS, ideally with their own backup connectivity.

How often should we test the plan?

Review the plan and checklist quarterly and run at least one drill per year, plus a refresher whenever you change PMS, lock system, internet provider or key staff.

How GGG Technologies Can Help

GGG Technologies has supported more than 500 hotels since 2010. We help hotels design resilient PMS environments through our PMS integration and PMS and hotel systems services, protect data with disaster recovery and backup, and provide a UK-based 24/7 helpdesk with a 1-hour on-site response in London as part of our 24/7 IT support — so someone is there when the PMS fails at 2am.

For more practical guidance, read our articles on fixing hotel WiFi problems, hotel IT support costs in the UK and how to choose a hotel IT support company. Ready to talk? Request a quote or call +44 20 3642 4958.