What Hotel Revenue Managers Know About Events That Marketers Don't
There is an industry that has quietly understood something about events that almost nobody else has: hotel revenue management.
A revenue manager does not care what a conference is about. They care that eight thousand people will need beds in a specific city on specific nights, that a proportion will fly in, and that the ones flying in behave differently from the ones driving across town. Get that right and you price correctly. Get it wrong and you either leave money on the table or sit empty during the busiest week of the year.
They worked this out because their business is unforgiving about it. Everyone else's business is affected by the same thing and has never had to notice.
Events are a demand signal for far more than hotels
Once you see the pattern, the list of businesses whose demand moves with events is long: restaurants, transport, retail near venues, out-of-home advertising, staffing, parking, local services. Anyone whose customers are physically present in a place has a demand curve that events shape — often more sharply than weather or season.
Yet outside hospitality, almost nobody plans against it. Most businesses discover a major conference in their city by noticing the traffic.
Why the signal was hard to use
Knowing there is an event is easy. Any calendar has that. The hard parts are three:
How many people, really. Advertised attendance is a marketing figure. What matters is a defensible estimate, computed on the same basis for every event.
Where they are coming from. Ten thousand locals and ten thousand international visitors produce entirely different demand. One fills restaurants; the other fills hotels, airports and taxis. This is the distinction hospitality learned first and most of the economy still misses.
What overlaps. Three medium events in the same week produce a different peak than one large one, and neither is the sum of its parts — attendees overlap, venues compete, and the compounding is not linear.
How we model it
We separate two things that are usually conflated.
Demand Impact describes one event: the pressure a single event creates at its location, from expected footfall, the audience's composition, and how much of it is travelling in.
Demand Score describes a place on a date: the composite of every event active there that day, with overlap accounted for rather than summed. It is the number that answers "what is coming, and which days will peak."
The distinction exists because we saw the two conflated and producing contradictions — an event that looked significant on its own, in a week where three others made it marginal.
What it is not
It is not a forecast of your revenue. It says demand is arriving; what you do with it depends on your pricing, capacity, staffing and the hundred local factors we cannot see.
It is also an estimate, labelled as one. Attendance figures beyond today are modelled from history and stated as forecasts, never presented as fact. Where our record of a city is thin, the honest output is a gap with its reason rather than a confident number.
The wider point
The reason this signal has been underused is not that it is weak. It is that it lived in an industry that treated it as operational trivia — the conference calendar taped to a revenue manager's wall.
It is a leading indicator of physical commercial activity, available before it happens, for every city with a meaningful events calendar. Hospitality got there first because their business punished them for missing it. Everyone else has simply been absorbing the variance without naming it.
Calculate your Share of Presence at whr.ai.