Rail Service Data Gets Real: What OETA and ISP Reporting Mean for Shipper Scorecards

Rail service performance has always been measurable inside individual shipper networks. The problem is that too much of the evidence has lived in emails, spreadsheets, carrier portals, and disputed appointment histories. That makes it hard to compare service, prove chronic failures, or turn rail reliability into a disciplined procurement conversation.

That is why the Surface Transportation Board's new reporting requirements matter. Beginning July 8, Class I railroads must report two additional weekly metrics: original estimated time of arrival, or OETA, and industry spot and pull, or ISP. According to Supply Chain Dive, OETA measures the percentage of shipments delivered within 24 hours of the original estimated arrival time, while ISP measures a carrier's success rate in loading or unloading goods at a facility when the railroad said it would.

Those are not abstract regulatory datapoints. They go straight to the service questions shippers argue about every week: Did the railroad hit the arrival promise? Did it place the car when expected? Did it pull the car when the facility was ready? Was the miss an isolated event or part of a pattern?

Why OETA changes the ETA conversation

Estimated arrival times are only useful if they are stable enough to plan around. A constantly revised ETA may look reasonable in a carrier portal, but it can hide the operational damage caused by the original miss. Labor gets scheduled. Production plans get adjusted. Yard capacity gets reserved. Customer promises get made. When the original estimate slides, the shipper absorbs the disruption even if the final update looks tidy.

OETA puts attention back on that original promise. By measuring the share of shipments delivered within 24 hours of their original ETA, the metric gives shippers a cleaner view of schedule credibility. It also creates a better foundation for scorecards because the comparison is tied to a baseline, not an endlessly refreshed expectation.

For rail-served manufacturers, bulk shippers, and distributors, this matters because rail reliability affects more than transportation. A late inbound car can constrain production. A missed outbound window can force extra yard handling or short-term storage. An unreliable ETA can push planners toward truck conversion even when rail would be the better economic or sustainability choice.

The better question is no longer simply, "Where is my car?" It is, "How often can I trust the first ETA enough to plan labor, inventory, and downstream transportation?"

ISP brings facility execution into the scorecard

Spot-and-pull performance is where rail service becomes painfully physical. If cars are not placed when expected, product cannot be loaded or unloaded. If cars are not pulled when ready, facilities lose track space and flexibility. That can create congestion, demurrage exposure, overtime, missed production windows, and unnecessary drayage or truck backup plans.

ISP reporting gives shippers another evidence layer for those operating failures. It helps separate broad network congestion from local service execution. A railroad may have acceptable line-haul transit but still struggle to serve a plant, mill, warehouse, or transload site on the promised cadence. For shippers, that distinction is critical.

A useful rail scorecard should therefore track both movement reliability and facility service reliability. OETA asks whether the shipment arrived close to the original promise. ISP asks whether the carrier performed the local spot-and-pull work when it said it would. Together, they make rail reviews more specific and harder to reduce to anecdotes.

Transparency improves accountability, not perfection

The new reporting rules will not magically make every railroad more reliable. They also will not eliminate every data argument. Supply Chain Dive noted that carriers have flexibility in how they report the data, with each railroad required to provide an initial methodology document to the STB. That flexibility matters. If methodologies differ, shippers should be careful about treating the first wave of public metrics as perfectly apples-to-apples benchmarks.

Still, imperfect transparency is better than opaque performance. Weekly public reporting gives logistics teams a common reference point for service discussions. It can support escalation with rail partners, strengthen evidence in disputes, and help procurement teams evaluate whether a lane's rail economics are being offset by hidden operational costs.

The timing is also important because rail volume is not standing still. Logistics Management reported Association of American Railroads data showing U.S. rail carloads for the week ending May 23 at 230,831, up 2.2% year over year. Intermodal containers and trailers reached 292,743 units, up 11.5% year over year. Through the first 20 weeks of 2026, U.S. rail carloads were up 3.3% and intermodal units were up 1.4%.

When volume is growing, reliability data becomes more valuable. More traffic can expose weak handoffs, yard constraints, and local service variability. Shippers need to know whether a rail lane is merely busy or structurally unreliable for their operating model.

How shippers should use the new metrics

The practical move is to bring OETA and ISP into existing transportation scorecards rather than treating them as regulatory trivia. A shipper should map public rail metrics against its own shipment history, accessorial costs, customer service failures, inventory buffers, and mode-conversion decisions.

That creates several useful questions:

• Which rail lanes have acceptable rates but poor original ETA reliability?
• Which facilities experience recurring spot-and-pull misses?
• Where do rail service misses trigger truck conversions, detention, overtime, or customer penalties?
• Which carriers are improving, and which are explaining the same failures every quarter?
• Where does rail remain the right mode if planning buffers are adjusted?

The strongest scorecards will combine carrier-reported data, STB-published metrics, shipper shipment milestones, and financial consequences. That is how rail performance becomes a procurement signal, not just an operations complaint.

The CXTMS takeaway

New OETA and ISP reporting gives shippers a better public data layer, but the value comes from turning that data into action. CXTMS helps logistics teams connect rail service metrics with shipment execution, exception management, carrier reviews, and procurement decisions. A late arrival should not disappear as a one-off delay. A recurring spot-and-pull miss should become a lane-level risk signal.

Rail can be a powerful cost and capacity tool, especially when intermodal and carload volumes are growing. But shippers need evidence they can trust. OETA and ISP reporting will not solve every service problem, but it gives transportation teams a sharper way to ask the right questions — and a stronger basis for deciding when to stay on rail, renegotiate service expectations, or protect the network with alternatives.

Ready to turn freight performance data into cleaner scorecards and faster exception decisions? Schedule a CXTMS demo and see how connected transportation management helps shippers move from visibility to control.