SafePort FAQs

Question 1

What is SafePort?

Accepted Answer

SafePort is the operational risk, safety, and compliance platform built specifically for marine terminals —one system of record for hazards, incidents, work observations, discipline, documents, credentials, and vessel operations.

‍

Question 2

Who is SafePort built for?

Accepted Answer

Multi-terminal operators, stevedores, and port authorities — the people who run terminal operations in PPE, not the people who write the RFP.

Question 3

What problems does SafePort solve?

Accepted Answer

It replaces the binders, spreadsheets, and disconnected point tools that most terminals run today with a single system that captures field data once and routes it everywhere it has to go — incident records, OSHA logs, LHWCA forms, observations, and discipline.

‍

Question 4

Is SafePort cloud-based or on-premise?

Accepted Answer

Cloud-based, hosted on Microsoft Azure. Nothing to install on-site — it runs in any browser.

Question 5

Can SafePort support multiple terminals and aggregate reporting?

Accepted Answer

Yes. Each terminal carries its own policies, procedures, and work rules, while field data rolls up for cross-site visibility.

Question 6

Is SafePort really built for ports, or a general tool with a maritime label?

Accepted Answer

Built for ports, from the first line of code. SafePort was conceived and built by people who have run terminal operations; the workflows and the language reflect that.

Question 7

How long does implementation take?

Accepted Answer

Most terminals are operational on existing capabilities within 30 to 60 days of contract signature — configuration, user provisioning, document import, and initial training. Timeline scales with terminal count and document-library size.

‍

Question 8

What does onboarding and training look like?

Accepted Answer

Implementation includes terminal configuration, user provisioning, document-library import, and initial training, guided by our onboarding playbook.

Question 9

Is SafePort configurable to our workflows, forms, and notifications?

Accepted Answer

Yes. Forms, workflows, notifications, dashboards, and the policy and disciplinary framework are configured per terminal.

Question 10

Can we import our existing policies and documents?

Accepted Answer

Yes. Your document library is imported into the governance artifact library — organized by category, versioned, with citable sections that link into observations and discipline.

Question 11

Can existing data be migrated into SafePort?

Accepted Answer

Historical data migration is handled case-by-case during implementation, depending on source format and volume.

Question 12

Where is our data hosted?

Accepted Answer

On Microsoft Azure. Subprocessors are disclosed in the Data Processing Agreement.

Question 13

Is user access role-based?

Accepted Answer

Yes. Role-based access control with permission tiers and module scope means users see only what their role and their terminal / department assignment allow.

Question 14

Is application security built into how SafePort is developed?

Accepted Answer

Yes. SafePort is developed with a security-first approach, with application security designed in from the start. Our practices are guided by the OWASP Top 10 and ASVS, and security review is built into our development process rather than added at the end.

‍

Question 15

What security standards does SafePort follow?

Accepted Answer

SafePort is built to a SOC 2 control framework, with single sign-on, role-based access, and encryption in transit and at rest.

Question 16

Can field workers use SafePort on a phone or tablet?

Accepted Answer

Yes. Field capture runs on phone and tablet through the browser, so supervisors enter data at the point of work.

Question 17

Can SafePort pin hazards and incidents to our actual terminal layout?

Accepted Answer

Yes. The Site Map is the spatial spine of the platform — every hazard, observation, and incident is pinned to your real terminal layout at the spot it happened, and visible on every supervisor’s dashboard within seconds.

‍

Question 18

Does SafePort handle vessel and voyage management?

Accepted Answer

Yes. A vessel library with blueprints, berth scheduling, and voyage management is built in, with hazards mapped per vessel.

Question 19

Do hazards logged on one vessel carry over to its next call?

Accepted Answer

Yes. The shared vessel library means a hazard logged on a vehicle carrier is available the next time that vessel berths anywhere in your operation.

Question 20

Can SafePort capture and investigate environmental incidents like spills?

Accepted Answer

Spills and releases can be captured as incidents with photo evidence and routed to corrective actions, and the hazard library flags downstream reporting destinations such as SPCC, NPDES, Tier II, and NRC.

Question 21

Can SafePort identify and track environmental hazards on the terminal?

Accepted Answer

Yes. The hazard library includes environmental hazard categories with risk scoring, controls, and reporting triggers.

Question 22

How does incident reporting work, from capture to closure?

Accepted Answer

An incident is captured in the field with photos, then moves through a structured workflow — triage, witness statements, root-cause investigation, corrective actions, and closure — all on one record with a stable ID across its lifecycle.

‍

Question 23

Can workers report incidents and near misses from a phone in under a minute?

Accepted Answer

Yes. Frontline capture is tap-driven and designed to take under a minute on a phone, with an optional one-tap anonymous report to drive participation.

Question 24

Can we document compliant and non-compliant work observations?

Accepted Answer

Yes. Every observation cites the specific policy section a worker complied with or violated, tying behavior directly to your governance library.

Question 25

Does SafePort track corrective and preventive actions to closure (CAPA)?

Accepted Answer

Yes. Corrective actions are assigned, tracked, escalated when overdue, and closed — linked back to the incident, observation, or hazard that generated them.

Question 26

Can SafePort generate disciplinary letters that cite our own policies?

Accepted Answer

Yes. A disciplinary letter drafts itself from the underlying observation and cites the exact policy section, following your terminal's progressive-discipline chain and union notice requirements.

The Details of the Deployment.

Let’s Get Your Terminal Dialed In.

Request a Demo