Seasonality
In hotel revenue management, seasonality is the recurring annual pattern in demand for your property, and the rate seasons you draw from it are how most independents translate that pattern into prices.
Almost every property has seasons. Rather fewer have checked recently whether the seasons they are pricing to are the ones their guests are actually in.
See how ampliphi prices for independent hotels
Get a free revenue audit · Book a demo
What is seasonality?
A repeating pattern, and there are three of them running at once.
The annual season is what the word usually means: summer against winter, high against low, whatever shape your market has. The weekly pattern is day of week, and at many properties it is the larger effect, with a Saturday routinely worth double a Tuesday. Event-driven spikes are the third layer, recurring annually because their causes do, but too short and too sharp to be a season.
Separating those three matters because they get conflated constantly. A property that prices September as high season because summer was strong has applied an annual pattern to a month that no longer belongs in it. A property that prices every day of a high-season week alike has ignored the weekly pattern entirely.
Rate seasons are the practical output: blocks of dates sharing a price level. Most independents run three or four, drawn once, and then leave them alone for years. That is where the trouble starts, because seasons drift. Weather patterns move, an event grows or dies, a competitor opens, a market's shape changes, and a calendar drawn six years ago is describing a property that no longer exists.
Seasonality is also not the same thing as demand being low. A shoulder period is part of a healthy annual pattern. A soft month that should not be soft is a problem, and reading the second as the first is how properties accept underperformance as normal.
Resources: Shoulder season · Occupancy rate · Booking pace
How seasonality works in practice
The exercise is plotting three years of occupancy by week and comparing it to the seasons you are actually charging.
Worked example. A 46-room inn runs three rate seasons set years ago: low from November to March, shoulder in April, May and October, high from June to September. Plotting three years of weekly occupancy shows something different. The genuine peak runs from mid-June to late August. There is a sharp secondary peak across two weeks in early October, a local festival that has grown considerably since the calendar was drawn. The real trough is only early January to mid-February. September, priced as high season, averages 54 percent. Early October, priced as shoulder, sells out. Two pricing errors, both caused by a calendar that stopped matching the demand.
That exercise takes an afternoon and is the highest-return piece of analysis available to a property that has never done it.
The everyday practice afterwards is smaller. Redraw the seasons from your own occupancy and rate history, price the day-of-week pattern within each season rather than applying a flat rate, and keep the event spikes on a separate list rather than trying to fold them into a season.
The discipline that keeps it honest is rechecking annually. Seasons drift slowly enough that no single year makes the case and steadily enough that five years makes it undeniable. An hour each January, comparing the last three years of weekly occupancy against your current calendar, catches the drift before it costs a full season.
Resources: Demand forecasting · Rate calendar
Why seasonality matters for independent hotels
Because a seasonal calendar is the entire pricing system at most small properties, and nobody audits it.
An owner-operator who sets rates by season and adjusts occasionally is effectively making four pricing decisions a year. If the season boundaries are wrong, all four are wrong, and they stay wrong for as long as the calendar does. That is a structurally different kind of error from mispricing a date, because it repeats every year until somebody looks.
The second reason is that independents are more exposed to seasonal swing than chains. A city hotel with a corporate base has a floor under its demand. A rural property with a leisure market has months where the difference between a good outcome and a bad one is entirely down to what it charged and how it handled the shoulder.
The third is that seasonal thinking, taken too far, becomes an excuse. A property that has decided February is dead will price it as dead, market it as dead, and confirm its own forecast. Some of those months genuinely cannot be fixed. Some of them were never tested.
Resources: Revenue management for independent hotels
How to use seasonality at your property
- Plot three years of occupancy and ADR by week. This single chart is the foundation of everything else here.
- Redraw your rate seasons from that, not from the calendar, the tourist board or what the previous owner did.
- Price the day-of-week pattern inside each season. A flat high-season rate misprices every Tuesday in it.
- Keep event spikes off the season calendar and on a named date list, because they are too short to be seasons.
- Recheck annually. Seasons drift, and the drift is invisible in any single year.
- Separate a genuine low season from an untested one. One is a fact about your market, the other is a habit.
What seasonality will not tell you
It describes the pattern and never the cause. A September that softened could be a changed school calendar, a competitor opening, an event that moved, or a shift in who is travelling. The chart shows the shape and none of the reasons, and the reasons determine whether it is fixable.
It is an average, so it misprices the dates inside it. A season is a block of dates treated alike, and within any block there are dates running far ahead and far behind. That is precisely what booking pace is for, and no seasonal calendar substitutes for it.
And it fails on the years that break the pattern. History is the only input, so a year with an unusual event, a disruption or a genuine change in the market is exactly the year the pattern is least reliable.
How ampliphi approaches seasonality
Ampliphi does not ask you to maintain a seasonal calendar, because the everyday rate suggestion is demand-based and built on booking pace and occupancy, assessing each date against how that same date has filled before.
Seasonality is therefore implicit rather than configured. A mid-August Saturday is compared with mid-August Saturdays, and a February Tuesday with February Tuesdays, so the annual pattern and the weekly pattern are both carried by the comparison rather than by a calendar somebody drew. The drift problem described above does not arise, since there is no calendar to become out of date.
That does not replace knowing your own year. A season you have decided is dead and never tested will look dead in the history too, and local knowledge about why a period is soft is yours rather than the system's. The suggestion covers your base rate and the differential between room types, you approve every rate before it publishes, and ampliphi runs on top of the PMS you already use.
Key takeaways: seasonality
- The recurring annual pattern in demand, and the rate seasons drawn from it.
- Three layers run at once: annual season, day of week, and event spikes. Keep them separate.
- Rate seasons drift. Most independents are pricing to a calendar drawn years ago.
- Plotting three years of weekly occupancy against your current seasons is an afternoon that usually finds two errors.
- A season is an average, so dates inside it still need pace.
- A genuine low season and an untested one look identical in the data and are not the same thing.
Frequently asked questions about seasonality
How do I define my rate seasons?
From three years of your own weekly occupancy and ADR, not from the calendar or anyone else's definition.
Plot occupancy by week for three years on one chart. The blocks will be visible, and they usually do not land on month boundaries, which is the first thing most properties discover. A season that starts mid-June and ends in the last week of August is normal and a calendar built on whole months cannot express it.
Then sanity-check the boundaries against rate. A period where occupancy holds up but ADR collapses is a different situation from one where both fall, and they should not share a season.
How often should I redraw my seasons?
Check annually, redraw when the evidence supports it, which in practice is every few years.
Seasons drift slowly. No single year makes a convincing case, and by the time the drift is obvious it has usually been costing money for several years. An hour each January comparing the last three years against your current calendar is enough to catch it.
Redraw when two consecutive years agree that a boundary has moved. Redrawing on one unusual year is how a property ends up chasing noise and loses the year-on-year comparability that makes the analysis work.
What is the difference between seasonality and a compression night?
Seasonality is a broad recurring pattern. A compression night is a single date where the whole market runs short of rooms.
A high season is weeks or months of sustained higher demand that you price with a rate level. A compression night is one date, often inside an otherwise ordinary period, where displaced travellers pay far above normal.
They need different handling. Seasons set your baseline. Compression nights are individual decisions made from an event calendar and a rate shop, and folding them into a season underprices them badly.
Should I close during my low season?
It depends on arithmetic that is specific to your property, and it is worth doing properly rather than by feel.
The question is whether low-season revenue exceeds the variable cost of staying open, including staffing, heating, cleaning and the marginal wear of operating. Some properties find it does not. Many find it does, by a smaller margin than they expected.
The considerations that do not appear in that arithmetic are worth weighing too: keeping staff through the year rather than rehiring, maintaining your ranking and review flow on the OTAs, and losing repeat guests who found you closed. Closing is a defensible decision and it should be a calculated one.
Does seasonality affect my booking window?
Yes, often substantially, and it is worth checking rather than assuming.
Peak-season dates typically book much further ahead, because travellers know availability is limited. Low-season dates book late, because there is no urgency and the traveller knows a room will be there.
That matters because your pace horizon should follow it. A property using one forward window across the year will watch peak dates too late and low-season dates far too early. Split your booking window by season and the grid becomes considerably more useful.
Related terms
Shoulder season
The transitional periods between peak and low. Where seasonal analysis pays off most, because those weeks respond to what you do.
Booking pace
How a future date is filling against its own history. What you need because a season is an average and individual dates vary.
Demand forecasting
Predicting how a date will finish. Seasonality is one of its inputs and the coarsest one.
Occupancy rate
The percentage of available rooms sold. The series you plot by week to find where your real seasons begin and end.
Need date
A date forecast to underperform. Common in shoulder and low periods, and distinguishable from normal softness only against the curve.