Loading...
operations

Cruise Ship Guest Food Allergy Declaration Form

Capture guest food allergies, dietary restrictions, and special handling needs before sailing so dining teams can plan safer meals across onboard venues.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Cruise Lines · Hospitality · Travel And Tourism

Overview

This Cruise Ship Guest Food Allergy Declaration Form collects the guest details dining teams need to plan safer onboard meals: name, booking reference, sailing date, cabin number, allergen types, reaction severity, cross-contact concerns, dietary restrictions, special handling instructions, and consent to share the information with dining staff.

Use it before sailing when a guest has a food allergy, sensitivity, or dietary restriction that may affect menu selection, ingredient handling, or service timing. It works well for pre-boarding intake, guest services follow-up, and venue-level planning across main dining rooms, specialty restaurants, and buffet service. The form is also useful when a guest needs a preferred contact method so staff can confirm details without collecting unnecessary PII.

Do not use this template as a general medical history form or as a substitute for emergency procedures. If the guest only has a simple preference, such as avoiding a cuisine for personal reasons, a lighter dietary preference form may be enough. If the guest needs urgent medical guidance, the form should direct them to the appropriate medical or emergency contact path. Keep the questions focused on what the kitchen and service teams actually need, and use conditional logic so follow-up fields appear only when relevant.

Standards & compliance context

  • Collect only the minimum necessary PII and dietary information needed to coordinate meal service, in line with GDPR data minimization principles.
  • If the form includes health-related details, limit access to staff who need the information and document sharing through an audit trail where possible.
  • Use clear consent language before sharing allergy details with dining teams or venue staff, especially when contact information is collected.
  • Design the form with accessible labels, validation, and keyboard-friendly controls to support WCAG 2.1 AA usability expectations.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Guest and Voyage Details

This section ties the request to the correct booking and sailing so staff can match the declaration to the right guest and itinerary.

  • Guest full name (required)
  • Booking reference (required)

    Use the reservation or confirmation number associated with your cruise.

  • Sailing date (required)
  • Cabin number

    Optional. Provide only if you want dining teams to help verify your onboard profile.

Allergy and Sensitivity Details

This section captures the specific trigger, severity, and cross-contact risk that drive kitchen handling decisions.

  • What allergens or sensitivities should the kitchen know about? (required)
  • If you selected Other, please specify
  • How severe is the reaction? (required)
  • Should the kitchen avoid cross-contact? (required)
  • Briefly describe the reaction or symptoms

    Only include information that helps staff understand the risk. Do not include unnecessary medical history.

Dietary Restrictions and Meal Preferences

This section separates true restrictions from preferences so dining teams can plan substitutions without guessing.

  • Do you follow any dietary restrictions in addition to allergies?
  • If you selected Other, please specify
  • What meal support would be most helpful?

Special Handling and Contact Consent

This section tells staff how to handle the request and confirms permission to share the minimum necessary details with the right teams.

  • Special galley handling instructions

    Describe any preparation or serving steps that reduce risk, such as separate utensils, ingredient checks, or advance notice before service.

  • Preferred contact method for dining follow-up (required)
  • Phone number
  • Email address
  • Consent to share this information with onboard dining and guest services teams (required)

    By checking this box, you consent to the use of the information provided here for meal safety coordination during your cruise.

Emergency and Acknowledgment

This section records an emergency contact and guest acknowledgment so the submission has a clear responsibility and follow-up path.

  • Emergency contact name
  • Emergency contact phone
  • I confirm the information provided is accurate to the best of my knowledge (required)
  • What happens after I submit?

    Your declaration will be reviewed by the appropriate guest services and dining teams. Staff may contact you to clarify details before or during the voyage. Please continue to inform venue staff of your allergies each time you dine, as menus and preparation conditions can change.

How to use this template

  1. 1. Add the cruise line’s booking, sailing, and contact fields, then mark only the truly necessary items as required.
  2. 2. Set up allergen and dietary restriction options with multi-select fields and conditional logic so guests only see follow-up questions that apply.
  3. 3. Route submissions to guest services and dining leadership, and define who receives the minimum necessary details for meal planning.
  4. 4. Review each form before embarkation to confirm severity, cross-contact concerns, and any special handling instructions that affect service.
  5. 5. Record the action taken, such as venue notes, chef review, or guest callback, so the request has a clear follow-up trail.
  6. 6. Update the form if the guest’s needs change before sailing and keep the latest submission as the active reference.

Best practices

  • Use multi-select checkboxes for allergen types instead of a single free-text field so staff can sort requests quickly.
  • Mark only essential fields as required and keep optional fields clearly labeled to reduce drop-off and support data minimization.
  • Add conditional logic for reaction severity and cross-contact concern so guests do not face a long form when only a few fields apply.
  • Include a plain-language consent statement before collecting contact details or sharing information with dining teams.
  • Ask for the minimum necessary detail about previous reactions, and avoid collecting unrelated medical history.
  • Use a date picker for sailing date and structured fields for booking reference and cabin number to reduce entry errors.
  • State what happens after submission, including who reviews the form and how the guest will be contacted if clarification is needed.
  • Keep special handling instructions specific to meal service, such as separate plating or ingredient verification, rather than broad personal notes.

What this template typically catches

Issues teams running this template most often surface in practice:

Guests leave the allergen field too vague, such as writing only 'allergies' without naming the specific trigger.
Reaction severity is omitted, which makes it harder for staff to judge whether extra precautions are needed.
Cross-contact concerns are not captured, so the kitchen cannot tell whether standard cleaning and separate utensils are enough.
The form asks for too much unrelated medical detail instead of focusing on meal-service needs.
Special handling instructions are written in general terms and do not tell staff what action to take.
Contact fields are incomplete, which prevents follow-up before sailing.
Consent to share with dining teams is missing, creating uncertainty about who may review the information.

Common use cases

Guest Services Pre-Boarding Review
A guest services agent reviews submitted allergy declarations before embarkation and flags severe cases for dining leadership. This helps the ship prepare venue notes and follow-up questions before the guest arrives.
Specialty Restaurant Meal Planning
A specialty dining manager uses the form to confirm ingredient restrictions and plating instructions for a fixed-menu reservation. The structured fields make it easier to coordinate substitutions without over-collecting personal details.
Buffet and Casual Dining Coordination
A buffet supervisor uses the cross-contact and severity fields to decide whether a guest needs staff assistance, ingredient verification, or a separate serving approach. The form supports faster handoff than scattered email requests.
Accessibility and Accommodation Intake
An accessibility coordinator uses the preferred meal support and special handling fields to document reasonable accommodations tied to dining. The template keeps the request focused on service needs rather than broad medical history.

Frequently asked questions

Who should use this food allergy declaration form?

Use it for guests who need the cruise line to know about food allergies, sensitivities, or dietary restrictions before boarding. It is especially useful when dining teams need advance notice to coordinate ingredient checks, cross-contact precautions, or special meal support. It is not a substitute for emergency medical care or a full medical intake form.

When should guests complete the form?

Guests should complete it as early as possible after booking and again if anything changes before sailing. Early submission gives the dining team time to review the request, confirm any needed accommodations, and flag the booking for onboard follow-up. If the cruise line allows updates, the form can also be used for pre-boarding changes.

Who reviews the information after submission?

Typically, the dining team, guest services, or an onboard accessibility coordinator reviews the form and shares only the minimum necessary details with the people who need them. The consent field supports that limited sharing with dining staff. If your process includes an audit trail, this form can also document who received the request and when.

Does this form replace medical clearance or emergency planning?

No. It helps collect food-related preferences and risk information, but it does not replace medical advice, emergency protocols, or onboard treatment procedures. Guests with severe allergies should still follow the cruise line’s emergency guidance and carry any prescribed medication they need. The form should clearly state what happens after submission and who to contact for urgent concerns.

How does this form support accessibility and accommodation needs?

The form can include clear field labels, required versus optional markers, and progressive disclosure so guests only see follow-up fields when relevant. That makes it easier for people using assistive technology and helps staff capture reasonable-accommodation requests without forcing unnecessary disclosure. If you collect contact details or health-related notes, include a plain-language consent statement.

What are the most common mistakes when using this template?

A common mistake is asking for too much detail, such as unrelated medical history or more PII than the dining team needs. Another is using free-text fields where structured options would work better, which makes it harder to sort allergens and plan meals. Teams also sometimes forget to explain whether the guest can submit anonymously for feedback forms, but for this declaration form the key issue is clear consent and follow-up contact.

Can this template be customized for different cruise itineraries or dining venues?

Yes. You can add venue-specific notes, pre-boarding deadlines, language support fields, or conditional logic for specialty restaurants, buffet service, and shore-excursion meal packs. Keep the form focused on what dining staff will actually use, and avoid turning it into a general health questionnaire. If you need different versions by itinerary, duplicate the template and adjust the meal support options.

How does this compare with handling allergy requests by email or phone?

A structured form is easier to review than scattered emails because it standardizes the fields, reduces missing details, and creates a clearer record for handoff. It also supports validation, required fields, and consistent consent language. Email and phone can still be used for exceptions, but the form gives the team a repeatable intake process.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Cruise Ship Guest Food Allergy Declaration Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?