ICD to port by rail: where the days go

An exporter in the NCR or Punjab rarely trucks a container all the way to the sea. The box goes from the factory to an inland container depot such as Tughlakabad, Dadri or Ludhiana, and then by rail to a gateway port like Mundra, Pipavav or Nhava Sheva. It is an efficient route. It is also the stretch where nobody is quite sure where the container is.

The steps, in order

1. The empty is picked up and stuffed at the factory.
2. It is trucked to the ICD and gated in.
3. Customs formalities can be completed at the ICD itself, up to the Let Export Order.
4. The box waits for a rake, is loaded and rails out.
5. It arrives at the port, gates in and waits for its vessel.

Detention has usually been running since the empty left the depot.

Where do the days go on the rail leg?

Three waits account for most of it:

• Waiting at the ICD for rake allocation.
• The rail transit itself.
• Dwell at the port before loading.

A rake that leaves a day late does not just delay one container; it can push a whole batch past the port's gate cut-off and onto a later vessel.

The most important event on this route is the one nobody sees: the box leaving the ICD.

Planning backwards from the vessel

The useful habit is to plan from the port's cut-off backwards:

1. When must the box gate in at the port?
2. So when must it rail out?
3. So when must it reach the ICD?
4. So when should the empty be picked up?

Picking up the empty earlier than that only adds detention days.

Visibility usually comes from a portal check or an email from the rail operator, which means the CS desk learns about a slipped rake late. In Freightflow the rail-out and port gate-in are recorded per container, and the expected port arrival updates from those events, so a delay shows up while there is still time to act on it.