Weekly revenue meeting: agenda, reports and a decision log for a small hotel
A weekly revenue meeting needs a fixed agenda, four one-page reports and a decision log. This guide shows how to run it in thirty minutes, who decides what, and how to record every choice with a reason and a review date.
Contents
Key takeaways
- Four one-page reports are enough: what is on the books, pickup since the last meeting, your rates against a named competitive set, and the state of groups and contracts.
- The meeting decides reversible moves inside written limits; anything that changes a contract, a rate floor or a commitment beyond the season goes to the owner with a deadline.
- A decision log records what was decided, why, who owns it and when it will be reviewed, and each meeting opens by checking the items that are due.
- Rates are set by a person: the meeting's job is to decide with reasons and write them down, not to hand the decision to a tool.
A weekly revenue meeting is a short, fixed-agenda meeting where the general manager, reservations, front office and accounting leads review what is on the books, decide rate and channel moves inside written limits, and record each decision with a reason, an owner and a review date. It lasts about thirty minutes.
The meeting starts with someone saying the numbers are down, moves through six topics at once, and ends with nobody sure what was decided last week. A small hotel does not need a revenue department to fix that. It needs a fixed agenda, four one-page reports and one page of decisions. After reading this you will be able to run that meeting, know exactly who decides what, and open each week by checking the decisions that are due for review.
Who should attend a weekly revenue meeting, and who decides?
Four roles attend and one person decides. In a hotel without a revenue department that person is usually the general manager, working inside limits the owner has written down.
Attend: the general manager as chair, the reservations or sales lead, the front office lead and accounting. Housekeeping joins only for a specific item, such as a room out of order that changes what can be sold. Keep the room small. Each extra attendee adds a report and a debate, and the meeting drifts past its time box.
Separate three rights and say them out loud once: the person who brings a number, the person who recommends, and the person who decides. Confusing them is why the same argument returns every week. Give every action one name, because an action with two owners has none.
Write the limits down before the first meeting: a rate floor and ceiling, a maximum discount, the largest group the meeting may accept, and who may give an upgrade or a complimentary night. The meeting then stops renegotiating its own authority every week.
Be clear about what this meeting is not. It is not a sales pipeline review and not a finance review. It decides what to sell, at what price, to whom, and what to stop selling.
What should you bring to a hotel revenue meeting?
Four one-page reports: what is on the books, pickup since the last meeting, your rates against the competitive set, and the state of groups and contracts. Each is produced the same way every week, with its source and date on the page.
On the books shows rooms and revenue already sold for the next 14 days and the next 90 days, compared with the same lead time before arrival last year, not the same calendar date. Comparing today with last year's final result tells you nothing you can act on. Pickup shows rooms added since the last meeting, split by arrival week and by channel; a pickup figure without a comparison is a number without a meaning. For reading pace properly, see how to read a hotel pickup report day by day.
The rate comparison sets your published and contracted rate for a handful of future dates against named rivals, same room type and same board basis. If the comparison is unfair, say why on the page; fair comparison rules are covered in choosing a competitive set and comparing rates fairly. Groups and contracts lists every block with a release date in the next 30 days, every allotment, and every contract expiring inside the selling window.
One page each, same layout, same definitions. A report that changes shape every week cannot be compared with itself. Put the source and the date in the header of every page: six weeks later, a number without a date cannot be defended or explained.
ChecklistWeekly report checklist
- On the books, next 14 days and next 90 days, against the same lead time last year
- Pickup since the last meeting, by arrival week and channel
- Rate comparison against named rivals, same room type and board basis, a handful of dates
- Groups and contracts: release dates in the next 30 days, allotments, expiring contracts
- Source and date on every page
- One page per report
One note on preparation. AI Otel's PMS assistant is built and writes a plain-language briefing every morning from the hotel's own numbers, and price suggestions arrive with their reasons, with a person approving them. It prepares the reason; the meeting still makes the decision.
What is a workable agenda for a weekly revenue meeting?
Five questions in a fixed order, each with a time box: last week, the next 14 days, the next 90 days, groups and contracts, channel issues. The order matters more than the content, because it stops the loudest topic from eating the meeting.
| Order | Question | Time | Output |
|---|---|---|---|
| 1 | What did we decide last week, and what happened? | 5 min | Log items closed or rescheduled |
| 2 | What are we doing about the next 14 days? | 7 min | Rate, minimum-stay and channel decisions for specific dates |
| 3 | Where is the next 90 days behind or ahead, and what can we do now? | 6 min | One or two moves, or a written note that nothing has changed |
| 4 | Which groups and contracts need a decision? | 6 min | Accept, hold, decline, re-price or release, with a reason |
| 5 | Which channel problems need an owner? | 6 min | Named actions with dates |
Last week is the only backward-looking item: what we decided, what happened, what we learned. It feeds straight into the decision log. The next 14 days is the window where a decision can still change the outcome: occupancy, rate, a minimum-stay rule, a channel opened or closed for a date range.
The next 90 days is where you look for pace that is behind or ahead and ask what move is available now. It is not a forecasting exercise and should not become one; the method for estimating that window is covered in estimating the next 90 days from what is on the books. Groups and contracts is a decision item, not a status item: accept, hold, decline, re-price or release, with the reason attached. Channel issues covers a rate or availability mismatch, a parity break, a channel that stopped producing, or a booking that arrived with the wrong details.
Anything that needs longer than its box becomes a separate item with two named people and a deadline, and it comes back to the next meeting.
Which decisions can the meeting take, and which go to the owner?
The meeting decides reversible, in-season moves inside written limits. The owner decides anything that changes a contract, a rate floor, a headcount or a commitment that runs past the season.
The meeting decides: opening or closing a channel for a date range, a minimum-stay rule, a rate move inside the agreed band, releasing an unsold block, accepting a small group inside the limits, an upgrade or a complimentary night inside policy. The owner decides: rate floor changes, new or renewed contracts, allotments, large group commitments, anything that obliges the hotel beyond the current season, and any capital spend.
Key pointThe reversibility test
If the move can be undone next week at little cost, the meeting decides it. If it cannot, it goes to the owner with the number, the options and a deadline.
Escalation is not delay. The item goes to the owner with the number behind it, two or three options and a date by which an answer is needed, and it appears in the log as open. Record who decided, not only what was decided: a decision without a name cannot be reviewed and cannot be corrected. Rates are set by a person. A tool can prepare the comparison and the reason; the approval is human, and the log shows who gave it.
What goes into a revenue decision log?
One line per decision: the date, what was decided, the reason, the owner, the review date and the outcome when it is reviewed. It is one page, kept in one place, by one person.
| Date | Decision | Reason | Owner | Review date | Outcome |
|---|---|---|---|---|---|
| 12.06 (for example) | Close one channel for a three-night window around a local event | Same room type cheaper on that channel than on our own site | Reservations lead | 19.06 | Parity restored, channel reopened |
The reason column is the one that survives. Six weeks later nobody remembers why a rate was cut or a block released, only that it happened. The review date is set when the decision is made, never later. A short move gets a short review: a weekend rate change is checked the following week, a contract decision at the next natural milestone.
Nothing is deleted. A decision that turned out wrong stays visible with its outcome, which is how the meeting learns anything at all. Keep it in one file with one owner; a log split across emails, notebooks and memory is not a log. One page per month is enough for a small hotel. The value is in the review, not in the volume. Distinguish the log from minutes: minutes record what was said, the log records what was decided and when it will be checked. The wider context is covered in revenue management for independent hotels.
How does the log open the next meeting?
The first five minutes belong to the previous log, not to new numbers. Read the items due for review, close them or move the date with a reason, and only then look at this week. This ritual is what turns a series of meetings into a system: each meeting checks the work of the last one.
How do you keep a revenue meeting to thirty minutes in season?
Pre-work, a fixed order, a timekeeper and one rule: anything unresolved leaves the room as an action with a name and a date. The length comes from preparation, not from the agenda.
Circulate the four reports the evening before. The meeting reads conclusions, not pages. Open with the log review, five minutes, then run the remaining four questions in order. One person keeps time and says the remaining minutes out loud at each transition; this is a role, not a personality.
Do not re-open a decision before its review date. If new information arrives, log it and move the review date, and say why. In high season, replace the 90-day item with a written note on weeks where nothing has changed, and spend the time on the next 14 days. End by reading the log back: decisions, owners, dates. If it is not written before people leave the room, it will not be written.
Cancel the meeting when there is genuinely nothing to decide, and say so in the log. A meeting held for its own sake teaches people to bring noise. For the daily rhythm between meetings, see what a GM's morning page should contain.
TipProtect the opening ritual
The first five minutes belong to the previous log, not to new numbers. Read the items due for review, close them or move the date, and only then look at this week.
What to do next
Write two things this week, before the next meeting: the one-page decision log and the short list of limits that says what the meeting may decide and what goes to the owner. Then run the next meeting from the log, opening with the items due for review. The four reports, the fixed order and the log are the whole system; the discipline of checking last week's decisions is what makes it work. OtelCiro, the ecosystem's hotel growth and consultancy arm, works with paying hotel clients today and can sit in on that first meeting. You can also request a briefing.
Frequently asked questions
How long should a weekly revenue meeting last?
About thirty minutes in season and no more than forty-five off season. The length is set by pre-work: reports circulated the evening before and a fixed order with time boxes. If it regularly runs long, the problem is preparation or an unclear decision right, not the agenda.
Do we need revenue management software to run this meeting?
No. Four one-page reports from the property management system and a spreadsheet are enough to start. Software helps with consistency, history and the log, but the meeting's value comes from the fixed order and the review of past decisions, and both can be done on paper.
What if the hotel has no revenue manager?
The general manager chairs and decides inside written limits, and the owner keeps a short escalation list: rate floor, contracts, allotments, large groups, anything beyond the season. The reservations lead usually owns the reports. The point is to name the decision maker, not to create a new role.
How is a revenue decision log different from meeting minutes?
Minutes record what was said. The log records what was decided, the reason, the owner and the review date, and it is read at the start of the next meeting. It stays open until the outcome is recorded, and nothing is deleted, including decisions that turned out wrong.
Should we still hold the meeting in high season when little changes?
Hold it, but shorter: keep the log review and the next 14 days, and replace the 90-day item with a written note where nothing has changed. Cancel it openly when there is genuinely nothing to decide, and record the cancellation, so the meeting keeps its meaning.