VGM and Dangerous Goods: Managing the Handover Between Shipper, Terminal and Ship's Master

A container does not become a maritime safety issue only when it reaches the crane. Data, evidence, and decisions arise much earlier with the shipper, freight forwarder, terminal, and on board. The handover becomes particularly demanding when verified gross mass, dangerous-goods data, stowage planning, and late changes meet. It is then not enough for each party to complete its own task. The team needs one traceable information state: which consignment is released, which source supports each value, which deviation remains open, and who may make the next decision? This guide sets out a practical handover chain. It does not replace review of the specific contract of carriage, current rules, or terminal and flag-State requirements.

Why this handover needs its own process

Shipping companies should not treat the handover as mere file transfer, but as a controlled point between cargo planning and safe operation. The shipping companies pillar provides the frame: vessel, shore organisation, and port work in different systems, yet they must be able to access the same decision-relevant information. For every booking, the team should be able to see who submitted the data, who checked it, which version is current, and which escalation applies when values conflict. This prevents a correct record from sitting in the wrong inbox or a change surviving only in one local spreadsheet.

The international baseline is clear without creating one universal checklist for every consignment. The IMO explains that the amendment to SOLAS regulation VI/2 requires mandatory verification of the gross mass of packed containers before loading. Its IMO guidance on verified gross mass also explains why incorrect mass declarations can lead to wrong stowage decisions, unstable container stacks, or loss of containers. For operational control, this means that the presence of a number alone is not enough. Method, source, time, unit, consignment reference, and release status matter as well. Always verify the requirements applicable to the voyage and contract in their current version.

A sound handover therefore separates three questions that are often mixed in daily work: is the booking and cargo reference unambiguous? Is the available value usable for the planned movement? And has it reached the systems of the parties that will make a stowage or operational decision from it? If one answer is missing, the consignment is not merely incompletely documented. It has an unresolved decision status. This view makes delays more visible without prematurely assigning blame and lets the team involve the right specialist role.

Break the handover into seven verifiable steps

Start with a shared minimum data set, not a long email chain. The compliance training matrix for shipping companies helps separate the roles of booking, cargo acceptance, dangerous-goods review, terminal communication, stowage planning, and the ship's master. For each role, define the input it owns, the plausibility check it performs, and the status it may set. A person may complete documentation without thereby granting technical release. This separation prevents a visible entry from being treated incorrectly as confirmed cargo.

Then connect the handover to the existing safety roles ashore and on board. The article on ISM and ISPS responsibilities and training evidence shows why responsibilities, evidence, and information routes must not disappear into one generic safety label. For VGM and dangerous goods, this means naming an owner for technical clarification, an owner for the operational decision, and a channel for feedback to the vessel. The ship's master does not need a data graveyard, but clear information on what is released, restricted, or still open.

Plan feedback with the terminal as a fixed step, not as an exception when trouble occurs. The port state control preparation guide shows that vessel and shore need to check evidence for consistency together. Applied to operations, the handover confirms not only that a message was sent, but also its receipt, assignment to the correct booking, and treatment of a deviation. For critical changes, record timestamp, contact, content, and resulting status. This later shows whether information arrived too late or whether its effect remained unresolved.

AI-generated

Treat VGM as a controllable data record

The VGM record should contain more than the numerical value: include at least container identifier, booking reference, unit, method used, submitter, time, and recipient status. This does not replace the form and reporting requirements that apply in each case. It is the minimum logic with which a team can find differences. The experience from EU ETS and MRV handoffs is transferable here: data handovers become dependable when source, accountable person, review step, and version are visible together. Avoid copy-and-paste between forms without a version marker. Every change needs a clear trigger and feedback to the parties that planned using the previous value.

Define a stop status that is not treated as a personal failure. If identifier, mass, method, or transmission route do not align, the consignment must not fall back into an apparently normal release flow. It needs technical clarification with a deadline and owner. The coordination described in the FuelEU Maritime daily-work article offers a useful pattern: not every data deviation is decided by the same role, but every deviation needs an accountable party and a traceable closure. A resolved conflict should therefore record the corrected value, the reason, and the date, not merely the word completed.

Dangerous goods introduce additional specialist information that a VGM value cannot replace. According to the IMO page on the IMDG Code, SOLAS chapter VII contains mandatory provisions for carriage of dangerous goods in packaged form, and the IMDG Code extends those provisions. For your handover chain, this does not mean remote diagnosis of individual substances. It means that classification, description, packaging, marking, documentation, and stowage or segregation questions must reach the operational decision through a technically accountable party. Always use the current applicable version of the rules and qualified advice when the consignment requires it.

Hand over dangerous-goods information so it remains actionable

The decisive check is not whether a dangerous-goods document has been filed somewhere. It is whether the relevant version is connected to the correct container, booking, and planned vessel. The article on a controlled crew-change handover shows how to manage a change of people: current information, named responsibility, a route for questions, and documented confirmation. The same logic protects dangerous-goods data. A change in the shift team, dispatch, or on the vessel must not create a gap in which nobody can say which information is authoritative.

Build a compact decision package for this purpose: booking and container number, cargo description, VGM status, dangerous-goods status, source and version, open questions, contacts, and the next decision with a deadline. The package does not need to duplicate every document. It must reliably point to the governing records and show whether their content is confirmed or merely received. The distinction matters because a received document is not yet a release. It also prevents teams from having to assemble information from several systems under time pressure.

AI-generated

Train escalations instead of merely describing them

A dependable handover chain includes pre-defined decisions for typical deviations. Example one: VGM is missing by the agreed deadline. Example two: VGM and booking reference do not match. Example three: dangerous-goods data change after planning release. For each scenario, it should be clear who sets the status, who clarifies technically, who assesses the operational effect, and who informs the vessel or terminal. Add a deputy for every critical role. The process then remains controllable when one person is unavailable.

Do not train with an abstract question such as what to do about wrong data. Give the team a real time limit and an incomplete record. Let booking, dangerous-goods review, terminal contact, and vessel representative make their decisions in sequence. Observe only four things: was the deviation recognised, was the owner unambiguous, did the right information reach the right party, and was closure documented? The result is not a test of individual employees. It tests interfaces, templates, and permissions. Observed gaps must then go back into the process, not merely into meeting minutes.

A 30-day start for shipping company and partners

In week one, map today's data sources and mark an owner, reviewer, recipient, and version location for each field. In week two, define the minimum data set and the three most important stop statuses. In week three, run a short exercise with a VGM deviation and a dangerous-goods change. In week four, correct templates, escalation contacts, and deputies, then test one case again. Do not measure processing time alone. Measure how often the team finds the governing version without a follow-up question and how many open cases have a named owner. These are simple metrics for a handover that remains actionable under time pressure.

The benefit of such a chain is not more documents. It is that shipper, terminal, shore organisation, and ship's master can answer the same question on the same current basis: may this consignment proceed as planned, does it need clarification, or must a decision be revisited? When the answer, source, owner, and deadline are visible, VGM and dangerous-goods information become a controllable part of safe operation. Update the chain after process, system, partner, or regulatory changes, and keep it short enough that the involved roles genuinely use it in daily work.