A strong event in your city is the easiest money of the year and the easiest money to lose. A trade fair, a stadium concert, a marathon or a long weekend can push the market rate to two or three times your normal level. The hotel that saw it coming sells those nights at the event price, with the right length of stay, through the channels it chooses. The hotel that reacts the same day sells them at last year's rate, watches the competition raise prices around it, and then tries to raise its own after the rooms are gone. What follows is a wave of cancellations and rebookings at whatever price the market is paying that afternoon.
The difference between the two hotels is not information. Both had the same calendar available. The difference is preparation: the rate, the restrictions and the channel plan were decided with two weeks of margin, or they were not.
This is the process for that preparation, from the annual calendar to the review after the event. It is written for an independent hotel working with a PMS and a channel manager, without a revenue management system.
Who this is for
Revenue managers, hotel directors and reservations teams at independent hotels in cities with a real events calendar: fairs, congresses, concerts, sports, festivals, public holidays and long weekends. It also applies to short term rental operators with more than a handful of units in the same city.
What you need before you start
- The calendar of your city for the next twelve months: venue calendars, the convention bureau, the fairground, the stadium, the public holiday list and the school calendar. Most of it is public and free.
- The pickup history of the last comparable event: how many rooms you had on the books at 60, 30, 14 and 7 days before arrival, and the ADR of each block of bookings. If you did not save it, start saving it today; the next event is the first one you will manage with data.
- A rate shop of the compset for the event dates, refreshed at least weekly from 30 days out and daily from 7 days out.
- The list of restrictions your channel manager and your booking engine actually support: minimum length of stay (MinLOS), MinLOS on arrival, closed to arrival (CTA), closed to departure (CTD), rate plan closures and allotment by channel. Not every channel supports every restriction, and you need to know which before the event, not during it.
- Your contracts: negotiated corporate rates, tour operator allotments and group blocks that touch the event dates, with their blackout dates and release dates.
The process, step by step
Step 1. Build the demand calendar from day zero
The demand calendar is the base of everything else. It is a simple table, one row per date, with the event, its expected strength, the nights it compresses (including the night before and the night after), and the rate level you intend to sell. You draw it once a year when you plan the budget, and you update it every month.
Three details separate a useful calendar from a decorative one. First, the weekday matters as much as the date: a public holiday on a Monday or a Friday makes a long weekend; the same holiday on a Wednesday can break the whole week. Second, an event that changes dates moves revenue between months, and your forecast and budget have to move with it, or you will chase a February figure that already happened in January. Third, the calendar has to be visible to whoever answers a group request or a corporate quote, because a block that looks fine in a quiet week is a disaster on a compression night.
Step 2. Classify each event by compression
Not every event deserves the same treatment. Ask three questions per event: how much of the city's inventory does it absorb (a citywide congress versus a local concert), how certain is it (a fair with fixed dates versus a match that depends on a draw), and which nights does it really compress. A three day fair usually compresses the two nights in the middle and leaves the arrival and departure nights soft. Your rate and your restrictions are set per night, not per event.
For each event write down the expected ADR at the peak night and the shoulder nights, based on what you closed at last time and what the compset is already quoting.
Step 3. Set the event rate with two weeks of margin, in steps
The rate for the event dates has to be loaded before the pickup starts, not after. Pricing after the pickup means your first bookings, often the ones with the longest lead time and the best channels, went out at the normal rate.
Load the event rate in levels. Start at the level you closed at last edition, and define in advance the triggers that move it up: a percentage of occupancy on the books at a given number of days before arrival. Raise in steps of 10% to 15% as pickup confirms the demand, never in one jump on the day the event is announced. A single 100% increase has two costs: guests who booked at the higher rate and see it drop later cancel and rebook cheaper, and guests who booked at the lower rate before the jump have already taken the rooms you wanted to sell at the peak.
If the event has flexible cancellation bookings on the books at the high rate, dropping the price later is the most expensive thing you can do. The market watches every change.
Step 4. Protect the nights with restrictions, not just with price
Price alone does not protect a compression night. A one night booking on the peak night at the peak rate can block a three night booking that would have covered the soft nights around it.
- MinLOS through the peak night: any stay that touches the peak night must be at least two or three nights. This is the restriction that makes the shoulder nights sell.
- MinLOS on arrival, where the channel supports it: applies the minimum only to stays starting that day, so you still accept a guest arriving two days earlier for a short stay.
- CTA on the peak night when you want arrivals before it, and CTD on the night after when you want departures later.
- Close the discounted rate plans (early booking, packages, long stay promotions, mobile rates) on the event dates. A promotion that runs on a compression night is a discount on the rooms you were going to sell anyway.
- Reduce the allotment on the online travel agencies to one or two rooms and keep the rest for the direct channel and the desk. On a night where demand exceeds supply the last rooms should carry the lowest distribution cost.
- Check your contracts. A negotiated corporate rate with no blackout dates will send you rooms at the contract price while you sell at three times that online. Blackout dates or a rate ceiling for event periods are written into the contract at signature, not improvised the week before.
Step 5. Read the pickup every day against the last edition
From 30 days out, compare the rooms on the books with the same point before the last comparable event, at the same days before arrival. If you are ahead, apply the next price level. If you are behind, look at the rate shop before touching the price: the most common mistake in an event week is a hotel dropping its rate because it was behind pace at 20 days, when the demand for that event books in the last ten.
Hold your nerve on the last rooms. When occupancy on the books for the peak night is above 90%, your last rooms should sit above the compset line, not below it. If those rooms sell, they sell at the best rate of the year. If they do not, you have lost a few rooms on a night where the hotel was already full.
Step 6. Manage the last week as an operation, not a spreadsheet
In the last seven days the job changes. Confirm the guaranteed reservations and the arrival times, review the group blocks and release what the group has not picked up, and set your overbooking for the peak night with real data on cancellations and no-shows. Event nights behave differently from normal nights: guests who paid a non-refundable rate for a concert arrive. Be more careful with overbooking on those nights than on a normal Tuesday. How to calculate it is the subject of the next piece this week.
Step 7. Record what happened before you forget it
The day after the event, save the pickup curve, the ADR by block of bookings, the cancellations by channel, the number of no-shows and the rate the compset closed at. That file is what makes the next edition a decision with numbers instead of a memory. Fairs that used to book six weeks ahead now book in two; a calendar that is not updated with that shift will make you raise the price at the wrong moment next year.
Situations you will meet, and what to do
- A second date is announced. The first concert filled the city the day it was announced; the second one is where the disciplined hotels made the year. Load the second date in the calendar the same hour, apply the same rate levels and restrictions, and check the compset before the end of the day.
- The event moves to another month. Move the expected revenue in the forecast and the budget, and tell whoever reads the monthly report why one month is up and the next is down.
- A group asks for a block on the event dates. Run the displacement: the rooms the group takes are rooms you would have sold at the event rate. A group rate that looks generous in a quiet week is a loss on a compression night. If you take it, tie it to a deposit and a cut-off well before the event.
- A corporate account with a fixed rate wants ten rooms on the peak night. If the contract has no blackout dates, you honour it; that is the cost of a contract signed without the revenue department. Fix it at the next renewal with blackout dates or a rate ceiling for event periods.
The three mistakes that ruin an event
- Reacting the day the demand appears. The rate and the restrictions were not loaded, the first bookings went out at the normal price, and every later change generated cancellations.
- Pricing the event without restrictions. The peak night filled with one night stays at a good rate and the shoulder nights stayed empty.
- Dropping the rate at 20 days because the pickup looked slow, when the event's booking window had not opened yet.
How do you price a hotel for a big event in the city?
A hotel prices a big city event in three moves, all before the pickup starts. First, the demand calendar: one row per night of the year, with every fair, concert, match and long weekend and the nights each one compresses. Second, the rate in levels: the event rate is loaded two weeks or more before bookings begin, starting at the ADR closed at the last edition and rising in steps of 10% to 15% as occupancy on the books confirms demand. Third, the restrictions: a minimum length of stay through the peak night so the shoulder nights sell, discounted rate plans closed on those dates, one or two rooms left on online travel agencies, and blackout dates in corporate contracts. From 30 days out, pickup is compared with the last edition at the same days before arrival, and the last rooms stay above the compset rate once the peak night passes 90% on the books. Raising the rate after the rooms are sold produces cancellations, not revenue.
Check your work
You have done this well when every event of the next twelve months has a row in the calendar with its rate level and its restrictions loaded in the channel manager, when the rate on the peak night moved up at least twice before the last week, when the shoulder nights closed above their normal ADR, and when the day after the event you have a file with the pickup curve to use next year.
This content was created with the help of artificial intelligence and reviewed by Rafael Osborne (Profit Guest Services) before publishing.
