When the system goes down: an IT contingency plan for hotels in 2026

Why contingency has become more important

When the PMS is unavailable, the front desk cannot stand still waiting for IT to fix the problem. The hotel keeps receiving guests, checking guests out, charging for consumption, issuing documents and handling bookings. The procedure for carrying on operating has to exist before the failure.

And the external dependencies have grown. Since 20 April 2026, the FNRH (Ficha Nacional de Registro de Hóspedes, Brazil's national guest registration form) is submitted exclusively through the Ministry of Tourism's digital platform, either through an integrated PMS or through the government portal. Issuing the NFS-e (Brazil's electronic service invoice) has also changed significantly with the expansion of the national standard. Pix (Brazil's instant payment system) has become one of the main payment methods, and much of the PMS, channel manager and door lock software runs in the cloud. All of this depends on power, the internet and third-party services working.

And failures happen. In the early hours of 14 October 2025, a blackout hit every Brazilian state and the Federal District, with power cuts lasting from a few minutes to about an hour, depending on the region. Beyond blackouts, there are carrier outages, software supplier failures and security incidents such as ransomware. The practical question is: when a system goes down, does the front desk know exactly how to keep the operation going?

What stops when each system fails

The table is not exhaustive: phones, access control and the food and beverage system also belong in the plan, depending on the operation. A UPS is not a generator. The useful question is how long each critical piece of equipment keeps working and what happens when that runtime runs out. That is why these dependencies need to be mapped before the failure.

What a contingency plan needs to include

A contingency plan does not need to be a hundred-page document. It needs to fit at the front desk and be known by whoever works the night shift. In practice, it covers:

• An owner and a chain of decision. Who declares that the hotel has gone into contingency, who informs management and who decides when to return to normal, including at night and at weekends.
• Critical systems, dependencies and priorities. List the systems that support the operation and what each one depends on to work: power, internet, network, DNS, user logins, integrations and supplier services. A cloud PMS, for example, depends on the internet, the firewall, user access and the supplier itself; the POS depends on the network, the internet and the payment provider. For each system, define how long the hotel can do without it (the maximum downtime, or RTO) and how much data it can lose (the acceptable data loss, or RPO). A PMS may need to be recovered within a few hours, while a less critical administrative system can tolerate a longer period. This guides the order of recovery and investments such as the second link or the UPS.
• Manual procedures ready to use. A contingency kit at the front desk: registration forms, the day's reports printed or saved offline, payment and guarantee rules and short scripts for each type of failure.
• Reconciliation when the system comes back. Check-ins, consumption, payments, room moves, cancellations, new bookings and key cards issued during the failure need to be checked and entered into the system. The plan defines who does that check and how to avoid duplicate entries.
• Communication. Who informs guests, management, the corporate office, OTAs, agencies, suppliers and emergency contacts, and through which channel. Keep the critical contacts outside the systems that can go down as well: if the contact list is only in cloud email and the email is down, the hotel has no list.
• Supplier contacts and SLAs. Who to call for each system, with up-to-date phone numbers, contract numbers and the contracted response time. Also confirm whether support covers the early hours and weekends, because not every contract does. See who answers for what between the hotel and its suppliers.
• Testing. A simulated exercise at least once a year and whenever there is a significant change of system, supplier or process, such as a new PMS or internet carrier. Without a test, the hotel does not know whether the planned contacts, procedures and resources work.

Digital FNRH: the point that still has no official answer

The Ministry of Tourism has published a user manual and an FAQ page (in Portuguese) on the digital FNRH. The official documentation we consulted does not set out a detailed operating procedure for when the internet, the PMS or the government platform itself is unavailable. At the same time, the FAQ makes clear that legal responsibility for the registration rests entirely with the accommodation provider.

Until there is official guidance, the hotel needs a procedure of its own:

• Ask the PMS supplier what happens to the forms when the integration with the government fails: are they queued and resent automatically, or does someone need to resend them manually?
• Define how to record guest data during the failure: only what is necessary, kept in a controlled place and disposed of once entered into the system, in line with the LGPD (Brazil's data protection law).
• Document the start and end time of the outage and its cause, to justify any delay.
• Confirm with the supplier and with the Ministry of Tourism, or through your hotel association, how to regularise the records afterwards.

Technical failure or attack?

Not every outage is accidental. If files appear encrypted, a ransom message shows up or several systems stop at once without a clear cause, the hotel may be facing ransomware. In that case, the procedure is different: do not restart, reformat or reconnect suspect equipment on your own, because that can erase evidence and spread the attack. Isolate whatever the incident response plan or the security supplier instructs. If guest data is involved, follow the steps for a data breach. Legal obligations, such as notifying the ANPD (Brazil's data protection authority), should be confirmed with the hotel's own legal advisers.

That is why the contingency plan and the incident response plan need to be aligned. The contingency plan keeps the operation going; the response plan guides how to contain the attack without destroying evidence or spreading the problem during recovery.

Questions to ask your suppliers

• PMS: does the system have any offline mode? What happens to the FNRH forms if the integration fails?
• Internet carrier: what is the contracted repair time, and does the second link run over different infrastructure?
• Locks: do the cards already issued keep working without the server? How do you issue a new card during the failure?
• Payments: does the card terminal work with a data SIM? What is the rule for pre-authorisations without the system?
• All of them: what are the contracted support hours, and who answers outside them?

Quick checklist: is your hotel prepared?

• A second internet link from another carrier using another technology
• A UPS on critical equipment, with known runtime
• PMS reports available offline
• A manual check-in and check-out procedure
• Contingency for payments
• A procedure for when the FNRH is unavailable
• A procedure for the locks
• Critical contacts kept outside the systems
• Each supplier's SLA and support hours known
• An incident response plan
• Backups with tested restores
• A contingency exercise carried out in the last 12 months

Next steps

Start with the map: list the systems, what each one brings down when it stops and which supplier is responsible. That exercise alone usually reveals the biggest gaps. HotelTI structures the contingency plan, defines roles and priorities, reviews supplier contracts and SLAs and coordinates the tests. The technical execution stays with the suppliers and the hotel's support team, under our coordination. Talk to our team.

Sources

• Ministry of Tourism, Portaria MTur nº 41, que institui a FNRH em meio digital (the ordinance establishing the digital FNRH, November 2025, in Portuguese), gov.br/turismo
• Ministry of Tourism, FNRH Digital: perguntas frequentes (FAQ, in Portuguese), gov.br/turismo
• Receita Federal and the NFS-e Management Committee, Portal da Nota Fiscal de Serviço eletrônica (in Portuguese), gov.br/nfse