The opening date doesn't move. Your IT has to be ready first.

Chapter 01

Every delay upstream lands on the IT schedule downstream.

In every opening, IT depends on everyone else: walls before cabling, power before racks, handover before testing. When construction slips, the IT window compresses, but the opening date and the first bookings do not move. The difference between a smooth opening and a chaotic one is decided months earlier: whether IT was in the build planning from day one, or invited in at the end to make it work somehow.

Consider a 120-room new build. The cabling plan depends on the wall layout. The rack room depends on power and cooling. The WiFi survey depends on finished rooms, because signal behaves differently in a concrete shell than behind furniture and glass. Every one of those dependencies sits at the end of someone else’s schedule. When the fit out slips two weeks, nobody moves the opening. They move the IT window.

That compression has a predictable shape. Installation gets rushed. Integration testing gets cut first, because it is the least visible line in the plan. Training gets cut second. The result is a hotel that looks finished and behaves like a building site: door locks that open but do not sync with the PMS, TVs that greet guests by the wrong name, payment terminals that fail on the one card the first guest presents.

None of this argues for moving the opening date. Openings are commercial commitments long before they are technical ones. It argues for treating IT readiness as a construction milestone, planned and tracked with the same discipline as the walls themselves. In a hotel opening, IT is the last trade on site and the first thing the guest touches. Plan it that way.

Chapter 02

Boring, in an opening, is the highest compliment.

A boring opening day means the systems already worked the week before. Nobody improvises, nobody discovers, nobody calls a vendor from the lobby. The front desk checks in the first real guest the same way it checked in the last test guest. We plan every hotel opening backwards from that outcome, through four milestones that each have a date, an owner and an exit test. Miss a milestone and you know weeks in advance, while there is still time to act.

Network, PMS landscape, telephony, TV and security designed and ordered while the building is still drawings. Long lead items, like network hardware and door lock systems, are secured before they can become the critical path. Delivery times do not care about opening dates, so we order against the date that does not move. Every vendor knows the integration plan and their slot in it, because one party wrote both. That removes the most common failure in opening projects: ten suppliers, each on schedule, and no working whole.

Racks live, network up, systems installed and integrated as the building allows. The PMS talks to payments, door locks, TV and WiFi in a test environment that mirrors day one. Integration issues surface here, between two project teams with time to fix them, not between a receptionist and a queue. The sequence follows the building: cabling when walls close, racks when power is stable, access points when ceilings go in. When construction slips, we resequence the work instead of cutting the tests.

Fake check ins, payments, casting, calls and checkouts, run by the people who will do them for real. We walk the full guest journey from booking to invoice and break things on purpose. Staff train on real systems with real screens, so the first arrival is a repetition, not a premiere. Issues get fixed while they are still cheap. A payment routing error found in testing is a ticket. The same error found at check in on opening day is a queue in the lobby.

Engineers in the building for opening week, walking the floors with the operation instead of waiting for tickets. Opening week is when small issues surface fastest: a printer that was never mapped, a room phone with the wrong extension, a charge that posts to the wrong folio. Fixing them within the hour keeps the team’s confidence intact. Then a structured handover into 24/7 managed support, with everything documented and monitored. The opening ends. The ownership doesn’t.

Chapter 03

What we sign up for on day one.

Opening commitments are easy to make and expensive to keep. Ours is specific: on day one, every system a guest or an employee touches is fully operational, and it has been proven operational before the first booking arrives. Not installed. Not configured. Proven. The distinction matters, because a hotel opening leaves no rehearsal space once the doors are unlocked. The first check in is real, and so is the first review.

Operational means the whole journey, not the parts. A key card that opens the door but does not talk to the PMS is not operational. A payment terminal that settles to the wrong ledger is not operational. WiFi that covers the lobby but drops on the fourth floor is not operational. We define day one readiness from the guest’s side of the desk, because that is where it will be judged.

The commitment also covers what happens when something does break, because something always does. An access point fails, a vendor pushes a late update, a terminal loses its pairing. In a tested environment these are isolated incidents with known fixes, handled by engineers already in the building. In an untested environment they are mysteries, investigated in front of guests.

That is what we sign up for. It is also why the earlier chapters matter: a commitment like this can only be kept if IT entered the planning when the building was still drawings. A commitment made in the final month is a hope with a signature. A commitment made at the design table is a plan, with milestones behind it and the time to keep them.

Chapter 04

The same structure for openings, rebrands and takeovers.

Our IT Strategy & Project Services team runs openings as a standard playbook with property specific detail: design early, build against milestones, test like guests and open with support in the building. The same structure carries rebrands and takeovers, where day one is a system switch instead of a ribbon.

Full IT design inside the build planning, with long lead items ordered early and every dependency on construction made explicit. The design covers network, PMS landscape, telephony, TV, security and the integrations between them. Each element carries a construction date and a technology date, written into a single schedule. When either side slips, the plan shows it immediately, not in opening week.

Install and integrate against milestones, coordinated with construction week by week. One integrator directs every vendor, so nothing arrives out of sequence and nothing is left half connected. A building in fit out changes daily, so the plan is walked on site, not assumed from a spreadsheet. Every system that goes in is connected to the systems around it before the next trade closes the ceiling above it.

Guest journey testing and staff training weeks before opening, on the real systems in the real building. By the time the doors open, the front desk has already checked in hundreds of imaginary guests. Night audit has run, invoices have printed and keys have been cut for rooms that were still under plastic. What remains for day one is repetition.

On site support at opening, then structured handover to 24/7 operations, with documentation, monitoring and clear escalation paths in place from the first night. The people who built the environment stay close to it through the first full occupancy cycle. What they learn on the floor feeds straight into the runbooks that daily support works from afterwards.

Takeovers get the same playbook with one extra chapter: untangling the previous operator’s IT without guests noticing. Contracts, licences, integrations and data all change hands on a fixed date, while the hotel stays full. Rebrands add brand standards to the mix, from guest WiFi portals to TV interfaces. The phases stay the same. Only the starting point changes.

Chapter 05

Day one should feel like day one hundred.

Think about what the first guest actually does. They arrive, they give a name, they tap a card, they take a key, they connect a phone, they order a drink, they sleep, they check out. Eight ordinary moments. On a tested foundation, each one is unremarkable. On an untested one, each is a coin flip, and the hotel only controls one side of it.

That is why we treat opening week as the end of the project, not the start of the relationship. The engineers who tested the systems stand next to the team that uses them. The handover to daily operations happens once the operation has found its rhythm. And the documentation, monitoring and lifecycle planning built during the project keep working long after the ribbon is gone.

The predictability compounds. A hotel that opened on a tested foundation spends its first year improving the operation instead of stabilising it. Staff trust the systems, because the systems held on the hardest day, and that confidence reaches the guest in ways no technology can. The team that survived a chaotic go live spends months working around its own tools. The team that opened calmly never learns to distrust them.

Openings are judged by first impressions that never get a second chance. The playbook makes IT the most predictable part of the most unpredictable week. It also sets the standard question for guest technology across the group: read one brand on every screen, and how to keep budgets predictable after opening in IT without a roadmap surprises your CFO.