CINS Li-Ion Container Guidelines Meet RoRo
CINS and the IG P&I Clubs published container Li-ion guidance. The procedural template translates directly to vehicle-carrier loading interfaces.
The Cargo Incident Notification System (CINS), the International Group of P&I Clubs, the TT Club, and ICHCA jointly published guidelines on lithium-ion battery carriage in containers. The document is framed for containerships. The procedural template — verification, segregation, declaration — translates to vehicle carriers without significant adaptation.
What translates directly
- Pre-shipment battery condition verification, with documented evidence retained.
- Segregation of damaged, defective, or recalled units.
- Declaration accuracy requirements aligned with IMDG/UN3480/UN3481 categories.
- Incident notification and shared-learning expectations.
What does not translate
- Container-specific suppression and isolation procedures (different geometry).
- Container-deck stowage rules (vehicles don't share the same geometry).
- Container handover documentation (shippers, not OEMs, often hold the data).
Sources
- CINS (Cargo Incident Notification System), TT Club, International Group of P&I Clubs, ICHCA — joint guidelines on the safe carriage of lithium-ion batteries in containers.
- IMO — International Maritime Dangerous Goods (IMDG) Code, UN3480 / UN3481 provisions.
- TT Club — Lithium-ion carriage guidance briefings.
- IUMI Cargo Committee — position papers on lithium-ion cargo.
Questions, answered
Do the CINS container lithium-ion guidelines apply to vehicle carriers?+
The joint CINS, IG P&I Clubs, TT Club, and ICHCA guidance is framed for containerships, but the procedural template — verification, segregation, declaration, incident notification — translates to vehicle carriers without significant adaptation. It needs adopting rather than re-writing.
Which parts translate directly to RoRo?+
Pre-shipment battery condition verification with retained evidence, segregation of damaged or recalled units, declaration accuracy aligned with IMDG/UN3480/UN3481 categories, and incident notification and shared-learning expectations all carry across to vehicle-carrier loading interfaces.
What does not carry across, and what is the real barrier?+
Container-specific suppression, stowage rules, and handover documentation don't translate, given different geometry and data ownership. The real barrier is institutional: aligning OEM dispatch, terminal operators, and carriers so the procedural template is actually applied.
Continue the thread
What the 2025 IMDG Code Changes for RoRo
IMDG Code Amendment 42-24, mandatory 1 Jan 2026, gives EVs their own UN 3556 class and retires generic UN 3171 — changing how car carriers declare them.
What the VCSF Guidelines Set in Motion
Operators and insurers formed the VCSF because the car-carrier loss record had outpaced existing guidance. The implications go beyond fire response.
What the New Vehicle Loading Guidance Requires
ICS/IGP&I Common Guidance sets a booking-to-discharge data chain for vehicles: declared propulsion type, recorded SOC, and an OEM emergency guide.