31 JUNE 2026 1. Documentation drift Procedures and forms get created during an audit cycle, then slowly stop matching reality. The crew adapts to the real world; the binder doesn’t. 2. Invisible risk Hazards get discussed informally—“watch that dock,” “that crossing gets sporty on a flood tide”—but the orga- nization lacks a consistent way to capture, prioritize, and learn from those insights. 3. Change without choreography Equipment is replaced, routes are modified, staffing mod- els shift, vendors change—often with good reasons. But the organization doesn’t consistently run those changes through a structured review that asks, “What new risks did we just create?” 4. Audit as theater Teams scramble to assemble proof: training records, main- tenance history, drill logs, corrective actions. The evidence exists, but it’s scattered—and the time spent “proving” safety competes with doing the work. None of these are moral failures; they’re workflow problems. THE LIVING SYSTEM CONCEPT Make Safety Easier to Do Than to Skip A living safety system is not “more paperwork.” It’s the opposite: a set of workflows that make safe operations the path of least resistance. Think of it like this: the best safety programs aren’t built around documents. They’re built around decisions. • What do we do today, with this vessel, this crew, this weather, this passenger load? • What’s changed since last week? • What needs attention before it becomes an incident? A living system connects the operational dots: main- tenance, training, drills, inspections, risk assessments, corrective actions, and change management—so they rein- force each other instead of living in silos. A PRACTICAL FRAMEWORK Five Building Blocks That Reinforce Each Other Here’s a field-tested structure that scales from small fleets to multi-port operators. 1. Clear standards that match the way you actually operate Start by defining the minimum non-negotiables: opera- tional policies, emergency procedures, maintenance rou- tines, and training expectations. The goal is not to write a novel; it’s to produce standards that are: • Specific enough that a new crew member can follow them • Flexible enough to reflect real operating conditions • Owned by operations (not just “maintained by the office”) This is where many programs overreach. If your manual requires perfection, your team will create workarounds. If it supports good judgment, they’ll use it. 2 A simple risk model people will actually use PVA and the U.S. Coast Guard have long emphasized risk- based thinking as a practical way to improve passenger ves- sel safety. The challenge is making risk assessment routine rather than ceremonial. The practical takeaway: you can’t “solve” safety with a one-time documentation push. When operations change —which they always do— your safety program needs to change with them.
View this content as a flipbook by clicking here.