Guided vessel setup
Workspace, Local Bridge, scanner, badge and printer profile, arrival rules, and a final go-live test follow one ordered setup path.
How Deckpass works
The superyacht visitor workflow, from roster to sign-out.
One record connects pre-arrival preparation, multilingual check-in, vessel acceptance, badge output, onboard status, sign-out, and supervisor review.
Expected or unexpectedBadge-readyCaptain-visible
One operating recordLive gangway operations
01 Prepare02 Process03 Oversee
The operating path
Six controlled moments. One useful vessel record.
Deckpass connects the decisions that usually become fragmented: who is expected, what they accepted, which badge was issued, whether they are onboard, and how the visit ended.
Prepare onceKeep vessel rules and hardware choices saved.
Capture at sourceBuild the visit record while the person is present.
Recover without duplicationResolve badge or visit exceptions against the original record.
01
Prepare
Make the vessel ready before the first queue forms.
Deckpass begins with the operating environment, not the first visitor. The crew confirms the station, vessel rules, scanner, badge layout, printer route, and expected list before live traffic begins.
- 01
Configure the vessel station
Set the workspace identity, pair the Local Bridge when the workspace is online, confirm the scanner, choose the badge and printer profile, define arrival rules, and complete a go-live test.
- 02
Prepare expected arrivals
Import and validate tomorrow's visitor or contractor roster before the queue forms. People who were not pre-registered can still be created safely at the gangway.
02
Process
Move quickly at the gangway without losing the record.
Expected, returning, and unexpected people enter one controlled path. Deckpass keeps the public-facing kiosk calm while the crew retains the context needed for approval, badges, and exceptions.
- 03
Identify the person
Use a pre-issued Deckpass code when available, search the expected list, recognise a returning person, or begin a controlled unexpected-arrival flow.
- 04
Complete the vessel workflow
Capture the required details, conditions acceptance, signature, optional visitor photo, host and work area, then render the badge through the saved printer route.
03
Oversee
Keep the onboard picture useful after the arrival is complete.
Arrival is only the start of the operational record. Live status, departures, evidence, company context, print recovery, and shift handover remain available to the people responsible for the vessel.
- 05
Keep the live roster current
Track who is expected, checked in, onboard, ready for handover, or signed out. Operators can recover badge output without creating a second arrival record.
- 06
Review, hand over, and close
Supervisors review evidence, visit and company context, exceptions, long-onboard people, exports, shift notes, and guarded sign-out or restore actions.
What keeps the path practical
The operating details are part of the product.
Deckpass includes the setup, hardware, recovery, and repeat-visitor choices required to make the workflow credible at a working gangway.
Flexible badge output
Saved profiles, browser previews, test printing, local queues, replacement badges, and print recovery support the physical handover.
Returning-person speed
Known contractors and visitors can reuse validated identity context while still creating a fresh visit, acceptance, badge, and onboard record.
Visible exceptions
Missing evidence, long-onboard visits, failed print jobs, manual interventions, and supervisor corrections stay visible instead of disappearing into notes.
Workflow questions
Practical answers before the first live arrival.
Deckpass can be introduced around an existing vessel process, then configured and tested before the crew relies on it during live traffic.
01Must every visitor be pre-registered before arriving?
No. Expected arrivals are faster because their details can be prepared before the rush, but Deckpass also supports controlled unexpected arrivals and returning-person workflows at the gangway.
02What information can Deckpass capture during arrival?
Depending on vessel settings, the workflow can capture identity and company details, person type, visit purpose, host, work area, vessel conditions acceptance, signature, an optional visitor photo, badge state, and the resulting visit record.
03How does Deckpass print badges from an online workspace?
Deckpass Local Bridge runs on the Windows, Mac, or Linux computer connected to the printer. It pairs with the vessel workspace, discovers the printer queues available to that computer, dispatches authorised badge jobs locally, and returns the result to Deckpass.
04Does Deckpass require one specific badge printer?
No. Deckpass uses saved printer and media profiles and can work with different local printer queues. The Brother QL-570 is a proven recommended option, but it is not mandatory.
05How can a visitor be signed out?
A visitor can use the fast sign-out path with a recognised Deckpass badge code, while authorised crew can search and sign the person out from the arrival, onboard, operations, or oversight workflow when manual intervention is required.
06What can a supervisor review after an arrival?
The available record can include live onboard state, visit timing, company and host context, vessel conditions acceptance, signatures, optional photos, badge jobs, departures, exceptions, corrections, visit history, exports, and shift-handover notes.
See the complete path
Bring the vessel rules. We will map the workflow.
Review the arrival station, badge route, crew workspace, oversight record, and rollout plan against the way your vessel actually operates.