What does a hotel revenue manager do? Duties and a weekly calendar

A hotel revenue manager decides what the hotel sells each night, to which segments, at what price and through which channels, then checks whether the result matched the plan. The job is the decisions: rates, restrictions, availability and mix. Reports exist to support those decisions, not to replace them.

A hotel hires a revenue manager, and six weeks later the sales manager still sets group rates, the general manager still approves every discount, and the new person produces reports nobody acts on. The hire was not the problem. The role was never defined. This article defines hotel revenue manager duties for the person who has to write the job description and judge the work: the decisions the role owns, the decisions it shares, the reports it signs off, and what its week actually looks like.

What does a hotel revenue manager actually do?#

A revenue manager chooses the mix of business a hotel sells across the calendar and the price and conditions attached to it, so that the whole month earns more than the sum of its best nights.

Start from the nature of the product. A room-night is perishable: a Tuesday in February that goes unsold is gone, and it cannot be stored for August. Revenue management is the practice of deciding, in advance, who gets which night at what price.

The role works four levers. Price, by room type, segment, channel and date. Availability and restrictions: stop-sell, closed to arrival, minimum stay, closed to departure. Mix: which segments and channels receive the rooms. And displacement: whether a group request is worth the rooms and the dates it takes.

The unit of output is a decision that changes something in the system. If no rate was loaded, no restriction was set, no allotment was released and no channel was closed, no revenue management happened that day, however many reports were read.

The role reads three inputs. First, what is on the books and how it moved. Second, what the market is doing: competitor rates, events, school holidays, flight schedules. Third, what the hotel can actually sell today: out-of-order rooms, room-type balance, a blocked floor.

Be equally clear about what the role does not do. It does not post charges, close the night audit, chase payment, write marketing copy or make sales calls. Confusing those tasks with revenue management is the most common hiring mistake, because they all touch the same numbers.

One trade-off has to be settled at hiring. Is the role measured on RevPAR, on total revenue, or on contribution after commission and cost to serve? Each answer produces different decisions, especially about online travel agency (OTA) mix and about group business.

Which decisions does the revenue manager own, share, or not touch?#

The role owns the nightly price and availability decisions inside limits the owner sets, shares group and contract pricing with sales, and does not touch refunds, compensation or house-use rooms.

Write the split down before the first day, in a table the general manager, sales and the revenue manager all sign. A verbal split lasts until the first disagreement, and the disagreement always arrives in high season.

The owner or GM sets the frame: a rate floor, a discount ceiling and a threshold in money above which a group or corporate rate needs approval. The revenue manager works freely inside that frame. The most common failure is a role that recommends everything and owns nothing; if every rate change needs a signature, the hotel has bought a reporting function and will get reporting speed.

State the escalation rule for the case where sales and revenue disagree on a group. Someone must have the final word, in writing: usually the GM above the threshold and the revenue manager below it. Front office executes the decisions, on restrictions, walk-ins, upgrades and no-shows. If front office can quietly override a minimum-stay rule, the rule does not exist.

Keep non-revenue decisions out of the role. Refunds, compensation for a bad stay and complimentary rooms are guest-relations and cost decisions, and mixing them into revenue blurs who is accountable for what.

Who does the revenue manager report to, and who has to work with the role?#

In a single hotel the revenue manager reports to the general manager; in a group, to a regional revenue director with a working line to the GM, and the hotel must state which of the two has the final word on price.

Reservations executes bookings. It usually does not report to revenue, but it must follow the rules revenue sets. The test is simple: can reservations override a restriction without telling anyone? If yes, the role is decorative.

Sales owns relationships and contracted volume; revenue owns the price and the displacement call. The two collide on group rates, and the money threshold from the decision table is what resolves the collision. Front office is the execution point for restrictions, upgrades and no-shows, and a five-minute daily handover between front office and revenue beats a monthly report that arrives after the dates have passed.

Housekeeping and engineering remove rooms from sale through out-of-order status, and the revenue manager needs that list daily, because a room out of order changes what the forecast is forecasting. In a small hotel the duty may sit with the GM or the reservations manager instead of a dedicated hire; that is a legitimate choice, but it should be made explicitly rather than by leaving the role vacant and the reports unread.

Groups add a second reporting line, and matrix structures fail quietly. Name the person who breaks a tie on price, and name the person who covers the role during leave. The same naming discipline matters across the whole hotel organisation chart, where departments, roles and decision rights are set out together.

What does a revenue manager's week look like?#

The week is one loop repeated at different horizons: read what changed, decide, load the decision into the system, then check that it took effect.

Every day starts with a short check, fifteen minutes or so: what came in overnight, what cancelled, which no-shows appeared, and whether any rate or restriction failed to load. A rate that was decided but never loaded is the most expensive kind of mistake, because nobody notices it until the month closes.

Monday reads the weekend, because the weekend is when the booking pattern for the coming weeks actually moves; the output is a short list of changes for the next fourteen days, each with a reason attached. Tuesday is the channel day: are the hotel's own website, the OTAs and the agencies showing the rates that were decided, and are the closed channels actually closed? Parity breaks are found by looking, not by assuming.

Wednesday belongs to sales, on the group and corporate pipeline. Each request gets a displacement check and one of three answers: accept, counter or decline, with the reason written down. Thursday looks further out, at thirty, sixty and ninety days, and adjusts the shoulder dates around events, holidays and flight schedules; rates changed on Thursday should carry the date they take effect. Friday closes the loop: what was decided this week, what happened to last week's decisions, and what goes into the log, the artefact the GM reads and the thing that makes the role judgeable later. A fuller version of this rhythm, with the meeting that carries it, is in our guide to the weekly revenue meeting.

What does the month add to the weekly rhythm?#

The month adds the forecast, the budget comparison and the contract and channel reviews, which are too slow to run weekly and too important to skip.

The rolling ninety-day forecast is rebuilt at least monthly and refreshed weekly. It should show what is on the books, what is expected to cancel, and what still has to be sold, by segment rather than as one total. The method behind it is covered in our guide to estimating the next 90 days from what is on the books.

Budget variance is reported with the reason, not only the number. A month below budget because a group cancelled is a different fact from a month below budget because the rate was cut too early, and the two lead to opposite decisions.

Contract work has a season in every market: tour operator allotments, corporate requests, agency agreements. The timing is set by the hotel's own market and should be written into the calendar rather than discovered each year. The channel review uses net revenue after commission and cost per booking, not gross; a channel that fills rooms at a high gross rate can still be the least profitable way to sell them.

Group business accepted last month gets a second look: did the rooms materialize, did the group displace better-paying business on those dates, and was the rate worth the space it took. The month ends with a one-page summary for the GM that asks for a small number of decisions, usually two or three, rather than presenting a wall of charts.

How do you judge a revenue manager's work?#

Judge the decisions and the record of them, not a single number, because the number is the outcome of the market, the weather, events and the mix the hotel already had on the books.

A good month can come from a bad decision and a bad month from a good one. If the hotel sold out because a city event filled the city, the revenue manager's contribution is what the rooms earned above what the event alone would have produced.

Ask for the log: what was decided, on what date, why, what was expected and what happened. A manager who cannot produce this is not managing; they are reacting and then explaining. Track forecast error over time rather than judging one forecast, because a forecast that is consistently optimistic in the same segment tells you something the monthly total never will.

Check execution separately from judgement. Were the rates live on every channel, were the restrictions loaded, did front office know? A correct decision that never reached the system has the same result as a wrong one. Look for self-review: the strongest signal is a manager who revisits their own past calls and says plainly which ones were wrong, and what they changed as a result. And be careful with a role judged only on RevPAR: it rewards filling the strong dates and can starve the weak ones, which is exactly where the marginal revenue sits.

What should the job description and the first 90 days contain?#

The job description should describe decisions, limits and outputs, and the first 90 days should be measured by whether the weekly loop and the decision log exist, not by the occupancy figure.

Open with one sentence of purpose, then list the decisions owned, the decisions shared, the reports signed off and the weekly rhythm. Leave out the tool list; software changes faster than the role does. State the authority in money: the rate floor, the discount ceiling and the threshold above which a group rate needs the GM. A limit written as a number can be applied; a limit written as "large groups" cannot.

State what the role is not, in one line, so that charge posting, night audit and marketing copy do not drift into the week. Name the person who covers the role during leave, and the person who breaks a tie on price; both absences happen in high season, when the decisions matter most. For structure and wording, see our template for writing job descriptions for hotel roles.

The first ninety days run in three blocks. Days one to thirty: learn the books, the segments, the channels and the system, and sit with front office and reservations. Days thirty-one to sixty: take over the weekly loop and start the log. Days sixty-one to ninety: own the forecast and present the first monthly pack with its decisions requested. Judge the ninety days by whether the log exists, whether the forecast is being used in decisions, and whether the rates the hotel decided are actually live. Those three are visible from outside the role, which is what makes them fair.

Before you write the advert#

Write the decision table first: what the role owns, what it shares, what it never touches, and the money limits around each. The job description, the weekly rhythm and the monthly review all follow from that one page, and so does your ability to tell a year later whether the hire worked.