Portfolio Operators
Portfolio-Wide Benchmarking: Start Learning Before Every Comp Set Is Perfect

Benchmarking gets harder when you are early. Maybe you operate ten parks, maybe twenty, maybe fifty. Some markets already have several comparable properties contributing data. Others have two. A few have nobody yet.
So what do you do? Wait six months for every local comp set to mature? No. You start with the data you already have: your portfolio.
Your Portfolio Is Already a Benchmark
Imagine you operate 12 RV resorts. One property finished July at 78% occupancy, a $142 ADR, and a $110.76 RevPAS. Your total portfolio averaged 84% occupancy, a $151 ADR, and a $126.84 RevPAS.
Even without a mature local comp set, you immediately know something. That property is trailing the broader portfolio. For RevPAS:
That gives the property a portfolio RevPAS index of 87. In plain English, it produced revenue per available site at roughly 13% below the portfolio benchmark.
Is the portfolio a perfect replacement for a local competitive set? No. Is it considerably more useful than flying blind? Absolutely.
Set Targets. Track the Trend.
A number means nothing without something to measure it against. Is 19% occupancy good or bad? That depends on what you're comparing it to: a target you set, a trend you've been tracking, or where this property stood a year ago.
That's why OHR lets you set a target for every park in your portfolio, not a generic number every property gets held to, but one specific to that park's market, size, and season. OHR also shows this month next to a property's trailing 1, 3, 6, and 12-month averages, so you can see not just whether you're up or down, but whether the trend is improving or sliding.
This month
19.3%
T1 avg
53.2%
T3 avg
55.8%
T6 avg
47.9%
T12 avg
24.7%
A month sitting well below every trailing window, 1, 3, 6, and 12 months, is worth a conversation on its own, before you even know the cause. Breaking it out by site type shows whether the whole park slid or one part of it did:
| This month | T1 avg | T3 avg | T6 avg | T12 avg | |
|---|---|---|---|---|---|
| Whole park | 19.3% | 53.2% | 55.8% | 47.9% | 24.7% |
| RV | 28.9% | 69.6% | 69.3% | 60.0% | 30.6% |
| Lodging | 21.3% | 71.7% | 72.7% | 61.2% | 32.5% |
| Tent | 3.0% | 14.7% | 22.6% | 19.6% | 10.0% |
Trailing averages tell you how a property is trending against its own history. Comparing to the same point last year tells you something else: whether a dip is normal seasonality or an actual shift. A property running 1,642 more occupied nights than it had at this point last year, and already ahead of where last year finished, is a very different situation than one that's merely keeping pace.
That's the real value of tracking it this way. Not just knowing this month's number, but knowing whether a property is on pace with the target you set for it, or quietly drifting off course before anyone notices.
Benchmarking Does Not Have to Be Perfect to Be Useful
There is a temptation with data to say: if we cannot build the perfect comparison, we should not compare anything. That sounds responsible. It can also waste a lot of time.
A Florida resort should not necessarily be judged against a seasonal campground in Michigan as though they compete directly. But portfolio-wide benchmarking can still uncover patterns: which properties consistently outperform, which ones lag, where ADR is unusually strong, which parks are filling too early, which properties struggle midweek, where booking pace looks different.
You may not have the final answer yet. But you know where to start looking.
Start Broad. Get More Specific.
Think of benchmarking as a zoom lens. At first, you might see the entire portfolio. As participation grows, you can move toward a regional portfolio, then property type, then local market, then eventually a true comp set.
Each level adds context. You do not throw away the earlier comparisons. You simply make them more precise.
A Portfolio Creates an Immediate Learning Loop
This is especially valuable for multi-property operators. Suppose three similar resorts in your portfolio are running 92%, 86%, and 74% occupancy.
That does not automatically mean the property at 74% has a problem. Maybe its market is softer. Maybe its season starts later. Maybe its rates are substantially higher. But it gives leadership a reason to investigate. That is useful.
Benchmarking does not always need to hand you the answer. Sometimes its job is to point at the right question.
Internal Benchmarking Can Reveal Best Practices
Portfolio benchmarking can also help operators identify what is working inside their own organization. Maybe one property consistently generates stronger ADR. Why? Maybe another books further in advance. Why? Maybe one region has significantly stronger Sunday-through-Thursday demand. What are they doing differently?
Now benchmarking becomes more than a scoreboard. It becomes a learning system. One park discovers something, the portfolio sees it, and other properties can test it. That is where data starts becoming operationally valuable.
Then the Local Market Makes It Better
As OHR participation grows in individual markets, local comp sets become increasingly useful. Now you can compare property versus portfolio, and property versus local market. Those two benchmarks can tell very different stories.
Maybe one resort trails your portfolio but dramatically outperforms its local market. Without the local benchmark, corporate leadership might think the property is weak. With market context, you may discover it is actually one of your best-managed assets. That is exactly why context matters.
Where OHR Fits
OHR does not need every local comp set to be fully mature before operators start learning. For portfolio operators, the first layer of value can come from understanding performance across their own properties, and across time. Then, as more market participation develops, the benchmarking gets progressively sharper.
Portfolio benchmark, then regional benchmark, then local market, then comp set. Each step adds resolution. You do not need to wait for the final picture before learning something useful, because the perfect benchmark might take time, but a better benchmark can start today.
Frequently asked questions
Can I benchmark my portfolio before a local comp set exists?
Yes. Comparing a property to the rest of your portfolio is a useful benchmark on its own, even before a local market has enough participants.
What are T1, T3, T6, and T12 averages?
Trailing averages over the past 1, 3, 6, and 12 months. Comparing this month against each shows whether performance is trending up or down over different windows of time.
Can I set performance targets for individual parks?
Yes. OHR lets portfolio operators set a target per property, so each park shows at a glance whether it is running above or below expectation.
What's the difference between comparing to my portfolio and to a local market?
Your portfolio shows how a property performs relative to your own properties. A local market shows how it performs against nearby comparable parks. Both are useful, and they can tell different stories.
Does portfolio benchmarking replace a comp set?
No. It's a starting point that's useful immediately, with local comp sets adding sharper, more precise context as market participation grows.


