Leading the revenue meeting — beyond the structure

Monday morning, Oct 26, 7:40. The weekly revenue meeting is scheduled for the usual Monday 16:00 slot, with the usual agenda. Daniel opens the pickup report with coffee in hand (pickup — the net change in bookings that arrived over a given period) — and his hand stops. November’s net pickup over the weekend: −104 room-nights.

He drills in. New bookings over the weekend were +16 — normal. Cancellations, however, were −120 room-nights, and all of them belong to the same company: one of the hotel’s largest corporate partners, a technology company, cancelled all of its November bookings on Friday evening. Spread across four weeks, weekday nights, at an 88 EUR negotiated rate. Daniel does the quick maths: 120 × 88 = 10,560 EUR of room revenue that was still sitting in the November forecast on Friday afternoon — and is gone by Monday morning.

At 8:10 Daniel messages the meeting participants — Adam, the GM, the sales manager and Esther, the marketing manager: “Today’s meeting focuses on the November corporate cancellation wave. We compress the routine agenda to 15 minutes. Please review the November numbers before the afternoon.”

This lesson is about what happens at 16:00. Many hotels know the structure of the revenue meeting — we built it in lesson 28 — but the meeting’s real value shows when the structure is not enough: when the week is not a routine week but a live situation. A good revenue meeting doesn’t collapse at that point — it switches modes. And for that you need a decision frame, a prioritisation logic and a follow-up system.

The routine revenue meeting — briefly

Before we switch to crisis mode, let’s fix the normal state — we covered the details in lesson 28 (The structure of the weekly revenue meeting). The weekly revenue meeting is a fixed element of the RM operation: at Hotel Peaqplus City it is Monday 16:00, exactly 60 minutes, with a standing cast (RM, GM, sales, marketing, F&B, front office). The agenda has five hard sections: last week review (10 minutes) → the next 14 days’ outlook (15 minutes) → top actions for the week (15 minutes) → group contracts (10 minutes) → other questions (10 minutes). Three principles hold it together — keeping to time, action orientation, data-driven debate — and the meeting always opens with the status of last week’s action list (we will come back to this).

This skeleton works as long as the week is a routine week. But a revenue meeting isn’t good because its agenda is pretty — it’s good because decisions are made in it, and they get executed. And that is decided precisely in the live situations. Lesson 28 gave you the structure — this lesson is about how you lead the meeting when the structure alone is not enough.

When the structure is not enough — the switch

By Monday morning the routine agenda had become pointless: reading through the next 14 days’ outlook as if 10,560 EUR were not missing from November would be a waste of time. The first leadership decision is therefore the agenda itself: Daniel doesn’t improvise at 16:00, in the meeting — he rewrites the focus at 8:10 and asks for preparation.

This looks like a small thing, but it isn’t. The bad script goes like this: the meeting starts on the routine agenda, in minute 12 someone mentions the cancellation, everyone starts talking at once, Adam immediately proposes a rate cut, the sales manager gets defensive, and after 60 minutes everyone leaves — without a decision. In a live situation the meeting needs leadership, not moderation. And the tool of leadership is a five-step decision frame.

One thing Daniel does not save for the meeting. The operational protection he can do on his own authority he completes before noon: he checks that no restrictions sized for high occupancy are left on the freed nights (MLOS, closeouts — lesson 42), and that BAR and channel visibility are in order — the booking window for the first November week is open right now, and every day counts. What reaches the meeting is therefore not a to-do but a status. Whatever touches money, priorities or someone else’s team — a promotion, a group callback, a partner call — is decided in the afternoon, run through the frame.

The decision frame for a live situation

Step 1: DATA — what exactly happened?

Before anyone offers an opinion, the data goes on the table. Not “a lot of November cancellations came in”, but in numbers, broken down by date:

And room revenue is not the whole damage. In lesson 45 (Introduction to Total Revenue Management) we saw that every guest brings ancillary spend too. The corporate guest spends modestly and typically travels alone (one guest per room) — at Hotel Peaqplus City the average is 12 EUR per guest per night (F&B beyond breakfast, parking). The lost ancillary: 120 × 12 = 1,440 EUR. The total revenue hole: 10,560 + 1,440 = 12,000 EUR.

Concentration matters too: in week 3 the cancellations run at 14 rooms a night, Tuesday to Thursday — in an 80-room house that is 17.5 points of occupancy a night. This is no longer noise: this is an event that redraws the picture of the month.

Step 2: DIAGNOSIS — isolated or systemic?

The second question is not “what do we do” but what are we facing. Three hypotheses need to be separated:

• A partner-specific cause: the company is cutting costs, closed a project, switched suppliers. The travel manager’s Friday-evening email says a lot here: “Q4 travel freeze, central decision.” This is a partner-side cost stop — they have no problem with the hotel, and none with the market either.
• A market signal: if several corporate accounts’ pace (pace — the speed at which bookings build compared to the usual booking curve, lessons 17 and 37) drops at once, that is a sign of an industry slowdown — an entirely different game (forecast revision, lesson 38). Daniel checks: the other corporate accounts’ November pace is in its usual band, and there is no panic signal in the compset’s behaviour either (lesson 44).
• A recurring pattern: in lesson 29 we saw the washing factor — the attrition between the rooms blocked and the rooms actually used. If a partner routinely over-books and cancels in blocks, that has to be priced into the forecast going forward. That is not the case here: the company travelled with 90%+ reliability for years.

Diagnosis: an isolated, partner-side event. This is critical because the response toolkit depends on it — for a market slowdown we change strategy; for an isolated hole we organise a tactical backfill.

Step 3: OPTIONS — with numbers

The third step is thinking through the resale options for the freed 120 room-nights — week by week, because the decisive variable is the booking window (how much time is left in which people typically book the given date; lesson 10, with the curve logic in lesson 37):

• Week 1 (one week out): business transient books 1-2 weeks before travel — this window is open right now. The operational protection (BAR, restrictions, visibility) was done in the morning; the meeting’s job is a realistic estimate of the backfill potential: 10 room-nights × 105 EUR = 1,050 EUR.
• Weeks 2–3 (2-4 weeks out): the window for leisure city-break demand is still open — this is where a targeted midweek promotion fits, using the toolkit of lesson 46. Realistic backfill: 22 room-nights × 92 EUR average rate = 2,024 EUR. And 92 EUR is above the cancelled 88 EUR negotiated rate — the backfill is not rate erosion.
• Week 3 — the group card: three weeks ago sales declined a 15-room, 2-night group request for exactly these days, at 75 EUR — back then the displacement calculation (displacement — the higher-value demand crowded out by a lower-value booking, lesson 40) said no. But the displacement inputs have changed: 14 rooms a night have been freed on these dates, and the refreshed demand forecast will not refill them — the group now displaces almost no one. If the request is still alive, the 30 room-nights × 75 EUR = 2,250 EUR is close to pure gain. The lesson generalises: a large cancellation reopens every earlier group rejection — the ceiling logic of lesson 41 is a living system, not a one-off decision.
• Week 4 (4-5 weeks out): the booking window here is still wide — normal pickup has a good chance of refilling part of the hole on its own. The right decision here is deliberate non-action: we track it, and we only touch it if pace is still behind two weeks from now.

Adding it up, the realistic backfill potential: 1,050 + 2,024 + 2,250 = 5,324 EUR — 50.4% of the 10,560 EUR room-revenue hole. This is an important, sobering number: a cancellation wave can almost never be fully recovered, and whoever promises the owner a 100% backfill is either about to erode rates or preparing a disappointment. The goal is the maximum realistic recapture — with rate discipline.

Step 4: DECISION + OWNER + DEADLINE

At the meeting the options become decisions — and here the form is the method itself: one decision = one sentence + one owner + one date, in writing. “Everyone keep an eye on November” is not a decision. “Esther takes the midweek promo live by Wednesday for the week 2–3 nights” — that is.

And the non-decision is recorded with the same discipline: “No action for week 4; we review next Monday.” If this isn’t written down, in two weeks nobody knows whether week 4 is empty because we decided so — or because we forgot.

Step 5: FOLLOW-UP — metric and review point

Every action carries a metric (what we watch to know it’s working) and a next review point. The promo’s metric is not “did the campaign go out” but how many bookings arrived for the affected nights. For the rate/visibility correction it is daily pickup on the targeted dates. And the keystone of the system: the first agenda item of the next weekly meeting is always the status of the previous action list — exactly as the structure in lesson 28 prescribes. Without it even the best meeting decision evaporates — an action list without follow-up is just minutes.

The action-prioritisation matrix

When a live situation produces more action candidates than capacity, the order is decided by a simple 2×2: revenue impact × speed of execution. Filled in with the November actions:

The matrix protects against two common mistakes. One is that the team starts with the most visible action instead of the fastest-biggest one. The other is postponing the slow-big actions (the group callback) on a “when there’s time” basis — when those are exactly the ones that must be started immediately so they mature in time. And the bottom-right cell’s lesson: whatever is not this week’s solution goes to the backlog explicitly, instead of hovering over the meeting.

Meeting-leadership principles in a live situation

The frame alone is not enough — poor leadership can wreck even the best frame. Five leadership principles Daniel holds to at 16:00:

1. Data on the table BEFORE any opinion is voiced. The first 5 minutes present the cancellation table and the diagnosis data. Until there is a shared picture of the numbers, every contribution only reinforces reflexes — Adam’s rate-cutting instinct included. The reflex response is rarely the system response.
2. Postponing the “who is to blame” conversation. The “could we have seen this coming?” question is legitimate — but not now. In a live situation blame-hunting kills problem-solving: everyone starts defending instead of bringing options. The lessons-learned loop gets its own slot, two weeks later, calmly.
3. Time-box. The routine block is 15 minutes, the live block 45 — subdivided too: 5 minutes data, 10 minutes diagnosis, 15 minutes options, 10 minutes decision, 5 minutes reading back the action list. The time-box is not bureaucracy: it is what keeps the meeting a decision-making forum when it wants to sprawl into an analysis workshop.
4. One decision = one sentence + owner + deadline, in writing. Captured live, during the meeting — not afterwards from memory. The read-back in the final 5 minutes exists so that everyone leaves with the same thing.
5. The non-decision is also a recorded decision. The week 4 line — “we don’t touch it, review on Monday” — goes onto the action list with the same weight as the promo.

The follow-up system — the action-list format

The output of the Monday meeting is a single table. This is not admin — this is the product:

Next Monday the meeting opens with this table, line by line: done / in progress / stuck — and if stuck, why, and what it needs. This feedback loop is what turns the revenue meeting into a system: the team learns that whatever goes onto the action list will be followed up — and from then on only things people genuinely commit to go on it. Cancellation management itself is a broader task, by the way: block-cancellation patterns must also be handled long-term in the forecast and in contract terms (cancellation windows, guarantees — lesson 23) — but that is the territory of contract policy, not of the Monday meeting.

Back to Monday

At 17:00, exactly at the end of the 60 minutes, the meeting ends. Five lines on the action list, each with an owner and a date. Adam’s rate-cut proposal is not among them — he took it off the table himself in the diagnosis phase, when it turned out the market hadn’t moved; a single partner had stopped. “So we’re not repricing the market — we’re patching a hole,” he summarised, and that is exactly the right frame.

Two weeks later, the standing: the group reconfirmed (2,250 EUR), the promo had brought 17 nights so far, and week 1’s business pickup, with the corrected visibility, refilled half of that week’s hole. Week 4’s pace is closing on its own — the non-action was the right decision. Total recapture is approaching half of the hole, just as the meeting estimated — and more importantly: the November forecast now shows reality, not Friday afternoon’s illusion.

The difference was not luck. The same cancellation wave with an unled meeting ends like this: 60 minutes of debate, a closing sentence of “everyone keep an eye on November”, and three weeks later a panic promo negotiated from a much worse position.

Manually vs. Peaqplus

Manually, meeting preparation is report-hunting: a pickup export from the PMS, an Excel comparison against last week’s state, cancellations collected by partner by hand — an hour in the good case; in the bad case the cancellation wave goes unnoticed until Monday morning. And the meeting’s output is typically a note sent around by email that sinks within a week: decisions can’t be looked up, nobody maintains the action statuses, and the question “what did we agree last week?” gets three different memories as an answer.

In Peaqplus, spotting the situation is part of the daily routine: negative pickup shows up immediately, date by date, and can be drilled into to see where it comes from — Daniel’s 7:40 discovery is not luck but routine (lesson 50 covers this in detail). And the meeting’s frame is provided by the Revenue Meeting module: the agenda is built on live data — no separate report pack to assemble —, and the decisions and actions made in the meeting can be recorded and tracked with owners and deadlines, so next week’s “previous actions status” agenda item is not a memory test but the reading of a list. It does not replace the five steps of the decision frame or the leading of the meeting — that is your job — but it takes the data-preparation and follow-up burden off you.

Key takeaways

• The revenue meeting’s value is not in its structure but in the fact that it produces decisions even in live situations. The structure comes from lesson 28 — in a live situation you must be able to set the routine agenda aside, and that is decided before the meeting, not during it.
• The five steps of the live-situation decision frame: DATA (in numbers, broken down by date) → DIAGNOSIS (isolated or systemic?) → OPTIONS (with numbers, by booking window) → DECISION (owner + deadline, in writing) → FOLLOW-UP (metric + review point).
• A cancellation wave can almost never be recovered 100% — in the November example the realistic potential is 5,324 EUR, 50.4% of the 10,560 EUR hole. The goal is maximum recapture with rate discipline, not a panic cut. And a large cancellation reopens every earlier group rejection, because the displacement inputs changed.
• The order of actions comes from the revenue impact × speed matrix: fast-big actions today, slow-big ones started today (so they mature in time), slow-small ones explicitly to the backlog.
• The non-decision is also a decision — recorded, with a review date. And the keystone of the follow-up system: the next meeting always opens with the status of the previous action list.