Your Revenue Meeting Runs 60 Minutes. How Many Decisions Come Out of It?

A note for GMs, revenue managers, and sales leads — for the meeting that reappears in the calendar every week whether or not it earned its place.

Thursday, ten o’clock. The revenue manager brings a pace export. Sales brings the pipeline. Marketing brings last week’s campaign numbers. The GM brings questions. Fifty-five minutes later everyone leaves, and by Monday the only trace of the meeting is that it happened.

Ask the awkward question at the end of the next one: what did we decide? Not what did we discuss — what did we decide, in a form someone could act on tomorrow.

If the honest answer is “we agreed to keep an eye on October,” the meeting is a status report wearing a decision’s clothes. That’s fixable, and it doesn’t take a new tool to start.

The three failure modes

Weekly commercial meetings go wrong in the same three ways almost everywhere.

The data gets assembled in the room. Someone pulls a report while eleven people watch. Someone else says their number is different. The next ten minutes go to reconciling two exports rather than deciding anything. Assembly is preparation work, and preparation done in the meeting is the most expensive way to do it.

Everyone narrates their own view. Sales reports the pipeline, marketing reports the campaign, revenue reports the pace. Four monologues in sequence is a round of updates, not a discussion — nobody is looking at the same picture at the same moment, so nothing connects. The campaign that filled the second week of October and the rate you dropped in that same week are the same story, but they arrive as two separate agenda items twenty minutes apart.

There is no defined output. A meeting whose output is “alignment” cannot fail and cannot succeed. Nothing gets written, so nothing gets checked next week, so the same topic surfaces again in a fortnight with the same level of resolution.

Notice that none of the three is about the people in the room. They’re structural, which is the good news: structure is cheap to change.

Fix one: the data is ready before anyone sits down

The rule is simple to state and unpopular to adopt. Whoever brings a number is not allowed to defend it in the meeting. Data questions (“why does your ADR differ from mine?”) go into a parking list and get resolved afterwards, by two people, offline.

For that to be fair, the numbers have to come from one place. One view, one definition of ADR, one on-the-books position that everyone can see. Four exports from four systems will always produce four slightly different truths, and the meeting will always spend its best fifteen minutes adjudicating them.

If you’re not there yet, the interim version works: one person owns the pack, publishes it the day before, and the rest of the team reads it before the meeting. That single change gives the room more time for decisions.

Fix two: an agenda that starts with the exceptions

The default agenda walks through everything and runs out of time before the decisions. Invert it. A 45-minute version that survives contact with a real hotel:

• 5 min — last week’s decisions. Status of every open item: done, in progress, or dropped. This goes first, deliberately: it makes the meeting a loop rather than a series of fresh starts, and it is the single most commonly missing agenda item.
• 10 min — the exceptions. Not “here is the month.” Which dates moved away from plan since last week, in either direction. Pickup and pace against expectation, ranked by how far off they are.
• 10 min — the next 30 to 90 days. Where a decision is actually needed now: dates approaching their booking window with the wrong shape, restrictions to set or lift, rate levels to confirm.
• 10 min — market and competitors. What moved outside the hotel: compset rate changes, events, market indexes. Read as context for the dates above, not as a separate performance review.
• 5 min — groups and pipeline. Open opportunities that need a rate call or a hold decision this week, plus anything that has slipped a stage.
• 5 min — read the decisions back. Out loud, in the room, before anyone stands up.

Two structural notes. Keep the room small — the people who can decide, typically four to six. A meeting with eleven attendees is a broadcast, and broadcasts should be documents. And if a topic needs more than five minutes of investigation, it isn’t a meeting item; it’s a task with a name and a deadline attached.

Fix three: what a decision actually looks like

The reason “we’ll monitor October” isn’t a decision is that it’s missing five of its six parts. A usable one has all of them:

1. What we’re changing — the specific rate, restriction, allocation, or answer.
2. Which dates it affects.
3. Why — the number or observation that prompted it.
4. Who executes it.
5. By when.
6. When we look again to see what happened.

Point 3 is the one that gets dropped, and it’s the one that pays. A year from now, “dropped BAR €15 on the last two weeks of October” tells you nothing about whether it was reasonable. “Dropped BAR €15 on the last two weeks of October because pace was 22% behind same point last year and the compset had already moved” tells you exactly what you were thinking — and lets you judge the thinking rather than re-litigating the result. That’s the raw material for a proper season debrief later.

Point 6 matters almost as much. A decision with no review date is a decision nobody will ever learn from.

How to tell whether it’s working

Four numbers, none of which need a system to track:

• Decisions per meeting. Not a target to game, but a floor to notice. A commercial meeting that produces zero decisions three weeks running is a meeting that should become an email.
• Carry-over rate. Share of last week’s decisions still open. Consistently high means you’re deciding things nobody has time to execute — a capacity problem masquerading as a discipline problem.
• Repeat topics. How often the same date or issue comes back without resolution. This is the clearest sign that discussions are ending without output.
• Length. A meeting that keeps overrunning is usually doing assembly work in the room. That’s fix one, not a scheduling problem.

The trap on the other side

There’s an opposite failure worth naming, because teams that read articles like this one sometimes run straight into it: the meeting that becomes a decision factory. Twelve decisions logged, none executed, everyone slightly embarrassed by week three.

Decide fewer things and finish them. Three decisions with owners and dates beat twelve entries in a document. The carry-over rate above is the honest check on this, which is why it’s on the list.

(Full disclosure, since this is our product: Peaqplus includes a Revenue Meeting workflow in BI Core on every plan — a fixed agenda assembled before the meeting from the same shared view, open decisions and follow-ups pulled to the top, and the record of what was decided kept with its reason and affected dates. The Decisions module holds the Revenue Track between meetings. The discipline in this article predates any software and works with a shared document plus a recurring calendar entry; the tool removes the assembly, not the thinking.)

Frequently asked questions

How often should we hold a revenue meeting?

Weekly for most independent hotels, with a fixed slot. Fortnightly works in genuinely stable, low-season periods, but the gap starts to hurt as soon as demand moves: decisions made two weeks late on dates inside their booking window are usually decisions made after the market already answered. A short daily check — often solo, not a meeting — covers what changed overnight; see the revenue manager’s morning routine.

Who should run it — the GM or the revenue manager?

Whoever owns the numbers should present, and whoever owns the outcome should chair. In practice that means the revenue manager (or whoever prices) walks the exceptions, and the GM holds the agenda, keeps it to time, and closes each item with a decision. If the same person does both and the meeting is drifting, hand the timekeeping to someone else — it’s harder to chair and argue simultaneously than it looks.

We’re a small hotel — it’s me and the GM. Do we need this?

The meeting scales down to twenty minutes; the parts that matter are the ones that survive. Keep the same three: last week’s decisions, the exceptions, and a written record of what you decided. Two people forget just as reliably as six, and a small team has less slack to absorb a decision that quietly evaporated.

Where to go from here

The glossary covers the vocabulary: revenue meeting, decision log, pace, and pickup. On the platform side, Decisions shows the meeting-to-follow-up workflow and Insight Engine the shared view the agenda is built from. For the season-scale version of the same loop, read the season debrief.

An hour a week is roughly fifty hours a year of your most expensive people. It should end with more than a shared feeling that October looks fine.