Record Intermodal Volumes Need a Terminal-Level Reliability Score

Record intermodal volume is good news for railroads and shippers, but it is not proof that every terminal can absorb another converted truckload. A national network can set a record while a particular ramp runs short of chassis, misses outbound connections, or accumulates containers beyond the customer's delivery window.
That distinction matters now. U.S. intermodal volume reached an all-time monthly high in October, rising 9.6% year over year, according to FreightWaves' report on the record. August, September, and October were the three strongest intermodal months on record. Shippers should treat that growth as a reason to measure terminal execution more closely—not as a blanket signal to shift freight to rail.
National growth can hide local constraints
Intermodal capacity is assembled locally. The usable product depends on an origin ramp accepting the box, a train making its planned departure, an intermediate connection working, a destination terminal grounding the container, and a dray carrier retrieving it within gate and appointment constraints. A failure at one node can consume the schedule advantage promised by the broader lane.
The latest weekly data reinforce the pressure. FreightWaves reported that U.S. rail traffic increased 6.6% year over year, led by intermodal. Higher throughput can improve train density and service frequency, but it can also expose bottlenecks that aggregate volume statistics cannot locate.
Los Angeles offers a clear example. The port handled close to 5 million TEUs over five record months, yet rail-bound containers were sitting for nine days or longer, according to Supply Chain Dive. An earlier September reading put average rail dwell at 7.19 days, up from 6.75 days in August. The lesson is simple: record throughput and reliable flow can coexist at the network level while diverging sharply at a terminal.
Build a five-part terminal reliability score
A useful score should be calculated for each origin-terminal, destination-terminal, and service combination. A single national carrier score is too broad. Start with 100 points and weight five operational components:
- Terminal dwell — 30 points. Measure median and 90th-percentile hours from ingate to train departure at origin and from train arrival to grounded availability at destination. The tail matters more than the average because late containers drive expedites and customer failures.
- Connection performance — 25 points. Track the percentage of shipments making every scheduled train connection. Record missed connections by terminal, day of week, and root cause. A lane with a fast published schedule but frequent misses is not a fast lane.
- Gate accessibility — 15 points. Score total gate hours, weekend availability, appointment lead time, turn time, and frequency of closures or rejected pickups. Capacity that cannot be accessed during the dray carrier's working window is theoretical.
- Chassis availability — 15 points. Measure the share of pickups completed without a chassis delay, average delay hours, street-turn availability, and pool imbalance. Separate terminal chassis failures from dray capacity failures so corrective action has a clear owner.
- Recovery time — 15 points. Measure how quickly service returns to baseline after weather, labor, equipment, or volume disruptions. Include time to clear backlog and the percentage of affected loads receiving a revised ETA within an agreed interval.
Normalize each metric against a lane-specific target. For example, a terminal may earn full dwell points when 90% of containers are available within 24 hours, half points between 24 and 48 hours, and zero beyond 72 hours. Set thresholds from actual customer promise requirements, not from whatever performance the network currently delivers.
Turn the score into a conversion rule
The score becomes useful when it governs tendering. Create three operating bands:
- Green, 85–100: Convert eligible truckload freight to intermodal under normal lead-time and commodity rules. Keep a routine monitor on dwell and chassis.
- Amber, 70–84: Convert selectively. Add one day to the customer promise, cap daily volume, protect high-value or appointment-critical loads, and prebook destination drayage.
- Red, below 70: Pause new conversions for affected service combinations. Use truckload, another ramp, or a different departure until recovery indicators meet a defined gate.
Do not let a strong network average cancel a weak destination result. Use the lower of the origin and destination terminal scores, then apply a connection-performance adjustment for the specific route. A Chicago–Los Angeles move and a Chicago–Dallas move should not inherit the same decision merely because they use the same railroad.
The rule also needs a volume trigger. A green terminal receiving a sudden block of converted freight may become amber before lagging dwell data reveal the change. Add planned weekly volume as a percentage of the shipper's validated allocation and require approval when the threshold is exceeded.
Connect reliability to customer promises
Customer-facing transit time should combine scheduled rail time with observed terminal variability. Use the 90th-percentile origin dwell, connection delay, destination availability, and dray pickup time for committed service. The median can support internal planning, but it should not define a promise that must survive a busy Friday or a holiday gate schedule.
Review the score daily during peaks and weekly in normal periods. Feed events from rail providers, terminals, and dray carriers into one exception workflow. When a component falls below threshold, the system should identify exposed shipments, revise ETAs, reserve alternative capacity, and notify the customer before a missed appointment.
Assign an owner to every component: rail procurement for connections, terminal operations for dwell, dray management for gates and chassis, and the control tower for recovery communication. Review root causes rather than merely debating the composite number. The score is a decision aid; its value comes from showing which constraint is eroding reliability and what action will restore it.
Record intermodal demand strengthens the case for rail, especially where shippers need economical capacity and lower-emission options. But conversion decisions should be earned terminal by terminal. A reliability score turns impressive national statistics into lane-level rules that operations teams can use without gambling customer commitments.
Make terminal reliability operational with CXTMS
CXTMS brings rail, drayage, shipment milestones, exceptions, and carrier performance into a shared transportation workflow. Teams can monitor terminal conditions, apply lane-specific routing rules, and intervene before local congestion breaks a customer promise. Request a CXTMS demo to see how terminal-level intelligence can guide intermodal planning.


