The revenue manager's day, the reports that run a hotel, and how to meet well. 5 questions, with the answer first and the working after it.
What does a revenue manager do all day?
A revenue manager forecasts demand, sets and adjusts room rates, and decides which business to accept so the hotel earns the most revenue possible. A typical day starts with the pickup report and pace review, moves through rate adjustments for upcoming dates, competitor checks, and group or displacement decisions, and ends with updating the forecast. It is a daily rhythm of reading demand and acting on it.
The morning routine is near-universal: review overnight pickup, compare pace to last year and to budget, and scan the next 30 to 120 days for dates that moved. Where a date is tracking ahead, consider raising rate; where it lags, consider stimulating demand. This read-and-react loop over the demand calendar is the core of the job.
Beyond daily pricing, a revenue manager evaluates group and corporate requests (is this business worth the rooms it displaces?), maintains the forecast, manages channel and OTA strategy, and prepares for the revenue meeting. They sit between sales, front office, and marketing, translating commercial goals into concrete rate and inventory decisions.
Much of the day is spent assembling and interpreting data — pulling numbers from the property management system, channel manager, and market sources into a picture they can act on. The higher-value part is judgement: deciding what the numbers mean and what to do. Reducing the assembly time is what lets a revenue manager spend more of the day on the decisions that matter.
What reports should a hotel revenue team produce daily, weekly, and monthly?
Daily: a pickup and pace report plus the latest on-the-books position. Weekly: a forecast update, a pace-versus-last-year and versus-budget view, and a competitor rate check from the hotel rate-shop feed. Monthly: a full performance review against budget with RevPAR, ADR, occupancy, rate-position context, and segment analysis. The cadence matches the decision — daily for pricing moves, monthly for strategy and accountability.
The daily pickup report is the workhorse. It shows what booked since the previous update, by date and ideally by segment, so the team can react to dates that heated up or stalled overnight. Alongside it, an on-the-books position for the coming weeks and months gives the base for every pricing decision that day.
Weekly reporting zooms out: how does pace compare to last year and to budget across the next few months, where are the gaps, and what are competitors doing on key dates. Monthly reporting closes the loop — actual RevPAR, ADR, occupancy, and comp-set penetration (MPI, ARI, RGI) against budget, with segment detail to explain what drove the result.
The reporting burden is real, and manual assembly eats the time that should go to analysis. RevPerfect can automate the daily pickup report from validated exports supplied by supported hotel systems, so the team starts from a ready view instead of building it by hand. The judgement layer — reading the reports and deciding — stays with the revenue team.
A revenue meeting is a regular (usually weekly) session where the commercial team reviews demand, pace, and forecast, then agrees pricing and inventory actions for upcoming dates. Attendees typically include the revenue manager, general manager, sales, and front office. A good one is short, data-led, and ends with specific decisions and owners — not a status update.
The purpose is decisions, not reporting. Walk in with the numbers already assembled — pace versus last year and budget, pickup trends, the demand calendar with events, competitor rates, and any group or displacement questions — so the meeting time goes to judgement and action rather than reading data aloud. Circulate the pack beforehand where possible.
A workable agenda: review last week actuals versus forecast, walk the next 30 to 90 days by date and flag anything off-pace, decide rate and restriction changes, review group and corporate requests, and confirm channel or promotion actions. Keep it to 30 to 45 minutes; if it runs long, it has drifted into reporting.
The output is a short list of agreed actions with owners and dates. Assembling the meeting pack is often the bottleneck. Platforms such as RevPerfect generate a daily brief from a hotel’s own data, which can seed the pack so the team debates decisions rather than building slides. The strategic calls remain with the team.
Overbooking is deliberately accepting more reservations than you have rooms, to offset expected cancellations and no-shows so you do not end the night with empty, unsellable rooms. Done with a disciplined forecast it protects revenue; done carelessly it leads to walking guests, which is costly and damaging. The right level is driven by your own no-show and cancellation history, not guesswork.
The logic is that cancellations and no-shows are near-certain, so selling exactly to capacity leaves rooms empty when some bookings fall away — revenue you cannot recover. If history shows you average, say, four no-shows on a typical night, selling a few rooms over capacity fills that predictable gap. The key word is predictable: overbooking works only where the wash is reliable.
The cost side is walking guests — turning away someone with a valid reservation because everyone showed up. Walking means paying for a room at another hotel, transport, and real reputation damage, especially with loyalty members or during high-demand periods when nearby rooms are scarce and expensive. One bad walk can cost far more than the room you saved.
Set overbooking from data, not habit: your no-show and cancellation rates by day of week, season, and segment, plus a buffer for high-risk nights. Many hotels overbook modestly on normal nights and not at all on sold-out peak dates where a walk would be catastrophic. Review actual walks and adjust — the aim is zero empty rooms and zero walks, in balance.
What is group displacement?
Group displacement is the transient business you turn away by accepting a group booking that fills rooms you could have sold to individual guests, often at a higher rate. Displacement analysis compares the group total value against the revenue it displaces, so you only take group business that beats what those rooms would otherwise earn — including non-room spend.
On a soft date, a group is pure upside — it fills rooms that would sit empty. On a high-demand date it is a trade-off: every room in the block is a room you cannot sell to transient guests who may pay more. Displacement analysis puts numbers to that trade so the decision is not a gut call.
The comparison must be like-for-like and total. Weigh the group room revenue plus meeting space, catering, and other spend against the forecast transient revenue for the same rooms (at the rate you would realistically achieve, not the rack rate). Include wash — groups rarely pick up the full block — and the cost of any transient business you formally turn away.
The frequent mistake is judging a group on room rate alone and rejecting profitable business, or accepting a low-rate block on your best date and displacing higher-value transient. A conference paying a modest room rate but filling banqueting can beat the rooms-only alternative; a bare-rooms group on a peak weekend usually does not. Let the total-value comparison decide.
