Occupancy and ADR Sensitivity: Stress-Testing Your STR's DSCR

Why stress-testing is different from just being conservative upfront

Building a conservative base-case projection is good practice, but it only tells you one number. Sensitivity testing goes a step further: it asks specifically how much your DSCR moves if occupancy comes in a certain amount below your base case, or if ADR does, or if both move against you at once. That gives you a range, not just a single point estimate — and a range tells you how much margin for error the deal actually has.

Recall that revenue is built from ADR × occupied nights (see /learn/understanding-adr-occupancy-revpar-definitions/ for the full breakdown of these building blocks). Because both variables multiply directly into revenue, a modest simultaneous dip in both can produce a larger combined effect on the bottom line than moving either one alone.

This is worth internalizing precisely because it's counterintuitive at first glance. A modest dip in occupancy alone and a similarly modest dip in ADR alone each reduce revenue by roughly that same percentage individually. But if both happen together, the combined effect on revenue is somewhat larger than either single change, since the two reductions compound against each other rather than simply adding. It's a small mathematical detail, but it means a mild-sounding double dip can hurt more than intuition suggests.

It's also worth thinking about why occupancy and ADR often move together in the real world rather than independently. A softening market tends to pressure both at once — guests become more price-sensitive, which pushes owners to lower rates, and overall demand can soften at the same time for the same underlying reasons (a weaker travel season, new competing supply nearby, a broader economic slowdown). That correlation is exactly why testing a combined downside scenario is more realistic than testing each variable in isolation and assuming the other will hold steady.

How to set up a basic sensitivity check

There's no universally correct amount to shave off each variable for the downside case — the right size of the haircut depends on how volatile the specific market and property type tend to be. The point of the exercise isn't landing on a precise number; it's seeing whether your DSCR stays above the level you're comfortable with even when the assumptions aren't perfect.

It can also help to run a version of this test using your actual monthly seasonal curve rather than a single flat annual number, if you have one available (from a market-projection tool's seasonality breakdown, for instance). Applying the same downside percentage to each individual month, rather than to the annual total, shows you whether your weakest months specifically would still hold up under a downside scenario — which is often the more useful question than how the annual average holds up.

What to actually do with the result

If your combined downside scenario still keeps DSCR in a range you're comfortable with, that's useful confirmation that the deal has real margin for error built in. If the combined downside scenario pushes DSCR uncomfortably low or below 1.0, that's valuable information to have before closing rather than after a slow season arrives — it might change your offer price, your down payment, or whether you proceed with the deal at all.

It's also worth revisiting this same exercise periodically after you close, not just once before the purchase. Market conditions, comp set performance, and your own operating results all evolve, and rerunning a simple sensitivity check once or twice a year is a low-effort way to catch a deteriorating trend before it becomes a real cash flow problem, rather than being surprised by it at your next renewal or refinance.