Stowage planning is the discipline of deciding where each container goes aboard a cellular ship, across every port on a multi-port voyage, so that the vessel remains stable and structurally sound, no box blocks another box discharging at a later port, dangerous goods stay correctly segregated, and reefer and out-of-gauge cargo land in the slots that can actually accept them. It sits upstream of container ship operations (the physical loading/discharge and lashing) and is governed at the framework level by the IMO CSS Code and SOLAS Chapter VI, on top of which each carrier layers its own stowage standards.
The master bay plan is the carrier’s (or the ship’s) authoritative plan for a given port call, expressing where each container is required to go to satisfy stability, stress, DG segregation, and no-over-stowage constraints. The terminal plan is the terminal operator’s execution sequence — which crane works which bay, in what order — built to load and discharge the master bay plan as efficiently as possible within the terminal’s own yard and crane constraints. The two must reconcile before work starts; a terminal cannot substitute slots freely without re-checking the constraints the master plan was built to satisfy.
Weight distribution across the stack — heavier boxes low, lighter boxes high, in general — drives the vessel’s metacentric height (GM). Too little GM makes a vessel tender (slow, sluggish rolling, at risk of large angles of heel and reduced righting ability). Too much GM makes a vessel stiff — a short, rapid, violent roll period that increases rack and racking loads on lashings and can itself induce cargo and lashing damage, and increase the risk of parametric-rolling resonance in head seas. Stowage planners work to a target GM band, not simply to a stability minimum, precisely to avoid the stiff-ship problem. See vessel stability and GZ curve for the underlying mechanics.
Every stowage plan is bounded by the per-bay stack-weight and lashing-force tables in the vessel’s Cargo Securing Manual, itself built to the CSS Code framework. A plan that is stable in the aggregate can still be rejected at the bay level if an individual stack exceeds its permitted weight or the lashing arrangement cannot hold the calculated racking and tension forces for the expected voyage conditions. See lashing forces and lashing force / CSS Code.
Cellular container ships are built around fixed cell guides sized for standard ISO boxes, which makes non-standard cargo — out-of-gauge units, breakbulk, or project cargo lashed onto flat-rack or open-top containers — disproportionately disruptive to plan around. These units typically occupy more than their own footprint (overhang into adjacent slots, reduced stack height above them), must be flagged early to both ship and terminal, and are frequently restricted to specific bays where the cell guide geometry and crane reach can accommodate them.
On most container lines, an initial stowage plan is produced by a shore-based planner (either the line’s own planning team or the terminal, depending on the trade) using planning software fed by BAPLIE data. The ship’s chief officer reviews and approves the plan before cargo work starts, checking stability, stress, DG segregation, and lashing-limit compliance independently, and retains authority to require changes. This division of labour is standard across container ship operations; final responsibility for the vessel’s safety rests with the ship, not the shore planner.
Last verified