Workboat Code & small vessel safety management
Workboat Code Edition 3: the 13 December 2026 safety management deadline, and how to self-assess against it
If your vessel is certificated under the Workboat Code Edition 3 (WB3), you must have a documented safety management system in place by 13 December 2026, and you must have completed at least one self-assessment against it in the 12 months before that date. This comes from MGN 710, which sets out what Section 31 and Appendix 8 of WB3 actually expect. The deadline isn’t new — the Merchant Shipping (Small Workboats and Pilot Boats) Regulations 2023 gave effect to WB3 back in December 2023 — but it is close, and surveyors are already warning of a rush of year-end bookings as it approaches.
What the deadline actually is
WB3-certificated small workboats and pilot boats must have a safety management system by 13 December 2026. Remotely Operated Unmanned Vessels (ROUVs) certificated under the Code, and their Remote Operation Centres, have had this requirement since WB3 came into force — there’s no grace period for new entrants.
If you already hold a valid ISM Code certificate — issued by the MCA or an MCA-recognised organisation — MGN 710 lets that stand in for the WB3 SMS requirement, provided it adequately covers any ROUV operations you run. Most small workboat operators won’t have one, which is why MGN 710 exists: to give operators who aren’t running a full ISM system a proportionate route to the same outcome.
The Workboat Association and MCA’s advice for the certification side of the deadline, separate from the SMS itself, is blunt: check the code, prepare the vessel, book the survey. Edition 3 changed requirements from earlier editions, and certifying authorities expect a bottleneck of vessels booking surveys in the same few months — a boat tied up waiting for a slot is its own kind of non-compliance.
What the self-assessment has to cover
MGN 710 doesn’t hand you a fixed set of questions — it asks for a self-assessment that reflects Section 31 and Appendix 8 of WB3, tailored to your vessel’s risks, policies, and operational practice, and comprehensive enough to cover safety management rather than tick a box. A template sits in the MGN’s Annexe A. At minimum, one self-assessment per vessel is required in each 12-month period — this isn’t a one-off exercise before the deadline, it’s an ongoing annual cycle.
In practice, a self-assessment against WB3’s safety management expectations ends up covering the same ground as any proportionate SMS:
- Certification and crew competency — are the vessel’s certificates, surveys and crew competency records current, verified and renewed before they lapse?
- Operational procedures — policies and procedures with version control and review dates, not a folder of PDFs nobody’s looked at since they were written.
- Risk assessment and change management — risk assessments and method statements that get revised when something about the operation actually changes, not just reviewed on a fixed anniversary.
- Training and drills — musters, drills and toolbox talks logged with who took part, checked against the interval the Code expects.
- Maintenance — a planned maintenance regime per component, with an overdue list that’s actually looked at.
- Incident reporting and investigation — near-misses and accidents captured, counted, and fed into statutory reporting where it applies.
- Feedback and review — a route for crew to raise concerns or suggestions, and a periodic management review that closes the loop.
Where operators usually find gaps
Running our own self-assessment against the full 26-question scope MGN 710 implies, the gaps that turn up most often aren’t the big obvious ones — they’re the specific, easy-to-miss items:
- Cybersecurity policy evidence. The policy document itself usually exists; what’s missing is evidence around connected systems and backup records.
- Statutory reporting fields on incidents. A record showing an incident happened isn’t the same as a record showing whether it was reported to the authority, and if not, why not — this is exactly the kind of gap a surveyor samples for.
- A change log for operational changes, separate from the risk assessment’s own creation date — what actually changed, and when, and which risk assessment followed it.
- A structured muster list or station bill — crew-to-station assignments as data that can be checked against who’s actually aboard, not a PDF nobody updates when the crew changes.
- A route for crew suggestions that isn’t only safety-framed — a place for “this would work better if…” that isn’t squeezed into an incident report form.
None of these are large undertakings on their own. They’re the kind of thing that’s easy to leave out of a self-assessment built from a generic template, and exactly what a surveyor or an MCA inspection tends to find first.
How Helmsman helps
Helmsman is built around the Case spine and compliance matrix pattern that this kind of self-assessment needs, rather than a form you fill in once a year and forget:
- A structured self-assessment record — the questions, a graded finding, a close-out action with an owner and due date, and a “last completed” date checked against the annual clock — so the self-assessment is a live record, not a one-off PDF.
- Crew certificates and competency, inductions and vessel-specific sign-off, tracked per person with expiry warnings before they lapse.
- Document control with version history and review dates for your policies, procedures, risk assessments and method statements.
- Drill and toolbox talk logging — who took part, what was covered, checked against the interval the Code expects.
- Maintenance tracked per component, with an overdue list that’s actually visible, not buried in a spreadsheet.
- Incident and near-miss reporting mapped to statutory reporting categories, so a nil return is a real answer rather than a guess.
Helmsman doesn’t do your self-assessment for you, and using it doesn’t by itself satisfy the deadline — the judgement in the self-assessment is yours, as the operator. It keeps the evidence behind that judgement in one place, dated and current, so completing it each year means checking records that are already there rather than reconstructing them from scratch under deadline pressure.
Quick checklist
- Do you know which code your vessel is certificated under, and whether MGN 710 applies?
- Have you completed a self-assessment against WB3 Section 31 / Appendix 8 in the last 12 months?
- Is your survey booked, not just planned, given the year-end bottleneck?
- Would your crew certificates, drills and maintenance records stand up if a surveyor asked for them today?
- Do you have a change log that shows what changed in your operation and which risk assessment followed it?
- If you hold an ISM certificate instead, does it actually cover any ROUV operations you run?
Sources
- MGN 710 (M): Safety management systems for small workboats and pilot boats — GOV.UK
- The Workboat Code Edition 3 — GOV.UK
- Workboat Code Edition 3 deadline — check the code, prepare the vessel, book the survey — IIMS
- MCA and Workboat Association urge operators to get ready for 2026 transition — Cyprus Shipping News
Helmsman runs this six-stage process for you — capture to close-out, with the records joined up so they survive an audit.
Join the waitlistAbout this guide. Written by John Wilmans, a working skipper who has been through a domestic safety management audit from the side of the operator being audited.Reviewed by John Wilmans on 13 October 2026.
This guide is general information, not legal advice, and it describes United Kingdom (MCA) — Workboat Code Edition 3. Requirements differ between flag states and administrations — always confirm with your own flag state or administration. Spotted something wrong?Tell me and I'll correct it.