UR E26, After the Mandate ③ — Through the Eyes of the Classification Society
“UR E26, After the Mandate” ③ — Through the Eyes of the Classification Society
Assurance, differentiation, and the weight of liability — what class assures, how far it differentiates, and the liability it bears for the result.
- LinkedIn : linkedin.com/in/abysstoinfinity
The third installment of a six-part series — the second stakeholder: the classification society. Where Part 2 looked from the position of the party buying the boundary (the owner), this part looks from the opposite side — the party that assures it. The aim is neither to defend nor to criticize the classification society, but to map, through its own internal logic, the forces it actually moves between.
1. The Classification Society’s Dual Identity
A classification society wears two hats at once on the same matter. One is the obligation, as an IACS member, to assure the mandatory floor uniformly — since the very reason Unified Requirements (UR) exist is to eliminate divergence, member societies bear a responsibility to apply that floor consistently. The other is the need, as a competing business, to differentiate above it. A classification society serves a non-profit public-interest function, yet it is also an organization that competes for customers. These two identities often do not point in the same direction: unification demands uniformity, competition demands difference.
Apply the floor consistently
Unification → uniformity
Compete for customers
Competition → difference
The society’s question is the owner’s, mirror-reversed —
what to assure, how far to differentiate, and what liability to bear.
2. What the Classification Society Actually Sells — Not a Guarantee, but a Verified Opinion
Let us first clear away a common misconception.
A classification society is not the party that guarantees safety at sea or the seaworthiness of the vessel; the non-delegable duty to ensure seaworthiness rests — legally — with the owner. A classification society does not design, build, operate, or maintain the vessel, nor does it control operations between periodic surveys.
And yet the entire market relies on this certificate
What a society sells is not a safety guarantee but trustworthy third-party verification —
a structure depended upon by all, yet guaranteeing nothing.
3. Why Classification Societies Interpret Conservatively — The Structure of Liability
The impression that classification societies often interpret conservatively is accurate, but the cause lies not in arbitrariness but in the asymmetry of the liability structure.
Liability may be found if negligence is proven
cf. Great American v. Bureau Veritas (US)
Nicholas H — no duty of care to cargo owners (UK)
Morning Watch — no duty to the purchaser
But limited legal liability and small exposure are entirely different matters. Major pollution casualties such as the Erika (1999) and the Prestige (2002) showed that third-party claims can overwhelm a society’s net worth or insurance limits. And here lies a more fundamental asymmetry — price.
Because class fees are negligible relative to the value of the vessel or the potential loss, a society cannot price in unbounded risk. The conservative interpretation is therefore best read as a rational response to an extremely asymmetric risk structure: where what is received is small and what can be lost is vast, the newer and more uncertain the domain, the stronger the conservatism. And cyber is precisely such a domain — threats evolve rapidly, the causation of incidents is complex, and accumulated case law and statistics remain thin. Much of the caution observed in E26 interpretation follows naturally from this structure.
4. The Force Pulling the Other Way — Competition
If liability pushes a society toward strictness, competition pushes the other way — and the tension between these two opposing forces is what produces its actual position. There was a time when classification societies used being less strict as a competitive instrument: in a structure where the owner chooses the society and pays the fee, the society that interprets most strictly risks losing customers to a more flexible one. Forum shopping — owners seeking a more favorable interpretation, discussed in Part 1 — flipped to the society’s side appears as competitive pressure discouraging any society from becoming the strictest interpreter.
Liability and reputation pull toward strictness —
competition pulls toward leniency.
The unification and quality systems of UR and IACS are precisely the mechanism for binding this tug-of-war at the floor. When all members agree to apply the same minimum line, the incentive for any one society to be dragged into a race to the bottom diminishes. In this respect, uniformity of the mandatory floor is not the owner’s interest alone but a common interest of the classification societies as a whole — for if the floor wavers, the asset of trust on which the entire institution of classification depends is eroded.
5. Where Differentiation Draws Its Justification — A Reflection of Real Capability
If the two forces above act on the floor, it is on the storey above that a society differentiates — and that differentiation, in large part, reflects differences in real capability. This is the key to understanding the voluntary notation tiers. Cyber is a domain in which classification societies had invested for years before UR became mandatory:
| Society | Cyber capability built up before UR |
|---|---|
| DNV | Cyber security RPs · CP-0231 type approval · Cyber Secure notation (2018) · security profiles SP1–SP5 ↔ IEC 62443 SL |
| Bureau Veritas | NR659 — Rules on Cyber Security for the Classification of Marine Units |
| ABS | CyberSafety programme |
| ClassNK | Own cyber security guidelines |
As seen in Part 1, this accumulation existed before UR was mandated; if anything, UR aligned itself to it. Differentiation through higher notations is therefore less about manufacturing value that does not exist than about turning capability built up through earlier investment into a product. The ability to verify higher SLs, methodologies for assessing cyber governance at operational and fleet level, broader verification extending to IT — these are products of R&D, and it is natural that their depth differs from one society to another. This is precisely the space IACS codified in stating that members are free to impose stricter requirements exceeding the minimum line.
6. The Tension the Classification Society Actually Manages — Performing Unification and Differentiation at Once
Here the hardest task comes into view. A single organization must be both, at once, on the same matter:
What makes this tricky is that the two layers are not cleanly separated. If interpretation of the floor diverges from one society to another, the fragmentation seen in Part 1 recurs, and that erodes the shared asset of trust. So for the societies too, uniformity of the floor is a common interest worth defending. The problem is that the conditions making such uniformity difficult all operate at once:
Seen in this light, the late-2025 moves to overhaul class rules — for instance, DNV’s split of its class notation into Design and In-Operation — can be read not as a mere product reshuffle but as an attempt to tidy up interpretation and clarify categories. Distinguishing a design-stage technical requirement from the domain of operational management sharpens the boundary between floor and upper storey. To perform unification and differentiation at once, one must, paradoxically, draw the boundary between them more clearly.
7. The Boundary, Seen from the Classification Society’s Position
In sum, a society balances between two layers: it assures the floor uniformly, differentiates above on the basis of real capability, and throughout manages an asymmetric liability structure. And running through all three is one principle:
A classification society earns the greatest trust when it does not blur the boundary.
Keeping the floor clear and uniform is the societies’ common asset of trust; the market rewards differentiation on the upper storey when it is anchored in real capability. Conversely, when the boundary blurs — when interpretation of the floor diverges, or when an upper-storey requirement is presented as if “mandatory” and seeps down into the floor — what is damaged is the very trust on which the society itself depends. This is where Part 1’s core proposition is confirmed anew from the society’s position: boundary management is not a task that matters only to the owner; it is also in the society’s own interest. If what a society sells is trust, the surest way to protect that trust is to let the market see clearly what is assurance and what is differentiation.
8. Closing
If a society asks “what to assure and how far to differentiate,” there is a separate party that actually produces and submits the technical deliverables on which that assurance rests. The society verifies; someone produces. The party that draws Zone and Conduit Diagrams (ZCD) and design descriptions by hand, and must satisfy the differing expectations of multiple classification societies on a single ship — the protagonist of the next installment: the shipyard.
The next installment moves to the other side of verification — the view of the shipyard, the system integrator.
The burden of implementing the mandatory floor in actual drawings and documents — and the reality of multi-class handling, several societies’ interpretations entangled in a single ship.
Key Bases
Owner-side maritime cybersecurity advisor focused on IACS UR E26/E27 compliance, Zone and Conduit Diagram (ZCD) development, and OT/IT security architecture for vessels.
🌐 More Articles ↗⚓ Join the ShipPaulJobs Community
Join →
Comments
Post a Comment