A hotel opening date is fixed long before the technology that has to work on it. This is the twenty-four-month pre-opening timeline for a Saudi property, phase by phase, with the decisions that hold the date and the ones that quietly move it.
Scope note: practical guidance drawn from hotel technology delivery practice; requirements vary by operator standards and local authority approvals. Verify against your project’s specifications.
The month-by-month schedule is EIE’s indicative planning model; durations vary with the property, the operator’s standards and authority approvals.
Our hospitality sector page summarises pre-opening delivery as six phases; this article is the month-by-month detail beneath them.
Why the timeline runs backwards from opening day
A pre-opening programme has one immovable fact: the opening date. Marketing has sold it, the operator has staffed for it, and the investor has financed against it. Every technology decision is scheduled backwards from that date, and the schedule carries almost no float at the end, because the closing months belong to finishing trades, furniture, licensing and training rather than cabling.
There is also no grace period afterwards. A property either opens with a working reservations platform, guest connectivity, in-room entertainment, room controls, telephony, point-of-sale and access control, or it opens badly in a way guests write about. Technology is a critical path, not a fit-out item.
The twenty-four-month pre-opening technology timeline
The table sets out the phases against months before opening, written as T-24 through to T-0. Durations shift with size and complexity; the sequence and the dependencies do not.
| Phase | Window | Technology work | Gate to pass before moving on |
|---|---|---|---|
| 1. Concept and design | T-24 to T-18 | Technology consultant appointed, brand standards translated into technical specifications, containment and riser strategy agreed. | Specifications issued and coordinated against the architectural and services model. |
| 2. Detailed design and procurement | T-18 to T-12 | Platform selections locked: reservations, entertainment, room controls, telephony, audio-visual, network. Long-lead orders released with clearance time included. | Purchase orders placed for every long-lead item, platform contracts signed. |
| 3. Back-of-house infrastructure | T-12 to T-9 | Structured cabling through service areas, kitchens, administration zones and plant spaces. Distribution rooms handed over and commissioned. | Distribution rooms secured, powered, cooled and formally accepted. |
| 4. Guest-floor infrastructure | T-9 to T-6 | Guest-floor cabling, room-control wiring, entertainment and lock wiring, coordinated with the furniture package. Platform configuration begins. | A completed model guest room signed off by the operator against brand standards. |
| 5. Systems integration | T-6 to T-4 | Interfaces proven one at a time: reservations to entertainment, telephony, locks, point-of-sale, room controls. Wireless deployed and tuned. | Every interface demonstrated individually against a written test script. |
| 6. End-to-end testing | T-4 to T-3 | Full journey scenarios: arrival flowing through to name display, welcome screen, welcome scene, key activation. Edge cases exercised. | Scenario pack passed, with defects logged, assigned and dated. |
| 7. Operational rehearsal | T-3 to T-2 | Live simulation with hotel teams: real arrivals, real food and beverage service, real housekeeping rotation, real fault reporting. | Rehearsal defect list closed, or accepted with a date against each item. |
| 8. Training and final tuning | T-2 to T-1 | Role-based training for front desk, housekeeping, food and beverage, security, facilities and the technology team. Handover documentation issued. | Teams signed off department by department, support model contracted. |
| 9. Soft opening | T-1 to T-0 | Limited operation with invited or early guests. Real behaviour drives final tuning of coverage, scenes, screens and workflows. | Stable operation across a full week, including a weekend peak. |
| 10. Grand opening | T-0 | Full operation, with the support agreement and its response targets live from day one. | Programme formally closed into lifecycle support. |
The phases that decide opening day
T-24 to T-18: getting technology into the design conversation
Almost nothing is procured in this phase, and it still carries the most leverage. Containment routes, riser sizes, distribution room locations, power and cooling provision, and the position of ceiling and wall devices are all set here by architects and services designers. Technology scope arriving after those decisions inherits them, and inherited constraints become change orders later.
The work itself is translating brand standards into technical specifications. Brand documents describe outcomes: guest connectivity, entertainment experience, in-room comfort. Specifications describe device positions, interface requirements and acceptance criteria. Ambiguity left here is paid for at T-6.
T-18 to T-12: the procurement window everything depends on
This is the phase that most often causes the failure appearing eighteen months later. Platform selection has to be locked here, because every subsequent interface, training plan and configuration task depends on knowing which platforms are being integrated. Long-lead procurement starts at the same time: telephony platforms, entertainment head-end equipment, control processors, cabling materials and network hardware all carry production and shipping lead times, and imported equipment carries clearance and inspection on top. A plan treating delivery as instantaneous hides several weeks.
T-12 to T-6: infrastructure, in the right order
Cabling runs back-of-house first, because service areas are available while guest floors are still with finishing trades. Distribution rooms are commissioned early so platform installation has somewhere secure, powered and cooled to live. Guest floors follow, and guest-floor cabling must be coordinated with the furniture package rather than with drawings alone, because bedside and desk positions move during procurement, and an outlet set to a superseded layout ends up behind a headboard.
The model guest room is the gate that matters here: a single room finished completely, every device installed and every service working, signed off by the operator. Every defect found in it is avoided everywhere else.
T-6 to T-3: integration is a phase, not a task
The interfaces are what make a hotel feel finished. An arrival at the desk should propagate a name to the room telephone, a welcome screen to the television, a comfort scene to the room controls, a valid key to the lock, and a charging route to the point-of-sale. Each is a separate interface with a separate configuration, proven individually before the chain is tested end to end.
Test with scripts rather than impressions. A written scenario pack, run by the operations team rather than the installer, produces a defect list that can be assigned and closed. A walk-through concluding that it all looks fine produces nothing anybody can be held to at T-1.
T-3 to T-0: rehearsal, training and the soft opening
The operational rehearsal is the only realistic test of the whole system, because it introduces the variable no laboratory test contains: staff under pressure. Real arrivals, real service, real housekeeping rotation and real fault reporting expose the workflow problems scripted testing misses, while there is time to correct them.
Training is role-based or it is decorative. Front desk needs the arrival and departure flows and the fault-reporting route; housekeeping needs room status and its reporting path; the technology team needs administration, escalation and the support agreement. A single session covering everything trains nobody.
What slips most often
- Platform selection locked late. A decision taken at T-9 that belonged at T-15 compresses configuration, interface work and training into a window that cannot hold them.
- Optimistic delivery assumptions. Production time, shipping and customs clearance are three separate durations, and they are additive.
- Brand standards revised mid-programme. A revision at T-8 is a redesign, and needs handling as a formal change with cost and time attached rather than absorbed quietly.
- Site readiness slipping from the main contractor. Technology is the window that gets compressed, because it sits last. The mitigation is a written access programme per floor, tracked weekly.
- Furniture coordination missed. Positions set against a superseded layout are discovered at the model room stage at best, and at handover at worst.
- Support model contracted after opening. The agreement governing response targets should be live on opening day, not negotiated while faults are already arriving.
The governance that holds the date
Programmes that open on time share three habits. Technology is represented at the weekly coordination meeting by somebody with authority to refuse a change that breaks a dependency. Every interface has a named accountable person on both sides, so a defect never sits unclaimed between suppliers. And one dated technology schedule is kept current against the construction programme rather than parked beside it.
Saudi factors worth planning for
Licensing and classification. Hotel licensing and classification requirements published by the Ministry of Tourism affect facilities and operational readiness, and the evidence for them is assembled in the same months as technology commissioning. Sequence the two so they do not compete at T-2.
Guest data obligations. Guest registration, personal data handling and network logging attract obligations under the national data protection and cybersecurity regimes, and platform decisions taken at T-18 determine how easily they are met later. Bring compliance into platform selection rather than commissioning.
Seasonal peaks. Properties serving pilgrimage and religious travel face demand patterns unlike a normal ramp-up. Capacity planning for wireless, telephony and the reservations platform should be sized against the peak the property will genuinely see.
Where EIE fits
EIE delivers pre-opening technology programmes from our Jeddah headquarters, with Kingdom-wide service coverage, building on a technology heritage dating to 1985 through predecessor ETE.
Frequently asked questions
Is twenty-four months always the right pre-opening window for technology?
It is a reasonable planning assumption for a full-service property. Simpler properties compress it; mixed-use developments with shared infrastructure often need longer. What does not change is the ordering: design participation, procurement, infrastructure, integration, rehearsal.
When does the technology team need to be appointed?
Before the design is fixed, which in practice means at or before T-18. Appointing later means inheriting containment, riser and distribution room decisions made without technology input, then paying to correct them.
Which gate matters most across the whole programme?
The model guest room, signed off by the operator against brand standards. It converts arguments about interpretation into a physical reference that every other room is measured against.
What happens if the opening date moves?
Reschedule deliberately rather than letting the programme drift. A date moved outward is a chance to close the defect list and repeat the rehearsal. A date moved inward is a scope conversation that has to happen immediately, because compression without a scope decision relocates the failure to opening week.
Sources and further reading
Licensing, classification and operational requirements for hotels are published by the Ministry of Tourism and should be read at source. Obligations covering guest personal data are published by the Saudi Data and Artificial Intelligence Authority under the Personal Data Protection Law and its Implementing Regulations. Cybersecurity expectations for the systems holding that data are published by the National Cybersecurity Authority in the Essential Cybersecurity Controls.
Related: Hospitality technology for Saudi hotels and talk to us about a pre-opening programme.