Occupancy, ADR, and RevPAR all tell you what happened. Pacing tells you what's about to happen. It's the only forward-looking metric in a standard STR analytics stack, and it's the one that gives you time to act before a weak month becomes a done deal.
What pacing means
Pacing compares how many nights are booked so far in a period against how many were booked at the same point in a prior period. If it's June 10th and you have 18 nights already booked for June, but on June 10th last year you only had 14 nights booked for June — you're running ahead of last year's pace.
Today is June 10th. You have 18 nights booked for June.
On June 10th last year, you had 14 nights booked for June.
Pacing: (18 ÷ 14) − 1 = +28.6% ahead of last year
Why pacing is different from occupancy
End-of-month occupancy tells you what happened. By then, there's nothing you can do about it. Pacing is a mid-period signal — it tells you where the month is tracking while you still have weeks left to influence the outcome.
The difference is meaningful. If you check your June numbers on July 1st and discover you were 15% behind last year, that's information — but the opportunity has closed. If you check pacing on June 10th and you're 15% behind, you can drop your nightly rate, reduce minimum stay requirements, or push a promotion through your channels. You have 20 days to close the gap.
Pacing is the metric that separates operators who respond to performance from operators who can only react to it after the fact.
What to compare pacing against
Same period last year
Year-over-year pacing is the most commonly used comparison. It accounts for seasonality — comparing June pace to June, not to February. It tells you whether demand for this period is stronger or weaker than historical norm.
Same period last month
Month-over-month pacing is useful for spotting short-term momentum shifts. If March is pacing ahead of February but behind last March, you're improving but still below historical levels — a nuanced picture that neither comparison alone would show.
Your own portfolio average
For multi-unit operators, comparing a unit's pacing against the portfolio average helps identify outliers — units that are booking faster or slower than the rest, which might warrant a pricing adjustment or a listing review.
Reading the signals correctly
Ahead of pace — but be careful
Running ahead of pace sounds good, and usually is. But if you're tracking well ahead of last year early in the month, it may mean you've priced too low — demand is strong and you could be capturing more revenue per night. Consider raising rates on remaining open dates.
Behind pace — diagnose before acting
Running behind doesn't automatically mean you need to drop rates. First ask why:
- Is demand soft in the whole market? If competitor listings are also sitting open, it's a demand issue — rate drops may help, but listing promotion matters too.
- Are your rates above market? Check comparable active listings. If you're priced above them, a rate adjustment is the obvious fix.
- Have booking windows shifted? Some markets book further out than others. If last-minute bookings are your norm, being behind pace in week one of the month may not be meaningful.
- Did you change your minimum stay? A longer minimum blocks short-gap windows and reduces bookable nights — which shows up as slower pace even if demand is unchanged.
How far ahead to track pacing
Most operators track two pacing windows simultaneously:
- Current month — are we on track to hit this month's occupancy target?
- Next 30–60 days — are upcoming periods filling as expected, or do we need to adjust pricing now to influence bookings before the window gets too short?
The further out you look, the more volatile pacing becomes — a single large booking can dramatically shift a future period's numbers. Current-month pacing is more stable and more directly actionable.
Common questions
See your pacing automatically
BNBinsights tracks pacing alongside occupancy, ADR, RevPAR, and revenue — so you always know where the month is heading.
You're on the list.