We shifted our LA–Dallas stack train to a 22:00 departure to match the 15:00–19:00 dray surge and cut ramp dwell 11% in two weeks, but we’re still getting burned when vessel ETAs slide 6 hours. How are you setting flex windows or backup slots between port gates and rail departure to keep boxes from missing cutoff without padding the schedule to death?
We hold a rolling “ghost block” of 8–12 wells on the next departure and make it releasable at T‑90, triggered by AIS variance >2 hours so dray can pivot without padding the base plan. Paired with a soft internal cutoff 2 hours ahead of rail’s, it cut our misses about 9%; does your railroad give you a no‑penalty release window on backup slots, @OpsMike?
At that ‘22:00’ we run a 25–35 min flex band plus a pre‑negotiated swing slot at 00:30, only released when the vessel slips 5–6h after 10:00; dray sees it as a green lane in the TMS and can flip without padding the day. We also publish a micro‑cut at 18:30 for still‑on‑water boxes so dispatch stops chasing; @charlotte_dav94’s reserve‑wells angle helps, but without a named swing departure you just pile dwell at Hobart. Can your ramp host give you a 00:xx backup path three nights a week?
@steven70 that swing lane idea pairs well with a 4‑mile near‑dock buffer and a two‑stage cutoff: docs at T‑240, a ‘hot list’ can hit the ramp as late as T‑70 with pre‑advised waybills and a priority gate. When the berth plan slips, we pre‑pull those boxes in the afternoon and feed either the 22:00 or a 00:45 protect departure, which cut our miss‑cuts to about 3% — just mind yard dwell if chassis are tight.
On our LA–Dallas lane we added a paid ‘late gate’ at the ramp tied to the ‘22:00’ train: pre-advise the BOL by T-300, then anything that hits the port between 17:15–19:45 can ingate to a small hold track and still make the cut, and if the vessel slips about 6h we auto-flip those boxes to a 01:10 backup departure via API. It’s not free — the terminal wanted a per-box surcharge — but it trimmed misses from 9% to 2%.