Hotel IT annual calendar: what to do each month
The backup test, the access review and the notice not to renew a contract are rarely urgent, so they get put off. This calendar spreads a hotel's IT tasks across the 12 months and keeps non-essential changes out of high season.
Every month, check backups, security updates, alerts and FNRH Digital submissions. Across the year: avoid non-essential changes in high season (January, February and July for a leisure hotel), test a backup restore in March, review access in April, run the contingency exercise in May, handle PCI DSS and LGPD in June, train staff in August, update the inventory in September, review budget and contracts in October and test the whole operation in November.
The months follow the season of a leisure hotel in Brazil, with peaks in the summer (December to February), at Carnival (which falls in February or March) and in the July school holidays. A business hotel, busier from March to November, can move the months around and keep the logic; adjust for local events too. The calendar sets the reviews and tests. Security alerts, incidents and an employee leaving are dealt with when they happen, in any month.
| Month | Main task |
|---|---|
| January | Change freeze in high season |
| February | Post-season review of tickets and incidents |
| March | Backup restore test |
| April | Access review |
| May | Contingency plan exercise |
| June | Compliance documents (PCI DSS, LGPD) |
| July | Change freeze in the school holidays |
| August | Staff training against scams |
| September | Inventory and end of support |
| October | Budget, contracts and licences |
| November | Operations test before high season |
| December | Year review and next year's plan |
What to do every month
Check that the backups ran and whether any failed. Apply security updates to computers, servers and network equipment in the monthly cycle, outside check-in hours. A flaw that is already being exploited, or an attack alert in progress, does not wait for the cycle: it is handled at once, freeze or not. Read the antivirus or SOC alerts and see whether any went unanswered within the agreed time. Confirm with the PMS vendor that FNRH Digital guest records are being sent without errors. And check whether anyone who left the hotel still has active access: access is revoked when the person leaves (see the access to revoke when an employee leaves), and the monthly check catches what slipped through.
January to March
January: change freeze
With the hotel full, the rule is to leave what works alone: no migration, no equipment swap, no major PMS update. Only urgent and security fixes go in. Before January starts, confirm each vendor's on-call support and escalation contact for the period.
February: post-season review
After Carnival, or after high season ends in years when Carnival falls in March, gather the season's tickets and incidents: what went down, for how long, which vendor was slow. That list becomes the agenda for vendor meetings and feeds the October budget.
March: restore test
Only a restore test shows whether the backup can get the hotel running again. Restore a copy of the PMS database to a test environment, never over the live system, plus a folder of finance files. If the PMS is in the cloud or hosted by the vendor, ask the vendor to run the test and send the report. Check that the data opens and is complete. Note two things: how long it took to get the system working again (RTO) and how recent the recovered data is (RPO). Compare each with the hotel's targets (see the glossary).
April to June
April: access review
Ask each system for its list of active users: PMS, email, OTA extranets, channel manager, bank, POS, door locks, cameras. Compare it with the staff list and each person's role. Users who have left, generic accounts such as "frontdesk1" and admin profiles with no reason are what to look for. The April review checks the whole year; role changes and departures are handled on the day they happen.
May: contingency exercise
Before the July holidays, simulate a PMS outage on a quiet shift: can the front desk find the printed or exported arrivals list, check a guest in by hand, know whom to call and, once the PMS is back, enter the bookings and check-ins done by hand? Update the emergency contact list. See the IT contingency plan.
June: compliance documents
Set aside June for the annual compliance review. For PCI DSS, complete the self-assessment (SAQ) or assessment on the date the acquirer sets; if it asks in another month, follow its date. Check the compliance status of the vendors that affect card data (requirement 12.8.4), usually through the attestation of compliance (AOC) covering the contracted service, or through other evidence when the vendor has no AOC. Also check that it is written down what falls to the hotel and what falls to each vendor (requirement 12.8.5). For the LGPD, review the record of processing activities (art. 37) and the privacy notice.
July to September
July: change freeze
Same reasoning as January, with the hotel full for the school holidays. If Wi-Fi capacity was tight in the summer, this is the month to measure it at peak time and note the result for September.
August: staff training
With the hotel calmer, run a short session, with examples, for the front desk, reservations and finance: fake OTA emails, doctored Pix receipts, a "support" call asking for remote access. See AI scams in hotels and Pix fraud in bookings. Anyone who joins during the year takes the same training when they start, without waiting for August.
September: inventory and end of support
Update the list of computers, servers, network equipment, systems, cloud subscriptions and PMS integrations, with the date each one loses manufacturer support. The equipment and systems that lose support next year go into the October budget instead of turning into a surprise in July. With the July measurements, check whether the internet link, guest Wi-Fi and UPS units can handle the December peak. See legacy systems and unsupported Windows.
October to December
October: budget, contracts and licences
Build next year's IT budget from the September inventory and the February review. In the same week, review the list of technology contracts with each renewal date and the deadline for the notice not to renew. That list is kept up all year, and October only consolidates it: a contract that renews in January with 90 days' notice needs the notice in early October, and one that renews in May, by the end of January. Missing the deadline can renew the contract for another term. See the PMS contract clauses and how to reduce licence costs.
November: high season preparation
Major updates and equipment swaps finish by the end of October, with time to fix whatever goes wrong. November is for testing the operation end to end: do a booking through the booking engine and another through an OTA reach the PMS? Does the payment go through, is the door key encoded, does the guest connect to Wi-Fi, is the invoice issued and is the FNRH Digital record sent? Repeat a quick contingency test and confirm vendor on-call support from December to February. A change that can't wait goes in with approval, a maintenance window and a plan to roll it back.
December: year review
Before the freeze, gather the year's incident register, what is still pending and what changed in the operation. The register is filled in as each incident happens: ANPD Resolution 15/2024 requires the controller to keep a record of incidents involving personal data, including those not reported to the ANPD, for at least five years. In December it shows what kept recurring, and that becomes next year's plan.
Who owns the calendar
The calendar needs an owner. In a hotel with in-house IT, that is the IT lead. In a hotel that outsources support, the vendor carries out many of the tasks, but someone at the hotel checks they were done and keeps the evidence: the restore test report, the reviewed access list, the AOCs. See how responsibilities split between the hotel and its vendors.
Next steps
HotelTI's virtual IT manager builds this calendar with the hotel, follows up the vendors' execution and keeps the evidence for each task. Support is during business hours. We do not resell software or have agreements with specific vendors. Talk to our team.
Sources
- Presidência da República, Lei 13.709/2018, General Data Protection Law (LGPD), art. 37, planalto.gov.br
- ANPD, Resolution CD/ANPD 15, Security Incident Reporting Regulation (April 2024), in.gov.br
- PCI Security Standards Council, PCI DSS v4.0.1, requirements 12.8.4 and 12.8.5, pcisecuritystandards.org
Virtual IT manager
One person responsible for the hotel's IT, who plans the year and follows up the vendors.
View service- Annual IT calendar
- Vendor follow-up
- Evidence for each task
- Budget and contracts
Related reading
Why freeze changes in high season?
Because a failure with the hotel full affects more guests and leaves less time to fix it. Migrations, equipment swaps and major updates move to low-occupancy months; urgent security fixes still go in.
How often should the backup restore be tested?
At least once a year for the PMS and the finance files, and again after any major change to the backup or the system. Critical systems may need more frequent tests, depending on how long the hotel can do without them. The test counts when someone restores the data to a test environment and checks that it opens and is complete.
Does the calendar work for a business hotel?
Yes, with the months swapped. In a business hotel, occupancy tends to drop in December, January and July, which become the months for the larger tasks, and the freeze moves to event periods and the busiest weeks.
Does HotelTI carry out these tasks?
The virtual IT manager plans the calendar, follows up the execution by the hotel's vendors and keeps the evidence. The technical work stays with the hotel's IT support or its vendors.
Does your hotel's IT have a calendar?
Talk to our team and build next year's plan before high season.