Allergies or Dietary Restrictions: A Private Chef's Guide

You've just heard from the host, and the brief is already a little more complicated than expected. Eight guests. One nut allergy, one lactose intolerance, one pescatarian who avoids gluten. On the French Riviera, that isn't a problem, it's a normal planning brief, and the quality of the evening depends on how calmly the kitchen turns those notes into a menu that feels integrated at the table.

France has a clear allergy burden, and it changes how private dining has to work. Inserm states that the number of people affected by allergies in France has doubled in 20 years, and that around 20% of the French population now lives with some form of allergy. It also notes that allergic rhinitis alone affects roughly 20%, while food allergies affect about 3% of adults and 8% of children. In practice, that means allergy-aware menu design isn't a rare favour on the Riviera, it's part of normal hospitality Inserm allergy statistics.

What Happens When You Tell a Private Chef About Your Restrictions

The first hour after a serious dietary brief is quiet, methodical, and far less dramatic than most guests expect. A seasoned private chef doesn't rush to the stove, because the first task is to translate your list into a service plan that protects the table and still feels elegant.

On a villa terrace above the bay, I've often seen the same pattern. The host thinks in terms of “no nuts, no dairy, no gluten”, but the kitchen has to think in terms of ingredients, contact surfaces, supplier specs, service order, and plating. A guest's safety can be lost long before the first course leaves the pass if that translation is sloppy.

The first response is planning, not improvisation

The good chef stays calm because restrictions are normal operating conditions. The aim is to identify what must be removed, what can stay, and what needs to be rebuilt so the menu still tastes complete. That's the difference between a kitchen that is merely accommodating and one that is genuinely prepared.

Practical rule: the earlier the brief arrives, the more natural the final menu feels.

This is why the best private dining teams treat restrictions as a design input. They don't ask the guest to lower expectations. They adjust the menu architecture so the table still feels like a Riviera dinner, not a compromise.

Allergies, Intolerances, and Lifestyle Choices Explained

!Three bowls on a wooden table labeled Allergy, Intolerance, and Lifestyle containing pepper, milk, and leafy greens.

The biggest planning mistake is treating every restriction as if it behaves the same way in the kitchen. It doesn't. A medically diagnosed allergy calls for strict avoidance and controlled handling. An intolerance usually changes comfort and tolerance thresholds, but not in the same life-threatening way. A lifestyle choice changes the menu direction, but the response is different again.

For a private chef, that distinction decides the whole service. A pescatarian can often be served from the same kitchen flow as the rest of the table. A guest with a confirmed nut allergy needs ingredient scrutiny and cross-contact controls from the first prep move. Someone avoiding gluten for preference may need a different pasta or bread structure, but not the same level of kitchen segregation as a guest with severe coeliac risk.

The French Riviera context makes this more common than many hosts realise. Villa and yacht tables often mix several needs at once, and the menu still has to read as one coherent evening. That's why a well-run kitchen doesn't ask, “What can't you eat?” and stop there. It asks what the restriction is, how it behaves, and what kind of service it requires.

What the kitchen needs to know first

Before the chef starts designing, the restriction should be placed in one of three working categories:

• Allergy: strict avoidance, full ingredient verification, and cross-contact control.
• Intolerance: careful ingredient selection, with attention to the trigger and the individual threshold.
• Lifestyle choice: menu adaptation that respects preference without overengineering the kitchen.

The distinction matters because it keeps the menu honest. It also prevents the common error of over-restricting a guest who only needed a targeted adjustment, which can flatten flavour and make the meal feel unnecessarily narrow.

For a practical reference on how a private menu can be structured around guest needs, see the dietary intake reference.

The Pre-Service Briefing Every Allergy Guest Should Expect

A proper briefing is not a casual chat over WhatsApp. It's a structured intake, and it starts before shopping, before prep, and before anyone decides what the starter will be. The chef needs enough information to separate a manageable substitution from a genuine safety risk.

The questions that matter

The first question is whether the restriction is medically confirmed or self-reported. That doesn't mean self-reporting is ignored, it means the chef calibrates the level of caution. A second question is what happens when the guest is exposed. The kitchen needs to know whether the issue is digestive discomfort, hives, swelling, breathing symptoms, or a broader reaction pattern.

Medication matters too. If a guest carries an adrenaline auto-injector, the chef should know that before service starts, because it signals the seriousness of the risk profile. The same goes for recency, if the diagnosis is recent, the dietary pattern may still be uncertain, and the menu should be built conservatively until there's clarity.

For groups, the chef also maps the table course by course. That's not bureaucracy. It's how you stop one guest's safe dish from being plated on a surface that touched another guest's allergen. In a multi-course dinner, a single weak point can undo careful sourcing.

Practical rule: never brief a chef with only the label of the condition. Brief the reaction, the severity, the confirmed triggers, and the level of cross-contact concern.

That kind of honesty is what makes the evening smooth. It lets the chef build a menu with the right balance of confidence and caution, instead of guessing and hoping.

How a Private Chef Actually Prevents Cross-Contact in Your Kitchen

Cross-contact control is where amateur reassurance falls apart. A menu can look elegant on paper and still be unsafe if the kitchen flow is careless. The professional difference is physical, not cosmetic.

A serious allergy-aware service begins with separate equipment. I mean separate cutting boards, dedicated pans, clean utensils brought in for that service, and oil that hasn't been used for anything else. If a fryer has handled an allergen, it's no longer just a fryer, it's a risk. The same applies to shared grills, shared tongs, shared ladles, and even ice used in drinks or chilled displays.

The kitchen has to move in lanes

The safest kitchens run different components on different stations. Allergen-free elements move forward cleanly, while allergen-containing components stay on another route. Foil-lined trays help in the oven. Dedicated sauce pots reduce accidental transfer. Colour-coding helps, but only if the team already understands that colour is a reminder, not the control itself.

Supplier verification matters just as much. Every label gets read. Not the summary, not the thumbnail note from memory, the actual ingredient declaration. That's because a dish name tells you very little about what is hiding in a glaze, stock, emulsion, or garnish.

This matters in France because the EU framework requires declaration of 14 regulated allergens in both prepacked and non-prepacked foods, but disclosure is not the same as control. The legal framework helps the guest identify risk, while the kitchen still has to prevent cross-contact in real time. The same framework also covers drinks and non-prepacked foods, and it highlights allergens including gluten, celery, mustard, sulfites, and lupin in the broader European set EU food allergen framework.

Why label reading is not enough

A label tells you what's in an ingredient. It doesn't tell you what touched it in the previous stage, or what was carried over by a shared spoon, board, or fryer. That's why a private kitchen has to think in terms of workflow, not just product lists.

A label is the starting point. The kitchen controls are what make the dish safe.

That difference is especially important for Riviera menus with sauces, emulsions, desserts, and seafood dishes. Those are exactly the places where hidden dairy, egg, nut, wheat, sesame, and sulfites tend to appear in a quiet, very French way.

Rebuilding a Riviera Menu Around Gluten and Dairy

A classic Provençal dinner can be beautiful and still need restructuring. Take a simple three-course menu, daurade with citrus beurre blanc, a ratatouille tian, and a lemon tart with a sablé breton base. None of those dishes needs to lose its elegance when gluten and dairy are out, but the technique has to change.

The fish can stay the same. The visual plate can stay the same. What changes is the build. The beurre blanc no longer relies on dairy richness, so the sauce becomes a citrus reduction with controlled emulsion and a small amount of safe starch for body. The point is not to imitate butter badly, it's to create a sauce with the same shine, lift, and balance on the plate.

How the dessert gets rebuilt

The tart is where many menus go soft if the chef doesn't respect texture. A sablé breton is usually about that brittle, sandy snap, so the adaptation has to deliver the same response in the mouth. An almond and rice-flour biscuit can do that when it's baked properly and balanced with the right fat and sugar structure. The lemon filling stays bright, but the dairy element is removed and the finish becomes cleaner, not thinner.

The important part is that the table shouldn't read the adapted dish as a compromise. The temperature, the garnish, and the plating language stay identical. That's what preserves the rhythm of the meal.

A good menu brief sounds like this, not like an ingredient wishlist:

• Starter: keep the acidity and the herb profile, replace the dairy carrier.
• Main: preserve the seafood and vegetables, remove gluten from the thickening or crust.
• Dessert: rebuild the base first, then rebalance the filling so the texture still holds.

For a closer look at how a private menu can be shaped course by course, see this sample private chef menu.

Feeding a Mixed Table Without Singling Anyone Out

Mixed tables are the norm, not the exception. One guest avoids pork, another has a severe nut allergy, the host wants the whole group to enjoy the same evening, and nobody wants a guest to feel singled out. The answer is usually a single unified menu that naturally avoids the biggest triggers, with optional elements offered discreetly on the side.

That approach does two things at once. It simplifies the kitchen flow, and it protects the atmosphere at the table. If one guest needs a component held back, the service can handle it discreetly at plating, without announcing the difference to everyone else.

Service should feel effortless at the table

Menu cards help, but only if they're written with confidence. The language should describe the dish, not the restriction. A guest shouldn't have to hear a running commentary about what they can't eat. They should receive a beautifully plated course that already fits their needs.

The same discipline applies when someone tries to change the plan mid-service. A private chef can't safely improvise a new allergen-sensitive dish on the fly if the kitchen wasn't set up for it. Refusing that request isn't being difficult, it's being responsible.

Mixed tables work best when the host agrees to one clear plan before service begins. Once that happens, the chef can protect the entire group without turning the meal into a series of special cases.

The less the table is asked to manage, the more polished the evening feels.

That's the goal. Not to showcase accommodation. To make it invisible.

Why a Skilled Chef Often Prefers the Constrained Menu

People often assume restrictions make a menu smaller. In a capable kitchen, the opposite is often true. Constraints force better choices, cleaner flavour, and more disciplined composition.

If dairy has to go, the sauce can become lighter and more precise. If gluten has to go, the chef leans harder on vegetables, legumes, potatoes, rice, and well-built starches that let Riviera produce stand on its own. The menu stops depending on familiar crutches and starts showing what the ingredients can do.

A skilled chef doesn't hear a dietary brief as a limitation on hospitality. It's a brief that demands more attention, more organisation, and more taste. Handled properly, that's where some of the most memorable private dinners come from.

If you're planning a villa dinner, a yacht lunch, or a multi-course family evening on the Côte d'Azur, brief early and be precise about every restriction. Le Private Chef creates bespoke menus across Monaco, Nice, Cannes, Saint-Tropez, and beyond, with sourcing, service, and cleanup managed discreetly from start to finish. Visit Le Private Chef to plan a private dining experience built around your guests' actual needs.