Seasonality: Find the Pattern Before Changing the Price

Every market has a rhythm. The mistake is assuming that rhythm is flat.

Imagine the same two-bedroom beach property in two different months. Same bedrooms. Same view. Same amenities. Same location. Same owner.

In July, travelers are competing for limited summer inventory. Booking pace is strong, desirable dates are disappearing earlier, and guests are generally willing to pay more.

In January, far fewer guests may be searching. Comparable properties remain widely available, bookings arrive later, and guests have more alternatives.

The physical property has not changed. Demand has.

So why should the pricing strategy remain the same? It should not.

A property should not carry the same pricing philosophy through February, July, and Christmas simply because the asset itself is unchanged. Revenue management starts by recognizing a fundamental fact:

Demand moves through the year.

The Revenue Manager's job is to identify that recurring pattern before deciding what the price should do.

During genuine peak periods, the commercial objective shifts toward protecting ADR and valuable inventory. During weak periods, the objective changes. The property needs to become more competitive and give occupancy and conversion greater priority.

Not at any price. Not through indiscriminate discounting. But enough to reflect the market that actually exists.

The first question is therefore not “what should we charge?” It is:

“What does this market normally do at this time of year?”

What seasonality actually means

Seasonality is the predictable, recurring change in demand that occurs through different parts of the year. It is the market's normal rhythm.

A beach destination may strengthen every summer. A ski destination may strengthen in winter. A tropical destination may perform best during its dry season. A business-heavy city may weaken during holiday periods when corporate travel disappears. A university market may repeatedly strengthen around graduation, move-in periods, or other recurring academic cycles.

Those patterns can appear in occupancy, ADR, booking pace, booking lead time, minimum-stay behavior, and ultimately RevPAR.

Seasonality is different from a one-off demand shock. One unusually large concert is not seasonality. One cancellation is not seasonality. One particularly warm weekend is not seasonality. One sudden spike in bookings does not automatically redefine the season. Those are temporary conditions. Seasonality is what tends to happen again and again.

That distinction matters because recurring patterns should influence the broader pricing baseline, while temporary demand should usually be handled more tactically. A useful Revenue Manager question is:

“If I removed this year's unusual events, what demand pattern would I still expect to repeat?”

That recurring structure is seasonality.

Here is an illustrative demand index for a beach market, with broad periods shaded as peak, shoulder and low:

Illustrative beach-market demand pattern, not actual market data. The exact shape differs by destination. Revenue strategy should follow the actual market pattern rather than assuming every month carries equal demand.

Why does demand change through the year?

Seasonality exists because guest behavior is not random. Travel decisions repeatedly respond to factors such as weather, school calendars, holidays, corporate schedules, tourism cycles, and destination-specific conditions.

A beach destination may become more attractive when weather improves. A ski property may have enormous winter demand and limited summer demand. A tropical property may strengthen during the dry season rather than the conventional northern-hemisphere summer. A city dominated by corporate travelers may perform strongly from Tuesday through Thursday during business-heavy months but soften during long holiday periods. Family destinations can follow school calendars. Some markets have two strong seasons. Others have one short peak and a long low season.

That is why the Revenue Manager should never begin with “summer must be high season.” The better approach is:

“Show me when demand actually strengthens.”

The calendar does not define the season. Demand does.

July is not automatically peak season. January is not automatically low season. The same month can represent completely different demand conditions in different markets.

A beach destination may experience extremely strong July demand. A ski destination may treat July as low or shoulder season. A corporate urban market may soften during July because business travel declines. The word July tells us the date. It does not tell us the commercial value of the date.

The Revenue Manager needs evidence. That evidence can come from historical occupancy, historical ADR, RevPAR, booking lead time, current market occupancy, comparable pricing, and recurring booking patterns.

Seasonality belongs to the market, not the month name.

Three broad seasonal states

Most seasonal strategies can be understood through three broad conditions. They do not need to fit perfectly into three neat calendar blocks. They are simply a useful way to think about how the commercial objective changes.

Peak season. Demand is structurally stronger than normal. There are usually more guests competing for desirable inventory. The Revenue Manager gives greater priority to ADR and inventory protection.

Shoulder season. Demand sits somewhere between clearly strong and clearly weak. The Revenue Manager balances rate protection and conversion.

Low season. Demand is structurally weaker. There may be fewer guests relative to available supply. The Revenue Manager gives greater priority to competitiveness, occupancy, and conversion.

The objective is not to maximize one KPI in isolation. The goal remains the same throughout the year:

Generate the strongest possible value from available inventory.

What changes is the balance between rate and occupancy required to achieve that result.

Peak season: protect ADR

During peak season, demand is naturally stronger. That usually means greater willingness to pay, stronger booking pace, lower remaining supply, and often longer booking windows.

The Revenue Manager therefore becomes less willing to sell inventory cheaply simply to create early occupancy. This is where the lesson from A Full Calendar Can Still Be Underperforming becomes especially important. A full peak-season calendar can still underperform. If the property sells out months before comparable inventory at rates below the market, the operator may have purchased certainty by giving away ADR.

The primary peak-season objective should therefore shift toward protecting ADR. That does not mean ignoring occupancy. It means recognizing that scarce, high-demand inventory has more opportunity to support stronger rates. If demand is already healthy, there is little reason to create unnecessary discounts just to make the calendar look full.

A Revenue Manager may therefore protect higher rates, monitor whether inventory is selling too quickly, preserve desirable dates for later demand, avoid unnecessary early discounts, and use stronger stay controls when the booking pattern justifies them.

The danger in peak season is often not failing to get bookings. It is selling the best inventory before fully capturing what guests were willing to pay.

Peak-season pricing shifts the baseline

Imagine an illustrative property with a normal reference level of $200. Suppose its recurring peak period historically supports a baseline approximately 20% stronger. For educational purposes: $200 × 1.20 = $240.

That does not mean every peak-season date should be exactly $240. It means the expected value of an ordinary night during that stronger period has moved upward. Within the same peak season, a weaker weekday may still price below $240, a strong Saturday may price above it, and a compressed event night may price much higher.

Seasonality establishes the background demand environment. Other signals still move individual nights within that environment.

Illustrative only. Additional pricing signals influence individual nights. Peak season raises the baseline, not every date to the same price.

Low season: compete for a smaller demand pool

Now reverse the market. Demand weakens. Fewer guests are searching. Comparable inventory remains abundant. Booking windows may shorten. Guests have more alternatives.

The property is no longer competing primarily for rate. It is competing for a smaller pool of guests. The strategy needs to change. Low season should compete. That can mean lower pricing, shorter minimum stays, stronger last-minute adjustments, and greater flexibility around calendar gaps.

The primary objective shifts toward protecting occupancy and conversion.

Not at any price. The principles in Minimum Price: Your Floor Should Have a Reason still apply. But keeping a peak-season rate simply because that is what the property achieves in July can leave the listing commercially irrelevant in January. A Revenue Manager should be willing to accept lower ADR when the resulting increase in occupancy produces a stronger total revenue result.

An illustrative low-season shift

Using the same neutral reference of $200, suppose the recurring low period supports a 15% lower baseline. For illustration: $200 × 0.85 = $170.

Again, $170 is not automatically the final price of every low-season night. A weak Tuesday may fall lower. A holiday weekend can rise above it. A sudden booking surge can change the rate. The seasonal adjustment simply recognizes:

Normal demand during this period is structurally weaker.

Same property. Different demand environment. Seasonal strategy changes the pricing baseline because the balance between guests and available inventory changes.

Shoulder season: the difficult middle

Shoulder periods sit between clearly strong and clearly weak demand. They are often harder to manage than either extreme. Peak-season rate protection can be too aggressive. Deep low-season discounts can be unnecessary. Demand may depend more heavily on weekends, weather, individual events, short booking windows, and specific calendar patterns.

The Revenue Manager therefore needs balance. The objective becomes:

Stay competitive without giving away rate unnecessarily.

For example, a property with a neutral $200 reference might trade roughly around that level through a shoulder period, with individual dates moving higher or lower according to actual demand. The exact amount is market-specific. What matters is that the Revenue Manager does not treat shoulder season as though it were simply “half peak season.” It needs its own interpretation.

The commercial objective changes with recurring demand strength.

Example: a beach market

Now apply the concept to a beach property. Same property. Different season. Different commercial objective.

These are illustrative figures. The important lesson is the difference in commercial objective.

July: protect valuable inventory

Normal ADR is $300. The market is already approximately 70% occupied at 60 days. Booking pace is strong. Demand is arriving early. The recommended rate range is $330 to $360 with a 3 to 4 night minimum stay. The primary KPI is ADR and RevPAR.

Why? Because the biggest risk is not necessarily vacancy. The risk is selling scarce peak-season inventory too cheaply. A Revenue Manager looking at this environment might ask: are bookings arriving too quickly? Is remaining supply tightening? Are we priced strongly enough relative to demand? Are valuable weekends being protected? Are stay restrictions helping preserve desirable booking patterns?

The strategy does not chase occupancy for its own sake. It monetizes strong demand.

January: compete for conversion

Now look at January. Normal ADR is $180. Market occupancy is approximately 35% at 30 days. The market remains weak. The recommended rate range is $155 to $175 with a 1 to 2 night minimum stay. The primary KPI is occupancy and RevPAR.

The property is the same. But the competitive situation is completely different. There are fewer guests. Supply remains available. Holding July-style pricing would make the property less competitive. The Revenue Manager therefore becomes more flexible. Lower rate. Shorter minimum stay. Stronger attention to last-minute conversion. More willingness to fill usable gaps.

The goal is not to preserve the $300 July ADR. That rate belongs to a different demand environment. The goal is to monetize inventory that would otherwise remain empty while still respecting the property's commercial floor.

Occupancy has to be interpreted seasonally too

Suppose your property reaches 70% occupancy. Is that good? As A Full Calendar Can Still Be Underperforming established, the number alone does not tell us enough. Now add seasonality.

Imagine peak-season market occupancy is 90% and your property is at 70%. In that environment, the property may actually be behind.

Now imagine low-season market occupancy is 40% and your property is at 70%. Exactly the same property occupancy now represents substantial outperformance.

Occupancy only becomes meaningful inside the correct seasonal context. This is why a low-season calendar should not be expected to look like a peak-season calendar. The market itself is different.

ADR must also be benchmarked by season

The same principle applies to ADR. Suppose the property achieves $180 ADR. In low season, when comparable properties average around $150, that may represent excellent rate performance. In peak season, if comparable inventory is achieving around $260, the same $180 could indicate major underpricing.

The absolute ADR did not change. Its meaning did. That is why annual averages can hide important information. A Revenue Manager wants to understand:

How strong is this rate relative to the demand environment in which it was achieved?

RevPAR shows whether the seasonal trade-off is working

Seasonal strategy changes the balance between ADR and occupancy. RevPAR helps us evaluate whether that change is actually producing more value. Consider an illustrative low-season example.

$200 × 30% = $60. $160 × 50% = $80. The second strategy accepts lower ADR. But the additional occupancy produces stronger RevPAR.

Now consider an illustrative peak-season example.

$200 × 95% = $190. $250 × 85% = $212.50. Here, the lower-occupancy strategy produces more revenue per available night because the rate increase more than compensates for the occupancy difference.

These are illustrative scenarios. They are not universal demand curves. The lesson is:

Low season and peak season can reward different balances between rate and occupancy.

How a Revenue Manager finds the seasonal pattern

Seasonality should be measured before it is managed. A Revenue Manager can begin with several views.

Monthly occupancy. Which months repeatedly fill most strongly? Which remain structurally weak? One year is useful. Several comparable periods are better when available.

Monthly ADR. Does willingness to pay rise during the same periods where occupancy strengthens? If occupancy rises dramatically but ADR does not, the property may be underpricing the peak.

RevPAR. Which periods generate the greatest value from each available night? This helps separate genuine commercial strength from occupancy alone.

Booking lead time. Do July guests book earlier than January guests? Peak seasons often create longer planning windows. Weak periods can depend more heavily on short-lead-time demand.

Market performance. Does the property's pattern reflect the overall market? A listing can perform unusually because of its own quality or strategy. Market data helps reveal whether the pattern is structural.

Recurrence. Does the pattern repeat? One strong July does not automatically establish July as peak season forever. The Revenue Manager looks for repetition.

Anomalies. Was one month distorted by a major event? Extreme weather? A temporary closure? A major change in supply? Seasonality is the recurring pattern after those unusual influences are considered.

A simple monthly worksheet is enough to start: month, occupancy, ADR, RevPAR, typical booking lead time, and a seasonal interpretation (peak, shoulder or low). Find the pattern before creating the seasonal rule. Populate it with actual property and market data rather than assigning seasons from intuition.

Use more than one period when possible

Seasonality repeats. But it does not repeat perfectly. A single year can be distorted by extraordinary events, unusual weather, changing supply, regulation, economic conditions, or temporary closures. Where reliable history exists, a Revenue Manager compares multiple periods.

But history should not be used blindly. Suppose July performed extraordinarily well three years ago. Since then, hundreds of new listings have entered the destination. Demand may still peak in July. But the competitive environment has changed. The seasonal pattern can survive while the absolute rate opportunity changes.

Historical data is evidence of recurrence. It is not a guarantee of identical future performance.

What if the listing is new?

A new property does not yet have its own seasonal history. The Revenue Manager therefore begins with the market. Look at relevant comparable properties. Review market occupancy by month, market ADR, booking lead time, recurring tourism patterns, and similar property behavior.

This creates an initial seasonal hypothesis. Then allow the property's own booking performance to refine it. Over time, the Revenue Manager learns whether this listing follows the market, books earlier, commands a premium, struggles during certain months, or serves a different guest segment.

A market pattern is the starting point. Property-specific behavior provides the refinement.

Seasonality can change the booking window

Seasonality affects more than the amount guests are willing to pay. It can also change when they book.

Consider an illustrative beach property. Peak July average booking lead time is 75 days. Low-season January average lead time is 20 days. This matters enormously. Suppose January is only 30% occupied 90 days before arrival. That may look terrible if you compare it with July. But if most January guests do not book until the final 20 days, there may be no problem yet. Using peak-season pacing expectations during low season can trigger unnecessary discounting.

Seasonality changes not only how much demand arrives, but sometimes when it arrives. This connects directly to the framework in The Three Booking Windows Every Operator Should Understand. Lead times here are illustrative only.

Seasonality shifts the baseline. It does not flatten the calendar.

Even within a peak month, not every night should have the same rate. A Tuesday can still behave differently from Saturday. A normal Saturday can still behave differently from an event Saturday. A date where the property is far ahead of market pace can still deserve additional protection.

The same is true in low season. One holiday weekend can dramatically outperform the surrounding month. One weak midweek period can underperform.

So seasonality should not create a flat monthly price. It should create a different starting demand environment. Then dynamic pricing continues responding inside that environment. A useful principle is:

Seasonality sets the background. Dynamic pricing still reacts within it.

Be careful not to count seasonality twice

Modern dynamic-pricing systems may already account for broad recurring demand patterns. That creates another Revenue Manager responsibility. Before adding a manual seasonal premium or discount, understand what the pricing system is already doing.

Consider an illustrative example. The base reference is $200. The dynamic system already recognizes stronger summer demand and moves the date to $230. Now the operator manually adds another +20%: $230 × 1.20 = $276.

Is $276 correct? Possibly. If the property is still filling too quickly and market evidence supports stronger rates, the additional premium may be justified. But if the operator added the 20% simply because “summer is high season,” the same seasonal strength may have been counted twice.

The same risk works downward. A pricing system may already reduce winter rates. A second large manual winter discount can push the property farther down than intended.

Seasonal customization should solve an observed pricing gap rather than duplicate a demand signal already reflected in the rate. Dynamic Pricing: What Is Actually Changing Your Nightly Rate? explains how those layers combine.

Seasonality is not the same as live demand

One distinction deserves its own treatment. Suppose July is normally one of the strongest months of the year. That is seasonality. Now suppose a major concert causes one July weekend to sell far faster than a normal July weekend. That additional strength is not simply “more seasonality.” It is current demand exceeding the normal seasonal expectation.

The opposite can also happen. July may normally be strong. But unusual weather, a cancellation wave, or weak market pickup can cause a specific future period to perform below the expected July pattern. Similarly, January may normally be weak. But New Year's or another compressed period can still produce very strong rates.

So:

Seasonality tells us what normally happens.

It does not tell us everything happening right now. That distinction is the focus of Seasonality Factor vs. Demand Factor.

Common misconceptions

“My property should use roughly the same pricing all year.” No. The physical property may be unchanged, but guest demand, competing supply, booking pace, and willingness to pay can move dramatically through the year.

“Summer is always high season.” No. Summer may be peak for a beach market and weak for another destination. The market determines seasonality.

“Low season means discount everything aggressively.” No. The strategy becomes more competitive. That does not mean abandoning the minimum price, ignoring live demand, or discounting dates that are already performing strongly.

“Peak season means every night should be expensive.” No. Seasonality changes the baseline. Individual dates still respond to weekday patterns, booking pace, live demand, events, and remaining supply.

“Low-season occupancy should look like peak-season occupancy.” Not necessarily. If the whole market is less occupied, a lower absolute occupancy level can still represent strong relative performance.

“One strong month proves the seasonal pattern changed.” Not necessarily. One unusual event can distort an entire month. Look for recurring evidence.

“An event is seasonality.” No. An annually recurring season and a temporary event are different demand concepts.

“My pricing software handles seasonality, so I never need to review it.” Automation can model recurring patterns. Revenue management still needs to verify that peak and low periods are positioned appropriately.

“If one seasonal adjustment is good, a larger one must be better.” No. Over-adjustment can create under- or overpricing just as easily as no seasonal adjustment.

When the simple rule needs more context

Some markets have very smooth seasonal patterns. Others do not.

An event-heavy city may have relatively steady underlying demand punctuated by powerful compression weeks. A tropical destination may follow wet and dry seasons. A ski destination may have an extreme winter peak. A corporate market can depend more on weekday business cycles than traditional leisure seasons.

New competing supply can reduce occupancy even when the seasonal demand pattern itself remains intact. Regulatory changes can alter available inventory and distort historical comparisons. Weather-dependent destinations can see unusually early or late seasonal starts. And a new listing may not have enough history to identify its own pattern confidently.

The lesson is not that seasonality is unreliable. The lesson is:

Seasonality must be discovered from the market, not imposed on it.

What the Revenue Manager actually reviews

Before changing seasonal pricing, the Revenue Manager should be able to describe the market's annual demand curve.

Start with monthly market occupancy. Where does demand repeatedly strengthen? Where does it weaken? Then compare property occupancy. Does the property follow the market pattern or behave differently?

Review monthly ADR. Are stronger months actually producing stronger rates? Look at RevPAR. Which periods create the greatest value from available inventory?

Review booking lead time. Do peak-season guests reserve earlier? Do weak-season guests book closer to arrival? Look at historical booking curves. Does the timing pattern repeat?

Review comparable prices. Does the property carry an appropriate premium or discount relative to similar listings? Review market supply. Does low season create a large amount of competing availability?

And then identify unusual periods. Was this month's performance affected by a major event or abnormal disruption?

The Revenue Manager's central question is:

What does this market normally do during this period?

Only after answering that should the seasonal pricing strategy change.

Important: individual dates can still deviate from the seasonal direction because of live demand, booking pace, events, and weekday behavior.

Revenue Manager's desk: same condo, two seasons

Consider the same two-bedroom beach condo. The property's seasonal behavior has been mapped. Now compare July and January.

July

Normal ADR is $300. Market condition: strong booking pace, approximately 70% occupied at 60 days. Recommended range: $330 to $360. Minimum stay: 3 to 4 nights. Primary KPI: ADR and RevPAR. Revenue objective: protect rate and valuable inventory.

The Revenue Manager does not panic because some far-out nights remain open. Demand is strong. Guests book earlier. Inventory already has scarcity value. The focus is on avoiding unnecessary early dilution.

January

Normal ADR is $180. Market condition: approximately 35% occupied at 30 days, market remains weak. Recommended range: $155 to $175. Minimum stay: 1 to 2 nights. Primary KPI: occupancy and RevPAR. Revenue objective: become more competitive and prioritize conversion.

The market contains fewer guests. Comparable supply remains available. The property becomes more flexible with rate and stay restrictions. The objective is not to recreate July's ADR. It is to monetize January inventory effectively.

Same property. Different season. Different commercial objective.

How to explain seasonality to an owner

For peak season:

“July consistently carries stronger demand, faster booking pace, and tighter market supply. We are therefore protecting ADR rather than trying to fill every remaining night immediately.”

For low season:

“January has structurally weaker demand and much more available competition. We are using a lower rate range and more flexible stay controls because maintaining July-level pricing would reduce our ability to convert the smaller pool of guests.”

For shoulder season:

“Demand is between peak and low season, so the strategy is balancing rate protection with enough competitiveness to maintain healthy booking pace.”

These explanations are more useful than “the algorithm raised July” or “we discounted January.” They explain the commercial reason.

Best practices

Map the annual demand curve before creating seasonal rules.

Use property and market information together.

Benchmark occupancy within the relevant season.

Benchmark ADR within the relevant season.

Protect rate during genuine peak periods instead of filling too cheaply.

Become more competitive when the market is structurally weak.

Understand how booking windows change through the year.

Separate recurring seasonality from current live demand.

Check what the dynamic-pricing system already captures before adding another seasonal adjustment.

And revisit the pattern periodically because markets evolve.

Mistakes to avoid

Do not assume summer is automatically peak season.

Do not apply one pricing philosophy across the entire year.

Do not judge January occupancy against July expectations.

Do not protect peak-season ADR so aggressively that you ignore genuine weakness.

Do not discount valuable peak inventory too early simply because some dates remain open.

Do not treat one event spike as a seasonal change.

Do not treat one abnormal year as permanent truth.

Do not ignore seasonal changes in booking lead time.

Do not build seasonal adjustments from intuition alone.

Do not count the same seasonal demand twice through overlapping pricing rules.

And do not assume seasonality replaces dynamic pricing. Seasonality creates the baseline. Dynamic pricing continues working inside it.

The takeaway

Every market has a rhythm. The mistake is assuming that rhythm is flat.

The same property should not carry the same pricing philosophy through every month simply because the physical asset has not changed. Demand has.

During genuine peak periods: protect price and valuable inventory. Guests are competing more strongly. Booking pace is faster. Supply becomes scarcer. The Revenue Manager should avoid selling high-value inventory cheaply simply to reach occupancy early.

During genuine low periods: become more competitive and prioritize conversion. There are fewer guests. More inventory may remain available. The property may need lower pricing, shorter minimum stays, stronger last-minute adjustments, and more flexibility around gaps. Not at any price. But enough to monetize nights that would otherwise remain empty.

During shoulder periods: balance both objectives. Protect rate where demand supports it. Compete where it does not.

And remember that occupancy, ADR, booking pace, and RevPAR all need to be interpreted inside the relevant seasonal environment. A 70% occupied property can be behind in peak season and substantially ahead in low season. A $180 ADR can be strong in January and weak in July. Context changes the meaning.

Most importantly:

Seasonality tells you what normally happens.

It establishes the recurring demand baseline. It does not tell you everything happening right now. Because sometimes a normal July weekend becomes extraordinarily strong. Sometimes a weak January weekend suddenly compresses. Sometimes current demand behaves very differently from what seasonality predicted.

That creates the next question:

How do we separate the demand we expected from the demand happening right now?

That is covered in Seasonality Factor vs. Demand Factor