<aside> ⚡

With Hubfleet's Safety Management System you can:

• Meet your HVNL SMS obligations with a fully digital, auditable system
• Capture hazards, incidents and non-conformances from the field in real time, with every event linked back to the controls that manage it
• Track every piece of corrective work in one central Actions Register so nothing falls through the cracks
• Manage risk consistently using a configurable 5×5 matrix with escalation rules tied to your Safety Org Chart </aside>

The Safety Management System (SMS) in Hubfleet is your single source of truth for hazards, incidents, non-conformances, policies, procedures and risk controls. It's built around a central Risk Controls Library, with everything else — every hazard, every incident, every policy, every procedure — linking back to a control. This page is your starting point for setting up and operating the SMS.

<aside> 🆕

What's new in this upcoming release

• Configurable Policies and Procedures with templates aligned to the HVNL reforms
• New Hazard and Incident reporting workflows with embedded risk assessment
• Non-Conformance Reports (NCRs) integrated across fatigue, mass, maintenance and other safety categories
• A central Risk Controls Library linking hazards, training, policies and procedures
• A consolidated Actions Register fed by every hazard, incident and NCR
• A live Risk Register populated by every risk-rated item (Incident, Hazard, NCR or fault)
• A configurable 5×5 risk matrix with custom escalation rules tied to your Safety Org Chart </aside>

Overview — your build order

One step to understand the architecture, then three steps to build:

• Step 0 — Understand the Hubfleet SMS structure: the bow-tie model, Risk Controls at the centre, how risk rating works
• Step 1 — Set the governance layer: Safety Org Chart, 5×5 risk matrix, Incident Config, Hazard Config, Action Types, escalation rules
• Step 2 — Build the SMS foundation: Risk Controls, Roles, Training, Hazards, Policies & Procedures, Fit for Duty
• Step 3 — Operate the SMS: field reporting, Actions Register, Risk Register

<aside> 📘

For the step-by-step project plan covering the full Hubfleet build — sequencing, timing and Fleet and People setup — see How to Build Your SMS in Hubfleet. For HVNL reform readiness, work through HVNL Reform Readiness in Hubfleet. For NHVR Master Code alignment, see Using the NHVR Master Code of Practice with Hubfleet.

</aside>

Prerequisites

• Owner permissions to set up configuration
• A decision on who will be your overall safety leader, category leaders and escalation contact

Step 0 — Understand the Hubfleet SMS structure

Before you start clicking around, take 10 minutes to understand what you're actually building. Hubfleet's SMS isn't a binder full of policies on a shelf — it's a live, linked system with Risk Controls at the centre and every hazard, incident, NCR, policy and procedure connecting back to one of them. Get the architecture clear up front and the build steps that follow will make sense.

A) The bow-tie architecture

Hubfleet's SMS is built on a bow-tie model, with Risk Controls at the centre.

The bow-tie audit trail in Hubfleet — every Risk Control sits at the knot, with Preventive Links (Policies & Procedures, Required Training, Hazards Addressed) on the left and Reactive Links (Incidents, NCRs, Field-reported Hazards) on the right.