Transshipment is where plans slip. Containers change, feeders move, and hubs fill up. LSPs prevent rollovers by watching the right early signals, separating ocean time from hub dwell, and setting a clear recovery SLA. This guide gives operations teams practical indicators, thresholds, and paste ready SOP language that survives handoffs.
Why Transshipment Creates Disproportionate Risk
- Step changes. A missed feeder is not a small delay. It often adds a full cycle at the hub.
- Container changes. Boxes can swap at the hub. If you track only the old container number, the timeline breaks.
- Variable dwell. Berth, yard, and customs practices differ by hub. Average figures hide tail risk.
Early Signals That Predict Rollovers
- Cutoff integrity. VGM, docs, and gate in full met before CY cutoff. Any miss increases risk later.
- Feeder spacing. Tight windows between ATA at hub and next feeder ETD leave no buffer.
- Service load factor. High utilization and frequent blankings on the mother service correlate with higher roll ratios.
- AIS pace versus plan. Sustained speed below threshold or course changes that push ETA inside the feeder window.
- Hub advisories. Terminal yard density and labor bulletins that extend crane or gate times.
- Customs and carrier holds. Any hold at hub precludes a timely connection even if the vessel is on time.
What To Track In Real Time
- By string and hub. Build reliability cards per service string and per hub. Port pair averages are not enough.
- ETA to berth and a separate dwell band. Do not hide hub dwell inside transit time.
- Connection window. ATA at hub plus average discharge time compared to feeder ETD. Flag negative buffers.
- Missed feeder ratio. Rolling 4 to 8 week rate by string at the hub. Use it in customer promises.
Operations Playbook
Before origin cutoff
- Validate booking against intended service and hub. Confirm feeder plan, not only mother vessel.
- Set a preliminary ETA band using the string’s reliability and the hub’s dwell band.
- Escalate any risk on VGM, docs, or gate in that could jeopardize the first connection.
After departure to hub
- Use AIS to sanity check pace. If ETA compresses the connection window, notify customer and prepare alternates.
- Monitor hub advisories and yard turn times. Widen the dwell band if published metrics cross your trigger.
At hub pre connection
- Track first lift alongside and discharge progress. If progress falls behind threshold, pre build the rebooking request.
- Confirm the next feeder list and space status. Document screens and timestamps for evidence.
If rollover occurs
- Send a one screen update with cause, new plan, and delivery impact. Attach evidence and the carrier acknowledgement when available.
- Offer two resequencing options. Next feeder on same string, or alternate string or routing with pros and cons.
- Update last free day projections and trucking appointments that depend on availability.
Paste Ready Customer Language
Rollover risk disclosure
“We monitor connection windows at transshipment hubs. If our P90 ETA compresses the feeder window below our buffer, we alert you and propose two options within four business hours.”
Recovery SLA
“On a confirmed rollover we rebook to the next feasible feeder or alternate string within one cycle and provide updated delivery dates and last free day. Evidence includes carrier or terminal screens and time stamped logs.”
Credit language example
“If the rollover is caused by carrier capacity or schedule change and you accepted our published buffer and dwell band, we will request a waiver or credit from the carrier on your behalf and pass through any approved relief.”
Want rollover risk to surface before the window closes. Book a 20 minute TRADLINX Ocean Visibility review and see BL anchored timelines on your live lanes.
Metrics And Thresholds To Publish
- Missed feeder ratio by string at the hub. Update monthly.
- Average connection buffer in hours between ATA and feeder ETD.
- Hub dwell band berth to availability for the past 4 to 8 weeks with a trigger for change.
- Roll documentation rate percent of rollovers with carrier acknowledgement captured.
Design Patterns For UI And Alerts
- Risk score with inputs. Show which factors raised risk so users trust the alert.
- Event lineage. Display source next to each milestone. Carrier for intent, AIS for pace, terminal for availability.
- Actionable alerts. Fire only when the promise is at risk. Include two next best options with cycle time deltas.
How TRADLINX Helps
TRADLINX Ocean Visibility anchors on the BL and stitches container changes at the hub so the timeline stays intact. The platform scores rollover risk with AIS pace, hub dwell history, and feeder spacing. API endpoints push the same plan into your TMS and customer portal.
Assumption Checks
- Do not treat roll risk as a single number. It is lane, string, and hub specific. Publish the lookback window.
- Do not promise credits. You can request relief, not guarantee it. Keep the evidence pack ready.
- Do not make the container the only key. A new container at the hub will break the old thread unless you anchor on the BL.
References
- Digital Container Shipping Association. Track and Trace event vocabulary
- International Maritime Organization. Automatic Identification System overview
- Schedule reliability research and methodology notes
- FIATA. Model rules and BL guidance
Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe) or henry.jo@tradlinx.com (EMEA/Asia)
Leave a Reply