Keep the promise when the plan breaks.

A disruption moves faster than a handoff.

The carrier notice lands in an inbox. Shipment commitments sit in the transport system. Fallback terms live in an agreement. By the time someone assembles the picture, the best capacity may be gone. Pascal brings the disruption, commitments, and available options into the same decision.

A carrier fails. The customer promise still stands.

Horizon Freight files for bankruptcy with 42 active shipments on its lanes. Seventeen face a high risk of missing the 21:00 UTC cutoff. Meridian’s operations team needs a recovery decision while there is still time to act.

Follow the affected shipments into their source records and fallback agreement. Compare available capacity, review the exact reroute, and approve the 14 eligible shipments. Three hazardous lithium loads stay on hold for Compliance.

1. 01

   Find the commitments at risk.

   Start with the carrier failure, then open the 42 affected shipment records and the fallback agreement. Seventeen shipments need a response before the cutoff.

   
2. 02

   Compare a feasible recovery.

   The Atlas comparison brings available fallback capacity and projected service impact into the decision. Eligibility still depends on each shipment’s constraints.

   
3. 03

   Approve the reroutes. Retain the holds.

   The operator approves 14 eligible reroutes. Three hazardous lithium loads remain held. The result and follow-ups stay available for inspection.

   

What changes in the operation

The example ends with 14 recorded reroutes and completed carrier and customs follow-ups. Three hazardous loads remain held for Compliance. The next job is to track pickup and delivery events: zero new breaches is still a projection, not an observed service result.

Know what better looks like.

Agree on a baseline before the first operation. Use these measures to evaluate the change with your team.

Put each decision in the right hands

The operator approves the specific eligible reroutes once. That decision does not release the three hazardous loads or override their compliance requirements. A projected service result remains a forecast until the relevant shipment events confirm it.

Build on the first operation.

Extend from one carrier failure to missed pickups, capacity shortfalls, or customs holds. Reuse shipment and commitment context, then add the constraints, partner handoffs, and confirmation events that each exception requires.

1. 01

   Detect

   Bring the closure, delay, capacity change, or other disruption into the operation.

2. 02

   Connect

   Link the signal to affected shipments, orders, customer commitments, and responsible teams.

3. 03

   Predict

   Estimate which commitments are at risk and when recovery options will expire.

4. 04

   Decide

   Compare feasible responses against capacity, service, cost, and safety constraints.

5. 05

   Authorize

   Give the reviewer the proposed route, affected loads, exceptions, and decision scope.

6. 06

   Act

   Carry out the approved response through the transportation and customer systems involved.

7. 07

   Adapt

   Check the resulting records and physical progress, then keep unresolved exceptions in view.

Choose a first operation

Begin with one exception type, such as a missed pickup or corridor closure. Connect the source notice, shipments, commitments, route constraints, approval owners, and the system records that will confirm recovery.

Connect the commitments

One lane or exception type, its shipment events, customer cutoffs, carrier agreements, and fallback capacity.

Set the approval scope

The operator who can reroute eligible freight, plus the separate owners for hazardous loads and other restricted movements.

Follow the physical result

Confirm the routing change in the transport system and the recovery in subsequent pickup and delivery events.