Where this comes from
We do not write this from a framework. We write it from 14 locations producing over 8,000 meals a day against a $10-12M P&L, with the catering and event side sitting inside that number.
- 14 locations run in live production, not a case study read secondhand
- 8,000+ meals a day on standardized production and reporting
- A $10-12M P&L owned end to end, including the catering and event side
- Food cost moved from runaway variance back into a controlled band
This page is the catering-specific version of what we do across our operations consulting work. Same sequence: find the break, fix the system, keep it under control.
Where catering operations actually leak
Four patterns we see in nearly every catering operation that has outgrown its systems. They compound weekly.
The bid-to-delivery gap
The bid is written at a 32 percent cost. The event delivers at 42 percent. Procurement, yields, overtime, and last-minute substitutions pull the margin apart. Nobody reconciles until month-end. By then the next three events have already repeated the same pattern.
Production planning that does not match the actual week
The schedule was built from last week's job list. This week's list is different. The kitchen prepares for Tuesday events on Sunday and Wednesday events on Monday night. When Thursday lands heavy, the team improvises.
Labor flat across unequal weeks
Catering volume is lumpy. Staffing is rarely built to match. Slow weeks carry full payroll. Peak weeks run on overtime. Nobody is scheduling from the forward event list. The number shows up on the P&L as seasonality when it is actually a planning problem.
Senior staff churn at the worst times
The lead chef who holds the peak week leaves. The lead captain who makes the tough calls leaves. The replacement does not know the heroics. The operation drops to whatever the system actually supports. It is always lower than leadership thought.
Four moves that make catering hold at volume
None of these are clever. They are the four controls the operation is missing when the bid and the delivery keep disagreeing.
1. Bid templates that reflect real yields
Every bid built from actual yield data, not menu-engineered yields. Post-event reconciliation the morning after, every event. Variance logged against bid. The bid template updates when reality keeps disagreeing with it.
2. Forward production plan from the confirmed event list
The Monday kitchen meeting reads the next two weeks of confirmed events. Production sequences are built from that. Slow days front-load prep for heavy days. Peak days run a script, not a scramble.
3. Labor scheduled to the event curve
Base crew for baseline volume. Flex crew with consistent shift expectations. Overtime numbers reviewed weekly. Cross-trained staff so the schedule has give when an event grows late.
4. Procurement leverage from consolidated volume
Single purchase desk. Consolidated weekly orders. Price file updated quarterly. Substitutions documented. Vendor conversations driven by data, not by panic on Thursday afternoon.
Who this is for
- Catering companies between $5M and $50M revenue
- Commissary-fed multi-site catering groups
- Hotel banquet operations crossing into off-premise catering
- Corporate dining and institutional catering under margin pressure
- Catering groups preparing for a commissary expansion or second kitchen
"A catering operation does not fail on the big event. It fails on the fourth ordinary week nobody planned for."
An audit walks the commissary, the event pipeline, the bid process, and the labor model. You leave with a written list of what is broken, what it is costing, and what to do about it.