PLANNING — DIETARY

How to Collect Dietary Requirements from Guests — Before the Menu Is Written

A dietary requirement mentioned on WhatsApp becomes a menu decision; a requirement mentioned at the table becomes a compromise. The difference is almost always how the host collected the information. Here is a simple way to collect dietary requirements from guests, what to ask, and what happens to that list once your chef has it.

myCHEF editorialReviewed by the Cape Town teamLast updated November 2026

Ask every guest once, in writing, at the same time as the RSVP. Record their name, the requirement, and whether it is a preference, an intolerance or a medical need. Then send the whole list with your booking brief, before the menu consult, so the chef designs the menu around it rather than substituting dishes out. from R850 pp per person · Min invoice R3,900.

The short answer

Ask every guest once, in writing, at the same time as the RSVP. Record their name, the requirement, and whether it is a preference, an intolerance or a medical need. Then send the whole list with your booking brief, before the menu consult, so the chef designs the menu around it rather than substituting dishes out.

On our side, vegan, gluten-free, nut-free, allergy-aware and halaal-friendly menus all adapt at the consult stage at no extra charge. Our page on private chef dietary requirements sets out the protocols we run for each.

What to ask on the RSVP

Keep it short so people actually answer. These questions cover almost everything a chef needs to know.

Included

  • Name, so the right plate reaches the right person on the night.
  • Any foods you don't eat, and why: preference, intolerance or allergy.
  • For allergies: the exact allergen, and whether traces or shared equipment are a problem.

Quoted separately

  • Gluten: preference, intolerance or coeliac.
  • Religious or cultural requirements, for example halaal or kosher.
  • Anything else the chef should know, such as low-FODMAP, diabetic-aware or religious fasting windows.

Why severity matters more than the label

Two guests can both write 'no nuts' and need completely different things. One dislikes walnuts; the other carries an adrenaline pen. That is why the booking brief asks whether a requirement is preference, intolerance or medical: the protocol differs. For allergies we run a dedicated prep sequence for allergen-free dishes, separate utensils and equipment, and labelled service.

Gluten is the clearest example. We design genuinely gluten-free menus rather than menus with the bread removed, but we cook in home and villa kitchens, so for medical-grade coeliac requirements we discuss cross-contact openly in the consult and agree the safest practical setup together. If the honest answer is ever no, you will hear it in the consult, not at the table.

A chef plating courses at the pass of a home kitchen before service

Halaal, kosher and plant-based guests

We are halaal-friendly with strict, documented protocols covering sourcing, separation and service, and we don't claim certification we don't hold. We do not claim kosher capability; for Beth Din-supervised requirements we refer you to a supervised partner kitchen.

Plant-based guests are the easiest to plan for when you know early. Full vegan and vegetarian menus are built around Cape produce rather than meat substitutes, and mixed tables are the norm: the chef designs parallel dishes that share pacing and presentation, so the vegan guest and the steak guest finish each course at the same time. Our guide to hosting vegans and meat-eaters at one table goes deeper on that.

How the list is used on the day

At a seated dinner, dietary plates are identified to the table discreetly, without singling anyone out. At grazing tables and buffets, every dish carries a printed tent card with its dietary status, so guests can choose safely without questioning staff. For canapé events, vegan, gluten-free and allergy-aware pieces are passed as labelled runs. For large corporate events, an allergen matrix accompanies the menu as standard.

This is the structural advantage of cooking in your own kitchen: no fixed menu, no shared fryer, and no pass sending forty other dishes. One kitchen, one event and one list of requirements, designed in from the first message.

Collecting requirements for weddings and office events

The same rule scales up. For weddings we collect dietary needs with your RSVPs and build them into the menu plan, not around it: vegan, gluten-free and allergy-aware plates are produced in the same service and labelled at the pass. For corporate events, dietary needs are captured with the RSVPs and mapped onto labelled buffet lines or plated alternatives, with an allergen matrix supplied for large events.

For large-group buffets, dietary covers are planned as a percentage of headcount, which is why a final count by requirement matters more than a final count of guests. If you are using an online RSVP form, add the questions above as required fields and export the answers as a simple list: name, requirement, severity. That one sheet is all your chef needs to start the consult.

A message you can copy to guests

"We're having a chef cook for us on the night. So the menu works for everyone, please reply by Friday with anything you don't eat, and tell us whether it's a preference, an intolerance or an allergy. If it's an allergy, please name the exact food and say whether traces are a problem."

Send the replies with your date, guest count and suburb on WhatsApp. We reply within the hour, 08:00–20:00 SAST, and the menu consult starts from there. Every one of our private chef menus in Cape Town adapts this way at no extra charge.

Questions, answered.

We update this guide annually — figures re-verified November 2026.

Get an exact quote.

We handle everything else — menu, shopping, cooking, service, cleanup. Guaranteed.

Replacement-or-refund · Fixed itemised quote · Published cancellation tiers