Personal Chef Contract: Template and Key Clauses (2026)

A personal chef contract sets out what a chef will cook for a client, whether for a single dinner party, a weekly meal-prep service or an event, how much it costs, and what happens if plans change. It protects the chef from last minute cancellations, grocery costs and headcount surprises, and it protects the client by fixing the menu, the allergies and the price in advance. Without it, the usual fights are about a guest count that grew, who paid for the groceries, a dietary need that was not passed on, and whether the deposit comes back. This guide gives you a usable clause-by-clause skeleton, explains what each part does, and flags the mistakes that cause trouble. This is general information, not legal advice. Contract, food-safety and consumer rules differ by country, for example the United States, the United Kingdom and India, so have an important agreement checked by a professional in your area before you sign. ## When you need this contract Use a written contract for any booked chef work beyond a casual favour. It matters most for date-specific events, for recurring weekly meal-prep arrangements, for larger headcounts, and whenever allergies or strict dietary needs are involved. A short clear contract stops arguments when the menu, the guest numbers and the grocery budget were only agreed by message. ## The clause-by-clause skeleton 1. Parties and service. Name the client and the chef or business in full, with contact details, and describe the service, for example a set dinner for a date, or a weekly meal-prep plan with a number of meals per week. Give the kitchen address and the dates or recurring schedule. 2. Menu and headcount. The most important clause. Set out the agreed menu or how it will be decided, the number of guests or portions, and the courses. Price extra guests separately so a growing count does not blow up the quote. State how late menu changes are handled. 3. Groceries and ingredients. Say who buys and pays for ingredients, whether groceries are billed at cost or included in the fee, and whether the client must approve spend above a set amount. State what happens to leftovers and premium or hard-to-source items. This is a frequent source of disputes. 4. Allergies and dietary needs. Put the duty on the client to disclose all allergies, intolerances and dietary requirements for every guest in advance, in writing. State that the chef will take reasonable care but cannot guarantee a kitchen free of a given allergen unless specifically agreed. This clause is essential for safety and liability. 5. Fees and payment schedule. Give the total price and the breakdown between the cooking fee and groceries. State the deposit that holds the date, when the balance is due, the currency, the payment method and a late payment charge. Be clear whether the deposit is non-refundable. 6. Kitchen, equipment and access. List what the client must provide: a working kitchen, equipment, utilities, and clear access at the agreed time. State what the chef brings. Make clear that a poorly equipped or inaccessible kitchen can affect the service and is not the chef's fault. 7. Timings. Set out arrival, service and clean-up times, and how long the chef stays. Note that late guests or a delayed start can affect the meal. 8. Cancellation and kill fee. Say what each side pays if they cancel. Typically the client loses the deposit, and a cancellation close to the date may mean a larger fee plus the cost of groceries already bought, because the slot can no longer be filled. State what happens if the chef must cancel, usually a full refund and reasonable help to find a replacement. 9. Food safety and hygiene. State that the chef follows safe food handling practices and holds any required food-hygiene registration or certificate. Keep the specifics accurate to your area. <!-- [VERIFY] exact food-hygiene registration required for the chef's jurisdiction --> 10. Liability cap. Limit the chef's total liability, often to the value of the booking, and exclude indirect losses as far as the law allows. An allergic reaction from a need the client failed to disclose should not be the chef's risk. 11. Independent contractor status. State that the chef is an independent contractor, not an employee, responsible for their own taxes, tools and any assistants. This matters for tax and employment law in every jurisdiction. 12. Image and menu rights. Say whether the chef may photograph dishes for a portfolio or social media, and who owns any bespoke recipes created for the client. 13. Governing law and disputes. Name the country or state whose law applies and how disputes will be handled. ## Common mistakes to avoid The biggest mistake is a vague grocery term, so nobody knows if ingredients are included or billed on top, which causes the worst invoice shocks. The second is pricing a fixed headcount when the guest list grows, so always price per guest above an agreed number. Others include no written allergy disclosure, which is a safety risk, no deposit to cover groceries already bought, no kitchen-access clause, and no clear cancellation term. Fix these and most chef bookings stay calm from enquiry to service. ## From a signed contract to a managed service Writing a strong contract is step one. The harder part is keeping track of the agreed menu, the grocery budget, the disclosed allergies, the deposit and the recurring schedule across many clients and weeks. When these live in scattered messages, the terms get argued over later. Adira is an AI legal operating system built on Claude that keeps the whole cycle, from drafting and reviewing a contract for risk, to signing it, to tracking the key dates and payment terms, in one workspace tuned to how you work, with public per-seat pricing and a short free trial. You can see how it works at adiralaw.com. A single pane showing the status of every booking is on its roadmap. For one dinner a simple template and a clear quote are enough; the workspace helps once you are running a regular meal-prep service for many clients at once.