Recipe 27 - The Banquet and Catering Forecast Bridge: Build an Event-Level Forecast You Can Defend Line by Line

Build an Event-Level Forecast You Can Defend Line by Line

From The Spiral Sales Office Recipe Vault | By Paul Woodley

A catering forecast built from totals is a number without a story. When it misses, the question is always the same: which events underperformed, which additions did not materialise, and which risks were not reduced? If the forecast cannot answer those questions event by event, the miss cannot be diagnosed and the next forecast cannot be improved.

Recipe 27 builds the bridge from the beginning: validated on-the-books, evidenced additions, and quantified reductions, presented as a single table with a low case and a likely case, and an ask list that tells the catering team exactly what information is still needed to make the number defensible.

What This Recipe Makes

A complete catering forecast bridge for any period, built event by event, with every addition and reduction named and categorised by evidence type, an unsupported optimism list that makes visible what would otherwise be hidden inside the total, and a site-tour-ready summary as a bonus output.

• Head Chef: DOSM with Director of Catering and Events
• When to Cook It: Monthly before forecast submission; again mid-month if a large event changes
• Ingredients: Event-level detail for the forecast period, including event name, date, booking status, revenue by category (food, beverage, room rental, AV, service charge), guaranteed or expected covers, and contract status where available

The Forecasting Equation This Prompt Follows

Every output in Recipe 27 is structured around one equation:

Forecast equals Validated On-the-Books Revenue, plus Evidence-Based Pickup and Additions, minus Identified Risk and Reductions.

This equation forces every number in the forecast into one of three categories. If a number cannot be categorised, it does not belong in the forecast.

The Five Outputs This Prompt Returns

1. Validated On-the-Books - Total definite revenue for the period, subtotalled by revenue category. The prompt also flags any event where the status is definite but the contract is unsigned, the guarantee has not been received, or the covers look inconsistent with the revenue. These are on the books but not yet validated, and the distinction matters when the month closes short
2. Evidence-Based Additions - For each event, realistic incremental revenue with the evidence type labelled for each addition: contractual meaning a minimum not yet fully consumed, historical meaning this account or event type has reliably added revenue in past years, or in-progress meaning an active conversation or proposal. Any addition without an evidence type goes in a separate list labelled unsupported optimism. That label is intentional. It makes visible what would otherwise be folded into the total without scrutiny
3. Identified Risk and Reductions - Every event carrying downside exposure is flagged: unsigned contracts, attrition history, unconfirmed food and beverage minimums, groups whose room block has already reduced, or events on dates where similar events have historically cut scope. Each risk is quantified with a reasonable reduction range rather than a binary include or exclude
4. The Bridge Table - A single table: on-the-books total, plus each addition category, minus each risk category, equals forecast. Presented as both a low case and a likely case so the range of the commitment is visible rather than implied
5. The Ask List - Every piece of information still needed from the catering team to close the gaps in the bridge. Unsigned contracts to chase. Guarantees to confirm. F and B minimums to verify. The ask list makes the prep conversation specific rather than general

The Unsupported Optimism List

The unsupported optimism list is the most honest output in this prompt and the one that tends to change how the forecast is built in subsequent cycles. When additions with no evidence type are listed separately with their total dollar value, the number that was previously folded invisibly into the forecast becomes a visible commitment that can be questioned.

That visibility is the point. It does not forbid optimism. It requires that optimism be acknowledged rather than hidden, and that the person making the call knows exactly how much of their forecast rests on an assumption they cannot yet support.

Where the Output Goes

The catering forecast bridge field in the monthly forecast submission. The mid-month review if a large event changes status. The conversation with the Director of Catering or Events about which events still have open items on the ask list. The input to Recipe 41, the pre-submission reconciliation check, which runs after this bridge is complete.

The Mirror

For the current month's catering forecast: if your VP or GM asked you right now to explain the difference between your forecast and the validated on-the-books number, event by event, could you do it? If the answer requires opening several files and a few minutes of calculation, Recipe 27 is the prompt that makes that answer immediate.

A Note on Data Handling

Confirm what your employer, owner, brand, and management company permit before pasting event-level catering data into any AI platform. Event names, contracted revenue, cover counts, and F and B minimum details may be commercially sensitive or subject to group confidentiality. When in doubt, use event codes rather than client names. Every output is a starting position. The forecast commitment and the client conversations still belong to you.

Your Next Step

Pull your event-level detail for the current forecast month today. Paste it into Recipe 27 before you write a single number in the forecast submission. Build the bridge. Review the unsupported optimism list. Close the items on the ask list. Then submit a forecast that can be explained event by event, not just defended in total.

A forecast that can be explained is a forecast that can be trusted. Recipe 27 is how you build that kind of number.

Paul Woodley | The Spiral Sales Office