Building a Catering SOP for Your Corporate Flight Department

Most corporate flight departments have a catering SOP in one of two forms: either a documented procedure that nobody reads, or an undocumented tribal knowledge system where every coordinator makes different decisions. Neither produces consistent results. Here's how to build a catering SOP that actually works — one that standardizes quality, controls cost, and removes the anxiety of "what do I order when no one has told me?"

Why a Catering SOP Matters

Consider what happens without one: A new flight coordinator joins your department. Nobody has documented how catering decisions get made. Do they order from whoever the previous coordinator used? Do they Google "private jet catering [city]" and hope for the best? When a passenger asks for something specific, does the coordinator know who to call and how much latitude they have to spend?

A catering SOP creates institutional knowledge that outlasts any individual coordinator. It protects your passengers, your flight attendants, and your department's reputation.

SOP Component 1: Approved Vendor List

Your SOP should specify which catering vendors are approved for each airport in your operational footprint. This is not just a list — it should include:

• Primary vendor (preferred, vetted, approved for all orders)
• Secondary vendor (if primary is unavailable)
• Contact information for dispatch, not just sales
• Lead time requirements for each vendor
• Any airport-specific notes

For flight departments operating primarily in the Midwest, DFK serves as the primary or exclusive catering vendor for many programs. Our airport network typically covers every market your department uses.

SOP Component 2: Passenger Information Collection

Define exactly what information is collected from passengers before each trip and who is responsible for collecting it. The standard data set:

• Dietary restrictions (allergies, religious requirements, medical)
• Beverage preferences
• Seat time preference (when do they want to eat?)
• Special requests (birthday, celebration, specific items)

Define the collection method (standard form, email template, phone call with transcript), the timeframe (72 hours before departure minimum), and what happens when information isn't provided (default to department standard menu).

SOP Component 3: Menu Tier Decision Matrix

Who is traveling determines what's ordered. A useful tier matrix:

• Owner/principal: Full custom service, no budget constraint flagged to coordinator
• Senior executive (C-suite): Privé or Affiné tier minimum
• Client/guest flights: Affiné or Privé, confirmed by account manager
• Internal team travel: Élevé or Affiné, standard menu
• Crew-only repositioning: Crew meals only, no passenger service

This matrix prevents both overspending on routine legs and under-delivering on high-profile trips.

SOP Component 4: Budget and Approval Workflow

Define spending authority: What can a coordinator approve independently? What requires manager sign-off? What requires VP authorization? Typical thresholds for mature flight departments range from $500 for coordinator self-approval to $2,500 for manager approval for complex orders.

SOP Component 5: Confirmation and Receipt Protocol

Define the confirmation workflow: when to call/text to confirm delivery, how to verify the order on receipt, and what to do if there's a discrepancy. Include the specific escalation path — who does the flight attendant call if catering is wrong at T-30 minutes?

SOP Component 6: Post-Flight Documentation

Capture feedback systematically. A simple post-flight catering note — what worked, what didn't, passenger comments — builds the institutional knowledge that improves your catering program over time and gives you documentation when vendor problems recur.

DFK can provide a SOP template as part of our flight department partnership onboarding. Contact us to discuss your program and receive our recommended SOP framework.