A quick snapshot of today

• Give a one-sentence summary of your current port operation and which terminals you use most often.
• How many cruise calls does your team manage at this port in a typical month? Options: 0-3, 4-10, 11-20, 21-50, 51+
• Who on your team owns turnaround performance and day-of coordination? Options: VP of Port Operations, Marine Operations Director, Terminal Manager, Operations Manager, Other
• When you measure on-time departures today, what metric and window do you use, for example 'vessel underway within 10 minutes of scheduled'?
• Describe the typical peak embarkation window you operate to, including passenger count and hours.
• Given your typical monthly call volume, if it is below 4, would you pursue an external turnaround partnership now, postpone, or prefer an internal fix? Options: Pursue external partnership, Postpone and reassess, Prefer internal solution, Undecided

Where delays actually start

• What single predictable operational failure on double-ship or other peak days would make you cancel or delay a sailing?
• Walk me through the last time a peak embarkation failed to hit target throughput, what sequence of events unfolded, and how long did recovery take?
• Which checkpoints — curb arrival, check-in, security, customs, baggage sort, gangway — consistently create the longest queues for your passengers? Options: Curb arrival/valet, Check-in counters, Security screening, Customs/CBP, Baggage sortation, Gangway/boarding
• How often do baggage misses occur on a busy day, and what proportion of impacted passengers typically miss the sailing or require special handling? Options: Rarely (under 1%), Occasionally (1-3%), Often (3-7%), Regularly (7%+)
• Who notices the problem first during those incidents, and how is the information escalated? Options: Terminal Supervisor, Baggage Contractor, Cruise Line Ops rep, Port Authority Liaison, Other
• If nothing changed, what downstream costs or reputational hits do you expect after repeated peak-day failures?

Operational roles and the invisible handoffs

• Where are responsibilities blurry between your team, the port authority, and third-party vendors in a way that routinely slows responses?
• List the third-party functions you rely on for a turnaround, such as customs coordination, baggage handling contractors, provisioning vendors, or ground transport pools. Options: Customs and border coordination, Baggage handling contractor, Provisioning vendors, Ground transport / buses, Tender operators, Fueling / waste contractors, IT/system integrator, Other
• Do you have named contact owners for each of those functions and documented acceptance criteria for handoffs? Options: Yes, documented with SLAs, Yes, but informal, No, single points of contact only, No, must be defined
• What is your expected response time from a named vendor or port authority representative when a derailment happens during an embarkation window? Options: Under 15 minutes, 15-30 minutes, 30-60 minutes, Over 60 minutes, No guaranteed response time
• Which role approves emergency resource requests, such as adding baggage sorters or opening an extra security lane, and what is your expected approval timeline? Options: Terminal Manager (immediate), VP Port Ops (within hours), Port Authority (24+ hours), No formal approver
• Would you walk away from a partnership if on-site vendor response time exceeded 60 minutes during a peak embarkation? Options: Yes, unacceptable, Only with strong mitigations, No, acceptable with SLA credits, Depends on context

Constraints that will stop a launch

• Name one non-negotiable infrastructure or regulatory constraint at this port that would prevent you from agreeing to a new turnaround commitment.
• List the integration endpoints that must be available before go-live, for example CBP pre-clearance feeds, your reservation system handoff, or the cruise line's app APIs. Options: Passenger manifest feed, Baggage tag scan events, Queue/occupancy sensors, CBP pre-clearance feed, Provisioning order system, Ground transport dispatch
• Do your teams currently have the headcount and technical capacity to own integrations and day-of dashboards, or would you expect the seller to provide dedicated staff? Options: We have full capacity, We have limited capacity, need support, We expect the seller to staff, Unsure
• Where does the data that turnaround tracking depends on live today, and who controls release permissions?
• Rate how clean and consistently formatted your passenger manifest, baggage tags, and provisioning order data is on a 1 to 5 scale. Options: 1, 2, 3, 4, 5
• If any of these prerequisites cannot be met within the preferred launch window, what is your backup timeline or exit criteria?

What alternatives are still in play

• Identify the alternative ports, incumbent vendors, or internal solutions you are actively considering as the fallback to a new vendor partnership. Options: Regional competing port, Current terminal operator, Internal operations build, Third-party logistics partner, No alternative identified, Other
• Under what conditions would you decide to stay with your current approach rather than change to an outside operator?
• Has anyone on your team proposed solving the problem internally, and if so, what resource estimate have they provided? Options: Yes, with estimate, Yes, no estimate, No, not proposed, Unsure
• Please name the person or role that holds the relationship with the port authority, and indicate whether they must be involved in commercial terms or concession discussions. Options: Yes, must be involved, Optional, No involvement required, Unsure
• Describe the specific concession or short-term incentive that would cause you to accept an incumbent's offer instead of moving forward with a new partner.

Acceptance criteria and success signals

• Name the measurable outcomes that must be true on day one for you to call the launch a success. Options: On-time departure within agreed minutes, Baggage delivery SLA met, Passenger throughput target met, Customs wait below threshold, Provisioning complete on schedule, Other
• Explain how you will measure baggage SLA and who will sign off on the data each week.
• Specify the tolerance band for turnaround time that would trigger penalties or renegotiation, for example 'sailing delayed more than 10 minutes, three times in a month'. Options: 0-5 minutes, 6-10 minutes, 11-20 minutes, More than 20 minutes, Other
• Identify the approver role in procurement or legal who must approve the final SLA and concession terms, and indicate typical approval lead time. Options: Procurement Director, General Counsel, Head of Marine Ops, Port Authority Liaison, Other
• Tell which internal obstacle could still prevent you from signing a long-term agreement within 30 days if the pilot achieves the agreed KPIs.

Operational readiness, the practical checklist

• Imagine we handed you a launch checklist today, which three items would likely be missing or incomplete?
• Provide the approvals and permits that must be in hand before a go or no-go decision, and name who owns securing each.
• Confirm whether you have surge staffing plans and contingency rosters that scale for double-ship days, and indicate if staff are direct hires or agency-contracted. Options: Direct hires, Agency-contracted, Combination, No surge plan
• Indicate where physical site access, staging areas, and equipment go-live keys need coordination with the port authority and vendors.
• Are there blackout dates, special events, or military movements that could force a launch delay, and how often do they occur annually? Options: Yes, seasonal peak, Yes, scheduled events, Rarely, No
• Given a single readiness item remains unmet two weeks before launch, would you delay, proceed with mitigations, or cancel, and which option would your executive sponsor prefer? Options: Delay launch, Proceed with mitigations, Cancel launch, Escalate to port authority

Integration, data flows, and day-of systems

• Count the integration endpoints that will need real-time data exchange on day one, for example manifest feeds, queue sensors, or baggage sortation signals. Options: 0-2, 3-5, 6-10, 10+
• Provide the teams or organizations that own the APIs or interfaces supplying passenger and baggage data, and state whether test credentials can be granted within two weeks.
• Choose which staffing model you require for the first 90 days: seller-operated console, joint operation, or fully run by your team. Options: Seller-operated console, Joint operation, Buyer-operated, Unsure
• Differentiate the data elements that are mission critical versus nice-to-have for hitting turnaround KPIs, for example accurate arrival ETAs versus baggage tag-level scan events.
• State the contingency you will allow if a critical integration fails during the first two sailings: manual workaround, reduced SLA, or halt operations. Options: Manual workaround, Reduced SLA, Halt operations, Escalate to port authority

Decision steps and next moves

• Point to the internal milestone that, if achieved in the next 30 days, would make you ready to move from evaluation to a signed agreement.
• Specify the roles that must be present for the commercial and operational commit meeting to be final, and confirm whether they have availability within the next two weeks. Options: VP Port Operations, Legal/GC, Head of Procurement, Port Authority Representative, Terminal Manager, Other
• Declare whether an internal budget cycle or decision blackout could prevent signing within this quarter and indicate timing. Options: Yes, budget cycle, Yes, blackout period, No timing issue, Unsure
• Assuming a pilot meets your KPIs on two back-to-back sailings, list the internal approvals that would still be required before signing a year-long concession, and which of those are likely blockers.
• Share the best contact and preferred time window to follow up so we can keep momentum.

• Turnaround Experience Walkthrough

• You confirm the demonstrated terminal workflow removes the peak-day delays you described and is realistic given your passenger/berth profile.
• Confirm the current state and its cost
• Deliver a scenario-based turnaround runbook and SLA proposal showing timed steps for the demonstrated peak scenarios within five business days.
• You agree on specific, measurable SLAs to anchor the commercial and operational commitments (turnaround minutes, baggage on-time percent, provisioning on-time percent).
• Walk through a peak double-ship terminal flow
• Provide sample peak-day manifests, double-ship schedules, and your current baggage and provisioning performance data for validation runs.
• Schedule a site visit and an operations tabletop with the necessary stakeholders to validate resource commitments and finalize acceptance criteria.
• Show customs coordination and queuing mitigation
• You identify the remaining evidence needed before commitment, and agree the next seller deliverable and timing.
• Run the baggage sortation and delivery timing scenario
• Demonstrate ground transport and provisioning staging controls
• Validate the future state with the team
• Agree acceptance criteria and next evidence needed

• Turnaround Experience Walkthrough
• Solution Experience Deck
• Solution Brief: Turnaround Experience Walkthrough

• meeting
• slides
• document

• Embarkation and Debarkation Operations
• Baggage Sortation and Stateroom Delivery
• Customs Pre-clearance Coordination
• Ground Transportation Staging and Marshalling
• Cold-Chain Provisioning and Stores Handling
• Tender Operations and Gangway Logistics
• Expedited Boarding Lanes and Loyalty Processing
• Real-Time Queue Monitoring and App Feeds
• Terminal Lounge Management and Guest Services
• High-Volume Homeport Turnaround Execution
• Provisioning Vendor Coordination
• Fueling and Waste Removal Services

Embarkation and Debarkation Operations

• How many simultaneous embarkation or debarkation flows do you plan to run during your peak six-hour homeport window (for example two ships, or one ship plus tender operations)? Options: 1 flow, 2 flows, 3+ flows
• How often do you publish berth schedules and last-minute berth changes to partners in a day during peak season? Options: Once, 2-4 times, Continuous updates (push)
• How long is your target curb-to-gangway passenger movement time for standard passengers under normal conditions? Options: Under 30 minutes, 30-60 minutes, Over 60 minutes
• How quickly must passenger manifests be reconciled with your terminal access control system after cut-off to support timely departures? Options: Within 15 minutes, 15-45 minutes, Within 1-2 hours
• When will you require named owners for day-of operations (for example terminal operations lead, baggage lead, and CBP liaison) to be shared with us before the first embarkation? Options: 14 days prior, 7 days prior, 48 hours prior
• Which berth characteristics (length, tidal window, shore power availability) must we include in scope for each scheduled call?

Baggage Sortation and Stateroom Delivery

• How many checked-baggage pieces do you plan to process during a typical homeport embarkation peak (provide an estimate tied to passenger count)? Options: Under 1,000, 1,000-3,000, 3,000-5,000, 5,000+
• How often do you require staged stateroom deliveries by room-assignment windows (for example first wave within 60 minutes of arrival, final wave within 240 minutes)? Options: Two waves, Three waves or more, Continuous staging by ETA
• How long after bag arrival at the terminal do you expect the last-bag delivery SLA to stateroom (reference: baggage delivery time target in minutes)? Options: Under 60 minutes, 60-120 minutes, Over 120 minutes
• Which baggage identification artifacts do you use on bags (for example barcode tag ranges, RFID serial blocks) that we must support in the sortation map? Options: Barcode tag ranges, RFID serial blocks, Both, Other
• How will you verify that stateroom delivery meets your acceptance threshold for the sailing (for example passenger complaints under X per 1,000, or Y% delivered within window)? Options: Passenger complaints per 1,000, % delivered within window, Other metric
• Identify the physical sortation footprint you need us to include (conveyor lanes, chute count, secure holding bays) and provide approximate square footage or layout constraints.

Customs Pre-clearance Coordination

• Which customs pre-clearance artifacts do you currently submit and on what timeline (for example passenger e-manifest X minutes before departure, crew lists, prohibited-articles manifests)?
• How often do you require a CBP or border agency liaison on-site during double-ship days versus single-ship days? Options: Always on-site, Only on double-ship days, Remote liaison with on-call presence
• How long is your mandated lead time for final passenger manifest submission to the clearance authority prior to departure? Options: Under 60 minutes, 60-120 minutes, Over 120 minutes
• Which electronic interfaces must we support for pre-clearance (for example secure FTP manifest ingest, API endpoint for e-manifest, or portal upload)? Options: Secure FTP, API endpoint, Portal upload, Other
• What acceptance criteria will confirm customs pre-clearance is successful for a sailing (for example clearance received from agency X minutes before departure)? Options: Clearance received >30 minutes before departure, Clearance received >60 minutes before departure, Other
• Provide the list of documents or certificates border agencies require at the terminal (for example vessel declarations, crew manifests, food import permits).

Ground Transportation Staging and Marshalling

• How many drop-off and pick-up lanes do you need reserved for tour buses, private coaches, and rideshare during peak disembarkation? Options: 1-2 lanes, 3-4 lanes, 5+ lanes
• How often do provisioning trucks arrive relative to the vessel loading window and what delivery windows must we enforce (for example 02:00-06:00 prior to sailing)? Options: Fixed early window, Rolling windows with announced ETA, On-call deliveries
• Which marshalling documentation must drivers present on arrival (for example PO number, delivery manifest, certificate of food safety) to access the dock staging area?
• Who on your team approves temporary road closures or shuttle routes to support staged transport for embarkation events?
• Where will marshalling holding areas be located on the terminal map and what maximum dwell time is allowed before a vehicle must be turned away?
• Describe the peak vehicle throughput per hour you must support for shuttle and coach movement to avoid passenger queuing spillback onto public roads.

Cold-Chain Provisioning and Stores Handling

• How many cubic meters or pallets of temperature-controlled provisioning do you handle per call that we must stage and store? Options: Under 10 pallets, 10-30 pallets, 31-60 pallets, 60+ pallets
• How often do you require temperature logs for cold-chain deliveries and what retention period is mandatory for compliance audits? Options: Continuous logging retained 1 year, Continuous logging retained 2 years, Per-delivery logs retained 90 days
• What temperature thresholds must we enforce for chilled and frozen stores (for example chilled 0-4°C, frozen -18°C or below)? Options: Chilled 0-4°C, Frozen -18°C or below, Ambient
• Which receiving artifacts do you require at cold storage handoff (for example signed temperature certificate, supplier COA, PO match) to accept goods into terminal inventory?
• Identify any third-party cold-chain vendors you already use for last-mile provisioning that must be integrated into arrival scheduling.
• How will you verify cold-chain integrity on delivery (for example temperature log attachment to the bill of lading or real-time telemetry alerting)? Options: Temperature log attached to BOL, Real-time telemetry alerting, Post-delivery audit sampling

Tender Operations and Gangway Logistics

• How many tender runs per hour do you plan for port-of-call operations at peak times and what is your max per-boat passenger load per tender trip? Options: Under 100 passengers/run, 100-300 passengers/run, 300+ passengers/run
• How often do you require gangway certifications or safety inspections to be reported before passenger transfer operations begin? Options: Each shift, Daily before first run, Weekly
• Which tender manifest artifacts must be exchanged with tour operators or ground partners prior to the first tender departure (for example passenger manifest by name, excursion IDs)?
• Who on your team is the on-site tender operations lead responsible for passenger priority sequencing and wheelchair/stretcher handling?
• Where will tender staging and passenger marshaling occur on the pier map and what distance/time does that create to the vessel transfer point?
• Describe the contingency lift plan for tender delays (for example reserved extra launches, priority boarding lists, or re-sequencing rules).

Expedited Boarding Lanes and Loyalty Processing

• How many expedited lanes for loyalty-tier or priority boarding do you want configured and what cardholder groups qualify for each lane? Options: 1 lane, 2 lanes, 3+ lanes
• How often do you require integration of loyalty scans with boarding systems (for example real-time validation vs batch reconciliation)? Options: Real-time validation, Batch reconciliation within 60 minutes, No integration required
• Which boarding credential formats must expedited lanes support (for example QR boarding pass, NFC token, printed manifest name-check)? Options: QR boarding pass, NFC token, Printed manifest, Multiple formats
• Who on your loyalty or passenger services team will approve priority lane rules such as guest count per minute and lane opening hours?
• Specify the KPI threshold for expedited lane performance that you expect (for example average processing time per guest in seconds).
• List any accessibility or special-assistance protocols the expedited lane must include (for example dedicated staff, wheelchair routing, elevator access).

Real-Time Queue Monitoring and App Feeds

• How quickly must queue length or wait-time data be published to the cruise line app or partner endpoints (for example every 30 seconds, 1 minute, 5 minutes)? Options: 30 seconds, 1 minute, 5 minutes
• Which integration endpoints must we support for app feeds (for example REST API, webhook, SFTP drop for batch updates)? Options: REST API, Webhook, SFTP, Other
• How many queue cameras or sensor points do you plan to deploy that feed into the queue monitoring dashboard? Options: 1-5, 6-15, 16+
• Describe the mobile app artifacts you want fed (for example estimated wait time, lane open/closed status, push alert for lane changes).
• Who on your IT team will provide API credentials and SLA for endpoint availability for push integrations?
• Indicate acceptable data latency for feed delivery to the app in seconds to meet passenger expectations. Options: <10s, 10-30s, 30-60s

Terminal Lounge Management and Guest Services

• How many lounge seats and overflow areas must be available for peak morning embarkation groups and what occupancy threshold triggers overflow activation? Options: Occupancy 75%, Occupancy 85%, Occupancy 95%
• How often do you require luggage holding and express delivery desks to be staffed relative to ship arrival times? Options: 2 hours before arrival, 1 hour before arrival, On call
• Which guest services artifacts must be maintained in the lounge (for example medical kit, lost-and-found log, ADA assistance equipment)?
• Who on your guest services team is authorized to issue boarding-window extensions or priority passes in exceptional cases?
• Provide the SLA you expect for resolving a guest service incident logged in the lounge (for example initial response time and resolution window). Options: Initial response 15 minutes, Initial response 30 minutes, Custom
• List any lounge certification or concession license documents we must verify before operating guest services on site.

High-Volume Homeport Turnaround Execution

• How many passengers does your peak homeport six-hour turnaround plan need to process per call (provide a passenger count tied to the vessel class)? Options: Under 1,000, 1,000-2,500, 2,500-5,000, 5,000+
• How often do you perform full dress rehearsals or tabletop exercises before the first high-volume season to validate turnaround sequencing? Options: Full rehearsal each season, Tabletop only, No rehearsals planned
• How quickly must your on-time departure metric be reported after sailing (for example within 1 hour, end-of-day) for acceptance tracking? Options: Within 1 hour, By end-of-day, Within 48 hours
• Confirm the acceptance threshold for an on-time vessel turn that you will use to sign off on readiness (for example departure within X minutes of scheduled ETD or % of sailings meeting target). Options: Departure within 15 minutes, Departure within 30 minutes, % of sailings >= 95% on-time
• Identify the critical path tasks you consider non-negotiable for the turnaround (for example baggage loaded, CBP clearance, provisioning complete) and assign owners.
• Outline surge staffing levels you require (for example additional X agents per 1,000 passengers) and the maximum overtime hours allowed per staffer during peak calls.

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Concession & Port Access Agreement
• Pricing & Fee Schedule
• Dependencies & Risk Allocation Schedule
• Operational Acceptance Certificate
• Data Sharing & Systems Integration Annex
• Performance Security & Insurance Requirements
• Governance & Escalation Framework
• Change Order & Variation Process

• Go-live Health Check (Weeks 1-4)
• First Measurement Review (Weeks 4-10)
• 90-day Outcomes Audit
• Quarterly Operational Review
• Annual Strategic Success Review

• Prioritize and schedule resolution for the top persistent operational issues.
• Publish the 90-day outcomes audit report with per-metric status and remediation timelines.
• If incumbent remains, deliver an archival or decommission plan and a schedule to remove fallback activity.
• Schedule the first remediation verification checkpoint within the next 30 days.
• Publish the quarter's operational trend report and prioritized backlog.
• Maintain a 90-day rolling action plan with clear owners and dates.
• Trend review and variance analysis
• Ensure KPIs remain within agreed tolerances and identify any emerging risks to targets recorded in Operational Scope & Responsibilities.
• Re-confirm success criteria and owners
• Close or reassign any action items without progress for more than one quarter.
• Schedule targeted pilots or process trials for agreed improvements with start dates.
• Annual KPI summary and trend versus targets
• Confirm whether annual operational performance met the targets recorded in Operational Scope & Responsibilities.
• Agree a prioritized multi-quarter roadmap of structural improvements with owners and delivery windows.
• Ensure capacity and peak readiness gaps have committed remediation or investment plans.
• Publish the annual performance report with the agreed multi-quarter improvement roadmap.
• Initiate at least one structural improvement project with a documented scope and start date for the following quarter.
• Confirm the schedule for the next year's quarterly operational reviews and one annual review.
• Confirm the deployment is functionally complete and critical interfaces are operational.
• Identify and document the top three go-live issues and remediation owners.
• Agree dates for short-term remediation checkpoints before the first measurement window.
• Distribute a deployment health summary with open issues and owners within 24 hours.
• Deliver a short remediation plan for the top three issues and schedule verification checkpoints.
• Confirm data sources and dashboard ownership for the metrics to be reviewed at first measurement.
• Present first-period KPI data
• Determine whether KPIs are trending toward targets recorded in Operational Scope & Responsibilities.
• Have a documented root cause analysis for each material gap and a corrective action plan with dates.
• Confirm ownership and visibility for the KPI dashboards used for ongoing monitoring.
• Produce a written root cause analysis for any KPI outside tolerance and circulate within 7 days.
• Publish updated surge staffing and baggage handling procedures addressing identified gaps.
• Update the operational dashboard feed and confirm data refresh cadence and owner.
• Restate numeric targets
• Produce a clear status for each target recorded in Operational Scope & Responsibilities indicating on-target or remediation required.
• Ensure incumbent wind-down or data-archival obligations are closed or have committed resolution dates.
• Agree concrete remediation tasks with dates that will return any out-of-tolerance metric to target.
• Deployment and systems validation
• Capacity and peak-season readiness review
• Persistent issue backlog and incident postmortems
• Present 90-day outcome data against each target
• Diagnose root causes for gaps
• Enhancement requests and prioritization
• Lessons learned and structural changes
• Agree corrective actions with owners and dates
• Early operational signals and adoption
• Classify remediation need per metric
• Confirm timeline to acceptance or next gate
• Action item burn-down and owner review
• Incumbent operator or system wind-down status
• Agree multi-quarter improvement roadmap
• Blockers and open issues with owners
• Agree immediate remediation actions
• Agree remediation plan and resolution dates