Meetings and Events Drive Up to 30% of Hotel Revenue. Most Hotels Cannot Pace It.
M&E contributes 20-30% of revenue at the average hotel, per IDeaS, yet most events teams lack pace data. A new analysis lays out the case for weekly reporting.
Meetings and events generate 20% to 30% of revenue at the average hotel, according to IDeaS, yet most properties still measure that revenue stream with a function diary and a stack of proposals rather than a pace report. Conference-led hotels earn an even larger share from events. A revenue stream of that size operates without the weekly forward view that rooms have had for two decades.
The gap shows up in how teams answer a basic question. Ask a revenue manager how next March is tracking and the answer comes in seconds: rooms on the books, the same point last year, the variance, the plan. Ask the events team and the response is usually a walk through the diary and a list of promising proposals. The article's author notes this is not a failure of events teams, who in most cases have never received the data or the tools to answer differently.
What does half a picture cost?
Consider one worked example from the analysis. A two-night conference for 80 delegates produces $28,000 across function space, catering and AV. Its room block adds 160 room nights at $210, or $33,600. That is a $61,600 piece of business. The revenue manager sees only the room block in the group pace report. The events team sees only the $28,000 in the diary. Nobody weighs the full $61,600 against how the month is actually tracking.
The author argues each team then makes decisions that are right by its own numbers while the hotel still leaves money on the table. Revenue might reject a group because the room rate sits below transient expectations, without seeing the attached catering. Events might discount a room to win a day meeting on a date that could have anchored a residential conference.
Why pipeline reports are not enough
Most events teams already track a pipeline. The author draws a sharp line between the two formats. Pipeline shows what might come in. Pace shows what is actually on the books for a future period against the same point last year, or against budget. Pipeline is hope weighted by probability. Pace is a fact you can act on early enough to change the outcome.
The stakes are higher for function space than for almost anything else in the hotel, the author writes, because once an empty date passes the revenue is gone for good.
What broke the data?
Event bookings are structurally messier than room bookings. One booking can span three spaces over two days, with catering by day part, AV and a room block attached. It can sit as a tentative hold for six months and change value three times before contracting. Many event systems also report only from today's data, overwriting history and keeping no record of what was on the books a year earlier.
That last defect is the one the author would fix first. You cannot reconstruct last year's position after the fact. The recommended interim fix: start a weekly snapshot now, even a spreadsheet export. In 12 months the hotel has its first true year-on-year comparison. Every week of delay pushes that date back.
What should an event pace report contain?
The author specifies six components:
- Revenue by event date, not booking date. What is on the books for March, not what was signed in March.
- Definite and tentative business reported separately. Tentative holds inflate totals; optimistic holds should not hide a soft month.
- Movement, not just totals. New bookings, upsells, cancellations, value changes and room blocks cut before arrival.
- Segment and lead time. If corporate meetings book eight weeks out and weddings nine months out, a gap four months away remains a corporate opportunity.
- Day part. A month can look fine while Monday and Friday mornings sit empty.
- Lead source and salesperson. Which channels feed future business and whose pipeline has stalled.
Does a combined view change group decisions?
The author proposes placing events and rooms side by side for the same period, against the same comparison point. This exposes shifts neither report shows alone, such as a month healthy on event revenue while attached room nights run below last year, usually a sign of a drift from residential conferences to day delegates. Displacement analysis based only on room revenue tends to undervalue groups. A group that looks marginal on function space can look very different once room nights are added; a big room block with little food and beverage may deserve harder pricing.
How often is often enough?
Weekly review, the author argues, because corporate events book close in. FCM Meetings & Events' 2025 Global Trends Report found a third of corporate event venues were booked within three months of the event and 60% within six months. A gap can open and close inside a month, so a monthly report will miss it.
The recommended format is a 30-minute weekly meeting with events, revenue and the director of sales, restricted to three questions: where are we behind over the next 90 days and why, which tentatives need a decision, and what are we doing about it. One person owns the follow-through.
The author's claim that combined reporting improves every group decision is an argument, not a measured result, and no case data appears in the analysis. Still, the sector has already run this experiment once. Rooms forecasting became a discipline over two decades. The hotels that bring events to that standard, the author concludes, will make better calls on every group they are offered.
More from Marcus Bennett
Show full bio
Market editor covering technology and product news in Restaurant and hotel operations at The Pass Brief.
524 articles


