Loading...
operations

Cruise Ship Special Needs Guest Accommodation Request Form

Use this form to collect cruise guest accessibility requests before sailing, including mobility aids, cabin access, dietary needs, and muster station support. It helps operations review needs early and confirm what can be arranged.

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

Built for: Cruise Lines · Travel And Hospitality · Guest Services · Tour Operations

Overview

This Cruise Ship Special Needs Guest Accommodation Request Form is a pre-cruise intake template for collecting the accessibility and support details a sailing team needs before embarkation. It organizes guest identity and booking information, then branches into accommodation categories, mobility and cabin accessibility, dietary restrictions and food allergies, and muster station or safety adjustments.

Use it when a guest may need a wheelchair-accessible cabin, help with a mobility aid, meal handling for allergies or dietary restrictions, pre-boarding time, or a modified muster station process. The form works best when reservations, guest services, and onboard operations need a single record to review and act on. It also supports a clear consent step so guests understand how their PII will be used.

Do not use this form as a general complaint form or a broad medical intake. It should not collect unnecessary health history, diagnosis details, or sensitive data that is not needed to arrange the accommodation. If a request is simple and already confirmed in the booking record, a lighter workflow may be enough. If the guest needs urgent medical assistance rather than an accommodation, route them to the appropriate emergency or medical process instead.

The template is designed to reduce back-and-forth, keep required fields limited, and make it easier to review requests consistently before sailing.

Standards & compliance context

  • Keep the form aligned with GDPR data minimization by collecting only the PII needed to process the accommodation request.
  • Use accessible labels, keyboard navigation, and clear validation messages so the form meets WCAG 2.1 AA expectations for public-facing intake.
  • If the form is used for employee or contractor travel accommodations, include ADA reasonable-accommodation language where applicable.
  • Treat dietary and mobility information as sensitive operational data and limit access to staff who need it to fulfill the request.
  • Include an audit trail or submission record so operations can confirm what was requested, reviewed, and approved.

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 Booking Information

This section identifies the guest and sailing so the request can be matched to the correct reservation and routed without delay.

  • Guest full name (required)
  • Booking reference (required)
  • Sailing date (required)
  • Contact email (required)
  • Contact phone
  • Preferred contact method (required)

Accommodation Categories

This section captures the broad type of need first, which keeps the rest of the form focused through progressive disclosure.

  • What type of accommodation do you need? (required)
  • Please describe the other accommodation needed (required)
  • Is there a deadline or urgency we should know about?

    For example, equipment delivery timing or a time-sensitive medical or dietary need.

Mobility and Cabin Accessibility

This section matters because cabin layout, boarding, and onboard movement often require specific details to plan correctly.

  • Mobility aid used
  • Please provide details about the mobility aid
  • Cabin accessibility needs
  • Please describe any additional cabin accessibility needs

Dietary Restrictions and Food Allergies

This section helps food service separate preference-based requests from safety-related allergy handling and cross-contact concerns.

  • Dietary needs (required)
  • Please describe the dietary restriction or allergy (required)

    Include only the information needed for meal planning and safety.

  • Is cross-contact a concern? (required)
  • Would you like to share any emergency response instructions related to this allergy?

    Do not include sensitive medical history unless it is necessary for safe accommodation.

Muster Station and Safety Adjustments

This section records any boarding or emergency-drill support needed so safety teams can prepare in advance.

  • Muster station support needed (required)
  • Please describe the safety-related accommodation needed
  • Do you need pre-boarding assistance? (required)

Consent and Review

This section confirms consent, accuracy, and any final notes so the submission can be processed with a clear audit trail.

  • Consent to process accommodation details (required)

    I understand this form collects limited PII and accommodation details to coordinate my request, and that the information will be shared only with staff who need it to provide services.

  • Information accuracy confirmation (required)

    I confirm the information provided is accurate to the best of my knowledge.

  • Additional notes

    Use this field for any other relevant details not covered above.

How to use this template

  1. 1. Add the guest and booking fields, mark only the fields needed to identify the reservation, and include a clear note explaining what happens after submission.
  2. 2. Configure the accommodation categories with multi-select or conditional logic so guests only see the follow-up fields that match their request.
  3. 3. Route mobility, cabin accessibility, dietary, and muster station responses to the teams that can review feasibility and confirm next steps.
  4. 4. Review each submission for missing details, verify the booking reference, and contact the guest using the preferred contact method if clarification is needed.
  5. 5. Record the approved accommodations in the guest profile or operations workflow and flag any items that require pre-boarding or special handling on sailing day.

Best practices

  • Use conditional logic so guests only see the fields that apply to their request, instead of forcing them through every section.
  • Mark required versus optional fields clearly and keep the form limited to the minimum necessary information for accommodation planning.
  • Use a date picker for sailing date and structured inputs for contact details and booking reference to reduce validation errors.
  • Add a plain-language consent statement that explains how PII will be used, who will review it, and how long it will be retained.
  • Capture dietary allergies separately from general preferences so food service can distinguish safety-related needs from preference-based requests.
  • Include a clear field for cross-contact concern when allergy handling requires extra kitchen precautions.
  • Ask for specific mobility aid details, such as wheelchair, scooter, walker, or cane, so cabin and boarding teams can prepare appropriately.
  • Provide a free-text details field only after a structured field, so guests can explain edge cases without making the whole form unstructured.

What this template typically catches

Issues teams running this template most often surface in practice:

Guest name or booking reference is missing, which makes it hard to match the request to the correct sailing.
The form uses one large free-text box for everything, which hides critical details like allergies, cabin access, and pre-boarding needs.
Dietary restrictions are listed without stating whether cross-contact is a concern, leaving food service without enough context.
Mobility aid details are too vague, so staff cannot tell whether the guest uses a wheelchair, scooter, walker, or another device.
Muster station support is requested without explaining the specific limitation, which slows down safety planning.
The form collects unnecessary medical history or diagnosis information instead of only the accommodation details needed.
Required fields are overused, which creates friction and increases incomplete submissions.
There is no clear note about what happens after submission, so guests do not know when or how they will hear back.

Common use cases

Wheelchair-accessible cabin planning for a family cruise
A guest traveling with a wheelchair needs cabin access details, boarding support, and confirmation that the room layout can accommodate mobility equipment. The form gives operations a structured way to review the request before the sailing date.
Allergy-aware dining coordination for a premium itinerary
A guest reports severe food allergies and wants the kitchen team to understand cross-contact concerns. The template captures the specific dietary details needed for meal planning without asking for unrelated medical history.
Pre-boarding support for limited mobility
An older guest can board safely but needs extra time and a modified muster station process. The form records the support needed so guest services can coordinate timing and safety adjustments.
Scooter and mobility aid review for an expedition sailing
A guest plans to bring a scooter and wants to confirm storage, cabin access, and boarding logistics. The template helps the team gather the exact mobility aid type and any special handling details.

Frequently asked questions

Who should use this form?

Use it for guests who need accessibility or special needs accommodations before embarkation. It is typically completed by the guest, a travel companion, or a reservations team member on the guest’s behalf. The form is most useful when operations, guest services, and food service need advance notice to review feasibility.

What kinds of requests does this template cover?

It covers mobility equipment, cabin accessibility, dietary restrictions, food allergies, muster station support, and pre-boarding needs. The structure also leaves room for other accommodation details and urgency notes. That makes it suitable for both standard requests and less common situations that need manual review.

When should guests submit it?

Guests should submit it as early as possible before sailing so the cruise line has time to review the request and coordinate with relevant teams. The urgency field helps flag time-sensitive needs, but it should not replace advance planning. If a request is submitted close to departure, it may still be reviewed, but some accommodations may be limited by ship operations.

Does this form collect personal data, and how should that be handled?

Yes, it collects PII such as name, booking reference, and contact details, so the form should include a clear consent and disclosure statement. Only ask for fields needed to process the accommodation request, following data minimization principles. Make sure the form explains what happens after submission and who will review the information.

How should dietary and allergy information be handled?

Use the dietary section to capture only the details needed for meal planning and safety coordination. If cross-contact is a concern, the form should make that explicit so food service can assess risk and respond appropriately. Avoid asking for unrelated medical history or overly broad health details.

Should this form allow anonymous submission?

No, not for this use case, because the team needs booking information and contact details to arrange accommodations and follow up. Anonymous submission is better suited to feedback or whistleblower forms, not guest service requests. Instead, keep the required fields limited to what is necessary and explain why each is collected.

What are common mistakes when using this template?

Common mistakes include making every field required, using free-text fields where a date picker or multi-select is a better fit, and failing to use conditional logic for branches that do not apply. Another pitfall is not clarifying whether the guest needs pre-boarding or muster station support, which can delay review. The form should also avoid vague wording that leaves operations guessing.

Can this template be customized for different cruise lines or itineraries?

Yes, it can be adapted for ocean cruises, river cruises, expedition sailings, or charter operations. You can rename fields, add ship-specific accessibility options, or adjust the review workflow for different ports and onboard services. Keep the core structure focused on the accommodations your team can actually evaluate and fulfill.

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

A structured form is easier to review than scattered emails or call notes because it standardizes the fields operations need to act on. It also creates a cleaner audit trail and reduces the chance that a critical detail is missed. Ad-hoc intake can work for exceptions, but the form is better for repeatable pre-cruise processing.

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 Special Needs Guest Accommodation Request 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?