Hotel pre-opening: a month-by-month plan for a new property

Pre-opening is the period between the decision to open a hotel and its first paying guest. It is run as a countdown of dependent decisions, not a flat hotel pre-opening checklist: the critical path is the chain of tasks where one week's delay moves the opening date by one week. Everything else has slack.

The handover date is fixed, the first bookings are already in the system, and the general manager's boxes are still in the lobby. What decides whether that opening is calm is not effort but order: which decisions had to be made before which. After reading this article you will be able to build that order for your own property, from the owner's brief down to the first 30 days of operation.

What is hotel pre-opening, and what is the critical path?#

Pre-opening covers everything that must be true before a guest can be checked in, charged, cleaned for and reported to the authorities. The critical path is the shortest chain of those dependencies: the tasks that set the opening date.

Start by separating three dates and naming them in every document: construction handover, operational readiness, and the first paying guest. Most opening chaos comes from treating them as one date. Construction can hand over a finished building that is not operationally ready, and an operationally ready hotel can still be waiting on a licence before it may legally take a guest.

A task is on the critical path when its delay moves the first-guest date. The mechanism is dependency, not difficulty. For example, if the workplace licence needs a fire sign-off, and the fire sign-off needs the alarm system commissioned, those three form a chain: each one waits on the one before it. Finishing the lobby furniture early buys you nothing, because nothing downstream waits on the furniture.

The GM's start date is itself a critical-path item. Hiring, supplier contracts, systems configuration and SOP writing all wait on it, so a late GM start pushes everything below it by the same amount.

Pre-opening is not the pre-opening budget and not the sales plan. Both hang off the same dates and are managed separately; this plan only fixes the order. Give every line one named owner and one evidence date: a document, a test result, a signed contract. A line without evidence is an opinion. Review the path weekly on one page, and log every date change with its reason. Silent slips are how a calm opening becomes a rushed one.

Who do you hire first, and what does the owner's brief fix?#

The general manager comes first, and the owner's brief fixes what that GM is allowed to decide. Both must be settled before hiring waves, supplier contracts and system choices can move.

The owner's brief is a short written document. It covers positioning, target segments, service level, the boundary between capital works and operating spend, decision rights, reporting rhythm, and what counts as open: which date, how many rooms, which outlets. Without it, every disagreement during pre-opening is relitigated from scratch.

Hire the GM before the department heads. A GM who inherits a team cannot be held to the result, and department heads hired by the owner will report to the owner in practice, whatever the org chart says. Write the decision rights down: disagreements about who approves a supplier or a hire cost weeks exactly when weeks are scarce.

Hiring comes in waves. First the GM with a financial controller and a chief engineer, then department heads, then supervisors and line staff close to opening. Wages paid long before opening are pure cost with no revenue against them, so each wave should be timed to the work it makes possible.

Set up a pre-opening office early: one room, a working network connection, one shared document set, one calendar of gates that everyone can see. Keep the org chart and the decision rights in the same document, so a new hire can read who decides what on their first morning. A fuller treatment of roles and reporting lines is in our guide to the hotel organisation chart.

Which licences and certificates sit on the critical path?#

The ones that gate the building, the guest and the money: the municipal workplace licence that lets the building operate, the tourism operation certificate that lets it operate as an accommodation facility, and the tax and guest-notification setup that lets it take a payment and register a guest.

Order matters more than speed. The workplace licence depends on construction completion and on fire and infrastructure sign-offs; the tourism operation certificate depends on the property meeting the required qualities. Neither can be bought earlier by applying earlier, because the decision waits on physical facts. What you can do is start the file while construction finishes: collecting documents is work that runs in parallel, even though the decision does not. Our guides to the hotel workplace licence in Türkiye and the tourism operation certificate application walk through each in detail.

Compliance setup is a gate even where it is not a licence. Guest identity notification (KBS, the misafir kimlik bildirimi system), electronic invoices (e-Fatura and e-Arşiv) issued through a licensed integrator, and personal data rules (KVKK, the personal data protection law) covering consent, export and retention all need to work before the first guest. In Türkiye, every stay involves a payment, a fiscal document, a guest identity notification and personal data, so these are not optional extras at the end of the list.

Describe the duties in general terms and confirm dates, penalties and your own case with an accountant or legal adviser. Rules depend on your taxpayer status and your building.

Name one owner for the licence file and one evidence date per document. A missing signature is a lost week, and it is always the same signature. Keep every submission, receipt and reference number: the file is the proof, and the proof is what an inspector asks for.

What must systems, data and operating equipment be ready before the first guest?#

The systems must be able to take a reservation, assign a room, post a charge, close the business day and produce a report, and the equipment and supplies must be on site and counted before staff are trained on them.

Define the minimum system set before you compare products: reservations and room inventory, front desk, housekeeping room status, billing and the end-of-day close, restaurant sales, reports, and the compliance steps above. If a product cannot do one of these, the rest of its features do not matter.

Make the data decisions once and early: room types and room numbers, rate codes, taxes and fees, chart of accounts, department codes, user roles. Changing them after training means training twice. Agree what each room status means in your property and write it down. Terms such as clean, inspected, out of order and do not disturb are common practice, and systems differ, so your definition is the one staff will use.

Operating equipment follows the same rule. Set a par stock per department, fix delivery dates, confirm storage space, and count and tag items on arrival. Equipment that lands after training produces a second training. Suppliers and contracts need start dates before the first guest, not on it: linen and laundry, cleaning chemicals, food and beverage, waste, pest control, network and IT support.

Test the whole chain with a fake guest: a reservation, a check-in, a posted charge, the end-of-day close, a report, and an invoice draft held for a person's review before sending. If the chain breaks anywhere, you want it to break on a guest who does not exist.

For reference, AI Otel's hotel operating system (AI Otel PMS) is built for exactly this list: reservations, front desk, housekeeping, billing, restaurant sales, reports and compliance in one place, built and working, ahead of launch.

When should SOPs and training happen, and how do you staff a hotel with no guests yet?#

SOPs are written by the people who will run the shift, tested in dry runs, and finished before training starts. Staff arrive in waves timed to the training they need, not to the opening date.

Use one SOP format for every routine: what triggers it, the steps in order, who decides, what gets recorded, and what to do when it goes wrong. One page per routine. Our guide to writing hotel SOPs staff actually follow covers the format in depth.

Write the routines that cover the first week first: arrival, departure, the room cleaning sequence, lost and found, a complaint, a maintenance fault, a cash drop, and an exception at the end-of-day close. These are the routines that will run dozens of times in the first month, so they are the ones that must be right.

Run dry runs with staff in role, on the real system, with real equipment and a scripted guest. Log every failure and fix it before the next run. Two dry runs are usually worth more than a week of classroom training, because they surface the failures that only appear when a real person presses the real button.

Tie training waves to hiring waves, and cross-train for the first weeks, when headcount is thin and absences are certain. Publish who is on duty, who may remove a charge, and who is called at two in the morning. Unclear escalation is the most common first-month failure. Keep a training record per person: what they were trained on, by whom, when, and who signed off. It is also the document you reach for after an incident.

What does a soft opening require, and what should the first 30 days cover?#

A soft opening is a real opening with limited inventory and a short written list of things being tested, so that failures stay small and fixable. The first 30 days are for stabilising routines, not for hitting a revenue number.

Separate soft opening from grand opening. Soft means real guests, fewer rooms or fewer outlets, an explicit test list and a daily review. Grand is a marketing event and belongs after the test list closes. Sign the readiness gates before the first guest: licence in hand, systems tested end to end, equipment counted, staff trained and signed off, suppliers delivering on schedule.

Choose what to test in the first weeks: the arrival flow at peak, room cleaning turnaround, breakfast service, a complaint, a maintenance fault, the end-of-day close, and the invoice review step. Hold a short daily stand-up: yesterday's numbers, today's arrivals, open faults, one decision. Keep a decision log with an owner and a date, because memory is not a record.

Record incidents from day one: what happened, who was involved, what was done, who was told. Handling a guest whose room is not ready is hotel practice, not a legal rule, so write your own procedure and follow it. Our guide to hotel incident reports explains what to record.

Watch a small set of signals rather than a dashboard: rooms out of order, complaints by type, time to clean a room, exceptions at the end-of-day close, invoices held for review. Widen inventory only when the test list closes. Announcing a date you have not tested converts a small failure into a public one.

What to do next#

Take your first-guest date, count backwards, and write the chain of decisions that must happen before it, each with a named owner and an evidence date. Everything in this article hangs off that one page: the GM and the owner's brief at the top, the licence and compliance file running in parallel, systems and equipment frozen before training, and a soft opening that tests rather than announces. If you want to see how a hotel operating system built for this list looks in practice, request a briefing at https://ai-otel.com/contact.