The end-of-season revenue review: which decisions worked and which did not
Hold the hotel end of season review before seasonal staff leave. Compare plan with actual by month, segment and channel, score contracts on net revenue, and write three clear changes for next season.
Contents
Key takeaways
- Hold the review before the last manager leaves, not in January: the people who remember why a rate was cut are the people who cut it.
- Judge a channel or a contract on net revenue after commission, contract discount, included extras and refunds, never on room nights alone.
- A decision worked only if the reason it was made still holds and the result moved the way you expected; a full hotel at a lower net rate is not a win.
- Three written changes with an owner and a date beat a ten-point improvement list that nobody opens in April.
- Cancellation rates and booking windows vary too much by segment and market for an outside number to mean anything, so compare against your own previous seasons.
The hotel end of season review is a two-hour meeting held before seasonal staff leave, where the hotel compares plan with actual by month, segment and channel, tests each contract against what it promised, reads its decision log, and writes three changes for next season.
The last guests leave, the seasonal staff hand in their keys, and the season's numbers stay scattered across a channel extranet, a reservations spreadsheet and a notebook at the front desk. By January nobody remembers why the July rate was cut. This article gives you the meeting to hold before that happens: who to invite, which cuts of the numbers to read, how to score contracts and decisions, and how to end with three written changes instead of a folder of regrets.
When should you hold the hotel end of season review, and who should be in the room?
Hold it in the final two weeks of the season, after the last busy week and before the seasonal managers leave, in one two-hour slot with no more than six people.
Timing matters because the evidence has an expiry date. Extranet logins lapse, rate-change histories scroll out of view, and the reservations manager who knows why a minimum-stay rule was dropped is gone by November. The meeting is cheap in October and nearly impossible in January.
Chair it yourself as owner or general manager, and keep the room small: revenue or reservations lead, sales, front office manager, one person for guest relations or housekeeping, and finance for refunds and billing corrections. Invite the person who will run next season, even if they are junior now, because the review is also the handover.
Send the pack 48 hours ahead. The meeting is for decisions, not for reading numbers aloud; if people see the numbers for the first time in the room, the two hours go to explanation. Timebox the agenda: twenty minutes on results, twenty on contracts, twenty on the decision log, twenty on the guest voice, thirty on the three changes, ten minutes of buffer. Keep this meeting separate from closing a seasonal hotel for winter: an operations checklist, which is a shutdown sequence with its own owner.
ChecklistThe pack, sent 48 hours before
- Month-by-month rooms sold and revenue by segment and channel
- Each contract's terms beside its actual production
- The decision log
- Cancellations and no-shows by channel and rate plan
- Length of stay by segment
- Refunds, comps and upgrades given to fix problems
- The guest comment export with dates
- The budget and last year's actuals for the same cuts
Which numbers should you break down, and by what?
Cut the same three ways every year: by month, by segment and by channel, and read each cut against the budget and against your own previous season.
By month, you are looking for the week or month that broke the pattern, not the season average. An average hides a bad July behind a strong August and teaches you nothing. By segment, you learn who actually bought and how long they stayed; a segment that grew in room nights but shortened its stay has grown its cost to serve, not its value.
By channel, compare net revenue, not gross: subtract commission, contract discount, included extras and the refunds that channel generated. The biggest channel on room revenue is often not the biggest on net. Use per-room-night figures alongside totals, because totals hide mix: revenue per room night and nights per booking show whether you sold more rooms or better rooms. Read variance in both directions, as covered in budget vs actual in hotels: reading the monthly variance, because a revenue shortfall paired with a larger cost shortfall can still be a better season.
Do not treat published national occupancy as your benchmark. The Ministry of Culture and Tourism publishes an occupancy rate for Ministry-certified (İşletme and Basit) facilities, but the definition behind that column is not published, so it cannot tell you whether your own season was good. Source: Ministry of Culture and Tourism, accommodation statistics 2025. Public data. No endorsement implied.
| Cut | The question it answers | The mistake to avoid |
|---|---|---|
| Month | Where the season broke its pattern | Reading the season average and missing a bad July |
| Segment | Who bought, and at what length of stay | Ranking segments on room nights instead of net revenue |
| Channel | What each source cost to sell through | Comparing gross room revenue before commission and refunds |
| Room type | Whether the cheap rooms sold and the expensive ones did not | Counting a free upgrade as a sale |
Did each contract deliver what it promised?
Score every contract on what it actually produced against what it committed, and on the net revenue it left after discount, commission, included extras and the rooms it displaced.
Write the promise down first, in the contract's own words: allotment size, committed nights, rate, release period, payment terms, cancellation terms and what is included in the price. Then measure delivery: rooms actually taken rather than rooms allotted, pickup against the block, cancellations and no-shows, and the share of the allotment that was released unsold.
Convert to net. A contract rate that includes breakfast, a transfer and a late checkout is not comparable with a room-only rate until those costs are subtracted. Count displacement too: rooms given to a contract on dates you could have sold at a higher rate are a cost that never appears on the contract page. Check the release period against your own peak; if the contract holds rooms until a week before arrival and releases them late, you lost the chance to sell them elsewhere. Keep one page per contract with the same columns every year, so next season's negotiation starts from your own history rather than from the partner's summary. The same logic applies to agencies, as described in the agency production report: ranking partners by what they really bring.
Watch outVolume is not value
A contract can look strong on room nights and weak on net revenue: it fills dates you could have sold higher, includes extras you pay for, and releases unsold allotment too late to resell. Score every contract on net revenue after discount, commission, included extras and displaced rooms, and say so in the meeting before anyone praises the volume.
Which decisions actually worked?
A decision worked if the reason it was made still holds and the result moved the way you expected; anything else is a decision to review, not to repeat.
Read the decision log in date order and mark each entry worked, did not work, or too early to tell. Three marks are enough; a scoring system nobody maintains is worse than none. Keep the original reason beside the outcome, because a rate cut made to fill a weak week and a rate cut made to defend against a competitor are judged differently even if the numbers look the same.
Write the counterfactual in plain words: what you expected to happen if you did nothing. Without it, every outcome looks like it was caused by the decision. If no log exists, reconstruct one from what leaves traces: rate and restriction changes in the channel manager, promotion start and stop dates, contract amendments, staffing changes and the dates of guest complaints.
Look for decisions made twice. The same discount in the same week two seasons running is a pattern, not a decision, and it belongs in next year's plan as a rule. Separate the decision from the luck: a good decision in a month when the whole market was quiet still counts as a good decision, and a bad one hidden by a strong month will repeat. If you run one, the format comes from the weekly revenue meeting: agenda, reports and a decision log for a small hotel.
TipOne line per decision
Date, what was decided, why, who decided, what you expected, and the date you would review it. Six columns, no prose. The value is in the reason column, because that is the part everyone forgets by the following spring.
What do the booking window, cancellations and length of stay tell you?
They tell you whether the market bought early or late, how much of what you sold came back, and whether the guests you attracted stayed long enough to be worth the cost of serving them.
The booking window is the number of days between the reservation and the arrival. If it shortened, the market is buying later, and an early-booking discount is selling cheaply to people who would have paid more. If it lengthened, you sold early and cheap into a season that later filled on its own, which is a pricing decision showing up as a booking pattern.
Count cancellations and no-shows by channel and by rate plan. A free-cancellation rate that cancels often is a different product from a non-refundable one, and the two should not be compared on headline price. Remember the mechanism: a cancelled booking returns the room to inventory late, when the market has already bought. That loss is different from a room that never sold, and it needs a different fix.
Length of stay is a cost figure as much as a revenue figure. Two three-night stays cost more housekeeping, laundry and reception time than one six-night stay at the same total. Finally, check whether the restrictions you set did what you intended: a minimum-stay rule that pushed bookings into the channel that ignores it has moved the problem, not solved it.
What did guests complain about, and what did refunds cost?
Read complaints as a revenue document: the same complaint repeated is a cost you pay twice, once in the refund and again in the review that follows it.
Group comments by cause, not by date: room condition, noise, food and wait times, billing errors, and expectations set by the photos or the rate description. Total the refunds, comps, free upgrades and late checkouts given to fix problems, then attach that total to the segment and channel that generated it. One segment often carries most of the cost.
Billing errors are the cheapest to fix and the most expensive to leave: a wrong charge found at checkout becomes a refund, a card dispute and a public complaint. If the complaint is that the room was not what the photos showed, the fix is in the content, not in the training; change the description before you retrain the team. Give each recurring complaint two named owners, one for the physical fix and one for the description or process fix. Bring the guest relations lead to this part of the meeting even if they leave before the contract discussion; their evidence is the only part of the review that explains why a guest did not return.
How do you turn the review into three written changes?
Choose three changes, write each one as a change to a mechanism with an owner and a date, and check them in the first month of next season.
Three, not ten. A list of ten improvements is a wish list; three changes with names attached are a plan, and the season will start before you finish ten. Write the mechanism, not the intention: moving a release period from fourteen to seven days is a change, improving contract management is a sentence.
Each change needs four things: the evidence line from the review that justifies it, the person who owns it, the date it must be in place, and how you will know it worked. Put the three changes at the top of the same document as the decision log, so next season's review starts by checking them rather than rediscovering the problem. Set the review date before the season opens, and give one person the job of confirming the three are in place before the first busy week. Keep the rest of the findings in an appendix; they are not lost, and they are not competing with the three for attention. When the season approaches, the revenue checklist before the season opens: rates, contracts and restrictions is where these changes get tested.
| Change | Evidence from the review | Owner | In place by |
|---|---|---|---|
| Example: release period on a German allotment moves from 14 to 7 days | Allotted rooms released unsold in the peak week | Reservations manager | 1 March |
What to do next
Book the two-hour slot now, in the last two weeks of the season, and send the pack 48 hours before it. The pieces fit in one order: results by month, segment and channel show where the season moved, the contract pages show which partners paid for that movement, the decision log explains why you acted as you did, the guest voice prices the mistakes, and three written changes carry the season forward to the people who will run the next one.
Frequently asked questions
How long should an end-of-season revenue review take?
Two hours with a timed agenda and a pack sent 48 hours ahead. If it runs long, the pack was not read before the meeting and the time went to explanation instead of decisions. A second, shorter session can follow if the three changes need costing.
We did not keep a decision log this season. Can we still hold the review?
Yes. Reconstruct the log from what leaves traces: rate and restriction changes in the channel manager, promotion dates, contract amendments, staffing changes and complaint dates. Then start the log the same week, so next season's hotel end of season review does not depend on memory.
Should the review happen before or after the hotel closes for winter?
Before the last seasonal manager leaves, while systems are still open and people still remember the reasons behind the decisions. Closing the building is a separate operations checklist with its own sequence; the two meetings answer different questions and should not be merged.
How many changes should come out of the review?
Three. Each one written as a change to a mechanism, with the evidence line that justifies it, an owner, a date it must be in place and a way to check it. More than three and none of them survives contact with the opening weeks of the season.
Do we need revenue management software to do this review?
No. The review uses numbers the hotel already produces: reservations, invoices, channel statements, contract terms and guest comments. A spreadsheet with the same columns every year is enough, and consistency matters more than the tool.