Union Pacific Merger Scrutiny: Protect Rail Bid Data From Commercial Retaliation

Rail procurement depends on candid information. Shippers must be able to compare rates, document service failures, test merger claims, and explain their position to regulators without wondering whether a commercial response will follow.

That principle is under fresh scrutiny in the proposed Union Pacific-Norfolk Southern transaction. On November 4, the Surface Transportation Board rejected Union Pacific's appeal and ordered a recording of CEO Jim Vena's remarks to a shipper conference to lose its confidential designation. FreightWaves reported that the Board expressed “serious concerns” about whether stakeholder input had been influenced during review of the proposed $85 billion merger.

The episode does not establish that a shipper was retaliated against. It does show why procurement teams need a disciplined system for separating verified regulatory events, company explanations, shipper allegations, and their own commercial evidence.

Start with the facts that can be verified

The proposed combination is consequential. Reuters reported that Union Pacific and Norfolk Southern sought approval for an $85 billion tie-up intended to create the first coast-to-coast U.S. freight rail operator. In May, the STB paused its review while seeking more information from the companies.

The later disclosure dispute concerned remarks made at a shipper conference. According to Logistics Management, the STB ordered records and verified statements after concluding the remarks may have discouraged stakeholders from participating openly in the merger review. Union Pacific has characterized the comments as humor, while critics have described them as a threat to raise rates on opponents.

Those statements belong in different fields. The order and its date are regulatory facts. The railroad's explanation is a public company position. A shipper's interpretation is an allegation or opinion unless supported by comparable commercial evidence. Mixing all three in an email thread makes later analysis harder and can turn ordinary negotiations into an unreliable record.

Restrict sensitive bid data by role

Rail bid files reveal more than prices. They can expose a shipper's merger position, captive lanes, alternate routings, volume forecasts, switching options, service tolerance, and willingness to move freight to truck or another railroad. That information should not be visible simply because an employee has general access to transportation records.

Use role-based access around four data classes:

• Merger participation: Draft comments, regulatory questionnaires, association discussions, and internal positions should be limited to legal, regulatory, and designated executives.
• Lane bids: Rates, minimum-volume commitments, fuel terms, accessorials, and competing proposals should be available only to the sourcing team and approved decision-makers.
• Operating evidence: Dwell, missed switches, car supply, transit variance, demurrage, and claims should remain accessible to operators who must resolve service issues.
• Executive scenarios: Models estimating post-merger rates, routing changes, or facility exposure should have named owners and an access log.

The goal is not secrecy for its own sake. It is to prevent a casual comment, forwarded spreadsheet, or broad dashboard permission from connecting a regulatory viewpoint to commercially sensitive leverage.

Preserve comparable evidence, not impressions

If a shipper believes its rates or service changed after taking a public position, chronology alone is weak evidence. The procurement record must support an apples-to-apples comparison.

For every proposal, preserve the lane, commodity, equipment, annual volume, shipment profile, effective dates, fuel basis, accessorial schedule, service commitment, and expiration date. Record who requested the quote, who approved it, and which alternatives were available. For service, retain scheduled and actual events using the same definitions across the comparison period.

Then create a baseline. Compare the new offer with the shipper's prior contract, contemporaneous bids on similar lanes, published or permitted benchmarks, and changes in volume or operating requirements. A 12% rate increase means something different if volume fell by half, a switch was added, or a fuel formula changed. Without those details, teams may mistake a market adjustment for retaliation—or fail to identify an anomalous commercial response.

Version control matters too. Never overwrite a bid or scenario. Store the original, every revision, timestamps, participants, and the reason for the change. If a carrier representative makes a material verbal statement, document the date, attendees, exact recollection, and requested follow-up confirmation instead of paraphrasing it as established fact.

Build an auditable decision path

Governance should continue through award and execution. Require procurement to score rate, service, capacity, interchange exposure, and resilience using a predefined method. Legal or compliance review should be triggered when a commercial change occurs near regulatory participation, but it should not automatically label the change retaliatory.

A useful exception workflow asks five questions:

1. What changed in rate, terms, capacity, or service?
2. When did it change relative to the shipper's public or private merger activity?
3. Are the old and new offers commercially comparable?
4. What explanation did the railroad provide, and is it documented?
5. What independent evidence supports or contradicts the concern?

Assign an owner and resolution date to each exception. Preserve the evidence even if the concern is resolved. Consolidation reviews can last months, while contracts, employees, and memories change.

Make rail procurement defensible

The STB's disclosure order is a warning against informal data handling, not a reason to stop engaging with railroads or regulators. Shippers need the freedom to participate honestly and the records to show that their sourcing decisions remain grounded in comparable rates, service, and capacity.

CXTMS helps logistics teams connect bids, approvals, shipment events, service exceptions, and supporting documents in one controlled record. Role-based workflows and preserved decision history make it easier to evaluate rail options without losing the commercial context behind them. Request a CXTMS demo to build an auditable rail procurement process for a consolidating market.