Independent analysis · AI decision support in cruise ship operations

Briefing / Oversight

Keep the human decision loop

Maritime regulation already defines who decides. The task for decision support is to fit that structure, not to blur it.

Scope
Authority, governance, failure modes
Frameworks
SOLAS · ISM Code · EU AI Act
Decision owner
Master and company management
Start again
Itinerary constraints

Decision support versus decision

The phrase "AI system" covers very different things. In cruise operations, most tools discussed in this briefing are decision support: they forecast, compare options, check rules and flag conflicts. A decision is the act of committing the organisation, whether that means altering course, rebooking a berth, cancelling excursions or approving a roster. Keeping these two layers distinct is the core of good oversight. When a recommendation is accepted without review, the line between support and decision disappears, even if no one intended it.

The authority already in place

Three frameworks set the structure. SOLAS Chapter V, regulation 34-1, protects the master's discretion to act on professional judgement for safety and environmental protection. The International Safety Management (ISM) Code, adopted under SOLAS Chapter IX, requires each company to operate a safety management system, to establish the master's overriding authority and responsibility, and to appoint a designated person ashore with direct access to the highest level of management. Flag state administrations and port state control inspections verify that these arrangements work in practice.

A new tool does not change any of this. If a scheduling model recommends a diversion, the master decides. If a rostering tool proposes a pattern, the department head approves it within MLC 2006 limits. The safety management system should describe how such tools are used, by whom, and how disagreement is recorded.

Ownership matrix · tool role and retained authority
DecisionTool roleRetained authorityRecord
Proceed, wait or divertCompare scenariosMasterDeck log, voyage plan
Itinerary amendmentRank options, estimate effectsFleet operations with masterChange record
Embarkation slot planForecast queuesGuest services, terminalPort plan
Provisioning orderForecast demandHotel and purchasingPurchase order
Crew rosterCheck rest-hour rulesDepartment headsHours-of-rest records

The regulatory horizon

The EU Artificial Intelligence Act, Regulation (EU) 2024/1689, entered into force in 2024 with obligations phased in over the following years. It takes a risk-based approach, with stronger requirements for systems classed as high-risk, including human oversight, logging and transparency. Operators and vendors serving EU markets need to assess where their tools fall. At the IMO, work on a code for Maritime Autonomous Surface Ships addresses a different question, autonomy in navigation, but its emphasis on defined human roles is relevant to planning tools as well. Personal data used in passenger and crew models remains subject to the GDPR.

Designing the loop

  • Show reasoning: recommendations should state the main constraints and assumptions behind them.
  • Show uncertainty: ranges and confidence, not single confident numbers.
  • Offer alternatives: the second and third options, with what each sacrifices.
  • Record overrides: accepting or rejecting advice should be logged with a reason, without blame.
  • Fail safely: when data is missing or stale, the tool should say so and step back.
  • Train for it: bridge and engine resource management training, recognised under STCW, already teaches challenge and cross-checking; tool use belongs in the same culture.

Failure modes to watch

Automation bias

People tend to accept machine output, especially under time pressure. Requiring a brief stated reason for acceptance on significant decisions counters this.

Stale or partial data

A berth schedule updated yesterday or a missing flight list can make a confident recommendation wrong. Data age should be visible on every output.

Single-metric optimisation

A model tuned only for fuel may degrade guest experience or crew rest. Objectives should be explicit and balanced by people who own each outcome.

Vendor opacity

If a supplier cannot explain what a model uses and how it was validated, the operator cannot oversee it. Procurement should require that documentation.

Oversight as part of operations

The point of the whole briefing series is interdependence. A port change touches passengers, supplies and staffing at once; oversight has to see across those boundaries too. That means one owner per decision, a shared record of what the tools advised and what people chose, and periodic review of where advice was wrong. Done this way, decision support strengthens the existing chain of authority rather than competing with it. Return to the itinerary constraints or read the operational questions.

Darkened shoreside operations room with planners seated before several monitors showing charts and schedules
Shoreside planning supports; the ship decides.