# Logistics

Source: https://www.trypascal.io/solutions/logistics

Keep the promise when the plan breaks.

Connect a disruption to the shipments and customer commitments it threatens. Compare recovery options and coordinate the next move across your team and carriers.

## Who this is for

For supply chain leaders, dispatch, and network operations

## 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.

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.

## Workflow

### Detect

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

### Connect

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

### Predict

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

### Decide

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

### Authorize

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

### Act

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

### Adapt

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

## Result and action boundary

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.

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.

## Start and expand

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.

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.

## Related products

- [Ontology](https://www.trypascal.io/platform/ontology)
- [Integrations](https://www.trypascal.io/platform/integrations)
- [Atlas](https://www.trypascal.io/platform/atlas)
- [Compass](https://www.trypascal.io/platform/compass)
- [Agent Tasks](https://www.trypascal.io/platform/agents)
- [Workflows](https://www.trypascal.io/platform/workflows)
- [Context Graph](https://www.trypascal.io/platform/context-graph)
- [Work Surfaces](https://www.trypascal.io/platform/work-surfaces)

## Next step

[Discuss your workflow](https://www.trypascal.io/contact)