Rail Merger Environmental Review Turns Network Strategy Into a Data Filing

Rail strategy is usually discussed in operating language: lanes, ramps, dwell, interchange, drayage, transit time, and service reliability. The proposed Union Pacific and Norfolk Southern merger is forcing shippers to think about the same network questions in another form: evidence.

FreightWaves reported that Union Pacific and Norfolk Southern submitted the first portion of additional information requested by the Surface Transportation Board after the agency conditionally accepted their revised merger application. The STB set a July 27 deadline for the remaining data, and the start of the formal evaluation and environmental review of the proposed $85 billion merger was delayed pending the new submissions.

That timing matters even for shippers with no direct role in the filing. Before any transaction closes, the review process puts network claims under scrutiny. Which interchange points change? Which terminals remain neutral? Which corridors gain service? Which lanes become more concentrated? Which environmental benefits depend on freight actually shifting from highway to rail?

Those are not abstract policy questions. They are the same questions transportation teams answer every day when deciding whether a rail or intermodal plan is reliable enough to protect customer commitments.

The Merger Claim Is Operational

Union Pacific and Norfolk Southern have framed the deal as a way to create the first U.S. transcontinental railroad. In earlier FreightWaves coverage of the agreement, the railroads said the combined network would span 52,215 route miles, operate across 43 states, and serve around 100 ports. They also said the merger would create $2.75 billion in annual synergies within three years, split between $1.75 billion in revenue growth and $1 billion in cost savings.

For shippers, the most important claims are practical. The companies said the merged network would deliver faster, more comprehensive freight service by eliminating interchange delays, opening new routes, expanding intermodal services, and reducing distance and transit time on key corridors.

Those benefits sound attractive, especially for companies trying to reduce highway exposure, carbon intensity, and long-haul truckload volatility. But they also create a planning obligation. A promised service improvement is useful only if the shipper can map it to actual freight: origin, destination, ramp, commodity, service requirement, customer promise, equipment need, and fallback mode.

The environmental review raises the same issue. If a network change is expected to reduce congestion or emissions by shifting freight to rail, the assumptions need operating support. Which lanes are realistic candidates? How much drayage is added at each end? Are the intermodal ramps close enough to distribution centers? Does the customer allow longer transit if cost and emissions improve? Is there enough schedule reliability to avoid safety stock increases that erase part of the benefit?

A rail merger does not become a shipper advantage automatically. It becomes one when the network claim can be translated into executable lane decisions.

Rail Momentum Raises the Stakes

The regulatory review is happening while rail and intermodal volumes are already improving. Logistics Management's rail and intermodal review cited Association of American Railroads data showing U.S. rail carloads rose 1.5% in 2025 to 11,508,767, the largest annual gain since 2001. Through May 2026, total U.S. rail carloads were up 3.4% year over year to 4,756,909.

Intermodal is also moving in the right direction. Through May, U.S. intermodal volume reached 5,820,002 containers and trailers, up 1.8% annually. May alone posted an 8.1% gain, and container volumes reached a record year-to-date high in May. Logistics Management also noted that 2025 intermodal volume increased 1.5% to 14.06 million units, the second-highest annual total on record behind 2018.

That growth changes the shipper calculus. When rail demand is weak, companies can treat network strategy as a quarterly sourcing exercise. When volumes are rising, service design becomes more dynamic. Terminal fluidity, equipment availability, ramp cutoffs, appointment discipline, and drayage capacity all matter more.

It also means regulatory filings are not just background noise. If a merger review changes the conversation around terminal control, interchange neutrality, corridor service, or competitive access, transportation teams need a structured way to evaluate exposure before contracts, budgets, and customer commitments are locked.

Build the Shipper Rail-Risk File

The simplest preparation is a rail-risk file for every lane that could be affected by consolidation, interchange changes, or intermodal expansion.

Start with the lane itself: origin, destination, commodity, annual volume, seasonality, service promise, current mode, current railroad, intermodal ramp pair, drayage distance, and key terminal handoffs. Add the current cost baseline and transit-time range, not just the average. Rail variability is often more important than planned transit when customer penalties or plant schedules are involved.

Next, document interchange and terminal exposure. Which handoffs does the shipment depend on today? Are there local terminal railroads, neutral switching points, or jointly used facilities in the route? The first UP-NS additional filing addressed questions around the Terminal Railroad Association of St. Louis, Kansas City Terminal Railway, and TTX freight car equipment cooperative. That is a reminder that local rail infrastructure can matter as much as the headline Class I network.

Then add fallback routing. If a lane loses service quality, gains volume pressure, or faces a contested terminal issue, what is the practical alternative? Another rail route? A different ramp? Truckload conversion? Transload? A nearby distribution node? Shippers should document cost, transit, capacity, emissions impact, and customer-service consequences for each fallback.

Finally, capture environmental assumptions. If the company is counting on rail conversion to support sustainability goals, the file should include baseline truck miles, rail miles, drayage miles, expected shipment frequency, equipment type, and service tradeoffs. Environmental claims are stronger when they are tied to real shipment data instead of broad mode-shift averages.

Make Regulatory Change Visible in Execution

Rail consolidation analysis can feel remote from daily logistics work until a routing guide, customer promise, or capacity plan breaks. The better approach is to connect regulatory change to execution data early.

For freight forwarders and logistics companies, that means keeping rail lanes, intermodal ramps, carriers, drayage partners, customer commitments, service exceptions, documents, and cost baselines in one operating view. If a proposed network change affects a corridor, the team should be able to identify exposed shipments, model alternatives, and update routing rules without rebuilding the story from spreadsheets.

CXTMS helps logistics teams turn transportation data into operating decisions. When rail networks change, the critical work is not only reading the filing. It is knowing which customers, lanes, rates, carriers, and service commitments the filing could touch.

If your team needs better control over rail, intermodal, and fallback routing decisions, schedule a CXTMS demo. We will show how connected transportation workflows keep network strategy visible before regulatory change becomes an execution problem.