Operational Guide · Registers & Logbooks

# Loading/Discharging Plan

The document that turns a commercial operation into a safe one: stability, structural stresses and an operational sequence agreed before work begins.

cargo operations loading plan stability SOLAS

## Operational Explanation

The loading/discharging plan sets out the sequence of operations, the quantities per hold/tank, and the stability and structural stress checks needed to keep the ship in a safe condition at every stage of the operation, not only once it is complete.

The main risk is not a non-compliant final load, but the intermediate conditions: a poorly planned loading/discharging sequence can generate excessive bending or shear moments, or critical stability conditions, even if the final state falls within the limits.

## Regulatory Reference

SOLAS Chapter VI (Carriage of Cargoes) and, for dry cargo ships, the IMSBC Code (International Maritime Solid Bulk Cargoes Code): the loading plan must be agreed between ship and terminal before operations begin, and must ensure compliance with stability limits and permissible structural stresses at every stage.

## Scope of Application

Every loading or discharging operation, for every ship type (bulk carrier, container ship, general cargo, tanker), with additional specific requirements for bulk carriers under the IMSBC Code.

## Procedure / How to Complete It

1. Agree the loading/discharging plan with the terminal before operations begin, including sequence, quantities per hold/tank and expected timing.
2. Verify with the ship's loading software that every intermediate stage respects the stability limits (GM, metacentric height) and the permissible structural stresses (shear force, bending moment).
3. Communicate any operational constraints to the terminal (e.g. a mandatory sequence for structural reasons) before the start, not during the operation.
4. Monitor the operation as it proceeds, checking that the actual sequence matches the agreed plan.
5. Record any deviations from the original plan and the corresponding authorisation/safety assessment.

## Practical Example

Example: a loading plan for a bulk carrier with 5 holds, with a sequence agreed to avoid excessive amidships bending moment during the intermediate stages, verified with the ship's loading computer before starting, with estimated loading times for each hold communicated to the terminal.

## Real Cases

Several serious structural failures on bulk carriers have been attributed, in the resulting investigations, to loading/discharging sequences that did not follow the agreed plan or were not verified with the loading computer, with excessive structural stresses in intermediate stages that were not adequately monitored.

## Common Mistakes Mistake Library

Mistake | Consequence | How to avoid it
--- | --- | ---
Plan agreed only for the final state, not for the intermediate stages | Excessive structural stresses during the operation, even with a compliant final state | Verify every intermediate stage with the loading computer, not just the final result
Actual sequence different from the agreed plan, due to terminal requirements | Unforeseen and unverified stability or stress conditions | Formally authorise and verify every deviation from the original plan before proceeding
Structural constraints communicated to the terminal only after operations have begun | Difficulty correcting a sequence that is already under way | Communicate all operational constraints before loading/discharging begins

## PSC Observations

Although the specific loading plan is not typically subject to PSC documentary verification to the same degree as other certificates, inspectors may request evidence of the approved loading computer and of its actual use, especially on bulk carriers.

## Operational Tips

- Always verify the intermediate stages with the loading computer, not just the final state of the cargo.
- Communicate every structural constraint to the terminal before operations begin, not during.
- Formally document every deviation from the original plan together with the corresponding safety assessment.

## Checklist

- Plan agreed with the terminal before operations begin
- Intermediate stages verified with the loading computer
- Structural constraints communicated in advance
- Actual sequence monitored against the plan
- Deviations from the plan documented and authorised

## FAQ

Is the loading computer mandatory on all cargo ships?
It is mandatory under SOLAS for ships subject to specific stability requirements (in particular bulk carriers and other cargo ships under the applicable provisions), as an approved tool for verifying stability and structural stresses at every stage of loading.
Who is responsible for the safety of the operation, the ship or the terminal?
Responsibility is shared: the terminal manages the physical execution of the operation, but the Master has the authority and the responsibility to stop or modify the operation if he detects conditions posing a risk to the ship's safety.
What should be done if the terminal proposes a sequence different from the one agreed?
Immediately verify with the loading computer whether the new sequence respects the stability and stress limits; if necessary, request an alternative sequence or suspend the operation until the matter is clarified.
🎬 Additional photos, videos and interactive diagrams for this topic will be available in a future version of the platform.

## Related Topics

Cargo Securing Manual and Cargo Lashing Draft Survey and Determining Cargo Quantity

### Leave feedback

Help us improve the platform during the beta -- it takes thirty seconds.

How useful do you find the platform so far?
Comment (optional)
Sign me up for the newsletter
Role