Skip to content

GuidePricing & revenue management

Weekly revenue management: a system for small hotels

A hotel with 10 to 40 rooms has no revenue manager, but faces the same questions as a large property: is the Saturday six weeks away too cheap, or is Tuesday too empty? This guide is for owners and hotel managers. We explain how to use a fixed weekly review to turn metrics into decisions.

STRYK editorial teamUpdated 11 min read

In short

In a small hotel, revenue management is a fixed weekly routine lasting around 30 minutes. On the same day each week, you check occupancy, average daily rate (ADR), revenue per available room (RevPAR) and incoming bookings for the next eight weeks. You compare them with the previous week and the previous year, then make no more than two decisions about prices, minimum stays or booking restrictions. Record each change and assess it the following week.

Key points

  • A fixed weekly review is more useful than a detailed quarterly analysis because you can respond to demand while there is still time to sell rooms for the date.
  • Four metrics are enough: occupancy, ADR, RevPAR and incoming bookings (pickup) for the next eight weeks.
  • Every unusual result needs a dated decision. Without a record, you cannot check the following week whether it worked.
  • You can adjust more than the room price: minimum stays, arrival restrictions, rate conditions and channel availability.

What revenue management means in a small hotel

Revenue management means continually adjusting prices, availability and booking conditions to maximise the revenue from each room. In a hotel with 24 rooms, that does not mean operating a piece of software. It means reviewing bookings once a week and making targeted changes.

Two metrics provide the foundation. Average daily rate (ADR) is room revenue divided by the number of room nights sold. Revenue per available room (RevPAR) is room revenue divided by all available room nights. It combines price and occupancy in one figure, so a high price in an empty hotel does not look like a success.

This guide expands on the short introduction in the pricing playbook. For the principles behind dynamic pricing, see the guide to dynamic pricing.

The weekly 30-minute routine

Hold the review on the same day every week, preferably Monday morning. The weekend's accounts are complete and you know which arrivals to expect in the new week. Tie it to an existing appointment, such as the team meeting, and you will keep it up during peak season too.

The order matters: first the week just ended, then the weeks ahead, then the decision. Starting with the future makes it too easy to justify price changes on a hunch.

The weekly revenue management instructions explain this routine in STRYK: each week, you review and adjust prices, rules, channel markups and recommendations.

Six steps with time allocated to each

  1. Close the previous week (5 minutes)

    Enter occupancy, ADR and RevPAR for the last seven days in your table. Result: a new row to compare with the previous week.

  2. Review incoming bookings for the next eight weeks (10 minutes)

    Record the number of rooms booked for each weekend and weekday, alongside the previous week's figures. Result: you can see which dates are gaining bookings and which are stalling.

  3. Compare with the previous year (5 minutes)

    Check the position at the same point last year. For each difference, ask whether a trade fair, festival or building works explain it. Result: a list of dates with notable differences.

  4. Review channels (3 minutes)

    Compare how direct bookings, booking platforms and telephone bookings have developed. Result: an indication of whether a channel is bringing in unusually many or few bookings.

  5. Make no more than two decisions (5 minutes)

    Choose the two dates that need priority attention and select one adjustment for each. Result: two entries in the log, with the date, adjustment and expected outcome.

  6. Apply and record changes (2 minutes)

    Apply the price or restriction in the calendar and on every channel. Result: the log contains the old and new values.

Which metrics you need and what to do with them

A metric is only useful if it leads to a decision. The table below links each figure to a question and a possible action. Anything that does not answer a question has no place in the weekly table.

The weekly table itself is small: one row per week, four columns for past results and one column for the number of rooms booked for each upcoming weekend. An export from your PMS and a spreadsheet are enough.

Four metrics that each inform a decision
MetricQuestion to askPossible decision
OccupancyHow full was the hotel, and on which days were rooms left empty?Relax the minimum stay, offer a deal for empty weekdays
ADRWhat was the average price of the rooms sold?Raise the category's base price or limit discounts
RevPARDid price and occupancy together produce more revenue than the previous week?Check the overall effect of a price change
Incoming bookings (pickup)How many booked rooms have been added for a given date since the previous week?Raise or hold the price, or set restrictions

A weekly example with the calculations

Hotel Nordlicht has 24 rooms, giving it 168 available room nights over seven days. Suppose 109 of them are sold and room revenue is €12,535, excluding breakfast, tourist tax and VAT.

Occupancy is 109 divided by 168, or 64.9%. ADR is €12,535 divided by 109, or €115. RevPAR is €12,535 divided by 168, or €74.61. As a check: €115 multiplied by 0.649 also gives around €74.61.

These figures are a worked example. Use your own results from the previous week and the previous year as your benchmarks, not an average from other hotels.

How to interpret pickup and pace

Pickup is the number of rooms added to bookings for a given date since an earlier point in time. It shows the speed of demand, not just the number of rooms booked. Two dates with nine rooms booked each look alike, but their positions are very different if one has gained nothing for a week and the other has gained six rooms in three days.

Pace compares the current booking position with the position at the same point in the previous year. Read both figures together: pickup tells you whether bookings are coming in now, while pace tells you whether that is enough for this time of year.

How far ahead should you look?

An eight-week window is enough for a hotel serving holiday guests. Look further ahead for weekends with high demand: event calendars and school holidays in your guests' home markets identify dates you should start watching in spring. City hotels with short booking lead times focus on the next four weeks and check the coming ten days daily.

The shorter your guests' booking lead time, the shorter the window. You can see that lead time by sorting your last twenty bookings by booking date and arrival date.

Adjustments and rules for your decisions

Revenue management involves more than price changes. Price is an obvious factor to adjust, but minimum stays, arrival restrictions, rate conditions and channel availability often have a greater effect. They change the type of demand without lowering the price.

Set simple rules in advance so you do not have to start from scratch for every date on Monday. These rules are starting points and should be adapted to your own hotel after a few months.

Starting rules: observation, adjustment, review
ObservationAdjustmentReview the following week
Strong pickup, bookings ahead of last yearRaise the category's price graduallyAre bookings still coming in at the new price?
Weak pickup, bookings behind last year, no explanationRelax the minimum stay before lowering the priceHas pickup increased?
Weekend almost full, Friday or Sunday emptySet a two-night minimum stay or close Saturday to arrivalsAre gaps either side of the weekend being filled?
Tuesday and Wednesday consistently emptyWeekday offer or a two-night packageHow many rooms did the offer bring in, and at what ADR?
One platform supplies almost all bookingsReview the direct booking price and selectively limit availability on the platformHas the share of direct bookings changed?

One change at a time for each date

Make one adjustment per date per week. If you change the price and minimum stay at the same time, you will not know the following week which one worked. A log of the old and new values lets you trace the effect.

Make price changes in the same source that supplies prices to every channel. If you also change prices directly in a platform's extranet, after a week you will have two different prices and no clear overview.

Set limits you will not cross

Set a minimum price for each category that you will not go below, even when demand is weak. Base it on your costs per occupied room and the channel's commission. The guide to net ADR after commission covers the latter.

Also set a cap on weekly price increases, such as five per cent. This protects returning guests looking up your website from sudden price jumps.

Put comparisons with other hotels in context

Comparing with nearby hotels helps when your own figures fluctuate. Choose three to five hotels with a similar category and location as your competitive set. You do not know the prices their guests actually booked, but publicly advertised prices for selected dates indicate the trend.

Record these prices only at fixed intervals, such as every other Monday, and for the same stay dates. Advertised prices are not achieved prices: a hotel can display a high price and remain empty. Use the figures as an indication, never as a template.

The guide to the RevPAR index for your competitive set explains how to measure your share of the group's revenue using a RevPAR index.

Build your routine in four weeks

Start small. One table, one appointment and two decisions per week are enough. Expand the routine only once the appointment has become a habit.

The following list sets out your first four weeks. If, after the fourth week, you find that some points do not suit your hotel, remove them.

A starting plan for the first four weeks

  • Week 1: set the day and time, create the table and add the previous four weeks' figures
  • Week 1: record the calculation basis for ADR and RevPAR (including or excluding breakfast, tourist tax and VAT)
  • Week 2: enter the rooms booked for each weekend over the next eight weeks and compare with last year
  • Week 2: set the minimum price for each category and a weekly cap on increases
  • Week 3: log the first two decisions with the old and new values
  • Week 4: review the effect of the decisions and adjust the starting rules in the table

Frequently asked questions

How often should a small hotel review its prices?

Once a week is enough for most hotels. During peak season or when guests book shortly before arrival, it is also worth taking a quick look at the next ten days, for example daily. A fixed appointment with a log matters more than frequency.

What is the difference between ADR and RevPAR?

ADR is the average price per room sold, while RevPAR is revenue per available room. RevPAR accounts for empty rooms; ADR does not. A high ADR with low occupancy can therefore mean a low RevPAR.

Do I need revenue management software?

No. A PMS export and a table are enough for the weekly routine. Software becomes worthwhile when you manage several categories, many dates or channel synchronisation, and transferring data into the table takes too much time.

Should I lower the price if a date is selling poorly?

Not as your first step. Check whether there was a special event last year, and relax the minimum stay or booking restrictions first. Lower the price only if pickup still fails to materialise after a week, and never go below your minimum price.

How can I tell whether a price change worked?

Compare pickup in the following week for the same date with pickup before the change. If bookings are arriving faster and the week's RevPAR is above the previous value, the change has worked. Without a log of the old and new values, you cannot establish this.

Test STRYK with your real hotel day

14 days free, no setup fee. We set up your rooms, rates and first workflows together with you.