Know who is onboard
Live headcount, companies, hosts, work areas, and long-onboard visits remain visible.
Deckpass keeps identity, vessel conditions, badges, onboard status, departures, and supervisor evidence connected - with deployment and recovery choices designed around real gangway conditions.
Connectivity resilience is not one vague offline claim. It comes from choosing the right deployment, keeping printer dispatch close to the printer, and giving operators a recovery path when output fails.
A vessel-hosted deployment keeps the application path inside the onboard environment. An online workspace uses authenticated web access and therefore still depends on internet availability.
For an online workspace, Deckpass Local Bridge runs on the Windows, Mac, or Linux printer computer and dispatches authorised badge jobs through its local printer queues.
Operators can preview the saved badge profile, retry or replace a badge, and keep the original arrival and visit state separate from print recovery.
Live jobs, exceptions, visit evidence, exports, and shift notes remain visible so the next operator or supervisor can understand what happened.
Oversight connects headcount, evidence coverage, attention items, visit history, corrections, exports, and shift handover without forcing supervisors through the live arrival workflow.

Live headcount, companies, hosts, work areas, and long-onboard visits remain visible.
Missing evidence, print failures, unusual visit duration, and unresolved exceptions surface for attention.
Individual sign-out, guarded closeout, visit restoration, notes, and history preserve the operational reason for intervention.
Deckpass links the operational details needed for daily review while keeping the claims disciplined and the workflow understandable.
Name, company, person type, purpose, host, work area, and the current visit state stay attached to the person record.
The configured vessel conditions, language used, acceptance state, and signature can be reviewed against the relevant visit.
Queued, dispatched, failed, completed, and replacement badge jobs remain distinguishable from the person check-in state.
Open and completed visits support the live onboard roster, visit history, fast sign-out, and guarded supervisor closeout tools.
Attention items, missing evidence, long-onboard visits, restored departures, and operational notes can be reviewed without hiding the intervention.
Supervisors can prepare an operational export and leave a shift-handover note for the next responsible person.
Deckpass is a visitor-operations and evidence system. It supports the vessel security process; it does not pretend to replace the vessel's complete physical and cyber-security architecture.
The operating boundary, connectivity model, local printer agent, supervisor evidence, and account controls - stated plainly.
No. Deckpass manages the visitor and contractor workflow around arrival, conditions, identification, badge printing, onboard status, departure, evidence, and oversight. It does not claim to replace every physical lock, CCTV system, alarm, network-security control, or vessel security procedure.
The answer depends on deployment. A vessel-hosted installation can keep the application workflow on the onboard network. An online Deckpass workspace still requires internet access; its Local Bridge keeps authorised printer dispatch on the printer computer, but it does not turn the online application into a fully offline browser app.
The Local Bridge pairs to one Deckpass workspace, reports the printer queues visible to its host computer, downloads authorised badge artifacts, dispatches them locally, and returns the result. It is not a remote-desktop tool and does not provide access to personal files.
Depending on the vessel configuration and the visit, supervisors can review identity and visit context, conditions acceptance, signatures, optional photos, badge jobs, onboard status, departures, exceptions, corrections, visit history, exports, and shift-handover notes.
The crew workspace requires an authenticated customer account tied to the correct Deckpass workspace. Supervisor-only actions, including guarded bulk sign-out, are restricted to authorised roles such as workspace administrators and supervisors.
Walk through deployment, account access, arrival evidence, local printing, recovery, and supervisor oversight with the people who will actually operate Deckpass.