How to Run a Great Weekly Catering Production Meeting

Most catering companies have some version of a production meeting. Not all of them are particularly productive.

A bad production meeting is a room full of people reading BEOs aloud, answering emails under the table, trying to remember venue details from a walkthrough nobody wrote down, and discovering problems that should have been solved days earlier. A great production meeting is different. It brings the right department leaders together, gives everyone visibility into the upcoming event calendar, identifies remaining risks, confirms responsibilities, and sends each department away knowing exactly what needs attention.

There is no single meeting structure that works for every catering company. Team size, sales structure, event volume, and operational complexity all matter. What matters more is building a repeatable system that answers one question: are we ready to execute these events successfully?

“A production meeting is not where you plan the event from scratch. It is the recurring checkpoint that confirms the event is ready to execute.”

Who should attend the production meeting?

Think about attendance in terms of which functions need representation, not how many people you can fit around the table. The standing meeting should generally include:

• One Sales leader
• One Operations leader
• One Culinary leader
• A Senior or Lead Captain, if the company has that role
• A Staffing or Scheduling representative
• A Beverage or Bar production representative
• A Warehouse or Truck Loading representative

If one leader owns multiple functions, they can represent multiple areas. A smaller caterer doesn't need seven separate people simply because seven functions are listed. What matters is that each critical operational function has a voice in the room.

Give the room actual authority

Representatives should be able to make decisions for their departments. Avoid a meeting where every answer becomes "I'll have to ask someone." The point of the meeting is to solve problems and assign action, not add another layer of questions.

Should every captain attend?

Generally, no. If your company has a Senior Captain, Lead Captain, or similar role, that person is a strong addition to the production meeting. They bring the perspective of the field, the kind that's easy to miss from behind a desk:

• Unrealistic setup windows
• Difficult venue access
• Service transitions that need additional staffing
• Equipment challenges
• Recurring venue issues
• Captain-specific concerns from past events

The Senior Captain also becomes a communication bridge, carrying information in both directions:

• Production Meeting → Senior Captain → Captains Meeting → Event Captains
• Event Captains → Senior Captain → Production Meeting

Don't default to inviting every event captain to the full production meeting. It balloons the room and duplicates the purpose of a dedicated captains meeting.

Production starts before the production meeting

Basic event information should already be known before anyone sits down. The production meeting shouldn't be the first time someone asks:

• Where do we load in?
• Is there power?
• Can the truck stay onsite?
• Where is the catering kitchen?
• Is there an elevator?
• Where are rentals being delivered?
• What's the rain backup?
• Where can staff park?

If an event needs a venue walkthrough, do it before that event's production review whenever you reasonably can. The team should be discussing confirmed information, not guesses. "I think there's power near the station" isn't a production update. "There are two dedicated 20-amp circuits behind the station" is.

Treat missing walkthrough information as a production-readiness flag, not something to casually fill in with an assumption.

Review two weeks of events, not just one

Most catering companies hold their production meeting on Monday or Tuesday and review whatever's happening that week. Consider a rolling two-week production calendar instead. It gives most events two production discussions before they ever hit the floor.

First review: look ahead

About 7 to 14 days out. The goal is to catch problems while there's still time to fix them. Review:

• Venue walkthrough status
• Staffing plan
• Event leadership
• Culinary concerns
• Beverage requirements
• Rentals
• Specialty equipment
• Transportation
• Loading and logistics
• Timelines
• Dietary considerations
• VIP or client-sensitive details
• Unresolved decisions
• Anything unusual

The question behind this review is simple: what about this event could become a problem next week? Anything identified here gets a clear owner and a follow-up date.

Second review: final confirmation

The event comes back the following week. Don't repeat the entire first discussion. If nothing has changed, the salesperson should be able to say "no changes" and move on. That's a successful update, not a shortcut. Nobody needs to manufacture conversation just because an event is on the agenda.

If something has changed, discuss the change and what it affects. Say the guest count moved from 125 to 145. Don't reread the whole event. Ask:

• Does staffing need to change?
• Does the rental order need adjustment?
• Does culinary need updated quantities?
• Does the bar need more product?
• Does transportation or equipment change?

The second review is about changes and readiness. Not repetition.

Two good ways to order the events

Neither is universally better. Here are two legitimate approaches, and what each one costs you.

Approach A: review by salesperson

Core production leadership stays for the whole meeting. Salespeople join one at a time, review all of their events in the two-week window, answer questions, pick up follow-up items, and leave. The Sales leader stays in the room throughout.

• Efficient use of each salesperson's time
• A clear handoff from Sales to Operations
• Each salesperson owns presenting their own events
• Nobody sits through an hour of events that aren't theirs

The tradeoff: events aren't discussed chronologically. The team might cover a Saturday event, then Thursday, then Friday, depending on whose book of business comes up. Cross-event conflicts get harder to spot.

Approach B: review chronologically

The Sales team attends the whole meeting. Events are reviewed in calendar order, Thursday's events, then Friday's, then Saturday's, straight through the week. This gives the room a real view of the entire production week. Cross-event conflicts get much easier to catch, in things like:

• Trucks
• Equipment
• Staffing
• Captains
• Culinary production
• Warehouse loading
• Specialty equipment
• Rentals
• Bar production
• Overlapping load-in or departure times

The team stops seeing Saturday as six unrelated events and starts seeing it as one interconnected operational puzzle. The tradeoff: salespeople sit through events they don't own, which can mean disengagement and a longer meeting.

Choosing the right format

The best structure is the one that gives Operations enough visibility without burning hours of everyone's time.

What should actually get discussed

Resist the urge to turn this into a giant BEO checklist. Focus on exceptions, risk, changes, and coordination between departments. For each event, the room should be looking for:

• What changed?
• What's unusual?
• What's unresolved?
• What could affect another department?
• What could affect another event?
• Who owns the remaining action?
• When does it need to be resolved?

Information that's already documented and understood doesn't need to be read aloud. A production meeting shouldn't turn into a live audiobook version of the BEO.

Give every open item an owner

When the discussion turns up something unresolved, assign it on the spot. "We need to figure out the power situation" isn't an action item. "Jordan will confirm power requirements with the venue by Wednesday" is.

Look across events, not just within them

This is one of the best reasons for department leaders to stay in the room for the whole meeting. Salespeople naturally think about their own events. Production leadership has to think about the whole week, and actively look for collisions like:

• Multiple events needing the same specialty equipment
• Trucks with overlapping departure times
• Several large loads hitting the warehouse at once
• Staffing shortages
• Captain coverage gaps
• Heavy culinary production volume landing on one day
• Multiple outdoor events facing the same weather
• Rental delivery or pickup conflicts
• Bar-production-heavy days

The production meeting should surface these collisions while they're still easy to fix, not the morning of.

End with a production readiness check

The meeting should leave the room confident about the next two weeks. A simple framework works better than an elaborate one:

Don't turn this into project-management theater. It exists to help leadership see, at a glance, where attention is actually needed.

The larger meeting ecosystem

A production meeting shouldn't carry the weight of every operational conversation your company has. It works alongside a few other systems, each answering a different question.

Venue walkthrough

Establishes the physical facts an event runs on. Open the Venue Walkthrough Tool →

Production meeting

Confirms event readiness and coordinates across departments. This is the meeting this article is about.

Captains meeting

Prepares event leadership and frontline execution for what's actually going to happen on site.

Buffet and station mockups

Confirms physical setup and packing requirements before the truck gets loaded. Read the buffet mockup guide →

Event execution

Delivers the plan everyone in the previous steps already agreed on.

The best production meetings tend to get shorter as the system improves, not longer. The goal was never a two-hour meeting because there are a lot of events on the books. The goal is enough visibility that surprises happen in the conference room instead of at the loading dock, the venue, or the event itself.

“A great production meeting doesn't plan every detail of the event. It proves that the details have been planned.”

Frequently asked questions