A passenger manifest concerns the people travelling, not simply the number of tickets sold. Required registration, reporting and retention rules depend on the voyage and the applicable authority.
The booking contact, ticket purchaser and individual passenger can be different people. Decide how the required traveller information is captured and corrected in the operating process.
A booking contact identifies who arranged or paid for travel. A departure record may need information about each person travelling. Define the data and correction process your operation requires with the competent authority, then confirm the software fields and output. A booking preview is useful operational evidence, but its presence alone does not establish compliance.
A usable departure record needs a point at which the responsible team checks additions, cancellations and corrections. Agree the output and recipient required for your operation.
Check current requirements with your maritime and legal advisers or competent authority. EU passenger-registration rules and international reporting arrangements have defined scopes; software does not determine compliance.
Discuss required fields and output formats with our team. A daily booking preview is an operational view and should not be assumed to be a complete statutory manifest.
A passenger manifest records the people associated with a voyage.
Explore Passenger Manifest
Organise scheduled passenger crossings from booking to ticket control.
Explore Passenger Ferries
Review bookings and sales alongside the departures they belong to.
Explore Operations & ReportingBring your questions about passenger manifest: data & operating process to a discussion of your routes and working procedures.
