For shippers

Keep the release decision tied to the customer’s current shipment state.

Freight Passport is being built to let shippers define the relationships and evidence that should be reviewed before a protected load changes hands.

Capability map

How this part of Freight Passport is structured.

Explore the interactive demo →
01

Customer-defined policy

The shipper defines the required relationship between the load, carrier, driver, equipment, facility, evidence, and release decision.

  • Published policy and version context
  • Current assignment and facility scope
  • Evidence freshness requirements
02

Current state at the handoff

A familiar carrier or pickup number alone does not establish authority for a particular shipment.

  • Server-evaluated shipment context
  • Explicit advisory reason codes
  • No cached-green shortcut
03

Protected changes

A material change should be reviewable and cause stale decision context to be reassessed.

  • Attributable change request
  • Review before protected updates
  • Fresh evaluation after change
04

Decision history

The intended workflow keeps the policy context, advisory result, and subsequent activity attributable for later review.

  • Decision and policy provenance
  • Audit/history view
  • Scoped review access

A pilot record is not a certification, insurance determination, or guarantee against theft or loss.

See it in context

Map one shipper workflow in SHADOW.

Start with one organization, one facility, named users, and a controlled advisory flow beside the existing release process.