The catering pace playbook: managing the one revenue line nobody paces

Picture the Monday revenue meeting. Rooms pace is on the screen and the team works it for forty minutes. Pickup by segment, the soft week three weeks out, the corporate hold that fell off Tuesday, the decision to drop the shoulder rate. Everyone knows the number to the dollar and everyone has an opinion about it. Then someone reads the catering figure off a second tab. One number. Nobody questions it. The meeting moves on.

That gap is the whole problem. At a full-service or convention hotel, catering and banquet revenue is often a quarter or more of the total, and at some properties it rivals rooms. It is also the line that gets paced the least, governed the least, and forecast the worst. Rooms get a revenue manager, a system, and a pace curve. Catering gets a sales team chasing events and a number that arrives after the month is already decided. We pace the smaller, more elastic, more visible line obsessively and let the larger, lumpier, harder line run blind. This is the playbook we use to fix that.

Why catering is the blind spot

The reason is structural, not lazy. Catering revenue does not live where revenue management lives. Rooms data sits in the PMS and the RMS, the two systems a revenue manager opens every morning. Catering data sits in Tripleseat, or Delphi, or Amadeus Sales and Catering, a system the rooms team rarely logs into and the sales team treats as a CRM, not a pace tool. The two never join. So the revenue manager paces what is in front of them and the catering managers chase the events in front of them, and no single person owns the pace curve for the larger line.

The second reason is that catering is lumpy in a way rooms is not. One wedding or one corporate gala can move a week. A single association that books three years out distorts every same-time comparison. Rooms pace is a smooth curve you can trust to trend. Catering pace is a step function, and step functions scare people off measuring them at all. That is exactly backwards. The lumpier the line, the more it rewards a disciplined pace view, because the lumps are where the money and the misses both hide.

What “pace” actually means for catering

Rooms people already know pace. The translation to catering needs three distinctions or the curve lies to you.

Booking pace versus consumption. Booking pace is revenue on the books for a future period, measured as of today versus the same point last year. Consumption is revenue that actually happened. Catering teams almost always look at consumption, because that is what the P&L shows. Consumption tells you how you did. Only booking pace tells you how you are going to do, while you can still change it.

Definite versus tentative. Every sales-and-catering system carries holds at different probabilities. A pace curve that counts only definite revenue understates the pipeline and panics the team. A curve that counts all tentatives at full value flatters it and hides the soft week. You need both lines on the same chart: definite as the floor, definite-plus-weighted-tentative as the ceiling. The gap between them is your conversion job for the period.

Pace to budget and pace to last year. These answer different questions and you need both. Pace to same-time-last-year tells you whether demand is stronger or softer than the shape you have seen before. Pace to budget tells you whether you will hit the number the owner is expecting. A period can be ahead of last year and behind budget at the same time. If you only watch one, you will be surprised by the other.

The playbook

Step 1. Build the curve before you build anything else

Pull definite and tentative catering revenue out of your sales-and-catering system by event date, not booking date, and stack it against the same snapshot from last year. This is the single artifact most properties do not have. Not a report of what booked this week. A curve that shows, for every future month, how much revenue is on the books today versus where it stood a year ago. If you can only make one thing, make this. Everything else is reading it.

Step 2. Pick the denominator, then segment

Pace is a ratio, and the denominator decides the story. Run it two ways, to budget and to STLY, every time. Then segment, because catering is three different businesses wearing one P&L line. Social (weddings, galas, milestone events) books weeks to months out and converts on emotion and space. Corporate (meetings, conferences, holiday parties) books on a tighter, more predictable window. Association and group-tied catering books years out and follows the room block. Each has its own pace shape. Blend them and you get an average that describes none of them and warns you about nothing.

Step 3. Watch the booking window, not just the total

The total on the books is the lagging number. The leading number is the window: how far out events are booking compared to last year. When the booking window is shrinking, business is coming in later, and a period that looks soft today may fill late. When the window is stretching, you are pricing or holding space in a way that is pushing business out, and a period that looks fine today may be quietly emptying. The window turns before the total does. Most teams never plot it, so they react a month late, every time.

Step 4. Separate the three levers

When a period is behind, “sell more” is not a plan. Catering revenue moves on three distinct levers and the fix is different for each. Space: are you out of sellable function space on the strong dates, or sitting on empty rooms on the soft ones? Spend per cover: is the average check holding, or are you booking heads at menu prices that have not moved in two years? Conversion: how much weighted tentative is sitting unconverted, and how old is it? A period short on space needs a yield decision. A period short on spend needs a menu and pricing decision. A period short on conversion needs the sales team working the aging tentatives this week. Diagnose the lever before you prescribe the work.

Step 5. Make it a weekly habit, on one screen, next to rooms pace

A pace view nobody opens is not a pace view. The catering curve has to live where the rooms curve lives, in the same Monday meeting, owned by a named person, read every week. This is the part that fails most often, and it is not a data problem. It is a habit problem, the same one that kills most hospitality dashboards inside ninety days. The curve earns its place by being on the screen the morning someone needs it, not by being technically impressive in a deck.

The data is already in the building

Here is the honest part. Nothing in this playbook requires new software. The definite and tentative revenue is in Tripleseat or Delphi. The actuals are in ProfitSage or your accounting export. The group-tied catering ties to the block in the PMS. You already pay for every system that holds a piece of this.

The reason you do not have the curve is that those systems do not talk to each other, and the pace view needs all of them at once. The sales-and-catering system knows the pipeline but not the actuals. The accounting system knows the actuals but not the pipeline. The PMS knows the block but not the banquet. So building catering pace is not a buying problem. It is an integration problem, the same single-source-of-truth problem underneath almost every reporting gap we see. Until those three sources join in one place, catering pace is a manual export-and-reconcile job that somebody does heroically for a few weeks and then stops.

That is the work we do, and catering is only one instance of it. Connect the sales-and-catering, accounting, and PMS sources into one view and the catering line gets the same weekly discipline as rooms. Connect the rest of the operation the same way and the operator stops running the building on five systems that disagree. That is the foundation of the Operator Intelligence model: one connected source of truth, an intelligence layer that reads the way an operator already thinks, and an operating cadence that makes it a habit. A catering pace curve is just the part of it you can feel the fastest.

You can build the curve yourself from the steps above, and some teams should. If you would rather it just existed and stayed current without a person babysitting a spreadsheet, that is the kind of thing we build. Either way, stop reading catering off a second tab as a number nobody questions. It is too big a line to pace after the fact, and it is too small a piece of the operation to manage alone.