A demand calendar with thirty events all marked "important" is a list, not an instrument. The score is what turns an event row into a pricing decision — and it's also where calendars quietly go wrong, because every event feels "high impact" to somebody. The festival has passionate fans, the organizer has a press release, the sales manager has a friend on the committee. Here is a scoring method anchored to the only thing that matters: observable effects on hotels.
Skip abstract definitions ("major event", "significant draw"). Define each tier by what it visibly does to the market, so two people scoring the same event reach the same answer:
| Score | Observable definition | What you do about it |
|---|---|---|
| High | Citywide compression: the comp set sells out or market rates spike 25%+ over the seasonal norm on those nights | Rate strategy, stay restrictions, group caps — positioned months out |
| Medium | Measurable pickup lift on specific nights or segments, but the city doesn't sell out | Watch the dates weekly; adjust rates when pace confirms |
| Low | Atmosphere, press, local buzz — no measurable room-night lift | Note it and move on; never restrict on a low |
The discipline: an event only earns "high" if you can point to the compression it caused (or credibly will cause), not to its cultural importance. A beloved street festival attended by 200,000 locals who all sleep at home is a low, however famous it is.
First editions and far-out announcements have no track record, so score with proxies and flag the uncertainty: announced attendance × a realistic overnight share, measured against city room supply; venue capacity (an 80,000-seat stadium act implies a different room-night wave than a 3,000-seat hall); whether the organizer is blocking hotel rooms (room blocks are the honest tell — organizers don't contract rooms for day-trippers); and what comparable events did in comparable cities. Score conservatively, mark the entry for re-scoring, and let the first edition's actuals promote it.
Scoring is a loop, not a stamp. After each edition, compare actual pickup on those dates against baseline — the same discipline as the weekly calendar review, applied backward. Promote what compressed, demote what didn't, and write the number into the event's note ("2026 edition: +18pts occupancy, ADR +31% — confirmed high"). Two editions of data make a score trustworthy; five make it bankable.
Every event in our city calendars carries a high/medium/low rating assigned by exactly this logic — room-night volume against that city's supply, overnight vs day-trip audience, and overlap with neighboring drivers — with the reasoning written into each event's note and unconfirmed editions explicitly flagged for verification. The full scoring worksheet is included in the DIY Demand Calendar Pack ($29) alongside the build method from the complete guide; or have Demand Calendar Pro ($99/year) deliver your market researched, scored and refreshed quarterly, so your team argues about rate moves instead of adjectives.