Private Chef Contract Template: What Every Agreement Should Include

You landed the client. The dinner is confirmed, the menu is set, and they're excited. Now what? A handshake isn't a contract — and a bad contract costs more than no contract. Here's what every private chef service agreement needs to actually protect you.

Why Contracts Matter More Than You Think

Most private chefs who skip written agreements do it because things feel good — the client is enthusiastic, the referral came from a trusted source, the event is straightforward. Then the scope changes. The date shifts. An allergy surfaces on the day of. The deposit never arrives. The client wants a refund three days out.

These situations play out constantly without contracts — and the chef absorbs the loss every time. A private chef contract template isn't bureaucracy. It's the document that defines what you agreed to so neither party is guessing when something goes sideways.

Three scenarios that contracts prevent:

• Scope creep. The client who booked a 4-course dinner for 8 now wants to add 4 guests, a cheese course, and a cocktail hour. Without a written scope, you're arguing about what was "included."
• Payment disputes. A client who cancels two days before the event and expects a full refund. If your policy isn't in writing, you'll struggle to enforce it — and the chargeback window is always open.
• Liability exposure. A guest has an allergic reaction and claims they disclosed the allergy. Whether they did or didn't, if your agreement doesn't address dietary responsibilities, you have no defense on paper.

For a deeper look at protecting your business from the ground up, see our guide on private chef business insurance — contracts and coverage work together.

Essential Clauses Every Agreement Needs

1. Scope of Services

Define exactly what you're providing. Vague language like "private dinner for 8" invites disagreement. A tight scope clause covers:

• Number of guests (and what happens if the count changes)
• Number of courses and service style (plated, family-style, buffet)
• Whether you provide tableware, linens, or service staff — or if those are client-supplied
• Setup and cleanup responsibilities (do you clear dishes? clean the kitchen?)
• Travel and prep time included vs. billed separately

The rule: if a client could reasonably assume it's included, put it in the contract — either as included or explicitly excluded. Assumptions kill margins.

2. Pricing and Payment Terms

Your personal chef agreement should spell out the full financial arrangement with no ambiguity:

• Total contract value — all-in price, itemized if possible (chef fee, ingredient estimate, travel, additional staff)
• Deposit amount and due date — standard is 50% at signing to hold the date; without this you don't have a booking, you have an intention
• Balance due date — typically 48–72 hours before the event or at the event
• Ingredient overage policy — if actual food costs exceed the estimate, how is the difference handled?
• Late payment terms — a modest late fee (1.5%/month is standard) makes payment timelines serious

For a full breakdown of how to structure your rates and what to itemize in proposals, our private chef pricing guide covers the mechanics in detail.

3. Cancellation and Rescheduling Policy

This is the clause most chefs forget until they need it. A clear cancellation policy protects your time and recovers at least partial revenue when bookings fall through. A common structure:

• 30+ days before event: Full deposit refund (or option to reschedule at no charge)
• 14–29 days before event: 50% of deposit refunded, 50% retained
• 7–13 days before event: Deposit non-refundable; ingredients already ordered may be billed
• 0–6 days before event: Full contract value due — you've blocked the date and ordered for the menu

Your specific numbers should reflect your actual risk. If you typically order ingredients 5 days out, your "non-refundable ingredient cost" window should start there. The point is to have a policy in writing before the cancellation call arrives, not after.

4. Dietary Liability Disclaimer

This clause matters more than most chefs realize. It should:

• Require the client to disclose all dietary restrictions, allergies, and intolerances in writing at least 48–72 hours before the event
• State that you will take reasonable precautions for disclosed restrictions but cannot guarantee a fully allergen-free environment
• Make clear that you are not liable for undisclosed allergies or reactions caused by cross-contamination in the client's own kitchen

This isn't about avoiding responsibility for carelessness — it's about establishing that you acted on what you were told. An undisclosed severe allergy that results in a reaction is a very different situation from one you were informed of and failed to accommodate. The contract creates that distinction in writing.

5. Recipe and Intellectual Property

If you create custom menus, signature dishes, or proprietary preparations, your contract should address ownership. The standard position: recipes and menu concepts you create remain your intellectual property. The client receives the dinner experience, not the right to reproduce or sell your recipes.

For most private chef work, this is a boilerplate clause that never gets invoked — but for high-end clients, corporate events, or anyone in the food industry, it's worth including. You don't want a signature dish showing up on a client's restaurant menu six months later without a conversation.

6. Confidentiality (For High-Net-Worth and Celebrity Clients)

If you work with clients who value privacy — executives, entertainers, high-net-worth households — a mutual confidentiality clause is expected, not optional. It should cover:

• Client identity and address
• Guest list and event details
• Any personal information disclosed during service
• Photos taken during the event (even for portfolio use)

Clients at this level often have NDAs they'll ask you to sign anyway. Having your own confidentiality clause signals that you understand the market and have done this before.

Pricing Structure in Contracts: Per-Event vs. Retainer vs. Hybrid

How you price affects what your contract needs to cover. Three common models:

• Per-event: The most common. Each event is a standalone agreement. Simpler contract, but you negotiate and sign a new one for every booking. Good for chefs building a varied client base.
• Retainer: A client commits to a fixed number of events per month (or a regular weekly dinner) in exchange for priority scheduling and a monthly flat fee. The contract covers the entire engagement period, minimum booking commitments, and what happens if the client wants to reduce or end the arrangement.
• Hybrid: A retainer for regular service (weekly family dinners, meal prep) with per-event rates for special occasions. Requires clear contract language defining what falls under the retainer vs. what triggers an additional charge.

Common Contract Mistakes

The errors that cost private chefs money:

• Verbal agreements. "We discussed it on the phone" is not a contract. Email confirms intent; a signed document creates obligation.
• Vague scope. "Dinner for 8" without specifying courses, dietary accommodations, setup, and cleanup is a blank check for scope creep.
• Missing cancellation terms. If it's not in the contract, your refund policy is whatever the client decides it is.
• No allergy disclosure requirement. Putting the burden of disclosure on the client protects you. Not requiring it in writing puts the burden on you.
• Deposit not collected at signing. A contract without a deposit is an intention, not a commitment. Dates don't get held; clients don't feel bound. Collect the deposit when the agreement is signed — not later.

When to Update Your Contract

Your contract should evolve with your business. Three moments that warrant a review:

• Scaling from solo to team. When you add a sous chef or server, your agreement needs to address staffing, labor costs, and who's responsible for additional staff conduct.
• Adding meal prep or recurring services. Weekly meal prep has different risk and scope from one-time events. It needs a separate agreement structure covering recurring payments, menu approval timelines, and termination notice.
• Entering a new market. Moving into corporate events, private clubs, or destination work means different client expectations, larger event scales, and often legal requirements for certificates of insurance. Your contract should reflect the market you're actually serving.

If you're starting your business from scratch and working out the full operational structure, our guide on how to start a private chef business in 2026 covers the legal and business setup alongside contracts.

Where Mise Fits In

A contract is the agreement. A proposal is how you get there. Mise generates complete, professional proposals — menu, pricing, dietary notes, and payment terms — in under 60 seconds from a client's intake form. Every proposal includes a customizable agreement section and a built-in 50% deposit link so clients can sign and pay in one step.

When the proposal becomes the agreement, the friction of sending a separate contract disappears. The deposit is collected at signing. The scope is documented. The client has a record of what they agreed to. Your admin time drops to near zero.