Build a Guest Meal Preference Card for Executive Hospitality

Build a Guest Meal Preference Card for Executive Hospitality

by ExecutiveAssistantAgency Editorial Team · 4 min read

A compact guest meal preference card for executive hospitality, covering intake, allergy handling, host briefing, day-of confirmation, and privacy limits.

In this article
  1. Small hospitality details carry real weight
  2. Collect preferences through the host
  3. Separate preference from safety
  4. Design the card for quick reading
  5. Brief the kitchen with names attached
  6. Confirm again on the day
  7. Update and retire the card

Small hospitality details carry real weight

A board chair who does not eat pork, a visiting client with a severe nut allergy, and a speaker who keeps a strict vegetarian diet all arrive at the same executive lunch. The assistant has three preferences to remember and one kitchen to brief. Guessing is not acceptable, and asking the guest the same questions at every visit is tiring. A meal preference card turns scattered notes into a short record the office can reuse.

The card is not a medical chart and it is not a restaurant order form. It is a hospitality reference that records what the guest has told the office, how the kitchen should handle it, and who confirmed the detail most recently. It should be easy to read at a glance and easy to correct. The point is to make the guest comfortable without making the office intrusive.

Collect preferences through the host

Ask the host to collect meal details when the invitation is accepted, not on the morning of the event. Add three short questions to the RSVP: dietary pattern, ingredients to avoid, and a preferred beverage. Ask whether the guest wants the information shared with the kitchen or kept with the host. A simple opt-in respects the guest and gives the office a clear basis for handling the record.

Do not ask for a diagnosis or a full medical history. Record only what the guest volunteers and what the kitchen needs to prepare a safe meal. If the guest mentions a severe allergy, ask how the kitchen should respond and whether the guest carries medication. Keep the answer factual and brief. The CDC food allergy guidance is a useful reference for why cross-contact matters, not a substitute for the guest's own instructions.

Separate preference from safety

Use two fields on the card: preferences and safety notes. Preferences include dislikes, favored cuisines, and beverage choices. Safety notes include allergies, intolerances, and any instruction the guest gives about preparation. Keeping the fields separate prevents a strong dislike from being treated as a medical restriction and keeps a real allergy from being lost among preferences.

Mark allergy entries with a clear label and the date they were confirmed. Note whether the guest has eaten at the venue before and whether the kitchen has a separate preparation area. If the venue cannot meet the requirement, say so early and offer an alternative. Never promise a safe meal on the kitchen's behalf without confirming the process with the chef.

Design the card for quick reading

Put the guest's name, the host, and the event date at the top. Add a short line for preferences, a highlighted line for safety notes, and a line for the confirmed beverage. Include the name of the person who collected the information and the date of the last confirmation. Keep the card to one page and use plain language rather than codes.

Store the card with the event file, not in a public shared folder. Limit access to the assistant, the host, and the catering lead for that event. If the card is printed, collect it at the end of the meal rather than leaving it on the table. The lobby arrival script can prompt the host to confirm the card when the guest checks in.

Brief the kitchen with names attached

Send the catering lead a short brief that lists each guest, the safety note, and the confirmed preference. Do not send a combined list that hides which guest has which restriction. Ask the catering lead to confirm receipt and to name the person who will handle the special meal. Record that confirmation on the event file.

For a plated meal, ask for a labeled plate or a separate serving marker that the server can identify without announcing the guest's medical information. For a buffet, ask for serving utensils that are not shared between dishes and a clear label for each item. The conference credential reconciliation sheet uses the same principle of tying one name to one controlled item. Label the plate on the underside so the guest is not presented with a visible medical note.

Confirm again on the day

Call the catering lead on the morning of the event and read back the safety notes. Confirm the final guest count and the timing of the meal. Ask whether any ingredient changed since the brief was sent. Record the name of the person who confirmed the details and the time of the call.

At the table, tell the host quietly which dish is the safe option for the guest. Do not announce the restriction to the room. If the guest declines the special meal, respect the choice and do not press for an explanation. The assistant's job is to make the safe option available, not to police what the guest eats.

Update and retire the card

Review the card before each event and after any change the guest mentions. Record the date of the update and the source of the information, such as the host's email or the guest's note. If the guest's preferences change, replace the old entry rather than adding a second conflicting line. Keep one current card per guest and archive the older version with the event file.

Retire the card when the relationship ends or when the guest asks the office to delete the information. Follow the office's records retention schedule and note the deletion date. Record the deletion in the office privacy log so a later reviewer can see why the card is gone. If your team needs help running executive hospitality with this level of care, contact us to discuss assistant coverage and event support.