A container may be discharged at the port but still not ready for final delivery. Rail transfer, ramp availability, inland terminal status, chassis planning, and delivery appointment timing can all add uncertainty after the vessel has arrived.
What teams should monitor
Watch for discharge, rail departure, rail arrival, availability at the inland ramp, outgate, delivery, and empty return where those events are available. Missing or late inland updates should trigger a review before the customer is already asking where the shipment is.
Port discharge
Rail departure and arrival
Inland availability
Outgate and delivery
Where manual workflows fail
Manual tracking often stops at vessel arrival because that is the most visible milestone. The problem is that customer-impacting delays may happen after discharge, when the shipment is already expected to move inland.
CargoScope workflow
CargoScope helps teams keep the container record active across available milestone changes so inland exceptions do not disappear inside spreadsheets, email threads, or separate carrier screens.
Example workflow
A logistics team adds a container number, watches milestone and ETA changes in CargoScope, receives a delay alert, and uses the dashboard to prioritize the next customer or operations update. The workflow is intentionally practical: start with the container, identify what changed, decide whether the shipment needs action, and keep the team aligned on the same record.
Operational checklist
Use the guide to define what your team should review daily: active containers with changed ETAs, shipments approaching port availability or last-free-day risk, containers with holds or missing milestones, and customers waiting on updated delivery timing. A good container visibility process should reduce repeated manual checks, not create another inbox for status noise.
Review changed ETAs before customer update meetings
Flag containers that may affect drayage, warehouse labor, or delivery appointments
Keep unsupported workflows, such as B/L tracking, clearly marked as coming soon
How CargoScope supports the work
CargoScope is built for container-number tracking today. It helps teams centralize available milestones, ETA changes, delay signals, and exception context so operators can spend less time switching between carrier portals and more time acting on containers that need attention.
FAQ
What teams ask first.
Who is this guide for?
It is written for freight forwarders, shippers, importers, exporters, logistics managers, and operations teams improving ocean container visibility.
Can CargoScope track by Bill of Lading today?
Not yet. Bill of Lading tracking is coming soon. CargoScope currently focuses public tracking on container numbers.
What problem should this workflow solve?
The goal is to reduce repetitive status checks, catch shipment changes earlier, and help freight teams prioritize containers that affect customers, drayage, warehouses, or avoidable accessorial cost exposure.