After the Check: The Part of Crew Compliance the Industry Ignores

I worked as a bosun on superyachts for years. Not in a compliance advisory capacity — on the boats, doing the job. I've been there when the chief officer's qualification turns out to be more complicated than their CV suggested. I've watched documents get chased over WhatsApp the evening before a charter. I've seen what happens when a certificate expires mid-contract and nobody caught it until flag state did.

The gap that bothered me most wasn't the background check. It was everything that came after.

The industry has one moment it cares about

Pre-placement vetting is where maritime compliance attention is concentrated. Background checks. Certificate verification. Right to work, identity documents, reference calls. The whole apparatus of due diligence that sits between a candidate and a vessel.

It's the right instinct. You need to know who's stepping aboard. But in most operations, the process ends there — and compliance is treated as something that was settled, rather than something that needs to hold continuously.

A background check comes back clear in January. That tells you something true about that person in January. Six months later, it's a six-month-old picture. A year later, it's a year old. Most employers don't have a clear policy on when a check should be refreshed — and even those who do often can't enforce it consistently across the crew they're responsible for.

Certificates are the sharper problem. An ENG1 medical certificate is valid for two years. Advanced first aid needs renewing every five years. GMDSS, AFF, PSCRB — each with their own validity window, each ticking down from the date the crew member took the course. A chief officer who joined fully certified in April might have two qualifications approaching expiry by October, with no system in place to flag it until an inspection surfaces it or they notice themselves.

Nobody in this situation was negligent. Nobody decided not to track it. There just wasn't a process for it, because managing that manually — across the crew of a single vessel, let alone a fleet — is an unreasonable thing to ask a person to do reliably.

Why "at placement only" became the norm

The one-time check exists because it's a manageable event. There's a clear trigger, a clear process, and a clear endpoint. You can sign it off and move on.

Ongoing compliance doesn't work like that. There's no natural endpoint, no clear event that triggers a review. It requires monitoring rather than checking — and historically, the tools to do that monitoring automatically didn't exist. So the industry settled into point-in-time verification: run a check before placement, accept checks within a certain recency window, and trust that nothing significant has changed in between.

For a stable crew on a single vessel, this holds well enough. For a recruiter managing a pipeline of hundreds of crew across multiple clients, or a management company responsible for fifteen vessels with rotating appointments, the gaps accumulate fast. And because nobody is watching the space between placements, certificates lapse quietly — often only coming to light when there's pressure to present a complete compliance record quickly.

What happens after the check, in practice

In most operations today, this is the actual workflow: certificates are uploaded or emailed at the start of an engagement. They sit in a folder — Dropbox, email, a shared drive, whatever the organisation was using when they set it up. Expiry tracking, if it exists at all, is a spreadsheet that someone has to remember to update. The person responsible is usually also running operations, managing crew movements, and answering emails about twelve other things simultaneously.

The industry describes this as compliance management. In practice, it's a reasonable bet that nothing will expire at the wrong moment — and a scramble when it does.

What changes when compliance continues past the check

The answer isn't a better spreadsheet. Spreadsheets don't verify documents. They don't send alerts automatically. They don't move with the crew member when they change vessels.

What changes the model is removing the manual burden entirely. When a crew member's profile tracks their certificates automatically — logging expiry dates at the point of upload, sending alerts before anything lapses, and carrying that record forward to every future employer — the ongoing compliance problem stops being an operational tax on someone's attention.

This is what we built CrewPass to do. Not just the background check that happens before placement, but the compliance record that continues afterwards. Every certificate uploaded is AI-verified and monitored. Every expiry date is tracked. When something is due to lapse, there's an alert — not a discover-it-at-inspection moment. And when that crew member moves to their next vessel, their verified history moves with them. The next employer doesn't start from scratch.

Why this matters more now than it used to

Flag states are tightening their requirements. Insurance underwriters are asking harder questions about how operators demonstrate ongoing due diligence, not just point-of-hire checks. Owners are thinking more carefully about what "properly managed" means for the vessels they've entrusted to their management company.

The one-time check model worked well for the world it was designed for — a world where continuous compliance tracking was genuinely difficult to do at any scale. That world has changed.

Operators who build ongoing compliance into their standard process now — not as an exceptional step when something goes wrong, but as a routine part of how their crew is managed — will be better positioned for what the industry is moving towards.

The check is where compliance begins. What you put in place after it is what determines whether it holds.