Catering Contract Template

In plain language: Identifies the event date, start and end times, venue address, and the specific catering services included — whether full-service, buffet, cocktail reception, or drop-off only.

Common mistake: Describing services in vague terms like 'full catering' without a Schedule A. When the client expects passed appetizers and the caterer planned a buffet, disputes are expensive and damage the relationship.

In plain language: Sets out the agreed menu in writing, including any dietary alternatives for allergies or religious requirements, and establishes the deadline by which menu changes must be submitted.

Common mistake: Guaranteeing a completely allergen-free environment in writing. Caterers preparing food in shared kitchens cannot make this guarantee — and doing so creates strict liability exposure if a guest has a reaction.

In plain language: Establishes the estimated guest count, the guaranteed minimum the client will be billed for regardless of attendance, and the deadline to submit a final confirmed count.

Common mistake: Setting no guaranteed minimum at all. If 40 guests RSVP and only 20 attend, the caterer absorbs food and labor costs for 20 plates — a guaranteed minimum eliminates this risk.

In plain language: States the per-head rate or flat fee, any additional charges (bar service, staffing, equipment rental, travel), and the schedule of deposit and final payment due dates.

Common mistake: Quoting a per-head rate without itemizing extras. Clients receive a $3,500 invoice expecting $2,400 and discover $1,100 in staffing, linen, and equipment charges they did not anticipate.

In plain language: Defines what happens to the deposit and any pre-paid amounts if the client cancels, scaled by the number of days' notice given before the event.

Common mistake: No cancellation scale at all — just 'deposit is non-refundable.' A caterer who purchases food and books staff for a 200-person event that cancels 10 days out has losses far exceeding the deposit.

In plain language: Specifies the number of service staff, their roles, uniform requirements, and the caterer's responsibility for staff conduct, background checks, and compliance with venue rules.

Common mistake: Omitting who is responsible for staff gratuities. If the contract is silent, disputes arise at the end of the night about whether the client owes an additional 18–20% on top of the service fee.

In plain language: Sets the hourly rate charged for each 30 or 60 minutes the event runs beyond the contracted end time, and requires the client to notify the caterer's supervisor to authorize an extension.

Common mistake: No overtime clause at all. A wedding that runs two hours long with no overtime provision leaves the caterer absorbing additional labor costs with no legal basis to invoice for them.

In plain language: Allocates responsibility for food safety incidents, personal injury, property damage, and third-party claims, and requires each party to carry adequate insurance.

Common mistake: No insurance requirement for the client. If a guest damages venue property or injures another guest and the venue holds the event organizer liable, an uninsured client leaves the caterer exposed too.

In plain language: Excuses both parties from performance if the event is made impossible by circumstances outside their control — natural disasters, government orders, or venue closure — and specifies what happens to payments already made.

Common mistake: Force majeure clauses that cover only natural disasters but not government shutdowns or public health orders — a gap that became costly for many caterers during 2020–2021 event cancellations.

In plain language: Specifies which jurisdiction's law governs the contract and how disputes are resolved — arbitration, mediation, or litigation — and where any proceedings will take place.

Common mistake: Choosing a governing jurisdiction with no connection to where the event occurs or either party operates. Some courts will refuse to apply foreign governing law and default to local rules, creating unpredictable outcomes.

A catering contract is a legally binding agreement between a caterer and a client that sets out the full terms of food and beverage service for a specific event. It covers the menu, guest count, pricing, deposit, payment schedule, cancellation policy, staffing, liability, and governing law. A signed contract protects the caterer's revenue and protects the client's expectations before any money changes hands.

At minimum, a catering contract should include: event date, time, and venue; a detailed menu attached as a schedule; confirmed guest count and guaranteed minimum; per-head rate or flat fee with all extras itemized; deposit amount and payment due dates; a tiered cancellation policy; staffing obligations; overtime rates; liability and insurance requirements; force majeure language; and governing law. Missing any of these is a common source of post-event disputes.

No law mandates a catering contract, but without one, either party has only verbal assurances and email threads to rely on in a dispute. Courts in most jurisdictions will enforce a written catering contract that includes the key terms, signatures, and consideration. For any event above $1,000 in value, a signed contract is considered standard practice in the industry.

Most catering contracts require a deposit of 25–50% of the total estimated fee, paid at signing to secure the date. The deposit covers the caterer's early costs — menu planning, initial food purchasing commitments, and booking staff. The balance is typically due 7–14 days before the event. For large events over $10,000, a three-installment structure (deposit, mid-point, and final payment) is common.

The cancellation policy in the contract governs what the client owes. A well-drafted tiered policy scales forfeiture based on how close to the event date the cancellation occurs — for example, deposit forfeiture only for cancellations 90+ days out, 50% of the total contract for 30–90 days, and 100% within 30 days. Without a written policy, the caterer must prove actual damages in court to recover costs beyond the deposit.

Yes, if the contract contains a force majeure clause that covers the specific triggering event — natural disaster, government shutdown, or venue closure. When force majeure applies, neither party is typically liable for non-performance. The contract should specify what happens to amounts already paid, whether the event can be rescheduled, and how documented pre-event expenses are handled before any refund is issued.

Liability depends on the contract's indemnification clause and applicable food safety regulations in the jurisdiction. Typically, the caterer bears responsibility for food safety in preparation, storage, and service. A catering contract should require the caterer to carry general liability and food contamination insurance and include an indemnification clause allocating responsibility between the parties. Consider consulting a lawyer when drafting liability language for high-attendance events.

Yes. A catering contract is only enforceable against a party who has agreed to its terms, and a signature — whether ink or electronic — is the standard evidence of agreement. In practice, caterers who collect a deposit without a signed contract often find that unsigned terms are treated as unenforceable in a payment dispute. Always execute the contract before accepting any payment.

A catering proposal is a non-binding document — typically a quote or service outline — that the caterer sends to a prospective client before terms are agreed. It may include a sample menu, pricing estimates, and a description of services. A catering contract is the binding agreement signed by both parties after they have agreed on the specific terms. The proposal leads to the contract; only the contract is legally enforceable.