 |
| Hotel growth magnifies coordination risk. The question is not how fast a hotel can be designed, but whether its decisions can survive procurement, construction, opening and operations. |
The question is not how fast a hotel can be designed. It is whether the decisions made today can survive procurement, construction, opening and operations.
India's hospitality sector is expanding into a more complex
delivery environment. More brands, more owners, more mixed-use conditions, more
specialist consultants, more technology, more operator requirements and tighter
opening programmes all increase the number of decisions that must remain
aligned from the earliest business case to the first day of operation.
That growth is an opportunity. It also exposes a weakness that
is easy to misdiagnose. The problem is usually not a shortage of capable
architects, engineers, operators, project managers or contractors. A hotel can
have excellent people in every discipline and still arrive at tender,
construction or opening with critical information unresolved.
The risk sits at the interfaces between those specialists. That
is where design management becomes more than a coordination function.
A hotel is not only a building
A hotel is an operating asset whose commercial performance
depends on hundreds of design decisions becoming reliable at the right time.
Room mix affects revenue and area efficiency. Arrival planning affects guest
experience and traffic. Back-of-house planning affects staffing, service
efficiency and waste movement. Plant and riser decisions affect room layouts,
ceiling heights and resilience. Brand standards affect architecture, interiors,
technology, services, FF&E, procurement and operations.
The building may be handed over once, but the consequences of
these decisions remain with the operator for years. A design issue that appears
small during concept design can become a procurement delay, a site instruction,
a repeated room defect, an operational inefficiency or a maintenance burden
later.
That is why hotel design management cannot stop at drawing
production or design-review meetings. It must govern how decisions travel
through the lifecycle.
The real problem is not missing tasks. It is weak transfer
between tasks.
Most large hotel projects already have programmes, drawing
registers, meeting minutes, comment sheets, BIM models and procurement
schedules. The difficulty is that these instruments can record activity without
proving that a decision has actually been transferred into the next dependent
piece of information.
An operator comment may be marked 'closed' in a spreadsheet but
not carried into the room data sheet. A value-engineering decision may appear
in a cost report but not in the specification. A plant-space compromise may be
agreed in a meeting but not tested against maintenance access. A substitution
may be commercially attractive but quietly weaken a brand, warranty or
lifecycle requirement.
The design-management question is therefore different from the
administrative question. It asks: what remains unresolved, who owns it, what
does it block, what happens if it is not closed, what evidence proves closure,
and what is being carried into the next stage?
Where the risk begins to multiply
1. Feasibility to concept
The first transfer is from business intent into spatial logic.
Key count, room mix, market position, operator strategy, site constraints,
approvals, access and area efficiency need to be tested before a concept
becomes emotionally fixed. A visually strong concept can still be commercially
or operationally weak if the assumptions beneath it have not been made visible.
2. Concept to schematic design
This is where guest experience collides with structure, MEP,
fire, vertical transport, kitchens, laundry, service routes and back-of-house
reality. Plant space, risers and service access are not secondary technical
matters. If they are not protected early, they compete later with saleable or
guest-facing area, often at greater cost and with less choice.
3. Developed design to tender
The pressure to issue a package can easily become stronger than
the discipline to test whether the design is mature. Room Data Sheets, operator
comments, specifications, BIM information, authority conditions,
value-engineering decisions and long-lead items must converge. Tender readiness
is not the same as drawing issue. It is a condition that needs evidence.
4. Procurement to construction
Procurement is a design stage because substitutions, approved
suppliers, FF&E decisions, mock-ups and long-lead purchases can alter the
final asset. A commercial decision that bypasses design governance may protect
an immediate budget line while creating a later operational or brand problem.
5. Construction to opening
Construction exposes the maturity of earlier decisions. RFIs,
shop drawings, material submittals, site changes and mock-up comments are not
isolated workflows. They are the mechanisms through which design intent is
either protected or eroded. By the time testing and commissioning begin,
unresolved design issues should not be discovering themselves for the first
time.
Design management is an owner-side governance layer
Operators protect their brand and operational requirements.
Architects and engineers protect their disciplines. Project managers protect
programme and delivery. Cost consultants protect commercial control.
Contractors protect construction obligations. All of these roles are essential.
But the owner still needs a layer that protects the business
case across the spaces between those responsibilities. That layer must keep the
project visible as a whole and ensure that relied-upon information remains
aligned as the project changes.
This does not mean creating another bureaucracy. In fact, good
design governance should reduce bureaucracy. It should make responsibilities
clearer, decisions easier to trace, escalation earlier and stage transitions
more deliberate.
A practical control philosophy
For the hospitality application of the Design Manager's Manual,
I am testing a simple principle: each stage should have a small number of
decisive control questions, and each unresolved issue should have a visible
downstream dependency and identifiable closure evidence.
The exact tracker structures remain part of the working manual,
but the public logic is straightforward. A stage should not progress simply
because the calendar says it is complete. A decision should not be treated as
closed because it was discussed. And a hotel should not be called ready because
the opening date has arrived.
Evidence matters: a coordinated drawing, a model update, a
revised specification, an approved sample, a mock-up sign-off, an authority
approval, a commissioning result, an asset-data record or an operator
confirmation.
Good governance is not the opposite of speed. It is what allows speed to remain intelligent.
The question for a scaling hotel market
As hotel development scales, the industry will naturally focus
on sites, brands, capital, demand, key count and speed to market. Design
management deserves to sit alongside those discussions because growth magnifies
interface risk.
The question is not whether each specialist is competent. It is
whether the system connecting them is strong enough to carry reliable decisions
from brief to operations.
That is the territory I will explore in the next series of
Design Management Field Notes: governance chains, stage gates, Room Data
Sheets, tracker ecosystems and opening readiness — not as paperwork, but as
controls that protect the operating asset.
