Expedition Cruise Operations Software: Tenders, Landings and Biosecurity

Expedition cruising takes the guest operation beyond the vessel. A landing may involve several small craft, changing weather, a strict people-ashore limit, site-specific guidance, qualified drivers, biosecurity preparation and a reliable record of who has left and returned.

Expedition cruise operations software should connect those moving parts with the active voyage and the people already held in the ship's operational systems.

The landing begins with the itinerary and site

A port call is not enough to describe an expedition landing. Operations needs the landing site, planned activity, guidance, timings, capacity constraints and local or association references connected to that voyage.

A landing-site catalogue gives the expedition team a consistent record to plan against. The itinerary can then connect the site with the scheduled landing, tender plan and subsequent reporting.

This avoids a common planning gap: the voyage schedule contains the location, while the operational guidance sits in a separate folder that is difficult to use during dispatch.

People-ashore control belongs in the dispatch workflow

The Antarctic visitor guidelines hosted by IAATO state that a maximum of 100 passengers may be ashore from a vessel at one time unless site-specific guidance requires fewer. They also state that vessels carrying more than 500 passengers do not make landings. The current visitor guidance should always be read alongside the applicable site, operator and authority requirements.

For operations, that means the people-ashore position cannot be a number updated separately after each boat leaves. Tender Operations should connect boarding, dispatch, landing and return so the team sees the live count and the individuals currently off the ship.

The dispatch view needs to answer:

• Which craft is preparing, away, landed or returning?
• Who is aboard each craft?
• How many people are currently ashore?
• How much capacity remains under the applicable limit?
• Has every dispatched person returned?

That picture supports both guest flow and the ship's wider accountability process.

Driver competency should be visible at assignment

A name on a staffing list does not show whether the person is current for the duty. Zodiac driver licensing connects the competency record with dispatch planning so the expedition team can confirm that assigned drivers hold the required current qualification.

The operational value is timing. An expired or missing record should be visible while the run is being planned, not after the craft has been assigned.

The same crew record can connect driver competency with contract dates and the active vessel, reducing the risk of using a qualification that belongs to a previous assignment or has since lapsed.

Biosecurity is a repeatable operational process

IAATO's marine decontamination procedures describe cleaning boots, clothing and equipment to reduce the transfer of non-native species and disease. The 2025–26 procedures apply to visitors broadly, including guests, crew, guides and small-boat drivers.

A biosecurity log should help the expedition team record the checks and decontamination connected to the operation. It is not a replacement for the procedure or the judgement of the responsible team. It provides a consistent record that the procedure was carried through for the relevant landing and people.

Wildlife sightings can sit alongside that operational record. Structured observations support voyage reporting and the citizen-science experience many expedition guests value, while keeping the data connected to the site and date.

Site reporting should draw from the completed operation

The best time to create the operational record is while the landing is happening. Craft runs, timings, counts and site activity should then feed the required post-visit or association reporting rather than being reconstructed from several notebooks after the voyage.

IAATO has long used post-visit reporting to compile activity and tourism statistics. The software should make it easier to prepare the operator's output from the voyage record while leaving the responsible team in control of review and submission.

Connectivity cannot be assumed at the landing

Tender dispatch often happens where open-internet connectivity is weak or absent. The shipboard workflow needs to remain available locally so boarding and return do not wait for a satellite link.

An offline-first platform can keep the operational record aboard and reconcile relevant information with shore when connectivity returns. That is particularly important for accountability: the live position must belong to the ship conducting the operation.

What to ask when evaluating expedition software

1. Are landing sites and their guidance connected to the voyage itinerary?
2. Does tender dispatch track each craft from boarding through return?
3. Is the live people-ashore count calculated from actual dispatch activity?
4. Can driver competency be checked during assignment?
5. Are biosecurity checks recorded against the landing operation?
6. Can completed operations feed site and post-visit reporting?
7. Does the workflow continue locally when connectivity is unavailable?

One operational picture beyond the shell door

An Expedition Operations system connects the itinerary, landing site, craft, driver, guest and environmental record. The expedition team still makes the operational decisions; the software keeps the plan, live position and completed history together.

That shared picture is essential when the guest operation moves off the vessel and into one of the most sensitive and changeable environments in the world.