The Season Is Over. Can You Still See Why You Priced That Way?

A note for GMs, owners, and revenue managers — for the two weeks after the season closes, before budget season swallows everything.

The summer is done. You pull the report: occupancy, ADR, RevPAR, month by month, against last year and against budget. Some months are up, one is down, and the totals get read out at a meeting where everyone nods.

Then someone asks the useful question: so what do we do differently next year?

And the room goes quiet — because the report you’re holding can’t answer it. Totals tell you how it ended. They don’t tell you what you knew in June, what you decided because of it, or whether the decision helped.

The lesson lives in the decisions, not the totals

A season is the sum of pricing decisions, group calls, and the moments where you either moved or didn’t — plus weather, plus a competitor’s renovation, plus a conference that moved cities.

Which is why “August was down 4%” isn’t a finding. It’s a prompt. The findings are one level down:

• We saw August 15–17 pacing behind in early June and dropped rate. Did the pickup actually come, or did we discount demand that was arriving anyway?
• We held rate through the last two weeks of July. Did we finish full at a strong ADR, or did we hold rate on empty rooms?
• The group we turned down in May — what did those nights end up doing?

Each of these has a real answer. Each requires something most hotels don’t have by September: the data as it looked on the day of the decision.

Why the evidence is usually gone

Here is the structural problem, and it isn’t a discipline failure.

Your PMS is an operational system. It maintains the current, correct state of the business: today’s bookings, today’s rates, today’s forecast. When a reservation is modified, the old value doesn’t move into an archive — it’s replaced. The system is supposed to work this way; a front desk needs one truth, not a history of truths.

The consequence for a season review is unforgiving. In early June you looked at August 15 and saw it pacing behind. Today, August 15 shows the final result: 94% and a decent rate. The number you decided on no longer exists anywhere. You remember it as “it looked weak,” which is a feeling, not a measurement — and by the time you’re reviewing in September, that feeling has quietly reshaped itself to match how things turned out.

So the review defaults to what’s still visible: the totals. And the totals are precisely the layer that can’t teach you anything, because they contain the decision and its alternatives collapsed into one number.

This is what a snapshot is for: a dated copy of the whole position, kept as it stood. A season with snapshots is a photo album — you can open any past day and see what you actually saw. A season without them is a single photograph taken at the end.

The four questions a season debrief answers

Ninety minutes, one page, the commercial team in one room. Four questions, in this order.

1. Where did pace diverge from what we expected — and when did we notice?

Not “which months missed.” Which dates ran differently from plan, and how many days of warning you had. A date that came in 20% behind and was spotted three weeks out is a very different story from the same date spotted four days out. The first is a pricing question; the second is a monitoring question, and they have different fixes.

2. Which of our moves changed the trajectory?

Take five to ten decisions you can name — a rate drop, a minimum stay you set, a group you took, a channel you opened. For each, compare the on-the-books curve before and after against a comparable date you left alone. This isn’t proof (see the honest caveat below), but a move followed by nothing, three times over, is a pattern worth respecting.

3. What was us, and what was the market?

The single most common misreading of a season is claiming the tide. If the whole market was up 8% and you were up 5%, that was a loss dressed as a win. This is what market indexes are for — your performance relative to the set of hotels you actually compete with. Read the season against them before you write conclusions about your own pricing. Our is 75% occupancy good? piece walks through this specific trap.

4. What can’t we answer — and what will we record so we can next year?

The most valuable output of a first debrief is usually the list of questions you couldn’t close. Write them down. They become next season’s instrumentation: the snapshot you’ll need, the reason field you’ll fill in, the group inquiry you’ll log even when you decline it.

The honest limit

You cannot prove a pricing decision was right. The night happened once; the version where you charged €20 more doesn’t exist and never will. Anyone selling you a clean attribution number for a rate change is selling you a story.

What you can do is narrow the guesswork:

• Compare against a market index rather than only against yourself, so at least the tide is factored out.
• Compare against comparable dates you handled differently — same day of week, same season, same rough demand shape.
• Read the pattern across many decisions and several seasons instead of adjudicating one.
• Keep the reason attached to the decision, so a year later you’re evaluating your thinking rather than reconstructing it.

None of that is certainty. All of it beats memory. We wrote about this at length in the autopilot essay and, from the ROI side, in how to measure an RMS you can’t prove — the same problem, seen from two directions.

Then hand it straight to the budget

A season debrief that ends in a document is half-finished. Its actual job is to be the input for next year’s plan, which — if you’re on a calendar year — is being drafted in the same weeks.

Three things carry across cleanly:

• Shape, not just level. Where the season’s demand actually sat by month and by day of week beats a flat percentage applied to last year.
• The dates you got wrong, with the reason. A date that surprised you twice is a seasonality assumption to fix, not a bad-luck story.
• The questions you couldn’t answer, which become the measurements you set up before next season rather than after it.

Our hotel budgeting guide covers the build itself — bottom-up by month and segment, tracked on pace instead of at month-end.

(Full disclosure, since this is our product: Peaqplus stores every imported PMS state as a dated snapshot, and Time Machine replays any past day’s position — which is what makes question 1 and question 2 answerable in September rather than aspirational. Decisions keeps the reason, the affected dates, and the owner attached to each call. You can approximate the same thing without us: export your on-the-books position on a fixed day each month and keep the files, and write one line of reasoning whenever you move a rate. It’s coarser, and it works.)

What to do this week

If you keep nothing else from this article, keep the starting position. It costs almost nothing and it’s the one thing you can’t retrofit:

1. Export your on-the-books position for the next twelve months today, and repeat it on the first Monday of every month. Even a spreadsheet in a dated folder makes next year’s debrief possible.
2. Start a one-line decision log. Date, what you changed, why, which dates it affected. Thirty seconds per entry.
3. Book the debrief for two weeks out, with the four questions as the agenda, before budget work eats the calendar.

Frequently asked questions

When is the right time to run a season debrief?

Within two to four weeks of the season closing, and before the annual budget is drafted. Any earlier and the last bookings haven’t settled; much later and the review becomes a formality that can no longer influence next year’s plan. For a summer-led hotel that means September; for a city hotel with a conference autumn, a mid-year debrief in January and a second one after the autumn season works better than one annual look.

We don’t keep historical snapshots. Is a debrief still worth doing?

Yes — with narrower questions. Without dated positions you can’t reconstruct what you saw when you decided, so skip question 2 and focus on question 1 (using booking dates in your PMS to rebuild a rough pace curve), question 3 (market indexes are external, so they’re still available), and question 4. Then start recording from now, so the next debrief has the layer this one is missing.

How is this different from a monthly performance review?

A monthly review asks whether the numbers are on track and what to do about the next sixty days — it’s operational and forward-looking. A debrief asks which of our decisions worked and what we should change structurally. Mixing them means the structural questions always lose to the urgent ones, which is why the debrief needs its own meeting and its own agenda.

Where to go from here

The glossary covers the machinery: snapshot, Time Machine, Same Point YoY, pace, and decision log. On the platform side, Business Intelligence shows the dated-snapshot foundation and Decisions the record-keeping. If the team is new to reading a season, the free Peaqplus Academy teaches pace and pickup from the beginning.

The season already told you everything it had to say. The only question is whether you kept enough of it to listen.