A preference sheet can tell you that eight guests love Mediterranean food, one avoids dairy and everybody wants to eat “light”. It may also reveal that “light” includes a cheese board at midnight. Your job is to turn those fragments into service decisions without becoming a detective with a fish knife.
Start by treating the document as the beginning of a conversation. It is a valuable brief, but incomplete answers, old information and ambiguous labels need confirmation before they become purchase orders.
First, separate requirements from wishes
Create distinct fields for food allergies, intolerances, coeliac disease or other stated medical dietary requirements; ethical or religious restrictions; dislikes; and positive preferences. Keep the guest’s wording alongside your clarified operational note.
An allergy involves the immune system and can be serious. An intolerance is different and can still make someone unwell. A preference describes a choice, not a diagnosis. Coeliac disease belongs in its own medical requirement category, not under casual gluten avoidance. Do not classify an unclear answer yourself or decide that a reported restriction is unimportant. The NHS explanations of allergy and intolerance are useful background; they do not turn a chef into a clinician.
Confirm directly with the guest, or an authorised representative, what they need to avoid and what information they have supplied. Ask practical questions calmly. Establish whether the galley can meet the requirement, including relevant cross-contact controls, before promising a dish. If that remains uncertain, explain the limitation and agree the next step with the appropriate onboard team.
A good preference sheet reduces guesswork. A good conversation removes it.
Look for the missing operational information
“No dairy” needs clarification; “likes fish” needs culinary detail. Does the guest enjoy whole fish, boneless fillets, shellfish, or simply salmon? Ask about preparation and presentation without turning breakfast into an interview panel.
Then add the details that determine your working day: arrival meal, expected meal times, children’s meals, shore dining, celebrations, snack habits and any dishes they especially want. Record the number of people at each service rather than assuming every guest eats every meal onboard.
Distinguish a firm plan from an estimate. A tentative restaurant booking should not quietly erase dinner provisions. Mark it as pending and set a sensible decision time with the chief steward or captain.
The three-question clarification
- What exactly does this statement mean for this guest?
- What decision changes once I know the answer?
- Who can confirm it, and by when?
This keeps your questions purposeful. Nobody needs a twelve-message discussion about parsley when a guest’s dietary requirement is still unresolved.
Build a matrix you can actually use
For each guest, show confirmed restrictions, favourite styles, dislikes and unresolved points. Add a date and version. Keep detailed personal information in the appropriate restricted location; the service team needs clear instructions relevant to their work, not somebody’s entire medical history in a group chat.
Translate the matrix into three outputs: a provisional menu, a purchasing specification and a service note. These documents serve different people. A supplier needs the correct product and ingredient information; the interior team needs to identify the correct plate and understand what was confirmed.
A worked example: one lunch, several needs
Imagine six guests request a relaxed Mediterranean lunch. One reports a sesame allergy, another dislikes olives and a third prefers a vegetarian meal. Confirm the allergy requirement and your ability to cater for it before finalising the menu.
You might plan a vegetable-led shared concept with individually plated main courses. Review every relevant ingredient and preparation step for the confirmed allergy controls; do not assume removing a garnish makes the meal suitable. Keep olives optional for the guest who dislikes them. Give the vegetarian guest a complete main course rather than the other plates with the protein missing.
The culinary idea stays coherent, while each requirement receives the attention it deserves. Your purchasing list should reflect the actual portions and approved ingredients, with any alternatives checked before ordering.
Close the loop before service
Reconfirm significant changes, update the working version and brief the people involved. If software extracts a scanned preference sheet, compare its output with the original, especially names, negatives and restrictions. “No nuts” is a remarkably important place to lose a word.
After service, record useful feedback factually: portion size, preferred preparation, an agreed timing change. Avoid speculative labels or jokes in guest records. Save the humour for the galley, and the clarity for the next person who has to cook dinner.