Seasonal Rate Cards Built From Two Years of Actuals
Pricing and Revenue

Seasonal Rate Cards Built From Two Years of Actuals

Localsbnb Editorial TeamSeptember 29, 20268 min read

One season tells a story, but a pattern needs two. Set the years side by side, mark the weeks where they agree and the weeks where they don't, and build seasonal bands wide enough to absorb a bad year. Then review the cards before the season opens, not during it.

Card: why two years of actuals beat one when you set seasonal rates
Two seasons side by side separate the weeks that repeat from the weeks that were one-offs.

One year is a story. Two years is a range you can price inside, and the second year is what tells you which weeks were unusual.

Last updated: September 30, 2026

One completed season feels like evidence. It has a shape, a busy month, a quiet one, and a few weeks you remember. The problem is that a season can look convincing and still be a one-off, and a rate card built on a single year inherits that year's accidents as if they were rules. Two years don't remove the guesswork, but they narrow it, because the second year is the control. This article shows how to set the years side by side, build bands that hold up when a season goes badly, and review the cards before the season opens.

Key Takeaways

  • One season is a story, not a pattern. A single year can look convincing and still be an accident of weather, a local event, or a news cycle.
  • The second year is the control. Where two years agree, you have a signal; where they disagree, you have a question.
  • Read the years week by week, not as totals. An annual average hides the weeks that behaved completely differently from each other.
  • Widen a band to survive a bad year. A band that only works in a good season is a band you'll abandon in month two.
  • Review before the season opens. Inside the season you can only react; before it, you can still choose.

Why one season is not a pattern

A season arrives as a sequence of events, and your memory keeps the dramatic ones. The week that sold out. The fortnight that stayed empty. The month a local event filled everything and then the next month fell away. None of that memory is wrong, but it's selective, and it's exactly the raw material a rate card is usually built from.

The trouble is that a single year can't tell you whether a strong week was strong because of demand that recurs or because of something that happened once. A conference that won't return. A road closure. A heatwave. Build a peak rate on a week like that and you'll be defending the number all next season, wondering why the guests didn't come.

One year gives you an average, and an average is the least informative summary of a season you can make. Two weeks at full occupancy and two weeks at nothing average out to something that never happened. A rate card built on that average prices a real week that behaved nothing like the average.

So the question isn't whether last season was good. It's whether any of it was typical, and one year alone can't answer that. A second year doesn't guarantee the answer either, but it turns a claim into a comparison, and comparison is where pricing starts.

Reading the two years side by side

Put the two seasons next to each other, week by week, and resist the urge to summarise them into two figures. The value is in the disagreements, and summary destroys them.

Start with occupancy per week, then add the rate you achieved and how far ahead the bookings arrived. Three numbers per week, across two years, is a small table to read, and it tells you things a total never will. A week that filled both years at a similar rate is a week you can price with confidence. A week that filled in one year and sat empty in the other is a question, not a band.

Then label the weeks into three rough groups. The agreed weeks are the ones that behaved similarly in both years. The divergent weeks behaved differently, and they're where your attention should go. The one-off weeks are the ones you can already explain: a holiday that moved, a local event, a once-in-a-decade disruption. Those last ones shouldn't set your peak rate, because they don't describe a season that will repeat.

One practical note on the data. Use your own occupancy, average daily rate and revenue per available room rather than a market figure, because a market average describes an average property and not yours. A week that's dead for your unit may be strong for a unit with a different size, location or guest mix, and only your own record knows which one you are.

Card: reading two seasons week by week, from agreement to divergence
Agreed weeks set the core bands, divergent weeks need widening, and one-off weeks shouldn't set your peak.
Card: three steps to a band that survives a bad season
Start from the agreed weeks, set each band between the two years, and give every band a written floor.

Building bands that survive a bad year

The purpose of a seasonal band isn't to be right. It's to be survivable, which means it has to work in a season that goes badly and still hold up in one that goes well.

Begin with the agreed weeks, because they carry the least uncertainty. Those weeks behaved the same way in both years, so they give you a starting figure you can justify without guesswork. Set your core bands from them first. If you start from the divergent weeks instead, one unusual year pulls the whole card toward a figure that only half your data supports.

Then widen each band deliberately rather than optimistically. A band is a price for a period, and periods don't repeat exactly. Set a band at the figure that was true in your best of the two years and you've built a card that only works when history repeats. Set it at the worst year and you've thrown away the upside. The useful position is between the two, weighted toward the year that tells you more about what's coming, and stated so you'd still be comfortable if the weaker year returned.

Then give each band a floor, and write it down. A floor is the figure below which you'd rather leave the dates closed or rethink the band than fill them. Deciding that in advance matters more than the starting number, because a season in progress gives you almost no time to think and a great deal of pressure to move.

One warning about the arithmetic: every figure in this method is a placeholder. Plug in your own actuals, because a band built from another host's seasons won't describe yours, and a band built from a market average won't describe anyone's.

Keep the bands where you actually set rates. Your calendar shows each connected channel's source rate and source status at localsbnb.com, so you can see what every channel is carrying before you move a band rather than finding a mismatch after the season has started.

Reviewing the cards before the season opens, not during it

A seasonal card isn't finished when it's written. It's finished when you've decided when it gets looked at again.

Review before the season opens, while you can still change things cheaply. Once the first booking of a period is in, that figure is committed, and moving it later means either renegotiating with guests or accepting a rate you've decided is wrong. A few weeks of lead time lets you adjust a band, open or close a stretch, and watch the effect.

Review the whole card at once, not one band at a time. Bands interact: raising a peak band can push demand toward an adjacent week, and lowering a soft band can pull demand away from a week you'd rather sell at the higher figure. Reading them together is the only way to see that movement before guests do.

Then, after the season closes, compare what happened with what you assumed. A band that consistently outperformed belongs a step higher. A band that never filled belongs lower, or closed. A band that behaved exactly as expected earns the right to be left alone next season.

And watch two things that aren't rates. Watch your booking window, because a window that's stretching or shrinking tells you demand is arriving earlier or later than last year. And watch the weeks you chose not to open, because a week you closed and later wanted back is usually a band decision you'd make differently, and it's worth knowing why.

LOCALSBNB — start free

FAQ

How many years of data do I actually need?

Two completed seasons is the point at which you can start comparing rather than remembering. Before that, use whatever you have, and label the weeks cautiously, because a single year can't distinguish a pattern from an accident.

What if last year was clearly an unusual year?

Then say so, and use the earlier year as your base. An unusual year is still useful data, because it shows you the range your property can reach and where the limits sit. What it can't do is set your standard rate, because it doesn't describe a season that will repeat.

Should I review seasonal rates during the season?

Only to respond to something you couldn't have known. The working review happens before the season opens, when you can still adjust bands cheaply. Mid-season, your options narrow to reacting, and reacting to one enquiry is how a card drifts.

A rate card built from one season copies that season's accidents. Built from two, it copies less of them, because you can see which weeks agreed and which didn't, and you can set your bands between the years rather than inside one of them. Read the two together, widen what needs widening, and decide when the whole card gets looked at again. When you want to see what each channel is carrying before a band moves, localsbnb.com shows each connected channel's source rate and status on one calendar, and keeps your occupancy, average daily rate and revenue per available room in the same place.


This article is general guidance for hosts and isn't financial or pricing advice. Rates, demand patterns and local short-term rental rules differ by place and change over time; check your own booking data and the requirements that apply where the property sits.

Reviewed by

Localsbnb Editorial Team