UK Certificate of Competency Verification: What It Means and How to Do It Properly
How to verify a UK Certificate of Competency — what CoC verification actually checks, where the gaps are, and how to make it automatic.
About 5 min read

You've received a CV. The officer claims to hold a UK Certificate of Competency — a Master Mariner, an OOW 500GT, a Chief Mate. It looks right. The document looks right. But verifying it is another matter entirely.
CoC verification is one of those tasks that looks straightforward until you're doing it at scale. A register check, a grade confirmation, a cross-reference against issue and revalidation dates — each step is manageable in isolation. Across a roster of crew, across multiple flag state administrations, across placements that run for months rather than days, it becomes a significant administrative undertaking. And the standard check at placement still doesn't tell you what happens to that certificate six months into a contract.
Here's what proper UK Certificate of Competency verification actually involves — and where the gaps tend to appear.
What is a UK Certificate of Competency?
A UK Certificate of Competency (CoC) is issued by the Maritime and Coastguard Agency (MCA) and certifies that a seafarer has met the required training, sea time, and examination standards for a specific officer or master grade. It is the formal qualification that allows someone to serve in a certificated role on a UK-flagged vessel.
Grades covered include Officer of the Watch (OOW), Chief Mate (ChMate), Master, Chief Engineer, Second Engineer, and several specialised endorsements. Each has its own STCW minimum standard and revalidation requirement.
The certificate itself is a legal document. Placing someone in a certificated role without a valid CoC isn't just a compliance gap — it's a potential breach of STCW and UK flag state regulations.
How UK CoC verification works
The MCA maintains a register of certificate holders that can be searched by name or certificate number. This is the authoritative source — if a CoC appears in the MCA register, it is genuine. If it doesn't, it isn't.
In practice, verification involves:
- Checking the certificate number against the MCA register
- Confirming the grade and endorsements match what the seafarer claims
- Checking the issue date and any revalidation dates
- Confirming the certificate hasn't been suspended or withdrawn
That's the core check. But there are two things a basic register search won't tell you automatically: whether the certificate has been revalidated since issue (CoCs require revalidation every five years under STCW), and whether any endorsements the seafarer is relying on are still current.
Where the gaps appear
Revalidation. A CoC issued ten years ago may be valid for the grade — but the seafarer's STCW endorsements and medical certificates have their own revalidation timelines. The CoC itself can be in the register and look fine while the underlying qualifications needed to use it have lapsed.
Non-UK certificates. Many crew working UK routes hold flag state CoCs from Cayman, Bermuda, Isle of Man, Bahamas, Marshall Islands, or other administrations. These are issued under the same STCW framework but through separate registers. Verifying an STCW CoC from a non-UK flag state requires contacting that administration directly — or using an AI-powered verification system that covers multiple flag state databases.
Document authenticity. The MCA register confirms that a certificate was issued. It doesn't confirm that the document in front of you is a genuine copy of that certificate. Fraudulent reproductions of legitimate certificates do occur. Proper verification checks the document itself — not just the number.
Expiry after placement. This is the gap that catches experienced operators. A CoC verified correctly at the point of placement can expire mid-contract — particularly STCW endorsements with five-year cycles. Without ongoing monitoring, you won't know until something prompts you to look.
The difference between a check and verified compliance
There's a distinction worth drawing here: running a manual check at the point of hiring is not the same as maintaining verified compliance over a placement.
A check answers: is this certificate valid today?
Verified compliance answers: is this certificate valid today, has it been verified against the issuing authority, and will I know when it needs revalidating?
For a recruiter placing crew on short contracts, a check at placement may be sufficient. For a management company or vessel operator responsible for certificated crew over longer periods, ongoing monitoring is a different requirement entirely — and one that manual checking can't reasonably support at scale.
How CrewPass handles CoC verification
CrewPass automates the verification layer that manual checking leaves to email threads and memory.
When a crew member uploads their Certificate of Competency, the platform's AI extracts the relevant data — certificate number, grade, issuing authority, issue date, revalidation dates — and cross-references it against the relevant register. Crucially, it doesn't just check that a certificate exists: it verifies that the issuing authority is legitimate. For flag state CoCs issued by non-UK administrations, that means confirming the administration is on the STCW White List and that the certificate format and numbering are consistent with genuine issue.
Expiry tracking happens automatically. When a CoC or associated endorsement approaches its revalidation date, the system flags it — so the crew member has time to act and you have visibility before a contract is affected.
For roles with specific certification requirements, Compliance Links allows you to define the exact CoC grade and endorsements a role requires, send a link to the candidate, and receive a compliant/not compliant result once the AI has verified their documents against your criteria. No email chains, no manual register searches, no guesswork about whether the grade they hold covers the role you're filling.
The result is a verification record that's auditable, timestamped, and maintained — not a snapshot that gets filed and forgotten.
A practical starting point
If you're currently verifying CoCs manually, a few things to check your process against:
- Are you checking the MCA register directly, or relying on the document alone?
- Are you recording the verification date and result in a way you could reference later?
- Do you have a process for monitoring revalidation dates post-placement?
- For non-UK flag state certificates, do you know which registers to check?
These aren't trick questions — they're the gaps that most manual processes leave open. The good news is that with the right verification infrastructure, none of them require significant time investment.
If you'd like to see how CrewPass handles CoC and certificate verification across your crew, visit crewpass.co.uk or get in touch to arrange a walkthrough.