Furniture and equipment arrive, licences get filed, the systems go in, staff are hired and trained, the first bookings land. The lists are accurate and largely interchangeable. The distinction they miss is the whole of pre-opening. A hotel is not built twice. The physical property is finished by contractors and the operating property is finished by whoever runs the runway, and only one of those two is visible when the doors open.
We are running that second build right now, on an 86-bed property in the heart of a Dutch university city, opening later this year. Nobody can book it yet. Which property it is, and what its runway looks like from the inside, comes at the end of this piece. Everything in between is what that runway is quietly deciding.
Not all pre-opening tasks are equal
Some decisions are cheap to reverse. The opening promotion, the breakfast format, the amenity in the room, the uniform, the layout of the arrival desk. These get argued about because they are visible, and they can all be changed in a season without anyone outside the building noticing.
The expensive ones are quieter. Who the supplier agreements are signed with, and on what terms. How rates and distribution are structured across channels, and what commercial history that starts accumulating. How the systems are configured, and who holds the administrator rights when the configuration needs changing. How the team is structured, which roles carry which responsibility, and what that fixes about the payroll for years.
None of those are dramatic on the day they are decided. Together they set the property's operating floor: the cost base it starts from, the flexibility it has, and how much of its own setup it actually owns. Unwinding any of them later costs money, downtime and goodwill, which is why most properties do not bother and simply live with what pre-opening handed them.
The useful question for an owner is not whether the checklist is complete. It is which items on it are permanent, and whether the person completing them knows the difference.
Day one is not the exam
Opening day is the most rehearsed day a hotel will ever have. Every senior person on the project is present, the team is fresh, occupancy is usually soft, and problems get solved by whoever happens to be standing there. It is a poor test of anything.
The real test is an ordinary busy week two or three months later, when the launch team has gone, two people have already left, the property is full, and something breaks that nobody wrote a procedure for. Systems training and written procedures transfer quickly. Consistency does not. A team can be trained enough to open and still be months away from holding a standard under pressure, and the gap between those two states is where most opening reputations are actually made or lost. Early guest reviews are written during that gap, and they stay online for years.
This is also why a soft launch earns its keep. It surfaces the things that testing does not: where the queue forms, which handover between shifts loses information, which supplier is slower in practice than on paper. A property is hardest to run in its first six to twelve months, and planning that ends at the opening date has planned for the easy part.
The handover gap
Most pre-opening work is delivered by people who leave when it succeeds. Specialists arrive for the runway, write the procedures, configure the systems, hire the team, and hand over a set of binders on the way out.
That creates two problems, and both are structural rather than anybody's fault. First, procedures written by people who will not have to run them tend to describe the ideal shift rather than the busy one. Second, the reasoning disappears. Six months in, someone asks why the property is set up a particular way and the honest answer is that the person who decided it is on another project.
The question worth asking any pre-opening partner is simple: which of the people setting this up will still be here in month six? If the answer is nobody, the property is buying a document rather than an operation, and the operating team will spend its first year reverse engineering decisions it was not part of.
Price the runway separately from the management
Pre-opening is a project. It has a scope, a cost and an end date. Management is continuous. Owners are frequently offered both inside a single open ended arrangement, which is convenient at signing and unhelpful afterwards, because there is no point at which anyone can say the setup work was delivered and here is what it cost.
Kept separate, both get better. The runway can be line itemed and closed out against what was promised. The management arrangement then starts from a property that is genuinely open, on terms that are about running it rather than building it. An owner who cannot see where one ends and the other begins will not be able to judge either.
The property in question
The runway from the top of this piece belongs to The Owl Inn in Leiden, an 86-bed boutique hostel on Steenschuur in the centre of the city, opening later this year. Weave runs the full pre-opening on behalf of ownership: procedures, manning structure and recruitment, supplier coordination, technology setup, distribution and brand support.
Two things about that engagement are deliberate. Operational thinking goes into the development phase rather than arriving after handover, so the property is shaped by people who will have to run it. And the same team carries through to opening and beyond, so the decisions above are made by whoever has to live with them. The supplier agreements point at the owner's entity from the start, which means the property owns its own setup on the day it opens instead of inheriting somebody else's.
That is a narrower promise than most pre-opening pitches. It is also one an owner can check, months later, by asking who is still in the building.
Further reading: The owner-aligned management model, explained · The Owl Inn, Leiden
Weave projects is a hospitality developer and operator based in Amsterdam, working across the Netherlands and Europe.