Virtuosos of Price

Weekly Pricing Review

Pricing a short-term rental is not a one-time decision. Market conditions shift across the week as local events are announced, competitors adjust their calendars, and your own booking pace either confirms or contradicts the rates you set. A host who sets prices once a month and checks back in when something feels wrong is always reacting to information that is already stale.

The weekly pricing review exists to close that gap. It is a structured habit, not a crisis response. Done consistently, it gives you a record of what you decided, why you decided it, and what happened afterward. That record is the only way to tell whether your pricing logic is working or whether you are repeating the same mistakes in slightly different conditions.

What a weekly review actually is

A weekly pricing review is a fixed block of time, ideally the same day and time each week, in which you examine a defined set of data, compare it against your competitive set, identify any calendar windows that need attention, and record what you changed and why. The output is not just updated prices. It is a log entry that future-you can read.

The review has a scope. It covers roughly the next ninety days of your calendar, with the closest thirty days receiving the most scrutiny. Beyond ninety days, the data you have is thin enough that large adjustments are usually premature. Within the next two weeks, you are mostly confirming or fine-tuning decisions already made, because last-minute changes carry their own risks around guest expectations and search presentation.

A worked example of scope: you sit down on a Monday morning. You scan the next fourteen days for any gaps or anomalies that need immediate attention. You then work through days fifteen to sixty in detail, looking at pace, competitive positioning, and any events or demand signals you have learned about since last week. You note anything beyond sixty days that has changed materially, such as a new event announcement or a competitor leaving the market, but you do not reprice that window aggressively yet.

Checklist for defining your review scope before you start:

Confirm the date range you are reviewing (next ninety days, broken into the three bands above)
Open your Airbnb host dashboard and your pricing tool if you use one
Have last week's log entry open so you can compare what you expected against what happened
Note any external calendar events you have learned about since the last review

Data sources for the weekly review

Your review is only as good as the data feeding it. The sources fall into two categories: your own listing data, which you can read directly, and market signals, which require interpretation.

Your own listing data comes from the Airbnb host dashboard. The metrics available there include views, clicks, booking rate, and calendar occupancy. These are the numbers you control and can verify. If your dashboard shows a drop in views over the past seven days, that is a fact you can act on. If someone tells you that views dropped because of a pricing change, that is a hypothesis, not a fact, because the relationship between price and views is not publicly documented by Airbnb.

Market signals come from observing competitor calendars and rates directly. This means opening the Airbnb search results for your area, filtering to match your listing type and guest capacity, and recording what you see. It is slower than a data tool, but it is verifiable. You are looking at the same interface your potential guests see.

What to record from your own dashboard each week:

Views over the past seven days compared to the prior seven days
Booking rate (bookings divided by views, if your dashboard surfaces this)
Current occupancy for the next thirty, sixty, and ninety days
Any new reviews posted, because review content affects future guests' decisions
Any messages from guests that signal a pricing concern, such as questions about discounts

What to record from the market each week:

The lowest, median, and highest nightly rates among your five closest competitors for the next thirty days
Which competitors have gaps in their calendars that suggest they are not booking well
Which competitors appear fully booked, which may indicate their pricing is below market
Any new listings that have appeared in your competitive set since last week

Competitive set analysis

Your competitive set is the group of listings a potential guest would reasonably consider instead of yours. It is not every listing in your city. It is the listings that match your guest capacity, property type, general location, and amenity profile closely enough that a guest comparison-shopping would put them on the same shortlist.

Defining your competitive set is a judgment call, and it should be revisited every few months because the market changes. A new listing with a strong amenity profile can enter your set. An older listing that stops getting reviews may effectively leave it.

How to build your competitive set for the review:

Search Airbnb as a guest would, using the dates and guest count most common for your bookings.
Filter by property type and the features your listing offers.
Identify the five to eight listings that appear most similar to yours in the results.
Record their listing IDs or names so you can track the same set week to week.

Once you have your set, the analysis each week is a comparison of rates and availability. You are not trying to match the lowest price in the set. You are trying to understand where you sit in the range and whether that position is intentional.

A worked example: your listing is a two-bedroom apartment. Your competitive set has eight listings. Three of them are priced below you for the coming weekend. Two are priced above you. Three are fully booked. The three that are fully booked tell you something: either they priced correctly earlier in the week, or they are running a discount that is not visible to you. The three priced below you tell you something different: either they are trying to fill gaps, or their baseline is lower than yours for reasons you should understand (fewer amenities, older photos, fewer reviews).

Decision rule for competitive set positioning: if more than half your competitive set is priced below you and you have open calendar days in the next fourteen days, that is a signal worth investigating. It does not automatically mean you should lower your price. It means you should ask why the gap exists before deciding.

Performance metrics evaluation

Performance metrics tell you whether your current pricing is producing the outcomes you want. The three metrics that matter most for a weekly review are booking pace, occupancy rate, and lead time.

Booking pace is how quickly your calendar is filling relative to a prior comparable period. If your calendar at this point last month had more bookings for the equivalent forward window, your pace has slowed. If it had fewer, your pace has accelerated. You measure this by comparing your current occupancy for the next thirty days against what your occupancy looked like for the equivalent thirty-day window at the same point in previous weeks or months.

Occupancy rate is the percentage of available nights that are booked. You can calculate this yourself: count the booked nights in a given window, divide by the total available nights, and you have your occupancy rate for that window. Track this number week over week so you can see the direction of travel.

Lead time is how far in advance guests are booking. If your average booking is coming in seven days before the stay, you are operating in a last-minute market. If it is coming in thirty days out, you have more time to adjust pricing before the stay date arrives. Lead time affects how aggressively you should price in the near term versus the medium term.

What to record in your performance log each week:

Metric	This week	Last week	Four weeks ago	Notes
Occupancy, next 30 days	(calculate from calendar)	(from prior log)	(from prior log)	Note any events in window
Occupancy, next 60 days	(calculate from calendar)	(from prior log)	(from prior log)
Average lead time, last 5 bookings	(calculate from booking dates)	(from prior log)	(from prior log)
Competitive set median rate, next weekend	(from your search)	(from prior log)	(from prior log)
New reviews this week	(count from dashboard)	(from prior log)	(from prior log)	Note sentiment

The table above is the core of your log. Fill it in before you make any pricing decisions. The decisions should follow from what the table shows, not precede it.

Identifying pricing exceptions

A pricing exception is a calendar window where your standard rate logic does not apply. Exceptions fall into two categories: demand spikes and demand troughs.

Demand spikes are periods when more guests than usual want to stay in your area. Local events are the most common cause: festivals, sporting events, conferences, public holidays, and school holiday periods. During a spike, your standard rate is likely too low. Guests are willing to pay more, and if you do not adjust, you will fill your calendar early at below-market rates and turn away guests who would have paid more.

Demand troughs are periods when fewer guests than usual want to stay. Shoulder seasons, mid-week windows in leisure markets, and periods following a local event are common examples. During a trough, your standard rate may be too high, and you may be better served by a lower rate that fills the calendar than by holding firm and finishing the period empty.

How to identify exceptions during your weekly review:

Check a local events calendar for your area covering the next ninety days. Note any events that draw visitors from outside the area.
Look at your competitor calendars for the same window. If competitors are filling up faster than usual for a specific weekend, that is a signal of a demand spike even if you do not yet know the cause.
Look for mid-week gaps in your own calendar. If you have open Tuesday and Wednesday nights surrounded by booked weekends, that is a trough pattern worth addressing with a specific rate or minimum stay adjustment.
Check whether any of your competitors have raised their rates for a specific window. A cluster of competitors raising rates for the same dates is a strong signal of a demand spike.

Decision rule for exceptions: treat any window where your competitor set is behaving differently from the surrounding weeks as a candidate exception. Investigate before adjusting. If you can identify the cause (a specific event, a school holiday), you can price with more confidence. If you cannot identify the cause, adjust conservatively and monitor.

A worked example: you notice during your Monday review that three competitors in your set have no availability for a Saturday six weeks out, and two others have raised their rates for that same Saturday. You check a local events calendar and find a regional music festival announced last week. You had not yet adjusted your rate for that date. You raise it to sit at the upper end of your competitive set for that specific night, note the reason in your log, and set a reminder to check booking pace for that date in two weeks.

Documentation and strategic adjustments

The review is only useful if you record it. A pricing decision made without documentation is a guess you cannot learn from. Documentation does not need to be elaborate. It needs to be consistent.

Your log entry for each week should contain four things: what the data showed, what you decided, why you decided it, and what you expect to happen. The last item is the one most hosts skip, and it is the most valuable. If you write down your expectation, you can compare it against the outcome next week and start building a real understanding of how your market responds to your pricing.

What a complete log entry looks like:

Date of review
The metrics table filled in (as described in the performance metrics section)
A list of any calendar windows you adjusted, with the old rate, the new rate, and the reason
A list of any windows you considered adjusting but decided to leave, and why
Your expectation for the next seven days: how many bookings do you expect, and for which dates

Strategic adjustments are changes to your pricing logic rather than to individual dates. An example of a strategic adjustment is deciding to raise your base rate for all weekends because your competitive set has shifted upward over the past month. Another example is deciding to introduce a mid-week discount because your occupancy data shows a consistent pattern of mid-week gaps.

Strategic adjustments should be made deliberately and infrequently. If you are changing your base rate every week, you are reacting rather than managing. A useful rule: make tactical adjustments (specific dates, specific exceptions) every week. Make strategic adjustments (base rate, minimum stay rules, discount structures) no more than once a month, and only when your log shows a consistent pattern over at least three to four weeks.

Checklist before making a strategic adjustment:

Do you have at least three to four weeks of log data showing the same pattern?
Have you checked whether the pattern is seasonal (and therefore temporary) or structural?
Have you looked at your competitive set to confirm the market has shifted, not just your own performance?
Have you written down what you expect the adjustment to produce, so you can evaluate it in four weeks?

What this means in practice

The weekly review is a habit that compounds. In the first few weeks, you are mostly building your baseline: establishing what your competitive set looks like, what your normal occupancy pattern is, and what your typical lead time is. You cannot make good decisions without that baseline, so the early reviews are partly about data collection.

By the fourth or fifth week, you will start to see patterns. You will notice that your listing fills faster for certain dates than others. You will notice that specific competitors tend to price higher or lower than you in predictable ways. You will notice that your lead time changes as you approach peak periods. These patterns are the foundation of a pricing strategy.

A practical example of the review in a mature state: a host with a beach property sits down each Monday. She spends about thirty minutes on the review. She fills in her metrics table, checks her competitive set for the next four weekends, identifies two exceptions (a long weekend in six weeks and a mid-week gap in the next fourteen days), makes two tactical adjustments, and writes a three-sentence log entry. She does not change her base rate. She does not reprice the entire calendar. She makes two targeted decisions based on specific evidence and records them.

That is what a functional weekly review looks like. It is not a long process. It is a disciplined one.

Common failure modes to avoid:

Reviewing without recording. If you do not write it down, you cannot learn from it.
Adjusting prices without a stated reason. "It felt low" is not a reason. "Three competitors raised rates for this weekend and I have no bookings yet" is a reason.
Treating the review as a crisis response. If you only do the review when something seems wrong, you lose the baseline that makes the review useful.
Over-adjusting. Changing prices on every date every week introduces noise into your data and makes it harder to understand what is working.
Ignoring the log from prior weeks. The prior log is the most valuable input to the current review. If you are not reading it, you are starting from scratch every time.

Where this becomes someone else's job

If the weekly review is producing good data but you do not have the time or inclination to act on it consistently, that is a signal that the process needs a different owner.

Revande's Performance service covers the full software stack for dynamic pricing, with daily adjustments made by experienced rate strategists, Airbnb listing performance monitoring and email alerts for low visibility or booking conversion, and monthly reports. The review cadence described in this guide is built into that service, and the rate strategists are doing the analysis and adjustment work on your behalf.

Revande's Maestro service includes everything in Performance, and adds done-for-you listing optimization, proactive Airbnb listing performance monitoring with visibility and booking conversion issues handled for you, works with Airbnb or your channel manager, and ongoing listing refinements. If your weekly review is surfacing issues that go beyond pricing, such as listing presentation problems or conversion gaps, Maestro is the appropriate level of support.

The distinction between the two is not just scope. It is who does the work after the data surfaces a problem. Performance tells you and your strategist what is happening and adjusts rates accordingly. Maestro handles the downstream work so that pricing adjustments are not undermined by listing issues that were never fixed.

How to define your competitive set
Understanding your Airbnb host dashboard metrics
Minimum stay strategy for short-term rentals
Seasonal pricing adjustments: when and how to make them
How to read your booking pace and what to do about it

Get Started