When Everyone Touches Rail but Nobody Owns It

A railcar is ordered because production needs material.

The railroad accepts the order, but the expected service day changes. The plant receives only part of the requested cars. Nobody documents the shortfall. Operations adjusts the production schedule. Purchasing orders additional inventory as protection. Another department releases cars late because unloading information is not shared consistently. Accounting receives a demurrage invoice several weeks later and begins asking what happened.

Every person involved completed part of the job.

Yet no one managed the complete rail cycle.

That is how many industrial rail operations become reactive. The problem is rarely one dramatic failure. It is usually a series of small gaps between departments, systems, facility practices and railroad service.

• The railroad manages its network.
• The plant manages production.
• Accounting reviews invoices.
• Transportation orders and tracks cars.
• Operations unloads them.
• Someone releases them.
• Someone else contacts the railroad when service breaks down.

“The expensive space between those responsibilities often has no single owner.”

That is the gap where missed switches, excess inventory, delayed releases, avoidable demurrage and recurring service failures begin to accumulate.

Demurrage Is Often the Invoice—Not the Original Problem

When a company receives a large demurrage bill, the immediate question is usually:

“How do we dispute these charges?”

That is a reasonable question. But it may not be the most important one.

A demurrage invoice can be the final result of several earlier failures:

• More cars were ordered than the facility could unload.
• Cars arrived in a different pattern than expected.
• A local service day was missed.
• Cars were placed after the unloading crew had left.
• The facility lacked visibility into cars approaching the plant.
• Weekend coverage was not aligned with free-time rules.
• Empty cars were released late.
• Release confirmation was not documented.
• The railroad failed to pull released cars.
• The company could not reconstruct the sequence when the invoice arrived.

The charge may be correct, incorrect or partly defensible. But the invoice alone does not explain why the cost occurred.

A company that focuses only on disputing charges may recover part of the money while leaving the underlying operating failure untouched.

That means the same problem returns the next month.

The Industrial Rail Cycle Has More Handoffs Than Most Companies Realize

A rail operation is not simply “cars arrive, we unload them, and they leave.”

A dependable rail cycle requires several connected decisions.

1. Demand planning

How many cars are actually needed?

The answer should reflect:

• Production demand.
• Current inventory.
• Cars already on the way.
• Unloading capacity.
• Storage capacity.
• Expected railroad service.
• Transit variability.
• Weekends and holidays.
• Empty-car availability.
• Customer demand on the outbound side.

Ordering additional cars may feel like protection against unreliable service. But excess cars can create their own problems.

More cars may mean:

• More inventory sitting in transit.
• More leased equipment.
• More congestion at the plant.
• More cars exceeding free time.
• More difficult switching.
• More money tied up in raw material.
• Less flexibility when production changes.

“The goal is not to maximize the number of cars available. The goal is to maintain the right flow of cars for the actual operation.”

2. Railroad service planning

What service has the railroad committed to provide—and what does the facility actually receive?

Many companies know their nominal service schedule but do not maintain a reliable record of:

• Requested service.
• Cars expected.
• Cars actually placed.
• Cars actually pulled.
• Partial switches.
• Missed switches.
• Unexplained delays.
• Cars left behind.
• Cars placed in an unusable sequence.
• Service performed outside the expected window.

Without that history, every service conversation starts over.

The plant says service has been unreliable.

The railroad says it has been serving the facility.

Both statements may be true because neither side is using the same definition.

A meaningful service record must distinguish between:

• A switch occurring.
• The correct cars being delivered.
• The correct cars being pulled.
• The full work request being completed.
• Service occurring within a useful operating window.

“A locomotive entering the facility does not automatically mean the customer received successful service.”

3. Placement and unloading

Once cars are placed, several clocks begin running.

The facility must know:

• When the cars were constructively or physically placed.
• Where each car was placed.
• Whether the cars were accessible.
• Whether they were placed in the requested order.
• When unloading began.
• When unloading was completed.
• Whether a mechanical, quality or safety problem delayed unloading.
• Whether the plant had sufficient labor and equipment available.

A facility may have enough theoretical unloading capacity but still struggle operationally because cars arrive in uneven groups.

For example, a plant may be able to unload four cars per day. That does not necessarily mean it can efficiently unload 12 cars delivered at once after several missed service days.

The railroad may view the delivery as successful.

The plant may suddenly face three days of work, limited track space and a shortened free-time window.

The issue is not simply unloading speed. It is the mismatch between service pattern and facility capacity.

4. Release discipline

A loaded car does not stop creating exposure when unloading is complete.

The car must be released correctly, promptly and in a way that can later be documented.

Common release problems include:

• The unloading team assumes transportation will release the car.
• Transportation does not know unloading is complete.
• The car is released in one system but not another.
• The release occurs after a daily cutoff.
• The release is entered with incorrect information.
• Empty cars remain physically blocked by loaded cars.
• The railroad does not pull the released car.
• No one follows up because everyone assumes the process is complete.

A strong operation records both:

• When the facility released the car.
• When the railroad actually removed it.

Those are different events with different responsibilities.

5. Invoice and charge review

By the time accounting receives a bill, the people who remember the event may have moved on to dozens of other problems.

Accounting may see:

• Car initials and numbers.
• Arrival dates.
• Placement dates.
• Release dates.
• Free-time calculations.
• Chargeable days.
• Tariff references.

What accounting may not see is:

• The service day that was missed.
• The car that was placed on the wrong track.
• The plant closure communicated in advance.
• The release confirmation.
• The railroad's promise to pull the car.
• The email documenting a service exception.
• The mechanical issue preventing unloading.
• The switching sequence that made the car inaccessible.

A strong charge-review process begins during the operating event—not after the invoice arrives.

The evidence needed to defend a charge should be collected while the failure is occurring.

6. Railroad communication and escalation

Repeated emails are not the same as an escalation process.

Many companies communicate with the railroad frequently but still lack a clear method for resolving recurring failures.

Effective escalation requires:

• A defined operating issue.
• Specific cars, dates and service events.
• Documentation of the business impact.
• A clear request for corrective action.
• An owner on both sides.
• A follow-up date.
• A record of the railroad's response.
• A higher escalation level when the issue remains unresolved.

Compare these two messages:

“Service has been terrible again. We need help.”

versus:

“The facility requested eight loaded cars for Tuesday service. Four were placed, two expected cars remained at the serving yard, and three released empties were not pulled. This is the third partial switch in four scheduled service days. The remaining inventory supports approximately two production days. Please confirm the recovery plan, cars to be placed, empties to be removed and expected service time.”

The second message gives the railroad something specific to investigate and answer.

It also creates a record that can be escalated if the response does not resolve the issue.

7. Internal accountability

This is usually the most important part.

Who owns the complete rail cycle?

Not just ordering.

Not just unloading.

Not just invoice review.

Who is responsible for understanding whether the entire process is working?

That owner should be able to answer:

• What cars were ordered?
• What cars are in transit?
• What cars are delayed?
• What cars were placed?
• What remains loaded?
• What has been released?
• What has not been pulled?
• What charges are developing?
• What service failures remain open?
• Who owes the next action?
• What should management know this week?

When no one can answer those questions in one operating review, the company does not have a rail-management process. It has several departments completing disconnected tasks.

Three Common Examples

Example 1: The building-materials receiver

A receiver unloads bulk material from railcars and historically had several days of free time. The serving railroad changes its operating practices, service becomes less predictable, and the available unloading window becomes much tighter.

The facility begins receiving larger groups of cars after service gaps. Employees work through the available cars, but the plant cannot always unload the entire group before charges begin.

Management initially sees the problem as unreasonable demurrage.

A closer review shows several connected issues:

• Orders are based on expected weekly demand rather than actual inbound inventory.
• Cars already moving toward the plant are not always included in the ordering decision.
• Missed service days are not documented consistently.
• Large placements exceed the practical daily unloading rate.
• Weekend staffing is not aligned with the new free-time exposure.
• Releases are entered correctly, but cars are not always pulled promptly.
• Accounting lacks the service records needed to support disputes.

The solution is not simply “unload faster.”

The operation needs:

• A daily view of inbound and placed cars.
• Ordering limits tied to unloading capacity.
• Documentation of missed and partial switches.
• A weekend and holiday operating plan.
• Release-to-pull tracking.
• A consistent charge-review package.

The demurrage invoice is the visible symptom. The actual problem is the absence of one coordinated operating process.

Example 2: The recycler with too many cars and not enough reliable service

A metal recycler depends on empty gondolas to keep outbound material moving.

Because railroad service is inconsistent, the company tries to protect production by maintaining a larger fleet. More cars should create more security.

Instead, the company experiences:

• Loaded cars waiting for pickup.
• Empty cars sitting at the wrong locations.
• Leased cars accumulating days without productive use.
• Yards becoming congested.
• Plant personnel struggling to distinguish usable cars from bad-order or unsuitable equipment.
• Management considering even more cars because shortages still occur.

The company appears to have a fleet shortage.

In reality, it may have a fleet-control problem.

A useful review separates the fleet into categories:

• Productively loading.
• Loaded and awaiting pickup.
• Moving loaded.
• Empty and moving.
• Empty and available.
• Idle.
• Bad order.
• Restricted or unsuitable.
• Excess to the location's operating need.

The company can then determine whether the problem is:

• Insufficient fleet size.
• Poor fleet distribution.
• Excessive railroad cycle time.
• Delayed releases.
• Long dwell after release.
• Cars assigned to the wrong location.
• A combination of those conditions.

Buying or leasing more equipment before answering those questions may increase cost without improving supply.

Example 3: The manufacturer solving rail unreliability with inventory

A manufacturer has experienced several material interruptions caused by inconsistent inbound rail service.

To protect production, the company increases safety stock.

That decision may be reasonable in the short term. But over time it can hide the cost of poor rail performance.

The additional inventory may require:

• More railcars in the supply chain.
• More onsite storage.
• More working capital.
• More leased equipment.
• More material handling.
• More exposure if production demand changes.
• Greater demurrage risk when several cars arrive together.

Management may conclude that rail is still cheaper than truck because the transportation rate is lower.

But a complete comparison should include:

• Inventory carrying cost.
• Added fleet cost.
• Demurrage.
• Plant congestion.
• Production risk.
• Emergency truck shipments.
• Management time spent resolving service failures.
• Cost of material shortages.
• Cost of excess material.

The right question is not simply:

“Is rail cheaper than truck?”

It is:

“What does our current rail operating model actually cost after all the protective measures are included?”

Sometimes the correct answer is additional inventory.

Sometimes it is a different fleet plan.

Sometimes it is a transload strategy.

Sometimes it is a stronger railroad service arrangement.

And sometimes the company can reduce exposure by managing the existing rail cycle more effectively.

But that decision should be based on measured operating facts—not frustration.

The Five Numbers Leadership Should See Consistently

Every operation is different, but industrial rail shippers should be able to establish a short list of meaningful performance measures.

1. Requested versus completed service

Track more than whether the railroad entered the plant.

Measure whether the requested work was completed.

Examples:

• Cars requested.
• Cars placed.
• Cars requested for pickup.
• Cars actually pulled.
• Missed switches.
• Partial switches.

2. Placement-to-release time

How long does the facility retain a car after placement?

This measure helps separate internal unloading and release performance from railroad dwell after release.

3. Release-to-pull time

How long does a released car remain at the facility before the railroad removes it?

This is essential for documenting railroad-controlled dwell.

4. Demurrage exposure

Do not track only final invoices.

Track:

• Charges developing.
• Charges under review.
• Disputed charges.
• Paid charges.
• Recovered amounts.
• Recurring causes.

5. Open service failures

Every significant service failure should have:

• A date.
• A description.
• Cars involved.
• Business impact.
• Railroad contact.
• Responsible owner.
• Next action.
• Current status.
• Resolution date.

If the same issue returns repeatedly, management should be able to see the pattern.

What Can Realistically Change in 90 Days?

Ninety days will not give a consultant control over a railroad's entire network.

It should not be presented as a guarantee that every switch will occur on time or that every charge will disappear.

But 90 days is enough time to replace a reactive operation with a defined management process.

Days 1–30: Establish the baseline

The first step is understanding how the operation actually works—not how the procedure says it works.

That includes:

• Mapping the order-to-release cycle.
• Reviewing available service and demurrage information.
• Identifying the highest-cost failures.
• Defining performance measures.
• Clarifying current responsibilities.
• Documenting railroad contacts and escalation paths.
• Separating carrier-controlled failures from facility-controlled failures.

The objective is a reliable current-state picture.

Days 31–60: Install operating controls

The next phase turns findings into repeatable practices.

That may include:

• Ordering controls.
• Daily or weekly rail reviews.
• Clear responsibility for releases.
• Service-failure documentation.
• Charge-protection records.
• Railroad follow-up routines.
• Escalation standards.
• Management reporting.
• A shared view of open actions and exposure.

The objective is not more meetings.

It is clearer ownership and faster decisions.

Days 61–90: Stabilize and measure

The final phase tests the new process.

Management should be able to determine:

• Are service failures being documented?
• Are orders better aligned with plant capacity?
• Are releases occurring promptly?
• Are unresolved cars receiving follow-up?
• Can accounting reconstruct charge events?
• Are railroad commitments being tracked?
• Are recurring problems visible?
• Does leadership have a useful performance view?

The objective is to leave the organization with an operating system it can continue using.

Rail Performance Improves When Accountability Becomes Visible

Industrial shippers cannot control every railroad decision.

They can control whether their own operation is measurable, documented and prepared to escalate.

They can control:

• How cars are ordered.
• How service is recorded.
• How unloading capacity is considered.
• How releases are communicated.
• How exceptions are documented.
• How invoices are reviewed.
• How the railroad is held accountable.
• How management sees the complete rail cycle.

The most expensive rail operations are not always the ones receiving the worst service.

They are often the ones receiving inconsistent service without a dependable way to measure, manage and respond to it.

When everyone touches rail but nobody owns the complete process, the company operates through reaction.

When responsibilities, measures and escalation are connected, rail becomes easier to explain—and easier to improve.

Is your rail operation becoming reactive?

Warning signs include:

• Recurring demurrage.
• Missed or partial switches.
• Unclear car-ordering responsibility.
• Cars released but not pulled.
• Multiple departments using different information.
• Service problems managed almost entirely through email.
• Excess inventory or railcars added as protection.
• Senior leadership unable to see one reliable performance picture.

The first step is not automatically a large consulting engagement.

It is establishing whether the problem is isolated—or whether several parts of the rail cycle are breaking down at the same time.

Move By Rail's Rail Service Scorecard helps industrial shippers identify where exposure may exist. For operations experiencing several connected problems, the 90-Day Rail Performance Recovery Program provides a structured path to establish the baseline, install practical controls and create clearer accountability.

Identify what is breaking down. Correct what is driving the cost. Regain control in 90 days.