▧ SOLUTION

Passenger Reporting & Manifest

Collect passenger identity details on overnight tours, prepare the official notification and produce an immutable manifest.

On overnight tours, passenger notification is a legal obligation. Identity details must be collected, submitted in the correct format and kept on record.

The module takes passengers from the same source as the booking form, prepares the notification record, and on confirmation produces an immutable manifest: the JSON snapshot is frozen and signed with a SHA-256 digest. It cannot be updated afterwards.

Because the module holds sensitive identity data it sits in its own permission scope; only authorised roles can reach it, and every view and change is written to the audit trail.

COMPLIANCE

How the module works

01
♙

Passenger collection

Identity fields are managed from the same source as the booking guest record.

02
▧

Notification record

Submission history with ready, sending, successful, failed and cancelled states.

03
🔒

Immutable manifest

A confirmed manifest is frozen and signed with a SHA-256 digest.

04
⌁

Pluggable adapter

Once the official service is configured, submission becomes automatic.

05
⚓

Overnight scope

Only overnight bookings are in scope; day tours are excluded.

06
▥

Audit trail

Every access and change is logged with user, time and IP address.

FREQUENTLY ASKED

Common questions

Is passenger notification required for day tours as well?

No. The scope covers overnight bookings, where the end date differs from the start date. The module does not engage for day tours.

Can a manifest be corrected after confirmation?

A frozen manifest cannot be changed — the integrity of the record depends on it. If a correction is needed a new manifest is produced; the old record stays in the archive with its hash.

Turn your yachting business into a connected ecosystem.

In a 30-minute live demo, let’s look together at how Yachtio would work in your business.